Sequencing the SCCM Admin Console is always a hassle. Prerequisites like .Net Framework and VC++ redists need to be in place. Sometimes other Microsoft products cannot be installed next to the ConfigManager Admin Console. And custom shortcuts are needed to have a working software package. Each new version brings new challenges!
I will sequence the Microsoft Configuration Manager Console 2012 R2 (aka Admin Console), with some extra’s like the famous Right Click Tools and the SCCM Toolkit (think CMTrace).
Sequencer version: App-V 5.0 SP2 (no Hotfix applied)
Sequencer OS version: Windows 7 x64 with SP1 (reflects the company OS, same patch-level and middleware installed, no anti virus)
.NET Framework 4.5 and Silverlight are very important to have installed on both sequencing machine and client machines.
I’m using version .NET Framework 4.5.1 because all client machines have this version installed. If you’re using Framework 4.0, be sure you have the FULL version installed.
Sequencing machine is build like Nicke Kallen suggests: http://www.applepie.se/setup-a-vm-for-packaging
Get the source files
SCCM 2012 R2 Admin Console
Sources files are copied from the SCCM server, you find them in “Program Files\Microsoft Configuration Manager\tools\ConsoleSetup”
ConfigMgr 2012 Powershell Right Click Tools (Now Micro Right Click Tools)
Can be downloaded from http://www.nowmicro.com/rct/
System Center 2012 R2 Configuration Manager Toolkit
To automate the sequencing process I use a batch script to –more or less- silently install the admin console and extra tools. (place in the “c:\temp” folder)
“C:\Temp\ConsoleSetup.exe” /q TargetDir=”C:\Program Files (x86)\Microsoft Configuration Manager\AdminConsole” EnableSQM=0 DefaultSiteServerName=YourSERVERNAMEorALIAS.FQDN.BLA
msiexec /i “c:\temp\Right Click Tools.msi” /qn
msiexec /i “c:\temp\ConfigMgrTools.msi”
regedit /s “C:\Temp\ReportBuilder.reg”
I don’t use the “/qn” msiexec parameter for ConfigMgrTools.msi, because I don’t want to install all features (you could make a transform file to accomplish a silent installation, but I don’t think it’s worth the effort).
After the monitoring phase clean up your sequence!
Remove shortcuts: EULA, HELP, ..
The console don’t behaves and crashes
My workaround for this issue was to use a custom shortcut to “Microsoft.ConfigurationManagement.exe” using the Dynamic Configuration XML’s.
Change original “pointer” to the shortcut from:
Console crash since R2
Starting from the R2 version the Admin Console crashes as soon as you create a collection or add resources to an existing collection (not limited to these actions!).
Event Logs pointed to .NET Runtime errors.
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Faulting application name: Microsoft.ConfigurationManagement.exe, version: 5.0.7958.1000, time stamp: 0x5230d1aa
Faulting module name: KERNELBASE.dll, version: 6.1.7601.18409,
The custom shortcut doesn’t fixes this issue this time (R2).
After troubleshooting a numerous of things, I fixed this by one the following actions:
Custom shortcut to “Microsoft.ConfigurationManagement.exe” is still needed in my environment (AppV 5 Publishing Server).