Hello,
I ran into a strange problem recently. I have an existing Server 2008 R2 server that holds all FSMO roles for the domain. After adding a Server 2008 R2 server to the domain and promoting it to a DC I noticed it did not have the sysvol or netvol volumes shared
out even though it was a freshly promoted DC....
I ran some diagnostics / tests on the DC only to discover that there was a journal wrap error on the PDC. I proceeded to attempt and fix the problem with a "Enable Journal Wrap Automatic Restore" option after working on fixing some of the DNS problems. The next day (~8 hours later) both the primary DC and the secondary DC did not have the sysvol or netlogon volumes available! No users could login, nothing was authenticating; the whole domain was at a stand still.
My only choice was to restore the entire DC to a couple days prior the problems occurance since I could not get ahold of Microsoft Critical response quickly enough to resolve the issue.
Since I reverted the domain back to before I promoted the secondary DC I'm wondering if someone can help me troubleshoot what went wrong or how I might be able to fix a repeat offense of this problem! I can post some of the errors I had discovered at the time for various DCDIAG / DNS tests if needed. Or run some tests if anyone would like to look at what errors are occuring on the DC.
I did try to repair some of these after I promoted the secondary DC to a controller. But the DC is now at the exact state it was before the problem happened.
My question is why would the sysvol / netlogon volumes disappear for this prolonged period of time (8 hours) and not become available again? And what can I do to fix this controller in advance before I make an attempt to join another DC to this domain
and potentially transfer FSMO roles to the new DC? Why would promoting a new DC not have the netlogon and sysvol volumes automatically shared out after promotion completion?
(Setting the "Enable Journal Wrap Automatic Restore" registry parameter to 1 will cause the following recovery steps to be taken to automatically recover from this error state. [1] At the first poll, which will occur in 5 minutes, this computer will be
deleted from the replica set. If you do not want to wait 5 minutes, then run "net stop ntfrs" followed by "net start ntfrs" to restart the File Replication Service. [2] At the poll following the deletion this computer will be re-added to the replica set.
The re-addition will trigger a full tree sync for the replica set. WARNING: During the recovery process data in the replica tree may be unavailable. You should reset the registry parameter described above to 0 to prevent automatic recovery from making the
data unexpectedly unavailable if this error condition occurs again.)
This person ran into a similar problem to this one:
http://www.tek-tips.com/viewthread.cfm?qid=1533492