Bad DCPROMO

[joelrob]

I have a Windows 2000 server that was DCPROMO'd into a domain controller, then Exchange Server 5.5 was installed and all mailboxes moved over from a dying Win2k server that was the PDC. After removing the dying win2k server, no users were able to log on. After some troubleshooting, I found there was no sysvol or netlogon on the new server. I went through Microsoft's paper for troubleshooting missing sysvol and netlogon with no luck.

Does anyone know a method to manually repair the dcpromo? The microsoft paper says not to share the sysvol and netlogon manually, but I don't know if the mailboxes will be lost or not by dcpromo'ing the server back to a member server and then back up to a domain controller.

Any help is greatly appreciated.

 

[BWilson77080]

im not sure if exchange 5.5 has a setup /disasterrecovery command, and if so whether it does the same thing as exchange 2000, but if i had to go back to a member server and re-promote, id run this afterwards to setup exchange again without changing the configuration

 

[1UnixNewbie]

Joelrob,

Did you ever find a solution to your problem way back in July? I have just experienced the same thing, i think do to the fact that FRS was not running on the PDC when i promoted the 2nd server. Problem is when i demoted and promoted the 2nd server it did not solve the problem.


Any input would be appreciated.

Thanks,

Brad

 

[joelrob]

I did find the solution, after setting up Win2k the first thing I did before even joining it to the domain was to install Symantec Small Business Anti-Virus Server. This was making the DCPromo go bad because it would not allow the SYSVOL and NETLOGON to be created and shared. I disabled Symantec, demoted, shut down, restarted and DCPROMO'd again and it came up fine.