When you start a server that is running Windows Server 2008 R2, the File Replication Service (FRS) does not start and the following error is logged in the FRS event log:
Log Name: File Replication Service
Date: 1/6/2009 11:12:45 AM
Event ID: 13574
Task Category: None
Computer: Server_name Description:
The File Replication Service has detected that this server is not a domain controller. Use of the File Replication Service for replication of non-SYSVOL content sets has been deprecated and therefore, the service has been stopped. The DFS Replication service is recommended for replication of folders, the SYSVOL share on domain controllers and DFS link targets.
Note In this error, the placeholder Server_name represents the name of the server on which FRS did not start.
This problem occurs because of a code defect that occurs when you upgrade a server that was running Windows Server 2008 Service Pack 2 (SP2) or Windows Server 2003 Service Pack 2 (SP2) to Windows Server 2008 R2. The FRS component is not removed during server upgrades.
Windows Server 2008 R2 deprecates the legacy FRS component on member servers. When you upgrade servers to Windows Server 2008 R2, you find that the upgrade process does not completely remove the FRS component.
On servers that are upgraded from Windows Server 2003 SP2, the following events occur:
The FRS service is removed.
The FRS event log is not removed, but the event log is cleared.
On servers that are upgraded from Windows Server 2008 SP2, the following events occur:
The FRS service is not removed or stopped.
At every restart of the server, an error is logged in the FRS event log.
Note Although an in-place upgrade is supported, it’s recommended that a server is loaded with a clean install of the OS.
To work around this issue, use one of the following workarounds.
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base: