Problem joining/adding rebuilt 2000 Server to 2003 Server with Active Directory-Integrated DNS.

I have a Windows 2000 Server box that runs exchange and went down and a new 2003 Server box w/ Terminal Services Server installed. I managed to get the 2000 Server box back up and setup and successfully got the the DNS server to replicate,the Active Directory to replicate(after running adprep with the /forestprep and /domainprep switches), and have managed to get the FSMO roles to transfer to the 2003 box. I setup the old Windows 2000 Server box as a GC. This is where the issue begins. The Windows 2000 Server OS has crapped out. So, on a different hard drive in the same 2000 box, I have reinstalled 2000 server, but the second I take the old OS offline to switch to the OS I've rebuilt, the clients can no longer find the domain which is on the 2003 Server box! I think it's DNS related, but then again...I don' know. If I open up the DNS server and AD in the 2003 server, they're both there. Also, the 2003 Server is the DHCP server too. I cannot get the DNS server to replicate onto the new Windows 2000 install and manually setting it up isn't fixing the problem either! Without being able to find the domain, I can't pull AD back over to make it a GC again! My question is, If I run dcpromo on the 2000 box/drive that is the GC and demote it, will that help fix my problem so I can take it offline and have the 2003 box as the PDC in order to replicate onto the new box and have the ability for the clients to see the domain by itself? Or will this hose my hole domain?
KionysusAsked:
Who is Participating?
 
SembeeConnect With a Mentor Commented:
You cannot just shutdown the old domain controller. You need to remove it correctly.
Run DCPROMO to demote the machine to a member controller. When it prompts to reboot, let it reboot in to the old installation. This will complete the process. Wait a little while for the domain to update. Finally drop the old machine in to a workgroup so that the machine is no longer part of the domain.

The clients will get upset with the domain controller going. Therefore you shoudl really do this at the end of the day so that when the clients come online the next morning they will attach to the new domain controller.

If you haven't already, make the other machine a global catalog. You can have more than one and in small environments it is a good idea to have two.

That should get you started. If you are having more problems, please post back.

Simon.
0
 
KionysusAuthor Commented:
I guess I'm just worried that after I DCPROMO the old server it won't take on the new one and at that point I'll have hosed the entire AD strutcture. Is this possible? No, the 2003 server isn't a GC, but I read today taht I should have both of them as GC's.
0
 
SembeeCommented:
Have you DCPROMO the new server in? If so, make it a GC. The DCPROMO process will fail if the other server isn't in a position to take on the roles.

Simon.
0
 
KionysusAuthor Commented:
I have DCPROMO'd the new server. I had to run ADPREP on it with two commandline switches first. But it isn't a GC. I manually transferred all 5 roles over to the 2003(new) server. What part of the DCPROMO process will fail? Are you telling me there are safeguards in place that won't let it hose itself?
0
 
SembeeCommented:
Make it a GC. That is very easy (enabling a box in AD).
When the DCPROMO process is going, if it it cannot find another server to replicate the settings to then it will fail.

Simon.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.