[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1227
  • Last Modified:

SYSVOL not populating on 1 Domain Controller

When looking at 1 of our 3 DC's over the network, the NETLOGON folder is there and replicating correctly. The SYSVOL has the domain.com folder but anything under it is missing.

When looking at it on the server itself, the C:\Windows\SYSVOL\sysvol\domain.com symbolic link is working correctly. NTFS and share permissions seem to be correct. If I follow it, all data is there.

Looking at the symbolic link though shows this on DC1:
C:\>ntfrsutl ds |findstr /i "root stage"
         Root      : c:\winnt\sysvol\domain
         Stage     : c:\winnt\sysvol\staging\domain

Looking at the symbolic link though shows this on DC2 and DC3:
C:\>ntfrsutl ds |findstr /i "root stage"
         Root      : c:\windows\sysvol\domain
         Stage     : c:\windows\sysvol\staging\domain

Is there an easy way to re-point the symbolic links or do I have to go through something like this: http://support.microsoft.com/kb/315457
0
tkmluv
Asked:
tkmluv
  • 4
1 Solution
 
Darius GhassemCommented:
Lets do the burflag method to fix.


Take backup of the policies and script folders from both the servers from c:\Windows\Sysvol\domain
Stopped NTFRS service on both DCs.

Make one of the DC authoritative server by modifying registry setting : Navigate to registry HKLM\System\CCS\Services\NTFRS\Parameters\CumlativeReplicaSets and Set the Burflags value to D4. This should be done with server which has the Updated information available or correct data.

Go to other DC and make that Non-authoritative by navigating to same registry location HKLM\System\CCS\Services\NTFRS\Parameters\CumlativeReplicaSets and Set the Burflags value to D2.
Restart Ntfrs service on both servers and force replication to see event 13516 in event viewer for FRS.
0
 
tkmluvAuthor Commented:
Yea, I am not looking forward to that solution. The only thing is that it appears that everything is replicating correctly. Just the junction point is pointing to c:\winnt\... instead of c:\windows\...

Wouldnt just recreating the junction point be easier and faster?
0
 
kardell2006Commented:
Is the domain function level still AD2000? DC1 is using the old directory. Make sure the server with the correct data is set as authoritative in AD.

In AD there's a tab called NTDS - make sure the authoritative DC is set to replicate to and from the 2 secondary DC's.
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
tkmluvAuthor Commented:
Yes, they are set to replicate. All DC's are Server 2008 and the functional level is 2008.

Like I said before, replication is working just fine. It is just that the SYSVOL\Domain.com folder is empty on DC1.

I am guessing this is the case because the junction point on the c:\windows\sysvol\sysvol\domain.com is pointing to c:\winnt\sysvol\domain instead of c:\windows\sysvol\domain
0
 
tkmluvAuthor Commented:
So....I just deleted the junction point and recreated it and now everything looks fine.

Create Junction point: http://technet.microsoft.com/en-us/library/cc794939(v=ws.10).aspx
0
 
tkmluvAuthor Commented:
All that was wrong was the junction point was pointing to the wrong location. I was hoping for someone who had seen this and could find some instructions but I ended up finding them myself.
0

Featured Post

Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now