As of today the current branch version for System Center Configuration Manager is now available. I won’t go into the new features or explain much about the new name. However, you can read more about the current branch on the following System Center Configuration Manager Team blog.
You can download the evaluation here.
This blog is based off of my experiences upgrading my lab from Configuration Manager 2012 R2 SP1 to the current branch version 1511. I will be doing an in place upgrade and keeping my existing SQL Server instance untouched. I have a stand-alone ConfigMgr 2012 R2 SP1 Primary site with SQL 2012 R2 installed on the same box. If you do by chance have a hierarchy with a CAS and multiple Primary Sites always start at the top of the hierarchy and go down. So start with your CAS, your Primary Sites and then move to your Secondary Sites.
On a side note, if you are not currently running R2 SP1 you can pretty much follow the same steps. The following versions of Configuration Manager are supported if you are planning on upgrading:
- SCCM 2012 SP1
- SCCM 2012 SP2
- SCCM 2012 R2
- SCCM 2012 R2 SP1
Here is a quick link to Microsoft’s TechNet Upgrade checklist for quick reference.
ADK for Windows 10
First, you will need the newest ADK for Windows 10, version 1511 if you haven’t already installed it. The ADK is has now been moved to the Hardware Dev Center and can be found here.
WSUS Update for Windows 10 Servicing
Next, download and apply the WSUS update to your current SUP. If you have your SUP installed on a Windows Server 2008 system you will need to upgrade to at least Server 2012 R2.
You can download KB3095113 here.
Backup, Backup, and Backup!!!!
Before we even begin to install the ADK for Windows 10, applying the WSUS update, and even thinking about upgrading to CB 1511, you should backup your current ConfigMgr environment.
Make a complete backup of:
- ConfigMgr Database.
- USMT folders if you usethe state migration features.
- Your current boot images.
Various Other Considerations Before Upgrading
Some other considerations to make before upgrading based off of the TechNet article posted above are:
- Disable Database Replication if used.
- Disable all SQL Maintenance task for the duration of the upgrade.
- Uninstall site system roles that are not supported by System Center Configuration Manager.
- Microsoft Intune Connector
- Out of Band Management Point
- Service Health Validator Point
- Install all applicable critical updates
- Test the database upgrade process on backup database.
- Reboot Reboot Reboot.
Install the Prerequisites
ADK for Windows 10
Before you install the ADK for Windows 10 you will need to uninstall the previous version of the ADK. Once you have uninstalled and rebooted your server launch the installation for the ADK.
Select the following features:
- Deployment Tools
- Windows Preinstallation Environment (Windows PE)
- Imaging and Configuration Designer (ICD)
- User State Migration Tool (USMT)
WSUS Update (KB3095113)
Install KB3095113 to your current SUP server. My SUP is located on my existing Primary Site server. Then reboot your server. Once this is done we will be ready to upgrade to CB 1511.
ConfigMgr Current Build 1511 Installation/Upgrade
The installation experience is very similar to installing a service pack or new ConfigMgr installation.
- Mount the ISO and run Splash.hta.
- On the main menu, select Install.
- Click Next on the Before You Begin screen.
- On the Getting Started screen, select Upgrade this Configuration Manager site and click Next.
- Select I accept these license terms on the Microsoft Software License Terms screen and click Next.
- On the Prerequisite Licenses screen, select all 3 boxes and click Next.
- On the Prerequisite Downloads screen, specify a location. Click Next. If you have already downloaded the required files, select previously downloaded files and browse to that location.
- Wait some.. wait even more… then right when you think it is done… wait just a little longer.
- Select the language you want on the Server Language Selection screen. Click Next.
- Select the language you want for your clients on the Client Language Selection screen. Click Next.
- Click Next on the Usage Data Screen.
I have heard that during the Service Connection Point Setup screen that if you didn’t previous remove the Microsoft Intune Connector like it stats to do in TechNet, that the connector will automatically be upgraded to the Service Connection Point. I myself do not have my lab connect to Intune so it has never been enabled. That being said the next screen should be the Service Connection Point Setup screen.
- On the Service Connection Point setup screen, selet the recommeded, Yes, let’s get connected bullet. Enter your server that has internet access here, since I have only one primary site and all my roles are on one box I will entre my stand-alone box here.
Note: This is a very important configuration. It allows your Configuration Manager to stay updated with the newest service release from Microsoft.
- On the Settings Summary screen, you should see that the Setup Type is an Upgrade, click Next.
- The Prerequisite Check will run and there shouldn’t be any errors since this is an upgrade and if you have installed the ADK for Windows 10. Click Begin Install once the Prerequisite Check has been completed.
- At this time the Install screen will show the overall progress of the upgrade. You can view the log by clicking View Log or by opening the ConfigMgrSetup.log file located on the root of the C drive. If you don’t already use CMTrace this would be a good time to start doing so.
- This process for my small lab took about 40 minutes. This time can range anywhere from 30 – 45 minutes depending on the site servers configuration. Go get some coffee, kick back and watch an episode of The Big Bang Theory and then come back.
- On the Install screen, once you see Core setup has completed you can close the wizard.
At this time the upgrade is pretty much completed. There may be some more configurations going on in the background but you can now move to the verification steps.
Verification of Succesfull Upgrade
There are a few things you can do to verify that the installation for both the Site Server and the Console.
Open the ConfigMgr Console and click the upper blue arrow. Select About Configuration Manager. Verify the Console now says System Center Configuraiton Manager Version 1511.
Open the Administation Workspace, Expand Site Configuration, and then select Sites. Right click your site and select Properties. The Site Version and Build Numbers should have been upgraded to 5.00.8325.1000.
Your site server client version should now be upgrade to 5.00.8325.1000
Verify that your Boot Images have been automaticlly upgraded to WinPE. Open the Software Library Workspace then expand Operating Systems and select Boot Images.
After a succesful upgrade there are various other things you can check, configure, etc. You should plan to upgrade all your clients unless you have that enabled to automaticly upgrade. If you have any secondary sites you should upgrade those as well. If you had disabled database replication make sure you enable these replicas and verify they work. Reconfigre any database maintance tasks. Test some deployments, verify your boot images work, etc.
I am pretty much done and ready to play with the current branch 1511. To be honest, I have not played at all with vNext and looking forward to the new features. I might blog one day about those.