ConfigMgr Current Branch 1602 has been out for six months now. One of the supported features of this release is the ability to upgrade the site server from Windows Server 2008 R2 to Server 2012 R2. Here’s the support statement from Microsoft https://technet.microsoft.com/en-us/library/mt757351.aspx.
If you have upgraded to ConfigMgr Current Branch and are still running Windows Server 2008 R2 then your support for this O/S will end with the first update released after 31/12/2016. This is also true for most site system roles, however note that Distribution Points are exempt from this deprecation. All the details are here https://technet.microsoft.com/en-us/library/mt628077.aspx.
So time is running out for you to get into a supported state. Hopefully this guide will help you make the transition smoothly.
I’m running this in my home lab. Currently this consists of 1 x site server with all the roles installed on it. SQL is local. At present SQL is running SQL Server 2008 R2 SP2. This isn’t supported in SCCM Current Branch and I need to be running at least SP3 (https://technet.microsoft.com/en-us/library/mt589592.aspx). Well SQL Server upgrade is an upgrade for another day and I’ll just run with this for now, however in a production environment I would ensure that I was running a supported release before performing any upgrades.
Since I have a Software Upgrade Point running in my environment…
I need to take note of Microsoft’s Warning message in the article https://technet.microsoft.com/en-us/library/mt757351.aspx ‘Before you upgrade to Windows Server 2012 R2, you must uninstall WSUS 3.2 from the server.’
Uninstall WSUS 3.0SP2 or the WSUS Admin Console from the Site Server
Uninstall WSUS 3.0SP2
Let’s start by removing the SUP role from the Site Server. Go to the Administration workspace>Site Configuration>Servers and Site System Roles. Highlight the site server hosting the SUP and right click the Software update point. Right click and choose Remove Role.
Click Yes when prompted to remove the SUP.
Keep an eye on the SUPSetup.log. This will let you know when the SUP has been removed.
Now I can remove WSUS. To do this load up Server Manager, right click on Roles and select Remove Roles.
Deselect ‘Windows Server Update Services’ and click Next.
I’m going to tidy up the WSUS install by removing all the components. Note that this will remove SUSDB from your SQL Server. Continue through the wizard.
When the WSUS removal is complete click Finish, then close the Roles Wizard.
Uninstall the WSUS Admin Console
If you are running a remote SUP then you will only have the WSUS Administration Console installed on the site server. This will need to be removed if you are planning to upgrade to Windows Server 2012 R2. To do this go into Control Panel\Programs and Features. Highlight the Windows Server Update Services 3.0Sp2 Console and click Uninstall.
Remove any log files if required and click Next. Continue through the wizard until complete.
Now that WSUS 3.0SP2 is removed from the site server I can start the upgrade process.
In-place Upgrade Server 2008 R2 to 2012 R2
Before you start the process to upgrade the server make sure that you have a backup of ConfigMgr. Makes sense huh!
As a pre-caution I have disabled all ConfigMgr and SQL services before running the upgrade.
Once complete restart the site server and then mount Windows Server 2012 R2 media.
At OS level run setup.exe from the Server 2012 install media.
Run through the standard Windows 2012 R2 install
Interestingly on my VM at the point I got to ‘Setup is starting’ I was thrown out of the install process and back to the ‘Install Now’ window above.
To remedy the problem I had to run the following command (with D:\sources pointing to my Windows 2012 R2 media):
C:\$WINDOWS.~BT\Sources\setup.exe /runlocal /BTFolderPath:C:\$WINDOWS.~BT /OSImagePath:"D:\Sources" /HideWelcome /uilanguage:en-US /targetlanguage:en-US
Choose whether to update the OS or not at this stage. I have chosen not to. Enter the product key and version when prompted.
Now the most important part of the process is that Upgrade is selected.
The upgrade process will begin.
Once the upgrade is complete then it’s time to enable and start up the ConfigMgr and SQL services.
A quick check of the Site Status and it shows things are looking good.
Next up the installation of the WSUS services, either full or Admin Console depending on which was installed previously, needs to be performed. In this instance I am going to install the full WSUS.
Open up Server Manager and click Add Roles and Features.
Click through to Server Roles and select ‘Windows Server Update Services’.
A pop up will appear. Click Add Features
Click through to to the WSUS Role Services screen and deselect WID Database and choose Database to be able to use the SQL server for the SUSDB.
Enter a location to store WSUS updates. I am using the same path I had used when running WSUS 3.0Sp2.
Enter the hostname of the server hosting the SQL server, in my case the site server itself and click Check Connection to connect successfully.
Remember to run the post installation tasks once the Role is added.
If you are looking to support Windows 10 feature upgrades in your environment then you will need to install KB3095113 Update to enable WSUS support for Windows 10 feature upgrades at https://support.microsoft.com/en-us/kb/3095113
When downloaded execute the Windows8.1-KB3095113-v2-x64.msu file.
If you get a ‘Update is not applicable to your computer‘ message when attempting to install KB3095113 then follow this guide.
Click Yes to install the KB
When complete restart the server
When WSUS is patched then add the SUP role back onto the server.
Again the SUPSetup.log reports all is good.
I’ll keep an eye on the site server and report back with any issues that were encountered post the OS upgrade.
Next up I’ll need to get my SQL Server into a supported state, so I’ll upgrade it to a later release. Look out for that blog post soon.
** Post update – 11.01.2018 **
Note that it has come to our attention, via the SCCM Product Group, that a site reset is required post upgrade to reinstall the site provider. This isn’t documented, at present, but has now been highlighted. More info on that here.