Forum Discussion
Solved
Upgrading server 2016 essentials to server 2022 standard
I have a few questions about upgrading my on prem server. It is currently running 2016 server essentials. It is acting as the local domain controller, as all essentials servers must. I have ...
I'd suggest installing the hyper-v role (as only role) on host, then stand up two (or more) virtual machines for the various roles. The domain migration should not be a problem.
The two prerequisites to introducing the first 2019 or 2022 domain controller are that domain functional level needs to be 2008 or higher and older sysvol FRS replication needs to have been migrated to DFSR
https://techcommunity.microsoft.com/t5/Storage-at-Microsoft/Streamlined-Migration-of-FRS-to-DFSR-SYSVOL/ba-p/425405I'd use dcdiag / repadmin tools to verify health `correcting all errors found` before starting `any` operations. Then stand up the new 2019 or 2022, patch it fully, license it, join existing domain, add active directory domain services, promote it also making it a GC (recommended), transfer FSMO roles over (optional), transfer pdc emulator role (optional), use dcdiag / repadmin tools to again verify health, when all is good you can decommission / demote old one.
A Windows Server CAL is a license that grants access Windows Server. CALs are used in conjunction with Microsoft Windows Server OS licenses to allow Users and/or Devices to access and utilize the services of that windows server
- User CALs allow a single user access to Windows Server from an unlimited number of devices
- Device CALs allow an unlimited number of users to access Windows Server from a single device
Also available in my licenses:
Windows Server 2022 Remote Desktop Services device connections (50) - 4 keys remaining
Windows Server 2022 Remote Desktop Services user connections (50) - 4 keys remaining
Would these act as the CAL's I need? 50 users/devices per license, so technically i have 200 licenses available?
Windows Server 2022 Remote Desktop Services device connections (50) - 4 keys remaining
Windows Server 2022 Remote Desktop Services user connections (50) - 4 keys remaining
Would these act as the CAL's I need? 50 users/devices per license, so technically i have 200 licenses available?
Just checking if there's any progress of updates? Please don't forget to mark helpful replies.
I'd suggest installing the hyper-v role (as only role) on host, then stand up two (or more) virtual machines for the various roles. The domain migration should not be a problem.
The two prerequisites to introducing the first 2019 or 2022 domain controller are that domain functional level needs to be 2008 or higher and older sysvol FRS replication needs to have been migrated to DFSR
https://techcommunity.microsoft.com/t5/Storage-at-Microsoft/Streamlined-Migration-of-FRS-to-DFSR-SYSVOL/ba-p/425405I'd use dcdiag / repadmin tools to verify health `correcting all errors found` before starting `any` operations. Then stand up the new 2019 or 2022, patch it fully, license it, join existing domain, add active directory domain services, promote it also making it a GC (recommended), transfer FSMO roles over (optional), transfer pdc emulator role (optional), use dcdiag / repadmin tools to again verify health, when all is good you can decommission / demote old one.
A Windows Server CAL is a license that grants access Windows Server. CALs are used in conjunction with Microsoft Windows Server OS licenses to allow Users and/or Devices to access and utilize the services of that windows server
- User CALs allow a single user access to Windows Server from an unlimited number of devices
- Device CALs allow an unlimited number of users to access Windows Server from a single device- Thank you, that is exactly everything that i needed to know. I was asking if i could do an in-place upgrade, but i have a fallback server that does not host mission critical resources, but is configured almost identically to the host that i do want to upgrade, so I am testing this upgrade process on that server now and if everything goes as planned, will be following this method on the primary host.
An in-place upgrade is a very risky move and not recommended. Plus, you'll end up with the domain controller on the hyper-v host which is also not recommended.
