I am migrating from an old SBS2003 environment to a virtual 2003 Standard Server environment. The SBS2003 server has already been demoted and removed from the network, leaving only a stand alone EXCHANGE server/DC for authentication. I created 2 new virtual Windows Server 2003 servers (DC1 & DC2), DCPROMO'd both of them. Both DC1 and DC2 showed errors in their event logs referencing problems with SYSVOL replication, and saying that they would not be fully promoted until SYSVOL was properly replicated.
Further investigation revealed that NTFRS on EXCHANGE was in an error state due to a recent disaster recovery. Had to create file "NTFRS_CMD_FILE_MOVE_ROOT"
and restart NTFRS in order to repair. Since DC1 and DC2 are also waiting for SYSVOL replication, there were no other fully promoted DC's on the network (my bad) so there are no replication partners, and now EXCHANGE is also not acting as a DC. As a result, no domain controllers are availalbe to answer domain requests, no GC servers, etc.
I have tried the SYSVOL rebuild methods (D4 and D2) outlined in the article:
And it does not appear to have remedied anything. There are still no SYSVOL or NETLOGON shares, and I'm continuing to receive event ID 13508, "The File Replication Service is having trouble enabling replication from EXCHANGE to DC1 for c:\windows\sysvol\domain using the DNS name EXCHANGE.domain.com. FRS will keep retrying."
I'm currently working on a new virtual network that mimics our current environment and hopefully we can move into that new environment soon, but in the meantime I have a very unstable network. Any help is appreciated.