The Realm of the Verbal Processor

SCCM Console Install and Update Using the Application Model

When you install a Service Pack or Cumulative Update for SCCM, you also need to update the SCCM console wherever it is installed. And…when you install the console it must be updated to the same SP and CU level as the site server. Unfortunately, the install of the CU only offers the option of creating a Package/Program for updating the console…not an Application that can take care of all of it with one deployment. So…here is how to deploy the SCCM Console via the Application Model.

First, we will need to create an Application for installing the SCCM Console. Create the Application with the name/app catalog/ etc info you wish. I am assuming that we are starting with a SP1 system. When you get to the Deployment Type, here are the settings to use:

• Script installer (since it is an EXE)
• Content location: Best practice is to copy the <SCCMinstall>\tools\ConsoleSetup folder to another location that you use for the source for this package.
• Programs tab:
  • Installation Program:
    • ConsoleSetup.exe /q EnableSQM=0 TargetDir=”%ProgramFiles%\<FolderName>” DefaultSiteServerName=<FQDN2SiteServer>
  • Uninstall Program:
    • ConsoleSetup.exe /uninstall /q
  • Make sure to select – Run installation and uninstall program as 32-bit process on 64-bit clients.
• Detection Method…Registry
  • Key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\CE6E19024E9D710409D3F46536E239F3\InstallProperties
  • Value: DisplayVersion
  • Leave the 32bit / 64bit box UNchecked
  • Data Type: String
  • Operator = Equals
  • Value = 5.00.7804.1000
• User Experience
  • Install for system
  • Whether or not a user is logged on

Second, we need an Application for the Cumulative Update (in this case, CU2). I used the Package Conversion Manager to migrate the existing Package/Program for the “SP1 Cumulative update 2 – console update” package into an application. Again…name/app catalog/etc are your choices…Deployment Type has the following settings:

• Script installer (this is a MSP patch)
• Content location: should already be set if you used PCM. If not, default is \\<SiteServerFQDN>\SMS_<SiteCode>\hotfix\KB2854009\AdminConsole\i386
• Programs Tab
  • Installation Program:
    • msiexec.exe /p configmgr2012adminui-sp1-kb2854009-i386.msp /L*v %TEMP%\configmgr2012adminui-sp1-kb2854009-i386.msp.LOG /q REINSTALL=ALL REINSTALLMODE=mous
  • Make sure to select – Run installation and uninstall program as 32-bit process on 64-bit clients.
• Detection Method…Registry
  • Key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\CE6E19024E9D710409D3F46536E239F3\Patches\AAD68D6F52CC8E349805BB5169C11B26
  • Value: DisplayName
  • Leave the 32bit / 64bit box UNchecked
  • Data Type: String
  • Operator = Equals
  • Value = ConfigMgr2012AdminUI-SP1-KB2854009-I386
• User Experience
  • Install for system
  • Whether or not a user is logged on
• Dependencies
  • Add a new dependency on the SCCM Console application that you created above.

Now all you need to do is deploy the SCCM CU2 Application to an AD Security Group that contains the users who should have the SCCM console. The applications above will:

1. Determine if the SCCM console is already installed
2. Install it if necessary
3. Confirm that the console installed successfully
4. Then it will determine if CU2 is already installed
5. Install the CU2 update if necessary
6. Then confirm that the CU installed successfully.

Now…I did not put anything in this to confirm things like the .NET 4 Framework which is a pre-req…but I’m assuming most of you already have that on your systems. If not, I’m sure you can figure it out on your own!

July 9, 2013 - Posted by Jarvis | ConfigMgr 2012, Packaging