I've tried this hotfix: https://support.microsoft.com/en-us/kb/974639
I've tried these steps:
"As a temporary workaround, manually edit the GPTMPL.INF file by adding the NT Service\ prefix in front of the wdiservicehost account name for the Profile System Performance user right in the Default Domain Controllers Policy. This has to be done everytime any security setting in the Default Domain Controllers Policy is administered with GPMC.
This step will prevent the 1202 event from being logged until the next time security policy is modified in the Default Domain Controllers Policy by the relevant operating system versions.
1. Open the GPTTMPL.INF file for the Default Domain Controllers Policy of a domain controller logging the Event ID 1202. The path to the GPTTMPL.INF file when SYSVOL is located below %SystemRoot% is:
2. Locate the SeSystemProfilePrivilege entry in the GPTTMPL.INF and modify it as follows:
Before: SeSystemProfilePrivilege = *S-1-5-32-544,WdiServiceHost
After: SeSystemProfilePrivilege = *S-1-5-32-544,nt service\WdiServiceHost
Note: NT Service\ should appear after the "," delimiter. Do not prefix NT Service\ with the "*" character.
3. Save the changes to GPTTMPL.INF.
4. From a command prompt on the console of the domain controller whose GPTTMPL.INF file was modified in Step 1, type Gpupdate /force"
I tried this: "From the command prompt, type: FIND /I "Cannot find" %SYSTEMROOT%\Security\Logs\winlogon.log"
The error I'm specifically trying to solve is this:
Event 1202, SceCli
"Security policies were propagated with warning. 0x534 : No mapping between account names and security IDs was done.
Advanced help for this problem is available on http://support.microsoft.com. Query for "troubleshooting 1202 events".
Error 0x534 occurs when a user account in one or more Group Policy objects (GPOs) could not be resolved to a SID. This error is possibly caused by a mistyped or deleted user account referenced in either the User Rights or Restricted Groups branch of a GPO. To resolve this event, contact an administrator in the domain to perform the following actions:
1. Identify accounts that could not be resolved to a SID:
From the command prompt, type: FIND /I "Cannot find" %SYSTEMROOT%\Security\Logs\winlogon.log
The string following "Cannot find" in the FIND output identifies the problem account names.
Example: Cannot find JohnDough.
In this case, the SID for username "JohnDough" could not be determined. This most likely occurs because the account was deleted, renamed, or is spelled differently (e.g. "JohnDoe").
2. Use RSoP to identify the specific User Rights, Restricted Groups, and Source GPOs that contain the problem accounts:
a. Start -> Run -> RSoP.msc
b. Review the results for Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment and Computer Configuration\Windows Settings\Security Settings\Local Policies\Restricted Groups for any errors flagged with a red X.
c. For any User Right or Restricted Group marked with a red X, the corresponding GPO that contains the problem policy setting is listed under the column entitled "Source GPO". Note the specific User Rights, Restricted Groups and containing Source GPOs that are generating errors.
3. Remove unresolved accounts from Group Policy
a. Start -> Run -> MMC.EXE
b. From the File menu select "Add/Remove Snap-in..."
c. From the "Add/Remove Snap-in" dialog box select "Add..."
d. In the "Add Standalone Snap-in" dialog box select "Group Policy" and click "Add"
e. In the "Select Group Policy Object" dialog box click the "Browse" button.
f. On the "Browse for a Group Policy Object" dialog box choose the "All" tab
g. For each source GPO identified in step 2, correct the specific User Rights or Restricted Groups that were flagged with a red X in step 2. These User Rights or Restricted Groups can be corrected by removing or correcting any references to the problem accounts that were identified in step 1."
If it's an account that needs to be deleted, that's fine, we have an average employee turnaround here so that's most likely the case.