Introduction
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.
All-x64-based Clients
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”
All-x86-based Clients
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… 
Enjoy.
24 Comments
Pingback: SCCM 2012 SP1 – Cumulative Update 2 released | SCCMfaq.ch
Hello
CU1 blog talks about updating the console. CU2 blog doesn’t. I gather it is assumed that you are already at CU1. Might be worth adding a comment in about doing the console if not already on CU1.
Dont worry about my previous comment. RTFP (read the full post) 🙂
Hi Ronni,
Thanks for an excellent post.
Do you know if you’re able to rerun the DB Upgrade step seperately? I was unfortune enough to run the installation as a user without execute permission on the SQL DB, and the step completed with a warning. The log tells me that the users didnt have the appropiate permissions which is true, but I cannot rerun the installation of the CU.
Regards
Martin
Hi Martin,
I’d asume you could do that. I’ve never tried this specific secnario, but running setup Again is supported with this update.
Hi Ronni. Good and clear blog. I am currently migrating a CM2007 site to CM2012SP1. There are 50 Secondary Sites and I am upgrading them to 2012 DPs. I’m interested in CU2 to avoid the known DP issue (packages Unknown and the upgrade being continually processed).
I have installed CU2 on the Primary Site Server. At what point can I and should I install the CU2 package on a DP. Do I install it after I have upgraded to 2012? Is it too late at that time to avoid the package issue?
Hi Gerry,
You don’t need to apply this update on distribution points. Only Site Servers, the database server and the SMS Provider needs to be updated. If you have all 3 roles on the same server, you’re done 🙂
Cool. Thanks Ronni
Thank you for this wonderful post!
there was a syntax error with those collection queries on my system, so this is what worked for me:
x-64 systems (adjust for x86 as needed):
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
where
SMS_G_System_SYSTEM.SystemType = “X64-based PC”
Thanks again!
Thanks. This is very helpful. I have question though:
I have the “Automatic Client Upgrade ” to uncheck/not configured but I do have “Client Push Installation for Configuration Manager Client” enabled. With this setting, what is the expected behavior after I install the CU 2? Note: I don’t have CU1 installed or Update Roll 1. I only have SCCM 2012 SP1 intalled.
Thanks
Pingback: SCCM 2012 SP1 – Using Linux Client on Debian 6 | SCCMfaq.ch
Hi ronnie thx for the excellent post
One Question
For OSD (in my deploy task sequence) do I need to give some parameters into the step Setup Windows and Configuration Manager so that the newe version of the client will be installed on newly installed (deployed) computers
Thx
Johan
Deployed CU2 onto site server. All OK. Deploy package to clients. They are succeeding. Open control panel and version is as expected 5.00.7804.1300, but console is not updating with this information. Look in registry and …Mobile ClientProduct Version is xxx.1000. Look at ClientIDManagerStartup, and it says SCCM Client version is .1000 (it appears to find this from the registry). Deployments etc appear to be working. What do you think is the problem?
Hi Kelvin,
I have exactly the same experience, except that at least *some machines update their version in SCCM as .1300 but not all… I also noticed that although I manually inventoried all computers it still takes days before SCCM update and show .1300 version for the machines. It’s like 50/50. 50% of my computer that was upgraded to .1300 still show as 1000, while 50% show now as .1300. Please let me know what you find out. Thanks!
2 quick points – the packages that are built don’t have estimated deployment times. If you have maintenance windows set up, this can cause issues if you don’t override the window during deployment.
ALso – it appears that CU2 does not initiate a discovery data cycle or hardware inventory, so the client version is not always updates in the database until the next cycle ..
With a brand new sccm deployment I want to install CU2 before I even set up my site and deploy clients. Do I need to worry about the client upgrade packages in this case? After installing CU2 all newly installed clients will already be the latest version, right?
Tyler, No. Either you package and deploy it to your clients or add this. Check this out how to add to your OSD TS.
http://social.technet.microsoft.com/Forums/en-US/531fb188-6b23-4140-b899-f733a9d526dd/after-installing-sccm-2012-sp1-cumulative-2-is-it-safe-to-add-the-cu-patch-update-on-my-osd-task
we installed new fresh SCCM 2012 then we upgraded to SP1, and then installed CU1 & CU2.
the issue here, I did not find the new packages for the latest version clients 5.0.7804.1300, in order to deploy it.
i checked the packages in the console and nothing is created.
how can i get the packages?
should I deploy it or can I depend on the older version 5.00.7804.1000
1. You don’t need to run both CU1 and CU2. The latest version includes all updates.
2. If you run setup again, you can re-create the packages.
3. CU3 has been released.
Hi
If I go to administration–> site configuration –> sites in the home tab there is a button called Hierarchy settings, the last tab is about Automatic client Upgrade, even if I installed CU1 or CU2 however the latest version is greyed out, I guess there is a way to push automatically the updates without requiring each time to create collection based on processor architecture and manually deploy the right package to the right collection (it’s a nigtmare if you have multiple primary sites altought!)
have you experieced this flag behaviour ?
Pingback: RONNIPEDERSEN.COM Links from MS-10474D Class - RONNIPEDERSEN.COM
Pingback: RONNIPEDERSEN.COM SCCM 2012: How does Automatic Client Upgrade work? - RONNIPEDERSEN.COM
Quick question, do the clients on the old version of the SCCM client after the upgrade still work fully, i.e. will the remote client still work and can you still push apps on to them. I want to upgrade but only want to release the upgrade to client on a phased basis.
Yes.. All the old clients will still work. But I’d recommend that you get them upgraded within a month or so.
Check out Jason Sandys awesome startup script. That is my preferred and recommended way to install and upgrade clients.
http://blog.configmgrftw.com/configmgr-client-startup-script/