AD Sites and Services: Expand your site, you should see a list of current domain controllers here. Here are some useful articles on these topics: Microsoft: Server , How to demote a DC using Server Manager or Powershell Technet: Server R2 Manually removing a domain controller from AD that was not demoted properly Microsoft Server R2: Manually seizing operations master roles Now to rename the previously domain controller!
Reboot as prompted. Make sure replication completes and your other domain controllers know that the computer name has changed before proceeding. If so, you should see an alert in server manager on the top-right corner. Click it, you will be prompted to promote this server to a domain controller.
Select Role-based or feature-based installation and click Next Select this server and click Next. If prompted to install dependencies such as management tools , say Yes, click Add Features and continue… Skip the features page and click Next Active Directory Domain Services information page displays. Click Next. Confirmation displays. Allow the server to restart automatically if needed. Click Install. Click Close. Give it 20 minutes or so..
When you click it, you will see Additional steps are required to make this machine a domain controller. Follow this link and select promote this server to a domain controller. Verify the correct domain is listed and a domain admin is listed for the credentials and click Next. Domain controller options displays. Enter a directory services restore mode password and make a note of it. DNS options displays: You may get a warning that the delegation for this DNS server cannot be created… that is very normal.
Additional options displays. You should be able to leave Install from media unchecked. Replication from: pick your best domain controller or the one with the best network connection. Prerequisites check: Warnings are normal, especially regarding domain functional level, delegation for DNS, and security. Errors are not normal. Click Install if everything looks OK. The server will reboot.
After reboot, give the server some time to replicate active directory and DNS 30 minutes to an hour. You may want to reboot again for good measure. Remove the secondary DNS server. Test your ability to resolve internal and external DNS ping google. This means a user account that has never logged on to that workstation before. It is normal to see one of these per reboot. If you see many, there is a problem. To rename a DC using netdom commands, perform the following steps: Make a full backup or image of your domain controller!
Open an administrative command prompt on the target DC. I would skip the FQDN unless you have multiple domains in your forest, or your netdom is having trouble resolving the names without it. Check current names listed for this server.. When the server restarts, open an administrative command prompt. Recommended tests can be found in this section: Testing your newly promoted domain controller Netdom references: Technet: Server — how to use netdom to rename a domain controller Spiceworks: Server R2 and — how to use netdom to rename a domain controller Selfish plug time sorry!
I ran the netdom commands in DSR mode and it changed it back to the correct domain. Thanks a lot for your article. It saved my day. September 13, at pm. Abel Munjalu says: Hello, Thanks for above info but once Domain name is grayed out. September 23, at am. John says: Hi. Any suggestions on how I might be able to successfully complete the demotion?
Thanks in advance for any help! December 28, at pm. Amira Armond says: Hi John, You need to solve the netlogon service first. Type the following command to designate the new name as the primary computer name , and then press ENTER key:. After the computer restarts, open a Command Prompt.
At the command prompt, type the following command to remove the old domain controller name , and then press ENTER:. Save my name, email, and website in this browser for the next time I comment.
Renaming domain controller is not an easy process like renaming standalone computer. Derek Schauland explains how you can rename domain controllers in Windows Server Windows Server has several advances over the Windows Server line.
One of these features is the ability to rename a domain controller without demoting and rebuilding the entire server. Many IT pros still say that rebuilding is the best way to accomplish this goal and, in many cases, they are correct.
Rebuilding a domain controller allows you to clean things up and start fresh with the server, whereas renaming the domain controller changes only the name in Active Directory. In some cases, a simple name change will suffice, and a complete server rebuild is overkill. Select the Computer Name tab and click the Change button.
You will see a message telling you that you cannot move a domain controller without demoting it and that you are only changing the name of the domain controller in an existing domain. Click OK to continue. Enter the new host name of the domain controller and click OK. A dialog box will ask you for appropriate credentials to complete the name change. The name change will be complete once the computer restarts.
0コメント