Event ID1000 and Event ID 1202 Messages Are Reported When You Set Security on the File Replication Service by Using Group Policy

If you configure the Startup mode and security settings on the File Replication service (FRS) through Group Policy, the following error messages may be logged in the Application event log in Event Viewer: If you enable Security Configuration Client logging (which produces the Winlogon.log file), the following error message is logged in Winlogon.log:

This issue occurs because of the locked-down security that was originally set on the FRS through Group Policy. When you attempt to configure the FRS through Group Policy, the policy engine no longer has the permission to set security on the FRS and does not attempt to take ownership of the FRS.

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:
To reset security on the FRS:

1. Navigate to the following policy in the Group Policy object (GPO) where security has been set on the FRS:
   Computer Configuration\Windows Settings\Security Settings\System Services
2. Right-click File Replication Service and click Security.
3. Give the System and Administrators groups Full Control permissions.
4. Verify that the edited policy has been replicated to all domain controllers.
5. Start Registry Editor (Regedt32.exe).
6. Locate and click the following registry key:
   HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\NTFRS
7. Delete the Security subkey.
8. Restart the computer.

To confirm that the security policy has been successfully applied, check for consecutive "Event ID 1704" messages in the Application event log.

This issue may also occur when you attempt to configure other computer services.