If you are promoting a new Windows Server server you do not need to run these manually. These are integrated into the PowerShell and Server Manager experiences.
For more information on running adprep see Running Adprep. Windows Server requires a Windows Server forest functional level. That is, before you can add a domain controller that runs Windows Server to an existing Active Directory forest, the forest functional level must be Windows Server or higher.
If the forest contains domain controllers running Windows Server or later but the forest functional level is still Windows , the installation is also blocked. Windows domain controllers must be removed prior to adding Windows Server domain controllers to your forest. In this case, consider the following workflow:. After you set the forest functional level FFL to a certain value, you cannot roll back or lower the forest functional level, with the following exceptions:. After you set the domain functional level to a certain value, you cannot roll back or lower the domain functional level, with the following exceptions:.
AD DS cannot be installed on a server that also runs the following server roles or role services:. This will automatically run adprep on the R2 forest and domain.
In Server Manager , click the yellow triangle, and from the drop-down click Promote the server to a domain controller. On the Deployment Configuration screen, select Add a domain controller to an existing forest and click next. On the Prerequisite Check screen, click install.
Once the restart has completed you can sign back in. You can type the name of each -OperationMasterRole or use numbers to specify the roles. Demote and remove the Windows Server R2 domain controller. For information on demoting a dc, see Demoting Domain Controllers and Domains.
Once the server is demoted and removed you can raise the forest functional and domain functional levels to Windows Server Then run following commands to make sure all DNS records are updated and also no errors are present. After finishing this part you can start migrating the rest of the services you have either to the new DC or separate virtual machines.
The procedure is pretty straightforward. You can easily google each step if more information is required. It would probably be best to build the new server with although if your licensing won't allow will be fine as a member server in the domain. Then promote the new server to a DC. After a suitable interval, you can demote the original and remove from the domain. That's what I feared.. There are some hostsfiles and stuff going on that makes us want to re-use the servername and IP,.
Is the process you mention easy to mess up? If you still hesitate to migrate the domain controller properly, you can just P2V it to new hardware. This is not recommended to say at least, but you may give it a try. The sequence would be similar. If you have other VMs on the old server, migrate them first. It might seem like it, but it's definitely not.
I speak from personal experience. To continue this discussion, please ask a new question. Cloud Help Desk: Delays for ticket imports:. Spiceworks Help Desk. The help desk software for IT. Track users' IT needs, easily, and with only the features you need.
Learn More ». Get answers from your peers along with millions of IT pros who visit Spiceworks. I have a couple of questions regarding this: 1. Will I risk getting errors like "There are currently no logon servers available to service the logon request" from 1 or any other solutions Thanks!
Best Answer. Ghost Chili. Supaplex This person is a verified professional. Verify your account to enable IT peers to see that you are a professional.
