Link to home
Create AccountLog in
Avatar of roywhitmore
roywhitmore

asked on

File Replication Service - ntfrs

Afternoon,

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?
Avatar of CITG_Carl
CITG_Carl

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?

Cheers
Hello roywhitmore,
Try to run Microsoft IT Environment Health Scanner:
http://www.microsoft.com/en-us/download/details.aspx?id=10116 

Regards,
Jarda
Avatar of roywhitmore

ASKER

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
OK, from your main site run the following command:

repadmin /syncall

then

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

Cheers
repadmin /syncall

CALLBACK MESSAGE: SyncAll Finished.
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.
Potentially

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

Cheers
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?
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:
    "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
 
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:
    "DOMAIN SYSTEM VOLUME (SYSVOL SHARE)"
 
    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.
ASKER CERTIFIED SOLUTION
Avatar of roywhitmore
roywhitmore

Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
Avatar of Seth Simmons
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.