With System Center 2012 Configuration Manager SP1 CU1 deployments starting to roll, I have received a few inquiries into how to determine if CU1 has been appropriately applied. As a cumulative update is not a major update, the version of your Configuration Manager Site will not be incriminated. That said, both the Configuration Manager Administration Console and the Configuration Manager client do receive an increment in version number. In this quick Wednesday evening blog posting I will be detailing methods by which to determine if your site servers, administration consoles, and clients have received the CU1 update.
What we will notice here, is that once the CU1 update has been applied to a site, the site version remains at 5.00.7804.1000 or that of SP1. This is the same version number that was present prior to the CU1 installation.
A simple way to verify the application of CU1 is to snoop the following registry location:
Here we can find a Key name CULevel with a value of the CU applied which will indicate the CU level, in this case CU1.
Click Image for better view:
For reference, here is the same Key from a site in which CU1 has not been deployed.
Once the console has been upgraded you will find that in Programs and Features the console is still listed at 5.00.7804.1000 or SP1 prior to CU1.
When checking out ‘About Configuration Manager’ however, you will find that the console version has been incremented to Version 5.0.7804.1202 (SP1 CU1).
Furthermore the file Microsoft.ConfigurationManagement.exe found in the AdminConsole\bin folder will be versioned to 5.0.7804.1202 (SP1 CU1).
Click Image for Better view:
Inventory data (software) on this file is going to be a decent indicator of console versioning if using a collection query to upgrade a set of deployed console.
Finally the client is straight forward, once upgraded, the client version will be incremented to 5.00.7804.1202 or that of SP1 CU1.
Client versioning as seen in the console.
Click Image for Better View:
A simple collection query will produce all clients that have not received the update, which you can then use for deployment targeting (taking into account x86, x64).
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 where SMS_R_System.ClientVersion < "5.00.7804.1202"
Hope this quick post on CU1 versioning has been helpful, as always feedback is welcome, subscribe to my twitter feed using the button found on this page, see you at MMS 2013!!