Installing this update is very similar to previous versions but a few things have changed since I did the last post on CU updates. In this blog post, I’ll walk you through the upgrade process step-by-step in a standalone primary scenario.
The full list of fixes and a link to request the hotfix is available here: http://support.microsoft.com/kb/3026739/
As always, you should start by checking the health of the system, verify the backup, etc.
At a minimum, you should check the following:
- Install any missing updates (security, critical and important).
- Verify you don’t have a pending restart.
- Verify that you have a valid SQL backup.
- Verify that the current installation of ConfigMgr is healthy.
- Verify that ConfigMgr 2012 R2 has been installed.
Download the update
After we have checked that the system is healthy, we need to download the update. SCCM 2012 R2CU4 is available for download here: http://support.microsoft.com/kb/3026739/
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
Update the Site Primary Site Server
To start the installation, log on to the Primary Site Server, and run “CM12-R2CU4-KB3026739-X64-ENU.exe“. The default settings should be ideal for most customers.
Note: You can follow the installation process in the “C:\Windows\Temp\cm12-r2cu4-kb3026739-x64-enu.log” file.
On the Welcome Screen, click Next.
Accept the license and click Next.
On the Prerequisite Check page, make sure to click “View Log”. This will open the setup log file and allow you to monitor the process as we move forward. Click Next.
If you check the log file, you’ll find all kinds of interesting information. Like the current CU Level.
Continue to follow the setup wizard. Default should be suitable for most.
Yes… Please update the database…
On the Deployment Assistance Options page, make sure all boxes are selected and click Next.
Continue through the wizard and accept all the default settings for creating the update packages.
Keep monitoring the process.
For most ConfigMgr Admins, the log file might be more fun compared to the UI.
When the job is done, complete the wizard and click Finish.
Verify that the setup was successful
After the setup is complete, there are a few things you can and should do to verify that setup was successful.
The first thing you should do is 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 directly on the Site Server and verify the build number of the console. If the upgrade was successful, the build number should be 5.0.7958.1501.
If you right-click and select “Properties” of the Primary Site to check the version number, you will notice that the build number is 5.00.7958.1000 (R2 RTM). This is expected; CU updates do not update the site server version.
An overview of all versions and build numbers can be found here: https://www.ronnipedersen.com/2014/07/configmgr-2012-versionbuild-numbers/
For additional verification, you may also check the CULevel registry data under HKLM\Software\Microsoft\SMS\Setup\. If the upgrade was successful, the value should now be “4”.
Update the Boot Images
As a best practice, I always recommend to update the boot images.
Just right-click your boot image and select Update Distribution Points.
The packages for SCCM 2012 R2 CU4 were created as part of the setup wizard but we need to distribute the packages to all distribution points before we deploy them.
Locate the new packages here:
\Software Library\Overview\Application Management\Packages\Configuration Manager Updates\
Select client packages. Right-Click and select Distribute Content. (Just follow the wizard).
Before we can deploy the CU updates, we need to create some collections.
You can create them yourself or you can use PowerShell.
I’ve created a small PowerShell script that will help you create the required collections for CU updates right here:
Deploy the updates
The default settings on the update packages are sufficient. However, I don’t want my users to get notified of this update so I prefer to suppress the program notifications.
I use maintenance windows for all of my servers, but this update in particular, I want to deploy now. So for this update, I will ignore the maintenance windows.
On the User Experience page of the Deployment Wizard make sure that Software installation will be performed outside maintenance windows.
That’s it… Deploy the package to the right collection, sit back and monitor the reports.
It goes without saying that you should test this on a limited number of clients first!
Update: Don’t forget to delete the old packages from previous CU updates versions.
More info: https://www.ronnipedersen.com/2015/02/sccm-2012-r2-deleting-old-cu-packages-using-powershell/