I'm planning a migration of our current domain controller from a bare metal Windows Server 2016 Essentials setup to a new Proxmox-hosted server running Windows Server 2025 Datacenter. I migrated from 2003 to 2016 about 8 years ago, and I currently have the domain function at 2003 level. Before I take the plunge, I want to ensure my steps are correct. Here's my current plan: 1. Full image backup with Clonezilla, 2. Raise the domain function level - is it okay to jump to 2016 level from 2003 directly? 3. Migrate from FRS to DFSR, 4. Enable AD recycle bin, 5. Add the 2025 server and promote it to DC, 6. Migrate FSMO roles, 7. Move over DHCP, 8. Move over DNS, 9. Change the IP on the 2016 server, 10. Give the 2025 server the old IP, 11. Migrate shared drives, 12. Shut down the 2016 server, 13. Monitor for issues, then 14. Demote the 2016 server and consider upgrading to the 2025 forest level. Also, I've always been told to have two domain controllers—how crucial is that compared to just having good backups? I could set up a second DC as a VM if necessary, but I'm unsure if that would be effective if it's on the same Proxmox node.
4 Answers
For moving DHCP, you don’t need to overthink it; you can back it up from the old server and restore it on your new one whenever you're ready to switch over. Once that's done, just make sure to deactivate the old server's scope!
Windows Server 2025 is still quite early in its lifecycle. If you're looking for stability, go for Windows Server 2022. Plus, you’ll need to consider licensing as jumping from Essentials to Server Standard demands additional CALs. Make sure your FSMO role transfer is one of the last steps because it can trigger unwanted reboots on your old server.
Having active/active domain controllers is definitely the way to go. It lets you perform maintenance without disrupting your services. If you always do maintenance outside business hours, that's fine, but having two running ensures redundancy.
It's generally better to create a new domain controller rather than migrating the old one. Spin up a new VM with Server 2022 instead of 2025 since 2025 is still too new and has unresolved bugs. Keep your DCs running the essentials—like just Active Directory and DNS, preferably with minimal services. Once everything is set up, you can migrate your services like DHCP and file shares to separate VMs to streamline operations.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures