• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 14484
  • Last Modified:

Is there any way to force replication of SYSVOL without danger?

Greetings -

Is there a low risk way to force replication of the SYSVOL folder (which I believe FRS handles) with low risk?  For instance, I can force AD replication using repadmin /syncall, but I know that doesn't replicate SYSVOL at the same time.

I'm curious if there's a way to do this... thanks!
  • 2
  • 2
1 Solution

Let's get an Idea of where you are at. Please go to the FRS event viewer logs and post any errors that are in the 13000's.

Now, I need to know what server you are fixing the Sysvol on> is it the PDCe or just another server.

To fix your sysvol records, use the burflag method outlined in this article:
For the PDCe, you want to do an authoritative restore (D4)
For any other DC, do a (D2) restore

((((((PLEASE NOTE: The inability to replicate FRS is most likely a DNS problem. Please run DCdiag and look in event logs for DNS error in the 4000's. ))))))))))
amendalaAuthor Commented:
Chief -

I'm not trying to fix anything that's damaged.  Everything is working just fine, there are no AD replication issues whatsoever.

What I am curious about is - if I ever have to make a rapid change to a script that I want to replicate more rapidly than the FRS delay, is there a way to do that?
To force replicate, and save yourself time:
a) go to the Active Directory Sites and Services Snapin
b) navigate to Default First Site>>Servers
c)Pick the server you want to replicate TO and expand it
d)right click what is showing (NTDS site?) and select "replicate now"
amendalaAuthor Commented:
Unfortunately, that does not force an FRS replication cycle.  It forces AD to replication its core NCs and policies but does not force an FRS replication.
This KB article references the "ntfrsutl forcerepl" command, which is apparently not well documented, as I couldn't find much about it anywhere else (scroll down about halfway):

Looks like the hotfix was released before 2003 SP1, so unless the command has been deprecated by a later fix or service pack, it should still be there.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

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.

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