Domain Controller Upgrade

This is well documented on Microsoft’s website.

If you have any specific concerns please let us know.

https://docs.microsoft.com/en-us/windows-server/identity/ad-ds/deploy/upgrade-domain-controllers

Here is a guide for and in place upgrade.

https://www.virtualizationhowto.com/2016/11/upgrade-windows-server-2012-r2-domain-controller-to-windows-server-2016/

I am trying to do the forestprep and domainprep commands but the command prompt window does not recognize the command.  I have the ISO image for Server 2016 on the desktop and initiated installation with it.  How do I successfully execute the forestprep and the domainprep.

Attached is the screenshot of the error
2016upgrade.docx

make Sure you are logged into an account that is a domain admin, schema admin and enterprise  admin.

Run the command prompt with admin priv.

Double check your path. In the command prompt.  It is incorrect.  Should be F:\support\adprep\adprep.exe /forestprep

Also you should burn iso to dvd and install or mount iso to drive in VMware or hyperv if it is a VMachine.  You will reboot at a later point in setup. Not sure if this is necessary but I would not install from an OS mounted iso.  Never tried it.

Please follow the instructions below:

1. From command prompt type: cd F:\support\adprep and press enter
2. Once the command prompt is pointing to F:\support\adprep> type adprep /forestprep

You don't run ADPREP anymore - havent for a while.  It's handled automatically by the DC promotion process.

You don't run ADPREP anymore - havent for a while.  It's handled automatically by the DC promotion process.

Even when you are performing an In place upgrade from 2012>>2016 on a dc?  Seems like the only way that you can.

If you are doing an in-place upgrade of an existing domain controller to the Windows Server 2016 operating system, you will need to run adprep /forestprep and adprep /domainprep manually. Adprep /forestprep needs to be run only once in the forest. Adprep /domainprep needs to be run once in each domain in which you have domain controllers that you are upgrading to Windows Server 2016.

https://docs.microsoft.com/en-us/windows-server/identity/ad-ds/deploy/upgrade-domain-controllers#adprep-and-domainprep

Lee I can tell that you are very passionate about you opinion. Professionals understand that people want choices.  Professionals provide facts not just those that fit their opinion. The Microsoft links clearly state the preferred method. If Eric chose to perform an in place upgrade I am sure he has his reasons.

In place is a viable choice even if it’s not the preferred method.  I was hesitant in 2012 and my preconceptions kept me off the fence.  I’ve done a number of 2016 In place dc upgrades without any real issue.

I used to do/want to do in place upgrades.  20 years ago.   Not anymore.  No OS upgrade can ever be as stable as a clean install. PERIOD.  Why would ANYONE want to INCREASE their risk of issues?  Makes no sense. There can be instances where an upgrade is otherwise "required", but for domain controllers - it's a MULTI-MASTER MODEL!  It's easy to add more and retire old without disrupting the network.

Not interested in the inevitable debate but I do in-place upgrades and have never had any issues. 2008 R2 -> 2012 R2/2012 R2 -> 2016 takes 30min of which 5min is network disruption.

Let's be clear.  I didn't say it was unsupported.  I didn't say you WILL have problems.  I didn't say it takes forever.  I said it can't be as stable as a clean install.  And if you want the most stable system you can have you would be well advised to do a migration to new DCs with new operating systems.

Did the install as a fresh install rather than an upgrade