Lost Schema Operations Master

[ramblinrek]

I "lost" my schema operations master a couple of days ago when attempting to use ntdsutil to transfer the schema operations master from one Windows 2000 server (server E) on my WAN to another (server A). There weren't any error messages when I performed the transfer, but as I was attempting to read and make sense of the info generated by ntdsutil, the server that was the original operations master crashed to a debug dump (this server has unexpectedly crashed 3 other times in the past 2 months). I rebooted with no obvious problems, except that now neither server seems to be the schema operations master. Both say "ERROR" for current operations master in the mmc, and that the server is offline.

All other operations master roles have been successfully transferred from E to A, but I need the the schema master functioning properly, as I am preparing to introduce two Windows 2003 servers into my existing network. Should I use ntdsutil and attempt to seize the role at server A, and what precautions should I take before attempting the seizure?

 

[jtb]

This is a good time to bring up the importance of backups...


Having said that,

http://www.microsoft.com/windows200...n/advanced/help/sag_ADrespondFSMOfailures.htm

states: "A domain controller whose schema master role has been seized must never be brought back online."

You may try seizing the role again... but I'd recommend reformat/reinstalling W2K and AD on the formerly dead box and rebooting the new one to see if that helps...

Good hunting!!



JTB
Senior Microsoft Consultant
MCSE-NT4, MCP+I, MCP-W2K, CCNA, CCDA,
CTE, MCIWD, i-Net+, Network+
(MCSE-W2K in progress)

 

[ramblinrek]

Thanks for your reply. Maybe some clarification is needed. Both servers are alive and well and to all appearances are performing normally, except that it seems that the transfer of the schema master role failed so that neither server E nor server A owns that role. Therefore, if server E, which was the original schema master, doesn't think it owns that role any longer, then why should seizing the role by server A cause a conflict?

 

[GlenJohnson]

Had a similar problem. Not exactly the same, but the result was users couldn't log onto the server unless they had the admin password. My solution, replicate all servers. On the bad server, run dcpromo and uninstall ad and make it a stand alone. Replicate all servers again so they know bad server is gone. Run dcpromo on bad server and make it a dc again with ad. Replicate all servers so they all know bad server is back. This fixed the problem. Real pain, but it did the trick. Good luck.

Glen A. Johnson
"Give the laziest man the hardest job and he'll find the easiest way to do it."

Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884