Cumulative Update 2 (CU2) for SCCM 2012 R2 SP1 and SCCM 2012 SP2 is now available. This post is a complete step-by-step SCCM 2012 R2 SP1 CU2 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.
As this is a cumulative update, you don’t have to install prior CU(1) before installing CU2. CU2 contains all the fixes included in previous CU.
There’s no new major functionality in CU2. 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. 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 CU2 Installation guide
To start the installation, lauch a remote desktop session on your Primary Site Server, and run CM12_SP2R2SP1CU2-KB3100144-X64-ENU.exe
A log file will be created in C:\Windows\Temp\CM12_SP2R2SP1CU2-KB3100144-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 restart 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_SP2R2SP1CU2-KB3100144-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.1301.
Open registry editor and check the HKLM\Software\Microsoft\SMS\Setup\ key. If the installation succeeded CULevel key value will be 2.
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.1301 (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 CU2 updates packages are created
- Go ahead and Distribute Content to your distribution points
- 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.1301′”/]
Happy updating ! 🙂
Pingback: Ms Sccm 2012 | mesotheliomacare.xyz
For free disk space bug, you can also just stop the MP_Control_manager service from console , then delete ccmsetup content and then push back the client. don’t forget to start MP_control_manager afterwards.
It worked like a charm for me.
I cannot connect to the Console remotely after the update.
Configuration manager cannot connect to the Site.
Ensure that the console has been updated by reviewing the logs. You probably don’t have the good version. You can manually install it. (Microsoft Configuration Manager\tools\ConsoleSetup)
Where is this path located?
In your SCCM installation directory
We need more ex-scientologists to speak out about the abuses within Scientology. The cult is very insular, so it is only through the voices of ex-members that we can know what is going on inside.Senator Xenophon has, unfortunately, an uphill battle to get anything done about them. The Senate doesn’t want to single out Scientology for inquiry, yet religion as a whole has a privilege that they don’t want to touch (“don’t go there”). It may be only bodies like OFT can act effectively against Scientology for things like breaking the minimum wage laws.
Zawsze robiÅ‚am jagody w cukrze. Takie bez cukru siÄ™ nie zepsujÄ…? Moje teÅ¼ byÅ‚y pasteryzowane, byÅ‚am pewna ze cukier jest niezbÄ™dny jako “konserwant”.
That Library Ban would have been one of the greatest political feats in the entire country…..Mary Ellen Baker probably never fully recovered from The Wrath of Palin.
that God doesn't give you more then you can handle. I think sometimes we feel like dang it god quit trusting me too much…lol. But you can do this. You are such a great person with so much goodness. Prayers are with your family to make it through this tough time. Hugs
I am exploring the Internet as I never have before. I have more time since I reitred. There is quite a rich diversity of information in blogs so I am getting involved and commenting. I think I really appreciate the basics of what you have here in this blog. I have started my own blog and website. I have incuded a website and email address. It seems to be customary to include these so I hope that its ok with you. TheVeryBest2You 13 12
After CU2 upgrade , it will modify the boot image version installed by ADK but what would happen to the custom boot images ? would that also be modified?
Also , if we have installed MDT and we have MDT boot images customized ? would that be also modified??
IF yes, do we need to perform any specific task after the upgrade ??
many thanks in advance.
Since installing CU2 I can’t open the console on any machine except for the server itself. It gives me an error saying “Extensions for Microsoft Intune have been enabled or disabled for this site” so I click yes, then I get “The feature update task requires that you close the Configuration Manager Console. Close all open configuration manager consoles and retry the operation” I click retry and nothing happens. Open the console again and it brings back the first message about enabled and disabled extensions. I’m going around in circles. I hate SCCM.
Try this. https://support.microsoft.com/en-us/kb/3118546
I bought and returned two other pairs of wireless headphones in the sub-$200 price range before springing for these, and simply put they are worth the extra money. There’s no interference, the sound quality is excellent throughout the range (bass, mids, highs) and the hiss that plagues most other wireless headphones doesn’t exist. Range is also excellent. The only thing to note is that the base station does not have optical audio input, only a standard 1/8th jack.
I have run into an issue with updating the admin console after applying cu2. Some of the clients targeted update successfully I do have several that fail with a Error: 0x643(1603). The code isnt very helpful. I have tried to go to the cccache and extract then run manually and get an error unable to locate file. path is valid on the package which is evident due to some clients getting updated.
After updating to CU2 my OSD task sequences now fail when installing the CM Client. It fails to retrieve the self signed certificate and seems to be stuck in provisioning mode. I have tried several “workarounds” for this issue but cannot seem to get my Task sequences to run properly. I have whittled down my sequences to only include the necessary steps, format drive, apply OS wim, apply drivers, join domain, and install CM client. Any help would be great.
OK here is a question. I was running SCCM 2012 under a Windows 2008 R2 server and at that time Microsoft was clear to indicate that if you Unicast “download directly from distribution point” it will apply the image directly to your drive vs Multicast which has to pull down the wim to a temp file then apply it to the drive. Anything over 14 or so unicasts kills our network so when we are doing a couple hundred computers at the same time we have to use multicast. However our WIM is 70 GB and takes up a good chunk of disk space and time to apply. I am now running a Windows 2012 R2 server with SCCM 2012 R2 Sp1 CU2. According to this – https://technet.microsoft.com/en-us/library/dn281955#BKMK_WDS2012R2 – they say – Improved multicast deployment by eliminating the need for making a local copy of the install.wim file. You can apply the install.wim file while it is being downloaded without significant impact to the application process.
There are a number of people that have been chasing this without any luck modifying the meta file in the boot wim, registry settings etc. Has anyone managed to pull this off? (Multicast a wim to a hundred computers and have it apply directly to the drive vs assemble it to a temp file on each workstation then apply it?)
Benoit, great articles. Thanks! After a CU is applied, can the client update be done by simply installing/reinstalling from the console via right click? Or does it need to be deployed from the created package or auto update? The right click option does not appear to change the client version for me.
For me after applying the CU to the server right click install would still only install the SP1 without the CU. What I had to do was create a directory called ClientPatch (c:\program files\Microsoft Configuration Manager\Client\x64\ClientPatch) and copy the configmgr2012ac-sp2r2sp1-kb3100144-x64.msp into this directory then re-distribute the package. When the agent installs it looks for this directory to see if there are any patches that need to be run on the client and will apply the CU automatically.
Rob – I appreciate your quick response, this worked for me. Thanks!
I’ve noticed that the update copies the msp into that location, but under “Hotfix” for 64Bit and “hotfix\KB3100144” for 32Bit. Will the Client Push find the msp file there or does it need to be re-copied into a ClientPatch folder as you suggested?
Client installations using the Client Push method will apply the new patch automatically
We just completed upgrading to 2012 R2 SP1 CU2 and we are unable to create collections now.
Has anyone else has that problem?
So after contacting Microsoft our Site Code was on the list of unsupported ones found at the bottom of this page: https://technet.microsoft.com/en-us/library/gg712320.aspx
We are now rebuilding our Primary Site Server to resolve the problem.
We have a production environment “System Center 2012 R2 Configuration Manager Sp1” we are looking to upgrade , so planning to install directly CU2 ( KB2780664). can we go ahead ? i mean i hope we no need to install CU1…..
Also clarify me , if we go ahead with above CU2 is our console version will show 1301 or 1302 ?
Yes you can install CU2 directly.
If you install CU2 for your console, the version will be 1301.
You can refer to this post for version numbers : https://systemcenterdudes.com/sccm-2012-version-numbers/
I installed the 1301 version of the CU2 but have read they re-released the CU2 and that version is 1302. Anyone know what was fixed and if it is worth trying to upgrade to the 1302 version of CU2? Can’t find anything on technet on it.
you are right about the re-release. There was a bug about the console. 1302 is only for the console. Clients will be at 1301
SCCM versions fun! 🙂
I read somewhere that having a child is like wearing your heart outside your body. This is both scary and wonderful. When tragedy befalls I imagine itâ€™s devastating.
we’ve updated our sccm 2012 R2 SP1 with CU2, but ours clinets are on the old version 5 00.8239.1000
We set automatcic client upgrade in the options, but they are still on the old version.
Do we need to do something else, or they will be updated for some time ?
Make sure the collection has an active maintenance window so they can install the client upgrade.
Do I need to deploy upgrade client package to the collection ? I didn’t do this, I thought that automatic update means that we don’t need to do that , only to distribute to the distribution point.
I did the upgrade just before the break and it will not automatically deploy to clients running the 2012R2 client (non SP1). I have been having to manually deploy the client to collections to get it to go. On a good note unless I missed it before I found if I create a directory called ClientPatch in c:\program files\Microsoft Configuration Manager\Client\x64 and dump in the CU2 update msp file it will also apply the CU2 patch on the tail end of the client install once I distribute to distribution points and deploy.
I found out something, when the build number of sccm is the same (if we install new CU) clients can’t update automaticly, in that case we must create collection and deploy updates to them.
Only when build number is different (sccm 2012 r2 sp1 to sccm 1511) in that case automatic upgrade will work for clients. There is difference between update and upgrade clients. That confused me, but I think now its clear.
great step by step thanks!
probably stupid question but hope you can clarify,why do we need to update the boot images? and do we need to updte all of them (the custom one we use to deploy win7 still seems to work; if we update it we’ll have to re-create the prestaged media and send it back to manufacturer, if I can avoid this I would).
Has anyone experienced problems with the SMS Agent Host service on clients after CU2 upgrade?
It crashes constantly on a few machines and that number of machines is slowly rising…
I don’t know if I should open a support case or wait for a fix.
Yes, same issue in our environment. Internet facing MP, with installation on F-drive. Fails with 90MB disk space error… Tried an old fix (uninstall MP role, reinstall client with ccmsetup SMSSITECODE= then readd MP role. But the client does not want to be installed.
Thanks for this, it helped a lot for an SCCM newbie.
I think the version in your code snippets for the client machines query and elsewhere are missing a 0. You have “5.0.8239.1301” but I had to update it to “5.00.8239.1301” to get my queries to work. Your screenshots are right. The console version is a single 0 though.
Thanks, I will fix that.
We upgraded our infra from 2012 R2 to 2012 R2 Sp1 Cu2 succesfully. We have a lot of clients on sccm build version 5.00.7958.1401, can we jump to lastest client version or have to do it in steps?
You can go directly to the latest CU
If I upgrade from 2012 R2 to 2012 R2 SP1 CU2 do I have to install the Win 10 ADK to deploy Windows 10 images or will the boot image that is installed as part of the SP1 & CU2 be enough? This is strictly to deploy existing pre-built W10 Wims.
You will need the Win10 ADK since WinPE 10 is needed.
You can still deploy older OS (7,8,8.1) using WinPE 10
Did you guys see all the applications in SCCM2012 getting re evaluated post applying the CU2 as we now see almost 70k files back logged in the objmgr.box and the processing is damn slow and we see the same behavior in both our primaries.
No, we’re not seeing that at all. The only thing we’ve seen thus far is the issue i posted. Oh and btw, that’s when CU2 v2 is reapplied on top of CU2 v1 (was applied previously).
I didn’t saw this behavior.
It appears that the latest CM12 R2 SP1 CU2 code has some issues with updating the MP. This appears to be consistent across 3 different CM Labs we applied this to. Please share if you’re experiencing the same. Thanks!
After installing this updated CU2 on the primary site, you may receive the following error in sitecomp.log when it tries to update or reinstall the MP.
“Bootstrap operation failed with error code 1”
Then looking at mpsetup.log, may see these lines below:
Installing pre-req using command line “D:\SMS\client\ccmsetup.exe” /UpgradeWithServer:mp
Pre-req installer “D:\CM12\client\ccmsetup.exe” /UpgradeWithServer:mp finished with exit code 1
Failed to Install Pre Req CcmSetup. Return Code is 1
This was a required Pre Req, can not continue.
Installation Failed. Error Code: 1
Within ccmsetup.log, you may see the following:
CcmCheckFreeDiskSpace. Check if the target volumn has enough space for the installation.
There is not enough available disk space on to complete this operation. Installation requires at least 90MB free disk space.
File C:\Windows\ccmsetup\configmgr2012ac-sp2r2sp1-kb3100144-x64.msp installation failed. Error text: ExitCode: 1603
There is not enough available disk space on to complete this operation. Installation requires at least 90MB free disk space.
Params to send ‘5.0.8239.1301 Deployment Error: 0x80070643, ‘
I have encountered the same issue with the re-install of the MP. I have tried to remove the role and then re-install several times no success. Is there a work around yet.
For the reinstall MP issues, we contacted MS and the workaround is to remove the role, uninstall the client, reinstall the client to a different drive\folder and put the role back on the server. That should work just fine. Apparently this issue only appears on systems with first version of CU2 version1 and with applying the revision version of CU2. If you have a hierarchy that’s never been touched with CU2, the final version should work just fine.
I had the same issue. The SCCM client was installed on drive D:
I posted a solution on my german blog: https://www.cmehren.de/2016/05/03/sccm-management-point-fehler-nach-update/
The solution translated to english:
1. Uninstall MP via SCCM console
2. Uninstall SCCM client agent (ccmsetup.exe /uninstall)
3. Install MP via SCCM console
The build number for me is 5.0.8239.1302
There was a minor bug in the first CU2 release. The product group has release a new build after my post. If you are installing using the new build, the console version will be 1302
I had some pain points helping a customer setup CU2. I posted my observations at https://t3chn1ck.wordpress.com/2015/11/16/cu2-for-configmgr-2012-r2-sp1/
Pingback: SCCM 2012 SP2R2 SP1– Sortie de la CU2 |
Always consult this site for SCCM news.
As for the old updates packages, it is good practice to remove them ? I mean the old CUs .
For the old update packages, I like to keep them to remember the upgrade I did in the past.
Be sure to remove the deployment 😉
No, you do not need to delete old CU.