The latest releases of SCCM Current Branch(1702 and 1706) bring a new round of requirements. With SCCM 1702, it’s required to run site servers on a Windows Server higher than 2008 R2. Now with SCCM 1706, some of the new features like Manage Microsoft Surface driver updates, requires that all Software Update Point (WSUS) runs on Windows Server 2016. We can assume that we’ll see more of those new features requiring Windows Server 2016 in the future.
In this post, we will detail how to do an in-place OS upgrade from Windows Server 2012 R2 to Windows Server 2016, on an SCCM primary site with SQL installed locally.
- SCCM Current branch minimum level 1602
- See our latest post to upgrade SCCM to 1706 here
- Minimum versions for SQL server, if installed on the site server :
- 2012 SP2 and up
- 2014 SP1 and up
- 2016 RTM and up
- See KB here for more details
Tasks before In-place OS upgrade
- Install all the latest Windows updates, as the Upgrade setup will ask for it.
- Uninstall System Center Endpoint Protection client, if used.
In-place OS upgrade SCCM server
- Insert/Mount the Windows Server 2016 media and Start Setup.exe
- Select Download and install updates and click Next
- If there are still update, the setup will let you know
- Enter Product key, click Next
- Select Windows Server 2016 (Desktop Experience)
[su_box title=”Note” style=”glass” title_color=”#F0F0F0″]Windows Server Core is not supported for Site server. [/su_box]
- Accept license terms
- Select Keep personal files and apps, click Next
- Gettings updates if still needed
- Validating before upgrade
- Warning about Windows Server upgrades. SCCM support it, so click Confirm
- Validating available space on C:\ drive
- If there is not enough space, you will receive the following screen. Otherwise, it will show that it is ready, click Refresh
- Installation will begin
- The installation will proceed and automatically reboot.
- Once completed, the logon screen will display
Post Upgrade tasks
In-place OS upgrade will require post upgrade tasks to be completed. Some services have been set to disable or haven’t started after the initial boot under the new OS.
- IIS services are stopped and disabled
- Many SCCM component require IIS, so this needs to be fixed
- Open the Services management console
- Browse to World Wide Web Publishing service, and set it back to Automatic
- Browse to Windows Process Activation service, and set it back to Automatic
- SCCM Services are also not running.
- Rebooting the server after validating they are set to automatic, will correct this situation.
- Reboot the server
- If the site server is hosting the WSUS/SUP role, action must be taken, as the WSUS Configuration Manager will return error about the availability of WSUS on the local server
- To fix this, Launch the Post-Installation tasks of WSUS from the Server Manager
- Be sure to have fixed the services of IIS/SCCM and rebooted the server prior to run the Post-installation tasks, as WSUS rely on IIS also.
- One last reboot is needed so WSUS/SUP are correctly configured.
- Look at the Monitoring/System Status/Component Status if any error remains. Fix them before going any further with SCCM functionally.
Do not forget about Antivirus action after the upgrade. Most probably an update or re-installation will be needed.
If you use System Center Endpoint Protection, it should be reinstalled to manage Windows Defender, just like Windows 10
Click here for more details about In-place OS Upgrade for SCCM servers
Share this Post
That’s it, you’ve successfully upgraded your server to Windows Server 2016.
Will this procedure work for secondary sites as well? If not, how do I in-place upgrade secondary sites ?
This is the 2nd time I’ve done an IPU for this site server. this guide helped tremendously this time…
First time was from 2012 R2 to 2016 which hit a few snags, but was ultimately successful – partly due to going into it relatively blind due to not a lot of info on the subject back when I did it
This time, following the steps here, it looks to have been much easier to upgrade from 2016 to 2019,
The only problems were that my SQL Server services hadn’t started – all the others, IIS, etc were running
Ran the site maintenance wizard and so far everything showing green
I’d delayed this for so long thinking it would be a bit of a nightmare…
Thanks for the feedback Gatt!
Gald the post helped!
Just in case anyone else see’s these.
After the IPU, cannot connect to site servers
In an admin PowerShell, on each site server starting at your CAS (if you have one)
Set-location “D:\Program Files\Microsoft Configuration Manager\bin\X64”
While running the post install tasks, you see an error relating to starting the WSUS service
Remove the Software update Services role
Completely remove WSUS from your update point – https://www.ajtek.ca/wsus/how-to-remove-wsus-completely-and-reinstall-it/
Add the role.
All the best
@MarkP, thank you for posting how you got the Management Console working again. I found that after the upgrade (to Windows Server 2019), the root\SMS namespace no longer existed. The sccmprovidergraph.exe WMI provider was also crashing. Running the mofcom ….mof commands you stated and then rebooting fixed the issue. The root\SMS namespace now existed when I checked in wbemtest and the sccmprovidergraph.exe was no longer crashing.
Hi, two questions:
Do you have to stop the SCCM services before upgrade?
Do you have to do a site reset after the OS upgrade?
Throwing out an experience I had upgrading a Distribution Point from Server 2012r2 to Server 2016:
– The Netlogon service was set to Manual and Stopped after the upgrade, which caused issues authenticating new users, resolving existing users, and updating Group Policy
– I installed Server 2016 1607 (14393.2248) which did not include a fix for CredSSP error when connecting via RDP. I remotely copied the MSU for KB4103723 to the machine, used a pssession to expand the MSU file, then DISM to install the extracted CAB file. After a reboot, RDP worked properly.
– Content Distribution was failing from my Primary site to the DP. Had to re-import “smsdpprov.mof” on the DP
I did an in-place upgrade from 2012R2 to 2016 and that went well so I then went from Server 2016 to 2019 and I’ve followed all the post installation tasks above and all services were already running but I cannot PXE boot to the server any more and when I try and run the SCCM program it says it cannot connect to the site database 🙁
After successfully upgrading the OS to Server 2016 do you need to perform a site reset in SCCM? Please clarify that step.
I don’t need to uninstall WSUS or anything to go from server 2012R2 to 2016 do I ? Just run the OS upgrade? You guys have helped me do my job for years. No one shares information about SCCM like you do. Thanks.
correct, no need to remove WSUS, but follow the steps after the OS upgrade, otherwise it will no longer work.
Glad we help 🙂
That is what I am talking about Jonathan. Try to get a straight answer on technet forums. There is just no support out there for SCCM. It is strange. Thanks again.
it worked. Thank you!
Windows 2012R2 to Windows 2016
SCCM 1806 Hotfix KB4459354
But in our case not the IIS Service was stopped after the upgrade, but the WSUS Service was disabled.
We have to enable the service and restart the server before we could Launch the Post-Installation tasks.
Had issue opening console after upgrade from 2012 r2 TO 2016. Ran mofcomp smsprov.mof and console started working.
I’m getting ready to do an in place upgrade of my 2012r2 to 2016. My ConfigMgr version is CB1802. When reading your article you say that removing the SUS role is no longer needed? Can you please confirm?
Tried following your guide upgrading SUP Site system from 2012R2 to 2016 that hosts FSP and WSUS roles with remote SQL (SCCM CB 1706). Run in to issues after upgrade when running WSUS postinstall tasks.
First got this error:
System.SystemException: The trust relationship between this workstation and the primary domain failed. No issues on the box itself just the wsus component that had trust relationship issues.
Rejoined the domain and was able to move further but then got another error when running WSUS postinstall tasks:
FixSubscriptionCategories failed. Exception: System.Data.SqlClient.SqlException (0x80131904): Cannot open database “SUSDB” requested by the login. The login failed.
Login failed for user ‘Computername$’.
Tried cleaning up WSUS install completely on SUP and SQL with complete reinstalls with no luck. MS pointed to article (https://docs.microsoft.com/en-us/sccm/core/servers/manage/upgrade-on-premises-infrastructure) and said that we should:
“Before you upgrade to a different operating system, you must uninstall WSUS from the server. You may keep the SUSDB and reattach it once WSUS is reinstalled. ”
Ended up getting a new site system for SUP (or could have reinstalled the OS on the box) and all worked afterwards, so it seems like even though it’s not exactly our scenario it is the only solution:
In this case, the only known corrective measure is to format the hard drive and reinstall Windows Server 2012 R2.
Pingback: Upgrade Code Server Hosting Hostgator 2018 | Web Hosting
Pingback: Server Hosting Upgrade Promotional Code | Web Hosting
Pingback: Server Hosting Upgrade Fee Promo Code | Web Hosting
Pingback: Server Hosting Upgrade Activation Code | Web Hosting
I had the following issues after the 2012 R2 to 2016 upgrade on the PS Server
SMS Host Service would not start –
Removed and reinstalled the SCCM Client on the Primary site server – FIXED
IIS Worker Process/W3wp.exe taking 100% CPU –
Ended w3wp.exe task(to free up CPU), Install latest Cumulative Update for Windows Server 2016 – FIXED
I gave this a shot and did an in place upgrade on our site server thats running wds, iis, and wsus. I followed the steps to re enable wsus services and go through the post installation tasks. When I click on the post installation tasks to finish it up, it errors out and disables the W3SVC service. Any ideas?
If you want to eventually go to 2016 v1709, for 2012r2 or older, it’s best to switch to Core. 1709 is core only AND Server 2016 can only be installed as “Desktop Experience” or “Core” and there’s no switching!
Andy Barzyk – that isn’t really relevant though. Server 2016 1709 is a completely different channel so you can’t upgrade from Server 2016 to 2016 1709 anyway, it has to be a clean install. Also, Server 2016 1709 is for two specific scenarios (hence making it core only), so you would never use it for System Center.
thanks Hackmuss 🙂
I am currently running 1606 on Server 2012R2 and although SCCM reports successful patching of our 2016 servers, when actually viewing installed updates on the machine they were not updated since July/August 2017. So we had to go back and run a script to force them to download and install latest updates directly from microsoft. All of the 2008R2, 2012R2 servers show patched and actually have the patches installed. Why might I be getting a false report on 2016 patch status and why might those servers not be getting patches installed?
My question is really are there any known issues in 1606 or WSUS or SCCM running on 2012R2 that may cause this?
Outside of this I’m in the process of opening a Premier Support ticket with MS…
I have 2 servers:-
1. Windows server 2012 R2 having Domain Controller
2. Windows server 2012 R2 having SCCM+SQL
i need to upgrade this windows server 2012 R2 to windows server 2016 using SCCM.
Can you please elaborate the steps and provide me the better resolution for this.
Thanks in advance
Here is the article:
In my case it seemed applying Windows updates addressed the missing root\SMS issue (though I also performed a site reset and that may have contributed as well).
I have a question about this and also another thing.
Is the process very similar to this guide if you are running System Center Configuration Manager 2012 R2 SP1 on a Windows 2008 R2 OS? I would like to upgrade to 2012 R2 OS before upgrading to the latest branch of SCCM or 1606 version. Note: We are running SCCM as a virtual machine using VMware.
I saw you guys have a guide for sale for upgrading to SCCM 1511. I was wondering if you guys had a new guide coming out soon or available now for either the current branch or 1607? Also, I’m interested in a in-place upgrade guide. If you guys don’t have any available is there a good step by step guide likes yours that you guys recommend?
Have a great day!
First thing, in-place OS upgrade for a SCCM site server is only supported from Current Branch v1602 and up.
You need to upgrade SCCM before thinking about the OS upgrade.
To upgrade your SCCM 2012 to Current branch, you can follow our post https://systemcenterdudes.com/sccm-1511-upgrade/ . Same apply for newest version of SCCM.
You could upgrade your SCCM 2012 to Current Branch v1606, as this is a baseline version.
We take note for a future guide.
Hope this help.
I ran into the issue described in the “Known issue for remote Configuration Manager consoles” on the MS docs site. However, when I navigate under Root there is no SMS entry. Have you seen this?
can you share the link to the MS article ?
I didn’t had this issue.
I assume Bryan is talking about this article:
Hi, did you ever resolved this issue?
I see the same behaviour.
OK, in the site reset procedure you can choose to reïnstall the SMS_PROVIDER. See note MS article. Then SMS reappears as node.