AD Problems after Domain Rename
Posted on 2007-08-03
I've been doing a few dry runs of a domain rename operation on some lab servers over the past week or so. After the latest operation, I started a new domain rename operation on the same domain following the same steps I've used before as list in the "Windows Server 2003: Step-by-Step Guide to Implementing Domain Rename" guide. There is a step that requires you to confirm the server that holds one of the FSMO roles using DSQUERY. When I run this command from the control station (a Windows Server 2003 machine that is NOT a domain controller, but is a member of the domain) it will not return any results and will not finish the command. I have removed the control station from the domain and added back to the domain, with the same results when I run the DSQUERY command.
I have been retrying the domain rename operation as we have been having issues with AD user logon domains not being properly updated during the operation. With the DSQUERY issue we are now having on top of the previous issue, I'm beginning to think that there are larger problems in Active Directory from the domain rename process.
I've been following each step in the guide as directed. The domain controller is running DHCP, DNS, WINS and AD.
Considering the two problems I'm now faced with after the domain rename operation, is there a way to tell which part of the operation is failing/causing these problems? I need to find a way to make this operation work properly.