From release, SCCM 2012 R2 has been extremely solid and you may never run into any of the issues resolved by updates that have been released since; however in working with a Microsoft PFE (Premier Field Engineer) it was recommended to me to stay with the current version or current version -1. And if you read through what has been added in each version CU1 – CU5 you will likely find some nice fixes or additions that you can use in your environment. This is especially true for myself when it comes to the PowerShell improvements.
If you have never installed a SCCM 2012 R2 CU before you don’t need to worry about the previous updates, you can just install the latest version to get the improvements added since release. To read more about and obtain CU5 just take a look at the Microsoft Knowledge Base article here (https://support.microsoft.com/en-us/kb/3054451?wa=wsignin1.0).
The CU5 update can be applied directly to the following:
- Central administration site
- Primary site (Standalone)
- Primary site (Hierarchy)
- Secondary site
- Configuration Manager console
You should apply this update from the top down starting with your CAS if you have one or your Primary if you do not use a CAS.
While the installer will do its own checks before applying the update, there is one often overlooked thing to be aware of before beginning which may not come up in a small lab environment but will most certainly come up in larger, production environments.
The account you use to perform the upgrade should:
- Be a local admin on the server you are upgrading
- Be a full admin in SCCM
- Be a full admin on the SQL Server (and likely any other site servers in your setup)
- Have full permissions to the SCCM SQL Database.
Once you have done this you should be ready to begin and can run the CU5 Upgrade executable.
ALWAYS take care of any errors or warnings before going forward from this point. It is also a good idea to View the Logs just to make extra certain you are ready to proceed.
In most cases you will want this option checked the biggest exception being Secondary sites. Also if you are running the console on your workstation and are just wishing to upgrade the console, this would be the option to do that (but why bother when we can have SCCM perform the console upgrade to our workstation later).
Again, I always prefer to let the installer upgrade the site database for me but if something goes wrong in this part of the install, it is absolutely possible to go back and manually upgrade the database later using the upgrade.sql file (that will be left on the Primary server after the installer completes) using SQL Management Studio.
Since we are upgrading a Primary site in this case, there is no reason not to leave ALL these options checked which will cause the installer to automatically create packages in SCCM that we can use to upgrade the rest of our SCCM infrastructure later.
If you want you can customize the names of the upgrade packages.
It’s always good practice to read over the setup summary and make sure you have set everything the way you intended to. Then click Install to begin!
Once all the steps have completed, I again recommend viewing the log file to make sure all went well. If you are using cmtrace.exe (and you REALLY should be) you can watch the log throughout the upgrade process.
This system has now been upgraded and you can begin upgrading your clients and the console on computers on which it is installed.
To verify your server is now running the latest CU, just check the following (copied directly from the CU5 KB article linked to at the beginning of this post):
The CULevel value is located under the following registry subkey:
Note The CULevel value is set to 5 for Cumulative Update 5.
The version that is displayed in the About System Center Configuration Manager dialog box is 5.0.7958.1604.
*** Keep in mind that at this point only your site server and database have been upgraded. Any other Site Servers (not to be mistaken with Site Systems), clients or Admin Console installations will still need to be performed (using the packages created by the installer).