發新話題
打印

FIX FOR FILE REPLICATION SYSTEM (NTFRS) REPLICATION PROBLEMS 13565

FIX FOR FILE REPLICATION SYSTEM (NTFRS) REPLICATION PROBLEMS 13565

http://analogduck.com/main/ntfrs

FIX FOR FILE REPLICATION SYSTEM (NTFRS) REPLICATION PROBLEMS

  |  |  | 

This fix worked for me in resolving an issue where a domain controller was in a death cycle of starting/stopping/restarting the FRS service every few minutes.

Symptoms

If, after you run DCPROMO to add a domain controller to the existing domain, after reboot, you run into a problem where the NETLOGON and SYSVOL shares are not being created and you check the File Replication Service logs in the Event log to find the following error messages:

(Event ID 13549)
The File Replication Service is unable to replicate from a partner computer because the event time associated with the file to be replicated is too far into the future. It is 30 minutes greater than the current time. This can happen if the system time on the partner computer was set incorrectly when the file was created or updated. To preserve the integrity of the replica set this file update will not be performed or propagated further.

The file name is: "[YOUR_PROBLEM_FILE_HERE]"
The connection to the partner computer is:
"DOMAIN SYSTEM VOLUME (SYSVOL SHARE)\NEWDC_NAME\\\PDC_EMULATOR_NAME.domain.com <- \\ PDC_EMULATOR_NAME.domain.com RemoteCxt"

Note: If this time difference is close to a multiple of 60 minutes then it is likely that this file may have been created or updated on the partner computer while the computer was set to the incorrect time zone when its computer time was initially set. Check that the timezone and time are correctly set on the partner computer.

For more information, see Help and Support Center athttp://go.microsoft.com/fwlink/events.asp.

(Event ID 13565)
File Replication Service is initializing the system volume with data from another domain controller. Computer NEWDC_NAME 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.

Resolution

Make sure and keep copies of all the folders and files.

Take these actions to resolve your problem:

On all Active Directory registered domain controllers:

  1. Stop NETLOGON Service
  2. Stop File Replication Service (NTFRS)

On the PDC Emulator:

  1. Rename all files in the %systemroot%\ntfrs folder and subfolders (change their extension to .old).
  2. Give an unlisted account full control of the directory %systemroot%\SYSVOL folder and reset permissions on all child objects.
  3. Change the registry key:
    HKLM\System\CurrentControlSet\Services\ntfrs\paramaters\Backup/Restore\Process at Startup\BurFlags (REG_DWORD) = D4 (The default on this is 0)
  4. Start the NETLOGON Service
  5. Start the NTFRS Service

On all non-PDC emulators:

  1. Change the registry key:
    HKLM\System\CurrentControlSet\Services\ntfrs\paramaters\Backup/Restore\Process at Startup\BurFlags (REG_DWORD) = D2
  2. Start the NETLOGON Service
  3. Start the File Replication Service (NTFRS)

At this point, the system in question should have recreated the SYSVOL share and the NETLOGON share. Check this by running 'net share' from a command prompt. You should also see the Group Policy Objects listed in the SYSVOL directory as:

%systemroot%\SYSVOL\domain_name\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}

%systemroot%\SYSVOL\domain_name\Policies\{6AC1786C-016F-11D2-945F-00C04FB984F9}

There may be more directories listed here, but these are the Default Domain Policy and the Default Domain Controllers Policy that are installed by default when the Active Directory is created. If these are being replicated, then file replication is functioning.

If you cannot find these directories, then you may have to manually recreate them. Here is a list of the proper directory structure of the %systemroot%\SYSVOL folder:

\SYSVOL
________\domain
________________\DO_NOT_REMOVE_NtFrs_PreInstall_Directory
________________\Policies
________________\Scripts
________\scripts
________\staging
________\staging areas
________________\domain_name
________\sysvol (shared as SYSVOL)
________________\domain_name
________________________\DO_NOT_REMOVE_NtFrs_PreInstall_Directory
________________________\Policies
________________________\Scripts (shared as NETLOGON)

If you have to manually recreate the directories, restart the File Replication Service (NTFRS) on all domain controllers to re-enable replication. This should get the file replication functioning normally.

TOP

發新話題