A couple of months ago, I wrote the “Installing SCCM 2012 SP1 CU1 – Quick Start Guide”, and this post has been one of most visited blog post I’ve ever created, so my guess is that it would good idea to create one for Cumulative Update 2 (CU2).
Installing this update is very similar to CU1, but a few things has changed. In this blog post, I’ll walk you through the upgrade process step-by-step, in a standalone primary scenario.
As always you should start by checking the health of the system, very the backup etc. Just like any other service pack or update.
Download the Update
After we have checked that our system is healthy, we need to download the update. SCCM 2012 SP1CU2 is available for downloaded here: http://support.microsoft.com/kb/2854009
This update can be applied directly to the following Systems/Roles:
- The Central Administration Site (CAS)
- Primary Site
- Secondary Site
- SMS Provider
- Configuration Manager Console
Prepare the Site Server
Before installing a new update for a server application, I consider it to be best practice to install all the latest updates from Windows Update, the latest SQL Updates, and restart the server.
Installing the update on a Primary Site Server
I don’t have a Central Administration Site (CAS) in my lab, so I’ll be starting by updating the Primary Site Server. If you do have a CAS, that’s where you should start.
To start the installation, log in to the Primary Site Server, and run “CM12-SP1CU2-KB2854009-X64-ENU.exe “. The default settings should be ok, for most customers.
Note: You can follow the installation process in the C:\Windows\Temp\ cm12-sp1cu2-kb2854009-x64-enu.log file.
On the Welcome Screen, click Next.
Accept the license agreement, and click Next.
Review the prerequisite checker, and very that everything is ok, and click Next.
If you check the log file you should be able to identify the roles/features that will be updated.
One thing that has changed in CU2 is, that we can now update the console directly from the wizard. Accept the default, and click Next.
The rest of the setup experience is more or less just default, so just follow the wizard.
Review the summary page, and click Install.
Setup is running
During setup, you can follow the process in the setup log file. As a ConfigMgr admin, we now you love the log files, try to follow the process as we move forward
When setup is complete, click Next, and Finish.
Verify that setup was successful
After setup is completed, there is a few things you can do to verify that setup was successful.
The first thing you should do is to check the log file. But if you followed this guide, you have already done that
The next thing you should do is Launch the System Center 2012 Configuration Manager Console, and verify the build number of the console. If the upgrade was successful, the build number should be 5.0.7804.1300.
If you select properties of the Site Server to check the version number, you will notice that the build number is 5.00.7804.100 (SP1 RTM). This is expected; CU1 and CU2 does not update the site server version.
To verify 100%, you can check the CULevel registry data under HKLM\Software\Microsoft\SMS\Setup\.
If the upgrade was successful, the value should now be “2”.
Updating the Clients
After updating the site server, we need to update the clients. This update contains 2 update packages for client installations. One for 32-bit clients and one for 64-bit clients.
First you should copy the 4 packages that was created during setup, to your preferred distribution points and/or distribution point groups.
Then we need to create two collections for the client upgrade. (Both collections should be limited to the “All Desktop and Server Clients” collection.
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_COMPUTER_SYSTEM on SMS_G_System_COMPUTER_SYSTEM.ResourceId = SMS_R_System.ResourceId where SMS_G_System_COMPUTER_SYSTEM.SystemType = “X64-based PC”
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_COMPUTER_SYSTEM on SMS_G_System_COMPUTER_SYSTEM.ResourceId = SMS_R_System.ResourceId where SMS_G_System_COMPUTER_SYSTEM.SystemType = “X86-based PC”
The default settings on the update package are by default pretty good. But I don’t want my users to get notified for this update, so I prefer to suppress the program notification.
I also use maintenance windows for some clients and servers, but this update, I want to deploy now.
So for this update, I want to ignore the maintenance windows.
That’s it… Deploy the package, to the right collection, sit back and monitor the reports.
No reasons to say that you should test this on a limited number for clients first…