aptnetworks
asked on
Missing SYSVOL and NETLOGON shares
We added a second domain controller, but before the SYSVOL and NETLOGON shares could be scanned and replicated, the original DC was deleted with the Active Directory Users and Computers GUI tool. So now while the SYSVOL and NETLOGON directories exist on the new server, they are not shared out and will not replicate with NTFRS. When I look in ADSIEdit.msc there are no null server references I can find. Also the FSMO transition (seizure) has been performed since the plan is to take the old DC out of service. But for right now, if the old DC is powered down, then users cannot logon to the new DC since it has no SYSVOL or NETLOGON shares. I tried to transfer the files and share them manually, but when the new DC was rebooted, it removed the shares and emptied the directories (I assumed as it tried to set them up to replicate?) I saw a work-around on the MS site that said I can turn off NTFRS and manually move the files over and share the directories but I don't want this long term so I haven't tried it yet.
First event ID is 13566:
File Replication Service is scanning the data in the system volume. Computer UNDERCR-PEBKAM2 cannot become a domain controller until this process is complete. The system volume will then be shared as SYSVOL.
To check for the SYSVOL share, at the command prompt, type:
net share
When File Replication Service completes the scanning process, the SYSVOL share will appear.
The initialization of the system volume can take some time. The time is dependent on the amount of data in the system volume.
Sure enough there is no SYSVOL share as I've stated, next error in event viewer is 13562 but it has no usable information in it:
***********************
HELP!!!!!!!!!!!!!!
************************
Following is the summary of warnings and errors encountered by File Replication Service while polling the Domain Controller undercr-pebkam2.UNDERCROFT
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
First event ID is 13566:
File Replication Service is scanning the data in the system volume. Computer UNDERCR-PEBKAM2 cannot become a domain controller until this process is complete. The system volume will then be shared as SYSVOL.
To check for the SYSVOL share, at the command prompt, type:
net share
When File Replication Service completes the scanning process, the SYSVOL share will appear.
The initialization of the system volume can take some time. The time is dependent on the amount of data in the system volume.
Sure enough there is no SYSVOL share as I've stated, next error in event viewer is 13562 but it has no usable information in it:
***********************
HELP!!!!!!!!!!!!!!
************************
Following is the summary of warnings and errors encountered by File Replication Service while polling the Domain Controller undercr-pebkam2.UNDERCROFT
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Also see following KBs for troubleshooting missing sysvol and netlogon
http://support.microsoft.com/kb/257338
http://support.microsoft.com/kb/316790 - describes howto set burflags as ChiefIT suggested.
http://support.microsoft.com/kb/257338
http://support.microsoft.com/kb/316790 - describes howto set burflags as ChiefIT suggested.
ChiefIT should receive the points
You shouldnt seize roles - is that what you did?
You need to transfer the roles to the new machine
I woudl then rebuild the sysvol and netlog on the new machine
http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B315457
Then let the machines replicate