Thomas Ellermanns view on System Center

This blog will discuss features, functions and views on Operations Manager and Service Manager

How to get the Service Manager 2012 Self-service portal running on Sharepoint 2013

How to get the Service Manager 2012 Self-service portal running on Sharepoint 2013

  • Comments 17
  • Likes

This blog post is written by my collegaue Nicklas Halme from Microsoft Consulting Services in Finland.

Great Work Nicklas :-)

 

 NOTE! The following steps are not a supported method and should ONLY be used for lab / testing purposes!!!

**************

I ran into a situation that my customer wanted to use only Windows Server 2012 in their environment and also wanted to implement the System Center Service Manager 2012 Self-service Portal. Thanks to my awesome Service Manager community at Microsoft I was able to get it to work.

Since this Service Manager 2012 does not yet officially support SharePoint 2013 I had to modify the Service Manager installer procedure to look for SP2013 installation instead of SP2010. I also needed to recreate the SharePoint site collection that Service Manager initially created and use the SharePoint 2010 experience instead.

NOTE! The following steps are not a supported method and should be used for lab / testing purposes only!!

After I had installed the SP2013 Foundation and the English language pack for SharePoint 2013 Foundation on Windows Server 2012 I did the following steps:

1. Extract the Service Manager 2012 SP1 media to a folder

2. Checked the SP 2013 Component GUID from the registry: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\

3. Modified the PrerequisiteInputFile.xml (<SCSM_extracted_media>\Setup\en.) to reference SP 2013 Component GUID for SP prerequisite check

a. Look for Check Order=41. You may change the Title and descriptions texts if you want. The highlighted GUID is for SP2013 Foundation.

b. Look for Check Order=46 and do the same GUID modifications

4. Uninstalled .NET 3.5 to force start all MSI CustomAction with CLR 4.0, that will load latest version of SP assembly from Global Assembly Cache (GAC).

5. Created a SetupWizard.exe.config file for SetupWizard.exe to be able to start it using CLR 4.0

a. Open notepad and paste the following:
<?xml version="1.0"?>
<configuration>
   <startup useLegacyV2RuntimeActivationPolicy="true">
      <supportedRuntime version="v4.0.30319"/>
      <!-- supportedRuntime version="v2.0.50727"/ –>
   </startup>
</configuration>

b. save the file as SetupWizard.exe.config

6. Copied the file to the .\Setup\ -folder

7. Modified the SM.msi (.\Setup\Server\) to bypass .NET 3.5 and IIS7.0 verification in LaunchConditions action. I removed action from sequence using ORCA (http://msdn.microsoft.com/en-us/library/windows/desktop/aa370557(v=vs.85).aspx)

a. Dropped both [NeedDotNet35] and [NeedISS7] rows from the MSI

b. Saved the changes

8. Used .\Setup\SetupWizard.exe to start installation instead of Setup.exe to bypass .NET 3.5 verification.

 

 

 

 

 

9. Installed SCSM SharePoint Web Parts application to SP2013 server. In my case I had dedicated server for the SP Web Parts and another box for the Content location server

10. After the installation completed successfully verified that feature name SMPortalSharepointSiteFeatures subfolder exists in folder C:\Program Files\Common Files\microsoft shared\Web Server Extensions\14\TEMPLATE\FEATURES

11. Opened SharePoint Central Administration as administrator

12. Clicked on Application Management link

13. Clicked on Delete a site collection link

14. From the Site Collection dropdown menu selected the Change Site Collection

15. From Select Site Collection – Webpage Dialog windows selected the site Service Manager created

16. Clicked Delete

17. Created a new site collection by clicking the Create site collection –link

a. Gave title and description like SMPortal

b. From Select experience version dropdown menu selected 2010

c. Selected Team Site as the template for the site collection

d. Added required user to site collection admin

18. Browsed to the new site and verified it works (ignored possible certification error and fixit later on with this info http://blogs.technet.com/b/servicemanager/archive/2012/05/04/faq-why-is-my-self-service-portal-service-catalog-blank.aspx).

19. Opened Sharepoint PowerShell as administrator

20. Executed the following command:
Stsadm -o activatefeature -name SMPortalSharepointSiteFeatures -url [URL TO SMPORTAL site collection e.g.: https://servername:443]

21. Navigated to url [https://servername:443/<THE GIVEN SITE NAME e.g. SMPortal>]

22. Now you should have a Service Manager 2012 Self-service Portal running on SharePoint 2013

Big thanks goes to to my Microsoft colleagues; Andrii Malinovskyi for the help to bypass the prerequisites checks and Jaakko Nikko to help me to repair the site in SharePoint 2013.

Comments
  • Great story

  • Thank you dear Thomas for the lovely post.

    Could you please advise if Service Manager 2012 R2 which will be released in couple of days will support SharePoint 2013?

    I am rolling out Service Manager 2012 SP1 in my environment and I don't want to use SharePoint 2010/Windows Server 2008 R2.

    I would like to use Windows 2012 and IIS 8.

    Your support is highly appreciated.

    Thank you.

  • Hi C.Nemnom

    I'm sorry, but SCSM2012 R2 will not support Sharepoint 2013.

  • Thanks you Thomas for your reply,

    What do you suggest?

    As  mentioned above, the following steps are not a supported method and should be used for lab / testing purposes only!!

    I need to run the Portal on  Windows 2012/IIS 8 using SharePoint 2013.

    Can I use the same steps above with SCSM 2012 R2 instead of SCSM 2012 SP1?

    Regards,

  • Hi CN, I haven't tried it with R2, but since the portal bits haven't changed that much, I believe it will work.

    If you deploy the portal on SPS2013, remember that it is unsupported and you therefore can't call MS for help if anything doesn't work.

    If you try it on R2 and SPS2013, please let me know if it works and I'll update the blog.

    Good luck.

  • I can confirm that this procedure works with SCSM 2012 R2...but I am not presently getting the Silverlight application to run in the browser. The installation went smoothly following this guide. I have not started to troubleshoot the silverlight issue and expect I can resolve it but the installation was successful. Thanks Thomas for your effort on this. Any hint on the silverlight issue before I start troubleshooting?

  • So after banging on this for a while, I'm about to give up. The WebParts are not registered properly and the Silverlight App does not even try to run. I am not using SSL and have tried the common silverlight fixes. Also tried to get the webparts trusted and registered but it's proving too much a challenge for this unsupported effort.

  • Thank you dear Jason for the confirmation that the above procedure works with SCSM 2012 R2.

    It seems we cannot use it if the Silverlight App does not run :(

    Dear Thomas, your support is highly appreciated please.

    I don't know why the Web Portal setup for Service Manger is complicated.

    Basically, I don't want to buy a third party tool to get the Web portal feature from a different vendor, I like to have all functionality using only Microsoft.

  • Hey Guys

    I'm not sure why the web parts shouldn't work for R2 as they haven't been changed since SP1.

    I don't have any time available for testing this, but will see if someone internally in Microsoft have tried.

  • Thank you dear Thomas for the reply,

    Please keep us updated when you have more info.

  • Hi Jason, To solve the problem with the silverligth app follow this tutorial http://www.scsm.se/?p=646

  • Just tried this with SP 2013 SP1 and SM2012 R2 had to delete the two of the pre req and was able to get to the SharePoint install but then fails on the configure portal SharePoint Web site.

  • Hi, I am trying to install Service Manger R2 on a 2012 R2 server with SP 2013 SP1 foundation. My Attempts to install the portal/sharepoint web parts fails with these errors;

    MSI (s) (DC:24) [13:31:59:095]: NOTE: custom action _CreateMOMRegKey.11EE91AB_EABF_48A6_9973_4DCD73190AC6 unexpectedly closed the hInstall handle (type MSIHANDLE) provided to it.
    The custom action should be fixed to not close that handle.
    CustomAction _CreateMOMRegKey.11EE91AB_EABF_48A6_9973_4DCD73190AC6 returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)

    and

    Assembly Install: Failing with hr=80070005 at RemoveDirectoryAndChildren, line 396


    and

    Calling custom action CAManaged!Microsoft.MOMv3.Setup.MOMv3ManagedCAs.CreateMOMRegKey
    Exception thrown by custom action:
    System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Net.Sockets.SocketException: No such host is known
    at System.Net.Dns.GetAddrInfo(String name)
    at System.Net.Dns.InternalGetHostByName(String hostName, Boolean includeIPv6)
    at System.Net.Dns.GetHostEntry(String hostNameOrAddress)
    at Microsoft.MOMv3.Setup.MOMv3ManagedCAs.CreateMOMRegKey(Session session)
    --- End of inner exception stack trace ---

    has anyone managed to get it working with these latest versions?

  • Hi, does anyone have any images of what the SSP looks like on SP2013?

  • @Matt - it looks the same as 2010, the same template (look) is used from 2010 but its technically installed on 2013

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment