How to Install Configmgr 2012 R2 CU1 Part 2

This is continues to my Previous post (Part 1) that we saw yesterday on how to install Configmgr 2012 R2 CU1 on Primary Site.

In this post,we will see how to install CU1 on Site Server s Secondary Sites,Admin Console and Clients.

Installation of CU1 on secondary Site can be done in 2 ways depends on hierarchy.If you have more number of secondary sites,prefer to go with software distribution method OR if you have limited say 1 or 2 ,prefer to CU manually on the secondary Site .

In this blog post,I will talk through the installation of CU using software distribution method on Secondary Site.

After the packages created in Console,we need to make sure they available on the DP’s.Lets distribute all the 4 created packages to DP’s.

Note:By Default,configuration manager create packages with simple command line(uses .exe) ,you can make use of msi to add /norestart and log file (l*v) etc.

Next,create collection for secondary sites,admin console and clients (x86 and x64).

Collection for R2 CU1-Site server to get all secondary Sites:

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.SystemRoles = "SMS Site Server"

Collection for R2 CU1-Console Update:

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_ADD_REMOVE_PROGRAMS on SMS_G_System_ADD_REMOVE_PROGRAMS.ResourceID = SMS_R_System.ResourceId where SMS_G_System_ADD_REMOVE_PROGRAMS.DisplayName = "System Center 2012 R2 Configuration Manager Console"

Collection for R2 CU1 Client x86:

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_SYSTEM on SMS_G_System_SYSTEM.ResourceID = SMS_R_System.ResourceId inner join SMS_G_System_SMS_ADVANCED_CLIENT_STATE on SMS_G_System_SMS_ADVANCED_CLIENT_STATE.ResourceID = SMS_R_System.ResourceId where SMS_R_System.Client = "1" and SMS_G_System_SYSTEM.SystemType = "X86-based PC" and SMS_R_System.Active = "1" and SMS_G_System_SMS_ADVANCED_CLIENT_STATE.DisplayName = "CCM Framework" and SMS_G_System_SMS_ADVANCED_CLIENT_STATE.Version != "5.00.7958.1203"

Note: Before you deploy CU1 patch on x86 collection,make sure ,all of your clients are running on configmgr 2012 R2 Version (5.00.7958.1000)

Collection for R2 CU1 client 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 inner join SMS_G_System_SYSTEM on SMS_G_System_SYSTEM.ResourceID = SMS_R_System.ResourceId
inner join SMS_G_System_SMS_ADVANCED_CLIENT_STATE on SMS_G_System_SMS_ADVANCED_CLIENT_STATE.ResourceId = SMS_R_System.ResourceId
where SMS_R_System.Client = "1" and SMS_G_System_SYSTEM.SystemType = "X64-based PC"
and SMS_R_System.Active = "1" and SMS_G_System_SMS_ADVANCED_CLIENT_STATE.DisplayName = "CCM Framework"
and SMS_G_System_SMS_ADVANCED_CLIENT_STATE.Version != "5.00.7958.1203"

Note: Before you deploy CU1 patch on x64 collection,make sure ,all of your clients are running on configmgr 2012 R2 Version (5.00.7958.1000)

with this,we are almost there to deploy the CU1 on respective collections.

Go to software library—application management—packages.

Deploy CU1 packages to respective collections and monitor the status of deployment.

Login to the secondary Site server,open software center,check for the status ..you can also monitor log execmgr.log from client logs (could be c:\windows\ccm or SMS_CCM)

also from registry(HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\SMS\Setup) ,you can check CULevel =1

If you look at client version from configuration manager applet,you will see the updated version of client to .1203

Until Next!