Service Manager Console Installation via Configuration Manager

Service Manager Console Installation via Configuration Manager

  • Comments 6
  • Likes

This is a guest blog post.  Originally it was written by Dejan Milic in German.  It was translated by Andreas Baumgarten into English.  Thanks you two for contributing this helpful blog post to the community!

======================================

Is it possible to deploy the Microsoft System Center Service Manager console as a Configuration Manager application to SCSM administrators? The answer to this question is YES.

Before a new application is created in the Configuration Manager console, it is required to first download from the Internet a few software requirements.

The software requirements and required operating systems for Service Manager Administration Console are:

- The 32-bit or 64-bit edition of Windows Server 2008 Standard or the 32-bit or 64-bit edition of Windows Server 2008 Enterprise
- The 32-bit or 64-bit edition of Windows Server 2008 Standard with SP2 or the 64-bit edition of Windows Server 2008 Enterprise with SP2
- The 32-bit or 64-bit edition of Windows Server 2008 R2 Standard or Windows Server 2008 R2 Enterprise
- The 32-bit or 64-bit edition of Windows Server 2008 R2 with SP1 Standard for the 64-bit edition of Windows Server 2008 R2 with SP1 Enterprise
- Windows 7 Professional and Windows 7 Ultimate
- Windows 7 with SP1 Professional and Windows 7 Ultimate with SP1
- Windows Vista Ultimate with SP2 or Windows Vista Enterprise with SP2
- Windows Powershell 1.0 or higher
- Microsoft Report Viewer Redistributable (available with the System Center 2012 – Service Manager media)
- Microsoft .NET Framework 3.5 with SP1
- ADO.NET Data Services Update for .NET Framework 3.5 SP1
- Microsoft Analysis Management Objects (AMOs)
For an installation of the console on a Windows 7 client the following software is required:

- ADO.NET Data Services Update for .NET Framework 3.5 SP1 (Hotfix KB982307)
(http://www.microsoft.com/download/en/details.aspx?id=8165)
- Microsoft Analysis Management Objects (AMOs)
http://www.microsoft.com/en-us/download/details.aspx?id=16978

NOTE: For “Microsoft Report Viewer Redistributable” there is no need to create an application in Configuration Manager. The software is available with System Center Service Manager 2012 and will be installed automatically when the installation (setup.exe) is started.

ADO.NET Data Services Update for .NET Framework 3.5 SP1

"ADO.NET Data Services Update for .NET Framework 3.5 SP1" is actually a Microsoft Hotfix which has an .msu file available. Therefore an application in Configuration Manager for its installation has to be manually created. There are 32-Bit and 64-Bit versions of the Hotfix (Windows6.1-KB982307-x64.msu and Windows6.1-KB982307-x86.msu).

An .msu file can be silently installed with the wusa.exe tool (Windows Update Stand-Alone Installer), a tool that comes with Windows Vista, Windows 7,Windows Server 2008 and Windows Server 2008 R2. The command line for the silent installation is:

wusa.exe [msu Datei] /quiet

The command line for the msu uninstallation is:

wusa.exe [msu Datei] /uninstall /KB:[Hotfix ID] /quiet

For this application we have to create two deployment types (x64 and x86)

The x64 Deployment Type installation/uninstallation command can be so defined:

image

Figure 1: ADO.NET Data Services Update for .NET Framework 3.5 SP1 deployment type’s installation/uninstallation commands

Now we have to specify how Configuration Manager determines whether this application (hotfix in this case) is already present on a client. One solution for it would be to specify a file system detection rule and to check the file version of %SystemRoot%\Microsoft.NET\Framework\3.5\DataSvcUtil.exe file. The version of this file after the installation of the hotfix should be greater than or equal to 3.5.30729.5022

image

Figure 2: ADO.NET Data Services Update for .NET Framework 3.5 SP1 deployment type’s Detection Rule

 

Now we have to specify requirements, such as hardware feature or the operating system version, that client must have before this deployment type can be installed.

image

Figure 3: ADO.NET Data Services Update for .NET Framework 3.5 SP1 deployment type’s requirements

 

 

Microsoft Analysis Management Objects (AMOs)

This software is available as both x86 and x64 version (SQLSERVER2008_ASAMO10_x64.msi and SQLSERVER2008_ASAMO10_x86.msi). Since this is an .msi file creating an application and its deployment types in Configuration Manager can be done easily.

image

Figure 4: Microsoft Analyst Management Objects (AMOs) deployment type’s installation/uninstallation commands

 

image

Figure 5: Microsoft Analyst Management Objects (AMOs) deployment type’s detection rule

SCSM Console

Finally, we need one more application for the installation of the Service Manager 2012 console. We need the installation files from the System Center Service Manager media that are available in both x86 and x64 version. Therefore we have to create two Deployment Types (x64 and x86).

The command line for the silent installation is:

setup.exe /Silent /Install:Console /AcceptEula:YES /CustomerExperienceImprovementProgram:NO /EnableErrorReporting:NO

For the uninstallation we can use MsiExec.exe and GUID of the installed console. The GUID can be found in Windows Registry under HKLM\SW\Microsoft\Windows\CurrentVersion\Uninstall, and then the command line for the installation is:

MsiExec.exe /X{B2D04755-A579-447E-866F-32947C3A817E} /q.

image

Figure 6: SCSM 2012 Admin-Console deployment type’s install/uninstall commands

And finally you have to define software dependencies (deployment types) that must to be installed before this deployment type can be installed. In our case we have two “Microsoft Analyst Management Objects (AMOs)” and "ADO.NET Data Services Update for .NET Framework 3.5 SP1".

image

Update June 19th 2012 : Note: the report viewer control is also a prerequisite.  Make sure that is installed prior to deploying the SM console.

 

Figure 7: SCSM 2012 Admin-Console deployment type’s software dependencies

 

image

Figure 8: SCSM 2012 Admin-Console deployment type’s software dependencies

Your comment has been posted.   Close
Thank you, your comment requires moderation so it may take a while to appear.   Close
Leave a Comment
  • Thanks for this info Trav, i just setup a lab environment with the system center 2012 suite. I will definitely be trying this

  • Thank you for the post, it helped me a lot.  In my environment the report viewer was not automatically installed and failed the prereq check.  Please update your blog...  

    Thanks!

    Brian

  • @Brian -

    Thanks for pointing that out.  Updated with a note about the report viewer control.

  • can you pls guiide me for vista x86 deployment as hotfix  ADO.NET Data Services Update for .NET Framework 3.5 SP1 (Hotfix KB982307 not suppporting

  • Please send me the step by step guide of scsm console deployment for vista x86 if you can

    Thanks

  • Do we have an updated post for SP1?