How to upgrade Configuration Manager 2012 R2 SP1 to Current Branch. This guide is based on my experiences after upgrading several ConfigMgr installations to Current Branch and is a step-by-step guide with everything you need to know to perform a successful upgrade.
This guide applies to the following Configuration Manager 2012 versions:
- SCCM 2012 SP1
- SCCM 2012 SP2
- SCCM 2012 R2
- SCCM 2012 R2 SP1
Step 1: Perform a Backup.
You need to perform a backup before you even think about doing an upgrade.
The following need to be backed up.
- SCCM SQL Database. I prefer to do a manual backup of the database from SQL Management Studio as it I can enable compression on the backup. SCCM backup is uncompressed and use considerable more disk space.
- Boot images.
- USMT shares. Only applies if you use User State Migration Tools.
Step 2: Install Prerequsites.
- ADK for Windows 10. This component is required for an upgrade and you want to use the latest version available. Version 1511 was the latest at the writing of this post. You will always find the latest version at Microsoft Hardware Development Centre. You want to install the following components:
- Deployment Tools.
- Windows Preinstallation Environment. (Windows PE)
- Imaging and Configuration Designer. (ICD)
- User State Migration Tools, (USMT)
- SUP / WSUS. Software Update Point and Windows Server Update Service is now required to run on Windows Server 2012 R2 or later OS. Migrate to new OS before you upgrade SCCM. KB3095113 need to be applied if running Windows Server 2012 R2 to enable WSUS support for Windows 10 feature upgrades. Download KB3095113 here. Your WSUS database will be full of garbage unless you have this KB installed.
Step 3: Disable components before the upgrade.
We don’t want any maintenance jobs do stuff while we perform the upgrade. Pay special attention to the following points.
- Verify if SQL Replication is configured and disable before the upgrade. Re-enable after successful upgrade.
- Disable All SQL Maintenance jobs. Re-enable after successful upgrade.
- Uninstall SCCM roles no longer supported.
- Microsoft Intune Connector
- Out of Band Management Point
- Service Health Validator Point
- Make sure Windows Server OS is updated.
Step 4: Test upgrade of the database.
Important: Never attempt a test upgrade on the actual SCCM SQL production server. The test upgrade will destroy your database and render it unusable.
- Copy your SQL backup of the SCCM database to a different SQL server. The SQL server for the test upgrade is required to be the same edition and at least the same version of SQL server as your production SCCM server.
- Attach it through SQL Server Management Studio
- Mount the SCCM ISO on the test server.
- Go to SMSSETUP\BIN\X64 in cmd prompt or Powershell.
- Run setup.exe /testdbupgrade CM_PS1. Replace CM_PS1 with the name of your SCCM database imported into test SQL Server.
Check out SystemCenterDudes for a more detailed guide on how to perform a test upgrade of the SCCM database.
Step 5: Restart server to clear possible pending reboot.
At this stage I always restart the server. It may not be necessary, and SCCM will tell you if there is a pending reboot on the server during install, but I always like the server to be fresh before I perform the upgrade.
Step 6: Upgrade SCCM to 1511.
Always start upgrading at the top of your hierarchy. Upgrade your CAS first and work your way down until every site is upgraded.
- Primary Site
- Secondary Site
The upgrade, step by step.
- Mount the Configuration Manager 1511 ISO and run “Splash.hta”.
- Select “Upgrade the Configuration Manager site”.
- Accept the terms.
- Check the three buttons regarding license terms and click next.
- Download the required prerequisite files.
- Select your supported languages for the SCCM console and reports.
- Select your supported languages for the SCCM client installed on client computers and servers. Personally I believe selecting anything else but English for the client should be illegal as it makes later troubleshooting a mess.
- You need to connect to the Cloud Service. If not you will not get any updates for your SCCM installation.
- Run the prerequisite check. It is recommended to fix every issue but you can chose to ignore warnings and proceed with installation. Errors have to be fixed you are allowed to start the installation and upgrade of SCCM.
- Start the installation and leave the office for lunch. The upgrade takes between 20-60 minutes to complete depending upon your server hardware.
- Congratulations. Your SCCM is now upgraded to version 1511.
Step 7: Upgrade SCCM to latest build.
The latest build of Configuration Manager is available in the Updates and Servicing under the Administration tab. Build 1602 is used in the illustration as it was the latest at the release of this blog post.
It is important to upgrade as you do not want to stay at build 1511. There is a bug with SUP and Windows 10 Servicing Updates that will fill your WSUS database with junk. This bug is fixed in 1602 and newer.
Always select run prerequisite check before you install the update pack. The prerequisite check gives you a good indication if the update will install successfully.