How to Upgrade Windows Server Version and not lose AD/DHCP/DNS/File Sharing

[vainsy]

Hey,

I currently have a server that runs my DHCP, Active Directory, DNS, while being NAS on my network. It currently is running Windows Server 2012 r2, however I was looking to upgrade it to Windows Server 2016. I was wondering if there is a way for me to upgrade without losing my AD settings and stuff previously mentioned. I know that there is simply the upgrade option when installing a new version of Windows, but Microsoft recommends clean installs for their server editions, so I was wondering how I could upgrade through a clean install and not lose data.

Thanks,

Vainsy

 

[ex_bubblehead]

Here's one place to look:

https://www.tactig.com/upgrade-windows-server-2012-windows-server-2016/

However, do not expect "easy" or problem free. The recommendation of a clean install is made for very good reasons.

 

[photonboy]

There's a good chance it will work actually, however I'd still create a backup Image before that with a tool like Acronis True Image should it fail or even succeed but you forgot something you needed.

Updates work a lot better than they did years ago... I believe they MOVE the data for supported folders (not all folders) and settings (but not all settings) to a temporary folder, then it does a CLEAN INSTALL of the OS then moves back the files and modifies the settings.

Chances are this will either work perfectly or work with some settings not applied. Files should be fine in the folders listed to save (no idea which ones) but again that's why you should make a backup image.

If you are missing files you can also browse the Acronis backup using Explorer then simply copy them. You should however write down EXACTLY which settings should be modified, programs are installed, and where the files are to make it easier later.

 

[molletts]

I think if I was doing this, I'd probably start by migrating the existing physical server (I assume that's what it is) to a virtual machine on another box (say, your desktop). That way, I could then carry out a clean install of 2016 on the current hardware, join it to the domain as a second DC (thus getting your AD onto it), migrate all the other services such as DNS & DHCP then decommission the old (virtual) server in an orderly way.

This is fairly advanced server-fu, though, and is by no means free of risk. Good, tested backups are essential.

(This is the approach I had to use to upgrade a 32-bit Server 2008 box to 2012R2 (64-bit only) a few years ago as there was no possibility of an in-place upgrade.)