Getting error on almost all servers "Security policies were propagated with warning. 0x534 . ."

Daniel Checksum
Daniel Checksum used Ask the Experts™
on
About 70% of my servers are getting these error messages logged.  I've run the "hotfix" listed for the domain controller - which said it wasn't compatible with Server 2008 R2 and I ran the "temporary workaround" -- neither of which resolved this issue.  What is causing it?  How do I make it stop?

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".
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Have you read the following E.E post to see if it help...

https://www.experts-exchange.com/questions/28571051/Security-policies-were-propagated-with-warning-0x534-No-mapping-between-account-names-and-security-IDs-was-done.html

Sounds like your have an orphan use SID in one of your GP's..

Author

Commented:
Ironically my supervisor just asked me about this project again.  Yes, I tried the hotfix and the "workaround" -- neither of which worked.  I'm trying to "delete the old SID" but . . .I don't understand the syntax of psgetsid I entered "psgetsid /SID S-1-5-#######etc"  and it didn't do anything.  

How am I supposed to find out which account this SID belongs to?
cross posted on my SID question:

That error is appearing on every server except for our domain controller and the new exchange server.  It's appearing on our:

appserver, print-related server, intranet server, all 3 backup servers(servers used for backing up, working on a migration), Old exchange(migration 99% complete), File server, document management server, indexer for DMS, storage for DMS, print server, and terminal server.  

These are the results from our app server:

C:\Windows\system32>FIND /I "Cannot Find" %SYSTEMROOT%\Security\Logs\winlogon.lo
g

---------- C:\WINDOWS\SECURITY\LOGS\WINLOGON.LOG
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal.
        Cannot find terminal

Same results on one of the backup servers, file server, and even the "new" exchange server.(Server 2012 running Exchange 2013)

Yes, each of these was on an elevated command prompt.  

When I ran the command on the DC I got:

C:\>FIND /I "Cannot find" %SYSTEMROOT%\Security\Logs\winlogon.log

---------- C:\WINDOWS\SECURITY\LOGS\WINLOGON.LOG

Author

Commented:
I was able to resolve this issue on another experts-exchange question and have resolved the errors.

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial