In the following post you can find information about performing a domain rename:

http://blogs.dirteam.com/blogs/jorge/archive/2005/11/24/154.aspx

 

In addition to that you will find here WHAT a domain rename impacts. As you can see it is NOT something you can underestimate!

A domain rename impacts the following "in some way" (!!!may not be an exclusive list!!!):

  • ALL DCs in the forest (and additionally the DNS names of the DCs in the renamed AD domain)
  • AD replication
  • DNS environment (zones, delegations, suffix search lists, etc.)
  • All places that use the NetBIOS name and/or DNS name of the AD domain that was renamed (think about paths, scheduled jobs, credentials for services, login scripts, batch files, GPOs, GPO configs using DNS pathnames, GPO configs for Primary DNS suffixes, Shortcuts, etc, etc.)
  • Certificate Authorities and certificates
  • Exchange servers in the renamed AD domain
  • Clients/servers in the renamed AD domain
  • Legacy clients/servers (e.g. NT4) in the renamed AD domain
  • Clients that connect through Dial-up/VPN
  • Outlook users with mailboxes on Exchange servers in the AD domain
  • Applications that use application partitions that are a child of the renamed AD domain
  • Trust relationships
  • Domain DFS namespace in the renamed AD domain
  • DFS link/folder targets used in the Domain DFS namespace in the renamed AD domain
  • GPOs and GPO links in the renamed AD domain and GPO links in other AD domains that use GPOs from the renamed AD domain
  • Folder redirection when used with DFS in the renamed domain
  • UPN suffixes for user accounts
  • ???

 

Jorge

-------------------------------------------------------------------------------------------------
* This posting is provided "AS IS" with no warranties and confers no rights!
* Always test before implementing!
-------------------------------------------------------------------------------------------------