Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

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

File Replication Service - ntfrs


I've had an issue with a domain controller in that the netlogon share has become out of date.  I've forced a replication and by editing the BurFlags to D2.  This unshares the %netlogon% folder and starts replication.  After an hour or so I check the %netlogon% folder has been shared again but with old contents.  
I check the
C:\Windows\SYSVOL\sysvol\mydomain\DO_NOT_REMOVE_NtFrs_PreInstall_Directory\NTFRS_31******* folder and it's up-to-date the same as all the other DC netlogon folders.

I've  dropped a text file onto another DC with today's date to test replication all the other DCs get this update/file but the problem DC in question doesn't. However I look in the C:\Windows\SYSVOL\sysvol\mydomain\DO_NOT_REMOVE_NtFrs_PreInstall_Directory\NTFRS_31******* folder and it's there.

Can anybody help please?
1 Solution
Can you answer the following?

How many domain controllers do you have on your site.
How many different sites do you have in your organization?
Do you have sites and services correctly configured?
What operating system is your domain controllers running?

Jaroslav LatalMSPCommented:
Hello roywhitmore,
Try to run Microsoft IT Environment Health Scanner:

roywhitmoreAuthor Commented:
32 Domain controllers - 2 at HQ
31 Sites - DC at each - all 31 DCs replicate with test file I meantioned earlier.
Yes - Sites and services configured to replicate 4 times per hour each Subnet config and in the site in question it has 2 two DCs on HQ and another site in the NTDS Settings as per all the other sites/DCs
All DCs at Sites are Windows Server 2008 - SP1
DCs at HQ is one Server 2000 and one Windows Server 2008 -SP1
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

OK, from your main site run the following command:

repadmin /syncall


repadmin /replsummary

Do you get any replication errors relating to any specific domain controllers?

What operating systems are you using? Windows server 2003/2008/2008 R2/2012

roywhitmoreAuthor Commented:
repadmin /syncall

SyncAll terminated with no errors.

repadmin /replsummary
Source DSA          largest delta    fails/total %%   error
No errors

Destination DSA   largest delta    fails/total %%   error
No Errors

OS: Windows Server 2008 on all DCs except 1 at HQ which is 2000

no replication errors on even on the DC at the site that is not complete.
On that server the
C:\Windows\SYSVOL\sysvol\mydomain\DO_NOT_REMOVE_NtFrs_PreInstall_Directory\NTFRS_31******* .  folder is all up to date.

I'm suspecting it could be the Jet database.

Are you just having file replication issues in the SYSVOL folder, or are you having any issues with user accounts, password changes etc?

roywhitmoreAuthor Commented:
No other issues just the file replication issue on the SYSVOL folder of that site DC.
Even when I run the repadmin tools on the DC with the Netlogon share issue it too reports no errors.
Anything in the event log of said server?
roywhitmoreAuthor Commented:
No, I've kicked of the Blur Flags process (also I tried a different method which does effectively the same thing.

The Eventlog when I kicked it off said:

File Replication Service is initializing the system volume with data from another domain controller. Computer ***-SRV 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 initialization 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, the availability of other domain controllers, and the replication interval between domain controllers.

Then at the same time it said
The File Replication Service moved the preexisting files in c:\windows\sysvol\domain to c:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog.
The File Replication Service may delete the files in c:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog at any time. Files can be saved from deletion by copying them out of c:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog. Copying the files into c:\windows\sysvol\domain may lead to name conflicts if the files already exist on some other replicating partner.
In some cases, the File Replication Service may copy a file from c:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog into c:\windows\sysvol\domain instead of replicating the file from some other replicating partner.
Space can be recovered at any time by deleting the files in c:\windows\sysvol\domain\NtFrs_PreExisting___See_EventLog.

The File Replication Service successfully added this computer to the following replica set:
Information related to this event is shown below:
Computer DNS name is "***-SRV.mydomain"
Replica set member name is "***-SRV"
Replica set root path is "c:\windows\sysvol\domain"
Replica staging directory path is "c:\windows\sysvol\staging\domain"
Replica working directory path is "c:\windows\ntfrs\jet"

More messages:
The File Replication Service successfully added the connections shown below to the replica set:
    Outbound to    "***DC01-SRV.mydomain.co.uk"
    Inbound from    "***DC02-SRV.mydomain.co.uk"
    Inbound from    "***DC01-SRV.mydomain.co.uk"
Final Message was
The File Replication Service is no longer preventing the computer ***-SRV from becoming a domain controller. The system volume has been successfully initialized and the Netlogon service has been notified that the system volume is now ready to be shared as SYSVOL.
Type "net share" to check for the SYSVOL share.
roywhitmoreAuthor Commented:
Thought I share the solution.  After modifiy the registry by setting the BurFlags to D2 all replication happened as expected.  However I read a technet article about FRS during the Domain controller promotion process.  I noticed that it states that when the server reboots and becomes a DC for the first time this is when the netlogon share becomes active.  So I rebooted the server this morning and the Netlogon area of said server is now populated with the correct contents the DO_NOT_REMOVE_NtFrs_PreInstall_Directory and that folder is now empty.  So all is good.  Thanks for those that took the time to respond.
Seth SimmonsSr. Systems AdministratorCommented:
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.

Featured Post

Efficient way to get backups off site to Azure

This user guide provides instructions on how to deploy and configure both a StoneFly Scale Out NAS Enterprise Cloud Drive virtual machine and Veeam Cloud Connect in the Microsoft Azure Cloud.

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