Here’s a step-by-step SCCM 2012 R2 CU4 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) before installing CU4. CU4 contains all the fixes included in previous CU.
Follow this Microsoft Support page to see a full list of issues that are fixed.
Windows Powershell changes are document on Microsoft Support as well.
There’s no new major functionality in CU4. It mostly applies the latest KB and fixes known bugs. The more important one is about Application installation step in Task Sequences.
If you’re a PowerShell fan, CU4 brings 36 new cmdlets as well of fixing 28 existing one.
Before you begin
Installing this update is very similar to CU3. 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-R2CU4-KB3026739-X64-ENU.exe
A log file will be created in C:\Windows\Temp\CM12-R2CU4-KB3026739-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
- 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.1501.
Open registry editor and check the HKLM\Software\Microsoft\SMS\Setup\ key. If the installation succeeded CULevel key value will be 4.
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.1501 (after updating, see section below)
This update also brings the anti-malware client version to 4.6.0305.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 CU4 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.1501′”/]
Happy updating ! 🙂
Everything installed nicely, the only thing I have observed is that the Parent Site SMS Agent will not stay running. I can start it but shortly later it just stops and somehow is affecting the MP role because clients can not resolve the site http://sccm.local/sms_mp/.sms_aut?MPLIST, we get 500 Internal Server Error. Any ideas?
is the CU installed on parent and child?
have you rebooted all of them?
yes, 4 out of 50, yes
46 sites dead, MP role hosed, critical DCOM permissions issues I’ve seen after CU3. Does keeps trying to re-install and fails.
I did have to re-create the upgrade package and dump the client.acu file in hman folder but still working on fixing MP roles.
parent and all 50 sites updates to cu4 successfully, had to fix upgrade package and run cu4 manually on each secondary.
some of the sites still having issues with sms agent services stopping, restarts fine but why is it stopping?
all sites have been rebooted and show cu4 installed.
any ideas on the sms agent issue?
Pingback: SCCM 2012 Version Übersicht | C-S-L K.Bilger
I followed your guide step by step, I keep getting SQL port errors no matter what I do… I have thoroughly followed your instructions on setting up SQL however I get an SQL Network Errors as if I haven’t opened the SQL ports. I have tried everything and I am getting pretty frustrated with uninstalling SQL and reinstalling. Please any help would be much appreciated.
NVM, since I was uninstalling and reinstalling SCCM 2012 r2, a simple name change to server and adding SPN for new servername got me past the errors. Just in case anyone else forgot a pre-req or just didnt do it for some reason or the other, and you have to uninstall and reinstall SCCM, just change the name of the machine and set the SPNs for the new server name and the applicable account.
Greetings from Alabaster. Magnificent post, i genuinely take pleasure in a effectively developed posting. I will subscribe to the RSS and look into your cultural profiles. I also needed to leave a message allowing you understand if you need any beneficial website maintenance recommendations to examine out my web site.
They don’t care nor did they ever. They’re a white lifestyle protectionist agency and nothing more. They exploit skinny white women for profit as well. Zero credibility.
I didn't know they grew coffee on any island other than the Big Island of Hawaii. I didn't like coffee the last time I was in Hawaii, so time to go back and learn even more.Chocolate Macadamia Nuts are delicious, so I bet the CM Coffee would be yummy too.
Hi I am On System Center 2012 R2 SP1, which does not support Windows 10. So I wanted to install the update, but my current system Center version is newer that this CU update. See install error message below:
Server update status: This update applies to product version 5.0.7958. The installed version on this computer is 5.0.8239.1000. This update is not applicable to this computer.
Console update status: No serviceable configuration manager role was found on the local system.
What do I do to upgrade my version of system center to support Windows 10 ?
SCCM 2012 R2 SP1 supports Win10 but with limited features. See our post on this : https://systemcenterdudes.com/managing-windows-10-with-sccm-2012/
The CU4 you are tryning to apply is older than the version you are running. The last CU for R2 SP1 is CU3. See our post on version list to get a good overview of versions : https://systemcenterdudes.com/sccm-2012-version-numbers/
How to install SCCM 2012 R2 SP1 CU3 : https://systemcenterdudes.com/step-by-step-sccm-2012-r2-sp1-cu3-installation-guide
To fully support Windows 10, you need to upgrade to SCCM 1511 : https://systemcenterdudes.com/sccm-1511-upgrade
Hope it helps 🙂
Does CU4 fix the Configuration Manager client push install to windows 10? I seem to still get the Unsupported version error.
You need Config Mgr 2012 R2 SP1 to manage Windows 10 clients properly.
Microsoft switched the AV back to Windows Defender for Windows 10 and Config Mgr doesn’t know what to do with it without SP1.
Pingback: Recordatorio! – ITROCKS
Pingback: Installing SCCM 2012 R2 CU4 | SCCM Deployment Tips
Hi, I have One primary and 3 secondary sites along with a separate DB and WSUS servers. Do I need to update the KB on each server?
You need to install the CU on your primary site and secondary sites. No need to update your DB and WSUS server (but you need to update their client as any other clients)
Thanks a lot for this complete article!
can someone advise, how to roll back the CU4 x64 client update. so that i can revert the config mgr client back to 5.00.7958.1000
To uninstall the CU, uninstall the client completely using ccmsetup /uninstall.
Once uninstalled reinstall the client using the source file on your SCCM Installation folder\Client (Your client will be .1000)
Thanks for this write up. When the install completed it stated a reboot was required.
There was an extra ” at the end of the query for the collection to capture clients that had not upgraded.
Thanks, I’ve updated it.
They are your government as well, And they deserve our full support, do you sleep good at night? do you eat well and shower well? All of these are thanks to our government pulling the strings they do to keep us safe at night. Of course a teenager like you wouldn’t appreciate that and go into the conspiracy theories made up by other teenagers.
Someone necessarily lend a hand to make significantly articles I’d state. That is the very first time I frequented your web page and so far? I surprised with the analysis you made to make this particular post incredible. Great job!
Franks Jacobs at Strange Maps has just had a really interesting post about the that five generations of one family have had in England.parental fears for their offspring’s well-being have been an important factor in reducing their childrenâ€™s unsupervised access to the great outdoors: fears of traffic, of predators, of being seen to have their children roam unsupervised.
Does the new Client require a reboot?
No reboot is required.
Great guide, thanks.
One question I’m a little confused about. If you have distributed the SCCM roles across mulitple servers, do they all need the upgrade or just the actual PS itself?
I have 1 Primary Server – but separate servers for 2 x MPs, 2 x SUPs, RSP, and mulitple DPs.
Primary site only need to be updated. Do not forget to update their client though.
I’ve recently completed the CU4 upgrade on the Primary Server, but it seems there is an issue with the site version according to AD.
When i pushed a client to a new machine, it recognised that the client version had been upgraded:
‘CcmSetup version: 5.0.7958.1501’
but then a little later in the set-up log I see this:
‘Retrived site version ‘5.00.7958.1000’ from AD for site ‘PS1”
– which is the old client version.
It is getting this from the properties of the System record for the Management Point in AD:
How do i change this??
I distributed the packages and attempted to install the update to the admin console. Installation failed with message “Error: 0x64C(1612)
Please cancel my last 2 posts. I re-ran install and it detected the KB was already installed but said I could recreate the packages.
Great Guide. I was successful with my install but the Server, Client, and Console packages failed to create. According to the logs my account didn’t have full administrative access to access the configuration manager provider as I used an account that had sa access to the db. So wondering how I can get those packages recreated or do I need to run the CU4 update again?
Great Guide. Install was successful except I had an issue during the CU4 update that my account I used that had sa rights to the db but not console rights failed to update the server, client, and console packages. Any ideas how to recreate those packages now that the install is complete or do I have to run the CU again?
Hi, I desire to subscribe for this webpage to obtain hottest updates, therefore where can i
do it please help out.
You can subscribe to our posts using Twitter,Facebook,RSS or email. Just look on the sidebar and site header for this.
Pingback: Updates to MDM and Intune in CU4 SCCM 2012 R2 | redkaffe
Thank you for sharing us!
I have installed CU4 and my admin console on the SCCM server is not able to connect to the site anymore.
I have another computer with CU3 Admin Console and I can connect to my site.
You don’t seem to have encountered this problem but I would appreciate any help.
Any error in the installation log ?