I'm looking for some guidance on upgrading my server from Windows Server 2008 R2 to 2022. Currently, we have an IBM system x3650 running Server 2008 R2, and we want to upgrade to new hardware while ensuring we keep the same domain. The server primarily runs Active Directory, DNS, and DFS. Can someone outline the best steps to achieve this? Also, I need to know how to safely migrate my DFS file system since the data is stored on a SAN. Any tips would be appreciated!
3 Answers
It's best to install the necessary services on your new hardware first. After promoting the new Domain Controller, transfer the FSMO roles to it, then update DNS settings to reflect the new IP. As for DFS, that's usually straightforward. You might want to consider migrating the storage access to your new DC and ensure your SAN volume is attached properly. It's all about maintaining that permission structure, so don't just create a new share without carefully planning.
You'll need to set up an intermediate Windows Server 2016 Domain Controller before moving to Server 2022. Windows Server 2016 is the last that supports SMB1 and FRS, which are important for your migration. Ideally, migrate from FRS to DFRS on your existing 2008 R2 before you upgrade. Also, keep in mind that if your 2016 is fully patched, it won't support FRS anymore, so you might want to test the migration on an unpatched version first. Check out these links for more details: [link](https://techcommunity.microsoft.com/blog/filecab/streamlined-migration-of-frs-to-dfsr-sysvol/425405#express) and [link](https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/windows-server-version-1709-no-longer-supports-frs).
Good point! I've also heard that recent Kerberos and DCOM updates can cause compatibility issues between 2008 and fully patched 2016 or 2022 servers, so make sure you're aware of that before upgrading.
During the migration, remember that data on your SAN should stay intact if mapped correctly. You can definitely map that SAN volume to the new DC. However, double-check your permissions after the move to avoid any issues. If you're unsure, you might consider creating a new share just to be safe. Better to be cautious!
Thanks for the info! About the DNS: If my current DC is set to x.x.x.20, and I change the new DC's IP to x.x.x.21, can I later switch it back to 20 once the old DC is retired? That would make things smoother for user connections.