![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(12.8, 38%, 11%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EL%3C/text%3E%3C/svg%3E)
Service Manager
A family of System Center products for managing incidents and problems.
237 questions
Hi @Limiw ,
as an in-place upgrade from Windows Server 2016 to 2019 is supported I don't see a problem with SCSM and with a proper backup/restore strategy I would give it a try.
(https://learn.microsoft.com/en-us/windows-server/get-started/upgrade-2016-to-2019)
Just be aware Windows Server 2019 is not supported for SCSM 2019: https://learn.microsoft.com/en-us/system-center/scsm/system-requirements?view=sc-sm-2016#server-operating-system
If you are planing updates like this take care you have a proper backup/restore strategy for a rollback if something goes wrong!
Also setting up a test environment is a good option to test the upgrade procedure of OS and/or SCSM.
SCSM 2019 supports Windows Server 2016 and 2019. It might be a good option to update SCSM first from 2016 to 2019. If this is done you can update the server OS in the second step.
----------
(If the reply was helpful please don't forget to upvote and/or accept as answer, thank you)
Regards
Andreas Baumgarten