Here’s a step-by-step SCCM 2012 R2 CU5 Installation guide.
Installing SCCM cumulative updates is very important to your infrastructure. It fix lots of issues, which some of them are important.
As this is a cumulative update, you don’t have to install prior CU(1,2,3,4) before installing CU5. CU5 contains all the fixes included in previous CU.
There’s no new major functionality in CU5. It mostly applies the latest KB and fixes known bugs. Follow this Microsoft Support page to see a full list of issues that are fixed.
PowerShell changes are no longer included in CU as described in our previous post. You won’t find any changes in PowerShell following this CU.
Before you begin
Installing this update is very similar to CU4. I’ll guide you through the upgrade process step-by-step in a standalone primary scenario.
- Download the update on the Microsoft Support page
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
In this guide, I’ll be updating a Primary Site Server, console and clients.
Update the Primary Site
To start the installation, rdp to your Primary Site Server, and run CM12-R2CU5-KB3054451-X64-ENU.exe
A log file will be created in C:\Windows\Temp\CM12-R2CU5-KB3054451-X64-ENU.log
- On the Welcome Screen, click Next
- Accept the license agreement, and click Next
- Ensure that everything is green, and click Next. On my screenshot, a restart is required before installing the CU.
- Check the box to update the console, click Next
- Select Yes, update the site database, click Next
- Check all 3 checkbox (Server, Console and Clients), click Next
- Edit the package name and program to your need, click Next
- Review the Summary page, click Install
- Installation is in progress
- You can follow the installation progress in the log file (C:\Windows\Temp\CM12-R2CU5-KB3054451-X64-ENU.log)
- When setup is complete, click Next and then Finish
After setup is completed, launch the System Center 2012 Configuration Manager Console and verify the build number of the console. If the upgrade was successful, the console build number will be 5.00.7958.1604.
Open registry editor and check the HKLM\Software\Microsoft\SMS\Setup\ key. If the installation succeeded CULevel key value will be 5.
You can also verify both client and console version using PowerShell :
- Server :
- Console :
:SMS_ADMIN_UI_PATH.Length – 5) +
The client version will be updated to 5.00.7958.1604 (after updating, see section below)
This update also brings the anti-malware client version to 4.7.0209.0. You can find the version information by clicking About on the Help menu of the Endpoint Protection client UI.
Navigate to Software Library / Packages / Configuration Manager Updates
- You’ll see that your CU5 updates packages are created
- Go ahead and Distribute Content to your distribution points
Updating the Clients
We now 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.
Create two collections for the client upgrade. (If not already done in previous CU)
All-x64-based Clients[pastacode lang=”sql” message=”” highlight=”” provider=”manual” manual=”select%20SMS_R_SYSTEM.ResourceID%2CSMS_R_SYSTEM.ResourceType%2CSMS_R_SYSTEM.Name%2CSMS_R_SYSTEM.SMSUniqueIdentifier%2CSMS_R_SYSTEM.ResourceDomainORWorkgroup%2CSMS_R_SYSTEM.Client%20from%20SMS_R_System%20inner%20join%20SMS_G_System_COMPUTER_SYSTEM%20on%20SMS_G_System_COMPUTER_SYSTEM.ResourceId%20%3D%20SMS_R_System.ResourceId%20where%20SMS_G_System_COMPUTER_SYSTEM.SystemType%20%3D%20%22X64-based%20PC%22″/]
All-x86-based Clients[pastacode lang=”sql” message=”” highlight=”” provider=”manual” manual=”select%20SMS_R_SYSTEM.ResourceID%2CSMS_R_SYSTEM.ResourceType%2CSMS_R_SYSTEM.Name%2CSMS_R_SYSTEM.SMSUniqueIdentifier%2CSMS_R_SYSTEM.ResourceDomainORWorkgroup%2CSMS_R_SYSTEM.Client%20from%20SMS_R_System%20inner%20join%20SMS_G_System_COMPUTER_SYSTEM%20on%20SMS_G_System_COMPUTER_SYSTEM.ResourceId%20%3D%20SMS_R_System.ResourceId%20where%20SMS_G_System_COMPUTER_SYSTEM.SystemType%20%3D%20%22X86-based%20PC%22″/]
Adjust the package options to fit your environments and deploy the update to your clients.
Once deployed I like to create a collection that targets clients without the latest CU. I use it to monitor which client haven’t been updated yet.
Here’s the query to achieve this: (You can also refer to our Set of Operational Collection Powershell Script)[pastacode lang=”sql” message=”” highlight=”” provider=”manual” manual=”select%20SMS_R_SYSTEM.ResourceID%2CSMS_R_SYSTEM.ResourceType%2CSMS_R_SYSTEM.Name%2CSMS_R_SYSTEM.SMSUniqueIdentifier%2CSMS_R_SYSTEM.ResourceDomainORWorkgroup%2CSMS_R_SYSTEM.Client%20from%20SMS_R_System%20where%20SMS_R_System.ClientVersion%20!%3D%20’5.00.7958.1604′”/]
Happy updating ! 🙂
After I upgrade to CU5, do I need to push the new client to all my workstations? If I have automatic client push enabled, will this take care of it?
After upgrade CU5 Management Point in Critical state ?
Anything that I can do to resolved ?
After upgrading to SCCM 2012 R2CU5, One of my secondary site is down and gives below error in sitecomp.log
*** [Microsoft][SQL Server Native Client 11.0]A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.
*** Failed to connect to the SQL Server, connection type: SMS ACCESS.
CSiteControlEx::GetCurrentSiteInfo: Failed to get SQL connection
Sorry, my SQL Express service was stopped on this server. I just started the service and working fine
Pingback: Step-by-Step SCCM 2012 R2 SP1 Upgrade Guide
Very well written, easy to follow. Thank you very much. Installed CU5 without any issues, now planning to upgrade SP1.
One quick question: I have automatic Client Push Installation setup, do I still need to deploy new client using collection?
I’ve heard that with CU updates you can skip over previous releases, but would just like to double check. Can I skip from the original 2012 R2 release and go directly up to CU5, or would it be a safer bet to ensure environment has enough time to update clients and servers up to CU1 first?
I read in a earlier comments within the Step-by-Step SCCM 2012 R2 CU3 Installation guide, that you could skip directly to it (CU3).
We skipped over 2,3,4 and went to 5. Although, at this stage I would install the SP1which system center dudes has a good tutorial on.
SP1 contains all fixes in prior CU. If you’re ready, go ahead and install SP1 following our guide 🙂
Same process i am following but i am received one error .
(Setup exiit status 3003 (Task state :Failed))
“Task ‘Create Software Update Catalog’ completed, state is ‘failed’ ExceptionText: Error: Setup detected an unexpected problem during installation. Error message: UpdatesPublisher catalog task: File ‘C:\Program Files\Microsoft Configuration Manager\hotfix\KB3054451\Server\x64\CM12-R2CU5-KB3054451-X64-ENU.exe’ does not exist, unable to create catalog. Check the MSI log for the update for information on why the file was not created.
Error: Setup detected an unexpected problem during installation. Error message: at Microsoft.SystemCenter.UpdateSetup.Tasks.GenerateCatalog.VerifyFileExists(String fileToVerify)
at Microsoft.SystemCenter.UpdateSetup.Tasks.GenericTask.RunThread(Object taskObject)
I had this. Copy the install exe you downloaded to the location it is looking for it in.
Thx for the article, and as well for all comments.
Just to doublecheck… does CU5 affect Win PE ? Will I need to update it ? (I have minor additions in)
There’s no changes in the Boot image in CU5
FYI: You do not need to create separate arch type collections ie. x86 and x64 as the program within the client update package already has requirements set to only update the respective arch type. As an example the x86 client program has a requirement to only update on Windows Server 2003 32-bit, 2003 R2 32-bit, and Server 2008 32-bit.
Nice guide! One question. Seeing that this is not published with Windows Updates, what is the best way to stay notified of these and other hotfixes? I would like to stay on top of these as they come out.
My server had no reboot pending during the pre-check, but I was asked to reboot after the install was done.
Clear & very interesting.
I know I asked this for CU4 but would just like to double check for CU5.
Will this require a reboot for my servers and client machines?
No reboot is required