[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
?
Solved

SYSVOL not populating on 1 Domain Controller

Posted on 2012-03-21
6
Medium Priority
?
1,217 Views
Last Modified: 2012-03-27
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
Comment
Question by:tkmluv
  • 4
6 Comments
 
LVL 59

Expert Comment

by:Darius Ghassem
ID: 37747626
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
 

Author Comment

by:tkmluv
ID: 37752157
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
 
LVL 5

Expert Comment

by:kardell2006
ID: 37752172
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
Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

 

Author Comment

by:tkmluv
ID: 37752185
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
 

Accepted Solution

by:
tkmluv earned 0 total points
ID: 37752225
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
 

Author Closing Comment

by:tkmluv
ID: 37770362
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

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Uncontrolled local administrators groups within any organization pose a huge security risk. Because these groups are locally managed it becomes difficult to audit and maintain them.
This process allows computer passwords to be managed and secured without using LAPS. This is an improvement on an existing process, enhanced to store password encrypted, instead of clear-text files within SQL
This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
Microsoft Active Directory, the widely used IT infrastructure, is known for its high risk of credential theft. The best way to test your Active Directory’s vulnerabilities to pass-the-ticket, pass-the-hash, privilege escalation, and malware attacks …
Suggested Courses

834 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question