Here is a bullet point list of the commands to run in order based on the provided text:
On the DC, from an Admin Command Prompt:
rendom /list
Edit the Domainlist.xml file it created to replace all existing domain names with
the new domain name, including the NetBIOS name if it’s changed.
rendom /showforest
rendom /upload
Ensure replication is complete, optionally using
repadmin.exe /syncall /d /e /P /q DomainNamingMaster-HostName
rendom /prepare
rendom /execute
After domain controllers restart, log on using the new domain name.
Restart the pretty much everything twice after all domain controllers are back
online.
Update GPO linkages with the new domain name using gpfixup . If FQDN is changed:
gpfixup /olddns:old-domain.local /newdns:new-domain.com
If NetBIOS name is changed:
gpfixup /oldnb:OLD-NetBIOS /newnb:NEW-NetBIOS
If needed, synchronise group policy changes with repadmin.exe /syncall /d /e /P /q DC-HostName NewDomainDN
Rename domain controllers with netdom commands:
netdom computername old.computer.name /add:new.computer.name
followed by
netdom computername old.computer.name /makeprimary:new.computer.name
Reboot domain controllers.
Reboot all domain member computers, workstations, and servers twice.
If using domain-based DFS namespaces, update any orphaned paths.
Run rendom /clean to clean up old domain references and unfreeze the forest
configuration.
rendom /clean
Open DNS Manager create the new zone, reboot and after you can delete the old domain DNS zone.
Remove the Active Directory Domain Services role from Control Station if
applicable.
The domain rename process is complex and can have far-reaching effects on your
network. It should not be undertaken lightly and requires thorough planning and
testing.
No comments:
Post a Comment