-
Title
Rule is not applied to all computers -
Description
A new rule is created, and it is applied to some computers but not all of them, also on some computers where the new rule was working it stops working or is not applied, even though validation logic is correct, the rule application follows a random pattern. -
Cause
Among the causes for this behavior, file replication service could be culprit for this issue. There are different ways in which it could be involved:
1) NTFRS morphed folder: When replicating, if file conflicts are found, new folders with policies_NTFRS_3adf000format can be found in under \SYSVOL\domain.name\ location, when only policies folder should be available.
2) Replication has not been done: If the replication is not done, then the new group policy object will not be available in \\DomainController\SYSVOL\domain.name\policies folder comparing the folder with other domain controllers the replication status can be verified.
3) Replication Service is stopped: The File Replication Service is stopped, in most recent Windows version the replication service changed to DFS Replication service, preventing the replication process to be done, it may be checked in Domain Controller's services.
Note: To check which domain controller is providing the policies objects to a computer, a "gpresult /r" command can be issued. To locate the server name look in "Group Policy was applied from" section.
-
Resolution
To solve this issues this steps can be taken:
1) Check for morphed folders and solve the issue or check Active Directory Sites and Services to verify the replication process. For more information about this issue, please refer to the Microsoft KB article (328492) Folder name is changed to "FolderName_NTFRS_".
2) To diagnose the File Replication Service status please refer to the Microsoft KB article (2498185) How To Diagnose Active Directory Replication Failures.
3) To start the File Replication (or DFS Replication) Service please refer to the Microsoft KB article (2498185) How to: Start Services.
If replication was done and the issue persists please refer to knowledge base article How to troubleshoot Privilege Authority (SL3564) and then contact support with retrieved logs.