There is a major step that is not included in this process. I doubt too many of us have an Active Directory domain with no member computers. If you follow this walk-thru completely, you will end up manually re-adding every workstation and server to the newly renamed domain. Not very efficient. To make this work correctly, you must pause before running "rendom /clean" and reboot all servers and workstations twice. Not power cycle; you must do a restart from the computer itself or "shutdown /restart" remotely. If you execute "rendom /clean" before all the machines in the domain get rebooted twice, they won’t be able to access the domain because "rendom / clean" removes the old domain name from Active Directory, including removing all values of ms-DS-DnsRootAlias from the domain name operations master. When you have rebooted computers that are members of the domain twice, run "rendom /clean" and then "rendom /end".
um, this did not migrate any of the DNS records from the old forwarding lookup zone to the new forwarding lookup zone. The forwarding lookup zone still exists and so do all the entries. Is this expected? How do I migrate these?
I tried this multiple times on a VMWare Window 2019 Server VM. After executing the rendom /execute command, I was unable to log in as Administrator, any other user . I tried both the old and the new domains. I would very much appreciate it if you had any guidance on this, otherwise this video was at best a waste of time.
FIRST HAVE A GOOD TESTED BACKUP OF YOUR DC! -- I just did that procedure, here are my notes: I did wait before the /clean to reboot all my clients (and servers) twice as suggested by @ckdunn12345. DHCP server stopped working for no reason, Service had to be restarted DHCP continued to push the wrong domain DNS suffix, had to change manually the DNS suffix in the DHCP options During migration, some machines were not reachable and had to be either reached trough old scheme, new scheme or plain IP. After first client reboot, they got the new address and worked flawlessly. Rebooting the switches and access points forced every client to re-register trough DHCP, saved a lot of issues.
There is a major step that is not included in this process. I doubt too many of us have an Active Directory domain with no member computers. If you follow this walk-thru completely, you will end up manually re-adding every workstation and server to the newly renamed domain. Not very efficient. To make this work correctly, you must pause before running "rendom /clean" and reboot all servers and workstations twice. Not power cycle; you must do a restart from the computer itself or "shutdown /restart" remotely. If you execute "rendom /clean" before all the machines in the domain get rebooted twice, they won’t be able to access the domain because "rendom / clean" removes the old domain name from Active Directory, including removing all values of ms-DS-DnsRootAlias from the domain name operations master. When you have rebooted computers that are members of the domain twice, run "rendom /clean" and then "rendom /end".
This is exactly what i was worrying about. How about the rest of the procedure. Is it safe to change the name through these steps?
i only wish i knew. people dont follow the vidoe!
Thank you so much, you pretty much saved my SA course project from ending up a total disaster.
I tried it and it didnt work? In powershell it said: failed to upload dns root alias on the dn:
This worked well in my case, a new DC in Azure that hasn't been implemented yet. Thank you.
Hi Rohit. Thanks for the knowledge sharing. Do we need to change all endpoint Primary DNS suffix to a new domain name?
Thank you it worked
When i type the rendom / upload its getting error failed to upload dns root alias on the
um, this did not migrate any of the DNS records from the old forwarding lookup zone to the new forwarding lookup zone. The forwarding lookup zone still exists and so do all the entries. Is this expected? How do I migrate these?
Thank you so much!!
Also make sure you have a local admin user to login with incase you can't login with domain admin.
rendom it is not an internal or external command executable program or batch file what to do?
Does it work on Windows Server 2012 e 2012 R2?
Did anyone try this? Is the 2019 exch server really supporting domain name change?
Don't do it.. remote desktop failed and a lot of services stopped working.
thank you so much for your help
What about old verisons of windows server? can we do that?
thx for that
very helpful!
Thanks!
Welcome!
I tried this multiple times on a VMWare Window 2019 Server VM. After executing the rendom /execute command, I was unable to log in as Administrator, any other user . I tried both the old and the new domains. I would very much appreciate it if you had any guidance on this, otherwise this video was at best a waste of time.
Hey there, did you ever figure this out, same issue I'm having
it does not work
Is there a way to rollback the name change if any issue reported?
Backup first before you do it then you can roll back.
FIRST HAVE A GOOD TESTED BACKUP OF YOUR DC!
--
I just did that procedure, here are my notes:
I did wait before the /clean to reboot all my clients (and servers) twice as suggested by @ckdunn12345.
DHCP server stopped working for no reason, Service had to be restarted
DHCP continued to push the wrong domain DNS suffix, had to change manually the DNS suffix in the DHCP options
During migration, some machines were not reachable and had to be either reached trough old scheme, new scheme or plain IP. After first client reboot, they got the new address and worked flawlessly.
Rebooting the switches and access points forced every client to re-register trough DHCP, saved a lot of issues.
It's very helpful