Error1001 Source SceCli flooding event logs

Question

Server 2022. All updates current

Body of error:

Security policy cannot be propagated. Cannot access the template. Error code = 2.

\\company.local\sysvol\companylocal\Policies\{31B2F340-016D-11D2-945F-00C04FB984F9}\Machine\Microsoft\Windows NT\SecEdit\GptTmpl.inf.

This file does not exist in that folder. This is the folder for the "default domain policy". the file does exist in all the other policy folder "SecEdit" and they all appear to have the same content:

[Unicode]

Unicode=yes

[Version]

signature="$CHICAGO$"

Revision=1

I tried making a change to the policy to see if it would re-create it. I can't imagine it's as simple as just creating it in an editor or copying it from another policy.

How to proceed to fix this?

Answer 1

Hello

Here's a step-by-step approach to resolve the Error 1001 Source SceCli flooding your event logs on Server 2022:

1.Check the Path and Permissions: Ensure that the path \company.local\sysvol\companylocal\Policies{31B2F340-016D-11D2-945F-00C04FB984F9}\Machine\Microsoft\Windows NT\SecEdit\GptTmpl.inf is correct and accessible. Verify that the necessary permissions are set correctly for the SYSVOL folder and its subdirectories.

2.Recreate the Missing File: Since the file GptTmpl.inf is missing, you can try to recreate it. Copy the GptTmpl.inf file from another policy folder where it exists and paste it into the SecEdit folder of the default domain policy. Ensure the content matches the template you provided:

[Unicode]

Unicode=yes

[Version]

signature="$CHICAGO$"

Revision=1

3.Force Group Policy Update: After recreating the file, force a Group Policy update to propagate the changes. Run the following command on the affected server:

gpupdate /force

4.Check for Replication Issues: Use tools like DCDIAG and the Active Directory Replication Status Tool to check for any replication issues that might be causing the problem. These tools can help diagnose and resolve replication-related errors.

5.Review Event Logs: Look for any other related events in the event logs that might provide additional clues. Sometimes, multiple events can point to the root cause of the issue.

6.Update ADMX Files: If the policy definitions are corrupted, download the latest version of ADMX files for your organization and place them in the SYSVOL folder. This can help resolve issues related to corrupted policy definitions.