I already have a domain controller running fine but had added a second Windows 2003 server as a backup. I had initiated the promotion of this second server as a "new domain on an existing forest". but due to corrupt files and OS, I plan to rebuild. But before I do so, how do I gracefully demote this server so that I can rebuild the server with different host name and then join the domain.
My mistake:
That error of DNS loading before AD was event ID 4004 and 4015 events. This is caused because the DNS service started before AD upon boot, not installation.
http://www.experts-exchange.com/Networking/Protocols/DNS/Q_22901131.html
After promoting it, you may run into not being able to communicate between servers and replicate between them. If this happens, you might need to register your DNS address with Server B after promoting it. Then force replicate that Host A record to the other Server. What causes this is the servers don't have a Host A record registered in DNS. So, they don't communicate between eachother because DNS does not make the name translation. A DCdiag report on Server B after promoting it will be a dead give away on this problem. You should see something like DCgetDCname error within the DCdiag test. If you see this, stop netlogon, type ipconfig /register DNS, start netlogon then force replicate as shown below. Or you can type dcdiag /fix:DNS and replicate that DNS record to the Server A.
I think you are ready to promote this machine back into the domain and replicate the AD database
FROM server A TO server B.
After all is said and done, you should be able to communicate and replicate with two clean DCdiag reports.
How to force replicate:
http://www.windowsitpro.com/Articles/ArticleID/13396/13396.html?Ad=1plicate:
No comments:
Post a Comment