Update SCCM 2012 Admin Console to SP1

Purpose: You have installed SCCM SP1, and now you need to update your Admin Consoles!

Updating the SCCM 2012 system with any major update that includes fixes to the Admin Console – generally means that you need to update all the Admin Consoles that you have in your environment to meet the version of your servers. In SP1, you cannot use the old console after the server update anymore at all, so you will be forced to update the Admin Consoles immediately. Neat to know at this point, right?

Installing SCCM SP1 Admin Console update
Create SP1 Admin Console Application (Before SP1 Installation)

If you thought it would be a good idea to create the SP1 Admin Console package before you install SP1 – just to be perfectly ready for the distribution, there is a suprize for you. When you navigate to the familiar location upon the System Center 2012 Configuration Manager SP1 installation media, the tools folder does not contain a folder for the ConsoleSetup. It is GONE.

However, you can still find the installation media for the Admin Console from a new location in the System Center 2012 Configuration Manager SP1 installation media. You need to fetch the AdminConsole.msi and ConsoleSetup.exe from the following folder.

Create SP1 Admin Console Application (After SP1 Installation)

After you have installed SP1 on your SCCM, you can find the new version of the Admin Console installer in the tools folder of the Configuration Manager.

You can now create the Admin Console application package before SP1 installation or after SP1 installation, the choice is yours. You will still need the silent installation switches for the Console.

ConsoleSetup.exe
/q TargetDir=(Where to Install?) EnableSQM=0 DefaultSiteServerName=(Your SCCM FQDN)

Next, you to create the device collections to gather all the Admin Consoles, that are not up to date.

Device Collection / Query Rule / SCCM 2012 Console (Below SP1)
select SMS_R_SYSTEM.ResourceID, SMS_R_SYSTEM.ResourceType, SMS_R_SYSTEM.Name, SMS_R_SYSTEM. SMSUniqueIdentifier, SMS_R_SYSTEM. ResourceDomainORWorkgroup, SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_SoftwareFile on SMS_G_System_SoftwareFile.ResourceID = SMS_R_System.ResourceId inner join SMS_G_System_ADD_REMOVE_PROGRAMS on SMS_G_System_ADD_REMOVE_PROGRAMS.ResourceId = SMS_R_System.ResourceId where SMS_G_System_SoftwareFile.FileVersion < “5.0.7804.1000” and SMS_G_System_ADD_REMOVE_PROGRAMS.DisplayName = “Microsoft System Center 2012 Configuration Manager Console”
Device Collection / Query Rule / SCCM 2012 Console (SP1)
select SMS_R_SYSTEM.ResourceID, SMS_R_SYSTEM.ResourceType, SMS_R_SYSTEM.Name, SMS_R_SYSTEM. SMSUniqueIdentifier, SMS_R_SYSTEM. ResourceDomainORWorkgroup, SMS_R_SYSTEM.Client from SMS_R_System inner join SMS_G_System_SoftwareFile on SMS_G_System_SoftwareFile.ResourceID = SMS_R_System.ResourceId inner join SMS_G_System_ADD_REMOVE_PROGRAMS on SMS_G_System_ADD_REMOVE_PROGRAMS.ResourceId = SMS_R_System.ResourceId where SMS_G_System_SoftwareFile.FileVersion = “5.0.7804.1000” and SMS_G_System_ADD_REMOVE_PROGRAMS.DisplayName = “Microsoft System Center 2012 Configuration Manager Console”

Finally, after you have deployed your new Admin Console installation package towards the right device collection, you can enjoy the profits. Your new Device Collection will automatically show you the amount of updated clients you have, or you can user reports, or just simply open a console and see its version as show below.

Leave a Reply

Your email address will not be published. Required fields are marked *


seven − five =

Post Navigation