Cumulative Update 3 (CU3) for SCCM 2012 R2 SP1 and SCCM 2012 SP2 is now available. This post is a complete step-by-step SCCM 2012 R2 SP1 CU3 Installation guide. If you’re looking for a complete SCCM 2012 installation guide, see our blog series which covers it all.
Installing SCCM cumulative updates is very important to your infrastructure. It fix lots of issues, which some of them are important. Microsoft recommends installing Cumulative Updates if you are affected by a resolved issues. If you are not on SCCM 2012 R2 SP1 or SCCM 2012 SP2, the latest CU is Cumulative Update 5.
If you are running SCCM 1511, this Cumulative Update is not applicable to your setup.
As this is a cumulative update, you don’t have to install prior CU(1-2) before installing CU3. CU3 contains all the fixes included in previous CU.
There’s no new major functionality in CU3. This update contains fixes for issues in various areas including software distribution and content management, operating system deployment, site systems and mobile device management. In addition, it applies the latest KB and fixes known bugs.
The most interesting updates is a new optional task sequence variable, SMSTSWaitForSecondReboot, to better control client behavior when a software update installation requires two restarts.
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 prior CU. 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, we’ll be updating a Primary Site Server, console and clients.
SCCM 2012 R2 SP1 CU3 Installation guide
To start the installation, lauch a remote desktop session on your Primary Site Server, and run CM12_SP2R2SP1CU3-KB3135680-X64-ENU.exe
A log file will be created in C:\Windows\Temp\CM12_SP2R2SP1CU3-KB3135680-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 the screenshot, a reboot is required before installing the CU
- Check the box to update the console, click Next
- Select Yes, update the site database, click Next
- If the Automatic Client Upgrade feature is enabled on a Site Server, the wizard will present the Automatic Client Update screen :
- Choosing the Automatically apply option results in following steps:
- Places the most recent client patch file on the site server
- Updates content on the distribution points for this site and any child sites. Note this only occurs when the cumulative update runs on the Central Administration Site (CAS)
- Updates the client package on the Management Point of the local site; this source is used in the event there are no distribution points available for client installation
- Future client installations using the Client Push method will apply the new patch automatically
- The time frame for updating the client depends on your Automatic Client Upgrade settings
- If you chose the Manually Apply option, you will need to update your client manually as in prior CU (See our Updating the clients section)
- 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_SP2R2SP1CU3-KB3135680-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.0.8239.1403.
Open registry editor and check the HKLM\Software\Microsoft\SMS\Setup\ key. If the installation succeeded CULevel key value will be 3.
You can also verify both client and console version using PowerShell :
- Server : Get-ItemProperty -Path HKLM:\SOFTWARE\Microsoft\SMS\Setup -Name “CULevel”
- Console : (Get-Item ($env:SMS_ADMIN_UI_PATH.Substring(0,$env:SMS_ADMIN_UI_PATH.Length – 5) + ‘\Microsoft.ConfigurationManagement.exe’)).VersionInfo.FileVersion
The client version will be updated to 5.0.8239.1403 (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 CU3 updates packages are created
- Go ahead and Distribute Content to your distribution points
After this cumulative update is installed on site servers, any operating system boot image should be updated
- Open the SCCM Console
- Go to Software Library / Operating Systems / Boot Images
- Select your boot image, right-click and select Update Distribution Points
- Repeat the steps for all your boot images
Updating the Clients
If you select the Automatically Apply option in the installation wizard, your client will update using your time frame settings.
- Open the SCCM Console
- Go to Administration / Site Configuration / Sites
- Click the Hierarchy Settings in the top ribbon
- Select Automatic Client Upgrade tab
- The Upgrade client automatically when the new client update are available checkbox has been enabled
- Review your time frame and adjust it to your needs
If you select the Manually Apply option in the wizard, you will need to update your client manually.
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.8239.1403′”/]
Happy updating ! 🙂
I would also mention that if OSD is used then all boot images should be updated: “After this cumulative update is installed on site servers, any operating system boot image should be updated. ” https://support.microsoft.com/en-us/help/3135680/description-of-cumulative-update-3-for-system-center-2012-configuratio
When I have a CAS, should I install only on it or can I install it on the primary site manually?
may suit you to workout wiuhtot feeling boring. can give you a completely coach by Tony Horton and you can enjoy the joy when you do once you purchase the . Shaun T’s is another good choice for you.
I would have thought this was much higher actually. I know I am one of them. I've been in my home for 5 1/2 years and if I sold it tomorrow I'd be lucky if I didn't still owe the bank a couple of grand. I'm not sweating it as long as I can afford to keep making the payments. I have no plans on moving in the next few years. Hopefully things will turn around by then. In the meantime, I am paying my mortgage weekly instead of monthly. It has smoothed out my budget drcmitaaally in addition to getting my extra payment a year in. Wish I could pay EVERYTHING this way…just a suggestion!
Pingback: SCCM 2012 Version Übersicht | C-S-L K.Bilger
Pingback: SCCM Server Update Guide - Rui Qiu's Blog
Update fails for me with the following errors:
Task status detail added: failed. The following MSI installation failed. MSI: cm12_sp2r2sp1cu3-kb3135680-x64-enu.msi. Exit code: 1603
Task ‘Install files for update KB3135680’ completed, state is ‘failed’ LastStatus: Installing cm12_sp2r2sp1cu3-kb3135680-x64-enu.msi failed. The following MSI installation failed. MSI: cm12_sp2r2sp1cu3-kb3135680-x64-enu.msi. Exit code: 1603
Update Setup has completed with at least one failure.
You can disregard my question. It hasn’t been approved yet anyway. Delete that and this one too. The problem with the hotfix hot being available for download was temporary. The page is responding now. Sorry for the confusion.
The link to download CU3 appears to be broken. I can click through to https://support.microsoft.com/en-us/kb/3135680, but once there the Hotfix Download Available link ( http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=3135680&kbln=en-us ) leads to “Sorry, the page you requested is not available.” Any idea how I can get this now?
To update CU3 on the distribution point server 2012, what is the prerequisite ?
example :.net framework 3.5 …
thanks in advance for your help
I installed SCCM 2012 R2 SP1 CU3 in my testing Environment with Automatic Client Update enabled. Site version still Shows 5.00.8239.1000 that causes the Clients not to be updated because the latest version has already been installed.
Any ideas on this?
What about OSD? Do I have to set the PATCH = propertie in the TS-Step for installing ConfigMngr. Client, or is the client Agent automaticaly installed on version 1403 after OSD?
I am trying to install this but it keeps failing at the applying configuration manager console update step which it claims it cannot find the installation package. Any ideas? Currently on SCCM 2012 R2 SP1 same thing happens when trying CU1 or CU2.
“If you are not on SCCM 2012 R2 SP1 or SCCM 2012 SP2, the latest CU is Cumulative Update 5.”. We are on CM12 R2. Recommendation between these options:
– upgrade to R2 SP1, then R2 SP1 CU3
– upgrade R2 CU5
– other options?
Reasons for your recommendation?
I’m in the same situation and have the same question. Would appreciate input.
If you have the SCCM client installed on your site server, updating to CU3 will break the MP role when SCCM tries to update the client on the site system. This happened to me and I had to remove the MP role, uninstall and clean up the client, then reinstall the MP role.