Solved

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

Posted on 2016-08-17
4
24 Views
Last Modified: 2016-08-28
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".
0
Comment
Question by:Daniel Checksum
  • 3
4 Comments
 
LVL 19

Assisted Solution

by:compdigit44
compdigit44 earned 500 total points
ID: 41761668
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..
0
 
LVL 1

Author Comment

by:Daniel Checksum
ID: 41761682
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?
0
 
LVL 1

Accepted Solution

by:
Daniel Checksum earned 0 total points
ID: 41766965
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
0
 
LVL 1

Author Closing Comment

by:Daniel Checksum
ID: 41773585
I was able to resolve this issue on another experts-exchange question and have resolved the errors.
0

Join & Write a Comment

New Windows 7 Installations take days for Windows-Updates to show up and install. This can easily be fixed. I have finally decided to write an article because this seems to get asked several times a day lately. This Article and the Links apply to…
The recent Microsoft changes on update philosophy for Windows pre-10 and their impact on existing WSUS implementations.
This tutorial will walk an individual through locating and launching the BEUtility application to properly change the service account username and\or password in situation where it may be necessary or where the password has been inadvertently change…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…

757 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

21 Experts available now in Live!

Get 1:1 Help Now