Home > IT Answers > Exchange > Exchange 2000 crashes after demoting last Act...
aa9922
0 pts.
 Exchange 2000 crashes after demoting last Active Directory 2000 domain controller
Exchange 2000, Active Directory
I recently installed 2 new domain controllers running on Windows Server 2003 to replace 2 old DCs running W2K. After running ADPrep /forestprep on the schema master and ADprep /domainprep on the Infra master, I installed AD on the 2 W2K3 servers. I then transferred all FSMO roles to the 2 new DCs, including global catalog. I uninstalled AD on one W2K DC and retained it as DSN and WINS server. Waited a day and no hiccups. After uninstalling AD on the second W2K DC, my Exchange 2000 server (member server) stopped responding. I rebooted the Exchange box and services will not start.

I immediately re-installed AD on the old box and everything was fine again. How can I remove the old W2K DC without crashing Exchange 2000? We want to raise domain functional level to 2003 and we can't do that with W2K DC still running.

Thank you in advance.

Armando Alorro
ASKED: May 10, 2005  4:30 PM GMT
UPDATED: May 13, 2005  4:38:04 AM GMT
RELATED QUESTIONS
wdorciak
0 pts.
Answer Wiki:
Did you also transfer Global catalog server role?

Look in the Exchange server event log, it should give you some indication why it stopped responding?
Last Wiki Answer Submitted:  May 10, 2005  5:02 PM (GMT)  by  wdorciak   0 pts.
To see other answers submitted to the Answer Wiki View Answer History.
RSS - Discussions Help
Discuss This Question:
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _



 

Actually, this is likely to be a known Microsoft issue:

http://support.microsoft.com/default.aspx?scid=kb;en-us;314649

There are a subset of the AD attributes for Exchange in the AD that get mangaled when the upgrade is executed. In the above metioned document is a way to check the status of the attributes.

PaulieEddie
 0 pts.
 

Yes, I transferred the global catalog role to the 2 new DCs running W2K3. No other roles are present in the W2K DC, except DNS and WINS.

Regards.

aa9922
 0 pts.
 

I ran the ldifde with all the parameters mentioned before running adprep. To be sure I checked any mangled attributes, I ran ldp utility, as described in the Microsoft KB, to check for dup* entries in the ldap and everything checked out fine.

Thanks.

aa9922
 0 pts.
 

By default, Exchange installed on a DC/GC will look to itself for all AD info. This becomes an issue if you demote the server back to a member server.

Before you demote the server, run Exchange System Manager, locate your Exchange server, and right-click=>properties. Check out the settings on the “Directory Access” tab and change as required. Now you should be able to demote the server.

Good luck..

ColinNZ
 0 pts.
 

Ooops… I forgot to mention…
There are some functions (5 FSMO Roles) that by default exist ONLY on the 1st AD controller that existed in your org - presumably one of the 2K DC’s that you are demoting.

This should have nothing to do with your Exchange problem - however you should check out MS KB article Q255690 for details of shifting the roles of:

Domain naming Master
Schema Master
RID Master
PDC Emulator
Infrastructure Master.

Regards

Colin

ColinNZ
 0 pts.