Service Manager 2012 R2 Console deployment via ConfigMgr 2012

Nicklas Halme, a Senior Consultant in Microsoft Consulting Services based in Finland, authored the article below on how to deploy the System Center 2012 R2 Service Manager (SCSM 2012 R2) console using System Center 2012 R2 Configuration Manager (ConfigMgr 2012 R2).
Great work Nicklas!
*******************************************
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.

  Software requirements

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

·        Windows Server 2008 R2 with SP1

·        Windows Server 2012 or Windows Server 2012 R2

·        Windows 7

·        Windows 8.1

 

·        Windows PowerShell 2.0 or higher (PowerShell v2 is already part of Windows 7 and Windows Server 2008 R2)

·        Microsoft .NET Framework 3.5 Service pack 1:

        Windows 7 (all editions) includes the .NET Framework 3.5.1 as an OS component. This means you will get the .NET Framework 2.0 SP2, 3.0 SP2 and 3.5 SP1 plus a few post 3.5 SP1 bug fixes. 3.0 SP2 and 3.5 SP1 can be added or removed via the Programs and Features control panel.

·        Microsoft Report Viewer 2008 SP1 Redistributable Update (http://www.microsoft.com/en-us/download/details.aspx?id=3203)

        .NET Framework version 3.5 SP1 must be enabled/installed prior to installing the Microsoft Report Viewer.

·        ADO.NET Data Services Update for .NET Framework 3.5 SP1 for Windows 7 and Windows Server 2008 R2 (http://www.microsoft.com/en-us/download/details.aspx?id=8165)

·        SQL Server 2012 Analysis Management Objects.

        For System Center 2012 R2 Service Manager: SQL Server 2012 Analysis Management Objects are required regardless of the SQL Server version that you use.

        x64: http://go.microsoft.com/fwlink/?LinkID=239666

        x86: http://go.microsoft.com/fwlink/?LinkID=239665

·        You must have Microsoft Excel 2007 or later installed in order view OLAP data cubes on the computer running the Service Manager console.

·        The latest Update Rollup for System Center 2012 R2 Service Manager (UR4: http://www.microsoft.com/en-us/download/details.aspx?id=44575)

This post will concentrate on 64-bit software but this you can do another deployment type to Configuration Manager for 32-bit software, if needed.

  Microsoft .NET Framework 3.5 Service pack 1

Windows 7 and Windows 8.x (all editions) includes the .NET Framework 3.5.1 as an OS component. Usually this component is already enabled so I will not cover process of enabling it in Configure Manager deployment.
However, if the component needs to be enabled you can use DISM:

·        DISM /Online /Enable-Feature /FeatureName:NetFx3 /ALL /NoRestart /LimitAccess /Source:installationMediaDrive:\sources\sxs

Where:
    • /Online targets the operating system you're running (instead of an offline Windows image).
    • /Enable-Feature /FeatureName:NetFx3 specifies that you want to enable the .NET Framework 3.5.
    • /All enables all parent features of the .NET Framework 3.5.
    • /LimitAccess prevents DISM from contacting Windows Update (this mean you do not need Internet access).
    • /Source specifies the location of the files needed to restore the feature (for example, the D:\sources\sxs directory).
Or PoweShell

Install-WindowsFeature Net-Framework-Core -source \\network\share\sxs

Where \\network\share\sxs is the location of the source files.
How to determine which versions and service pack levels of the Microsoft .NET Framework are installed: http://support.microsoft.com/kb/318785

  Microsoft Report Viewer 2008 Sp1 Redistributable

Microsoft has released security update for Microsoft Report Viewer 2008 Service Pack 1 Redistributable Package (MS09-062 / KB971119) that will be used.
The file is a traditional executable (.EXE) file and therefore installation procedure has to be manually created.
The x64 Deployment Type installation/uninstallation command can be defined as following:

image Figure 1: Microsoft Report Viewer 2008 Sp1 Redistributable Update deployment type’s installation/uninstallation commands

Now we have to specify how Configuration Manager determines whether this application is already present on a client. One solution for it would be to specify a registry detection rule and to check the registry key of HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Updates\Microsoft Report Viewer Redistributable 2008 (KB971119)\KB971119. From this registry hive you can define e.g. the PackageVersion value needs to exist on the target system to indicate the presence of this application.

image Figure 2: Microsoft Report Viewer 2008 Sp1 Redistributable Update deployment type’s Detection Rule

  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 or newer as well as on Windows Server 2008 or newer. The command line for the silent installation is:

wusa.exe [msu file name].msu /quiet

The command line for the msu uninstallation is:

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

For more info of the Windows Update Standalone Installer in Windows please see http://support.microsoft.com/kb/934307
The x64 Deployment Type installation/uninstallation command can be defined as following:

image Figure 3: 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 %Windir%\Microsoft.NET\Framework\v3.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 4: ADO.NET Data Services Update for .NET Framework 3.5 SP1 deployment type’s Detection Rule

Now we have to specify requirements, such as the operating system version, that client must have before this deployment type can be installed. Since the update is for Windows 7 x64 architecture we can define Windows 7 64-bit operating system as requirement:

image

Figure 5: 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. Since this is an .msi file creating an application and its deployment types in Configuration Manager can be done easily.

image

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

image

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

As this software is for 64-bit Windows operating system we can define the requirement rule as following:

image

Figure 8: Microsoft Analyst Management Objects (AMOs) deployment type’s requirements

  System Center 2012 R2 Service Manager Console

Next, we need an application for the installation of the Service Manager 2012 console. We need the installation files from the System Center 2012 R2 Service Manager media that are available only in x64 version. The Service Manager console can be installed on both the 32-bit and 64-bit editions of Windows.
The setup launcher is a traditional executable (.EXE) file and therefore installation procedure has to be manually created.
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\Software\Microsoft\Windows\CurrentVersion\Uninstall, and then the command line for the installation is:

MsiExec.exe /X{7B523367-360B-4EB6-9ED4-D2637816DD0F} /q

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

image

Figure 9: SCSM console deployment type’s installation/uninstallation commands

For detection rule we can use the MSI Product code. You can browse to the installation media .\Setup\Server\SM.msi to get the product code.

image

Figure 10: SCSM console deployment type’s detection rule

Then we need to define software dependencies that must to be installed before this deployment type can be installed. In our case we have three:

1.      Microsoft Report Viewer 2008 Sp1 Redistributable

2.      “ADO.NET Data Services Update for .NET Framework 3.5 SP1”.

3.      “Microsoft Analyst Management Objects (AMOs)”

image

Figure 11: SCSM Console deployment type’s dependencies

image

Figure 12: SCSM Console deployment type’s dependencies

7           Update Rollup for System Center 2012 R2 Service Manager

Time to time the Service Manager gets an update rollup that can contain multiple improvements to the product. It is recommended to apply these updates within a reasonable time. Since these updates contains the previous updates as well so only the latest Update Rollup is needed.
This guide will use the update rollup 4 as an example how to deploy the update through Configuration Manager. The update is Windows Installer Patch file (.msp) and therefore installation procedure has to be manually created.
The x64 Deployment Type installation/uninstallation command can be defined as following:

image

Figure 13: Update rollup deployment type’s installation/uninstallation commands

The update cannot be uninstalled so there for the Uninstall program is not defined.
Now we have to specify how Configuration Manager determines whether this patch is already present on a client. One solution for it would be to specify a registry detection rule and to check the registry key of HKEY_LOCAL_MACHINE\ SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\763325B7B0636BE4E94D2D368761DDF0\Patches\14FCBCA070A8BEF4AA39AD93AE166222. From this registry hive you can define that the DisplayName value needs to equal to “Hotfix for Microsoft System Center 2012 R2 Service Manager (KB2989601)” on the target system to indicate the presence of this application.

image

Figure 14: Update rollup deployment type’s detection rule

And finally you have to define software dependencies that must to be installed before this deployment type can be installed. In this case we have only one, the actual Service Manager Console installation.’
image

Figure 15: Update rollup deployment type’s dependencies

Now all you need to do is deploy the SCSM Update Rollup Application to users (or computers) who should have the SCSM console.
Nicklas Halme | Senior Consultant | Microsoft Consulting Services

Get the latest System Center news on Facebook and Twitter:

clip_image001 clip_image002

System Center All Up: http://blogs.technet.com/b/systemcenter/

Configuration Manager Support Team blog: http://blogs.technet.com/configurationmgr/ 
Data Protection Manager Team blog: http://blogs.technet.com/dpm/ 
Orchestrator Support Team blog: http://blogs.technet.com/b/orchestrator/ 
Operations Manager Team blog: http://blogs.technet.com/momteam/ 
Service Manager Team blog: http://blogs.technet.com/b/servicemanager 
Virtual Machine Manager Team blog: http://blogs.technet.com/scvmm

Microsoft Intune: http://blogs.technet.com/b/microsoftintune/
WSUS Support Team blog: http://blogs.technet.com/sus/
The RMS blog: http://blogs.technet.com/b/rms/
App-V Team blog: http://blogs.technet.com/appv/
MED-V Team blog: http://blogs.technet.com/medv/
Server App-V Team blog: http://blogs.technet.com/b/serverappv
The Surface Team blog: http://blogs.technet.com/b/surface/
The Application Proxy blog: http://blogs.technet.com/b/applicationproxyblog/

The Forefront Endpoint Protection blog : http://blogs.technet.com/b/clientsecurity/
The Forefront Identity Manager blog : http://blogs.msdn.com/b/ms-identity-support/
The Forefront TMG blog: http://blogs.technet.com/b/isablog/
The Forefront UAG blog: http://blogs.technet.com/b/edgeaccessblog/