Solved

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

Posted on 2016-08-17
4
41 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

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

This script can help you clean up your user profile database by comparing profiles to Active Directory users in a particular OU, and removing the profiles that don't match.
This article explains the steps required to use the default Photos screensaver to display branding/corporate images
This tutorial will walk an individual through locating and launching the BEUtility application and how to execute it on the appropriate database. Log onto the server running the Backup Exec database. In a larger environment, this would generally be …
This tutorial will give a short introduction and overview of Backup Exec 2012 and how to navigate and perform basic functions. Click on the Backup Exec button in the upper left corner. From here, are global settings for the application such as conne…

821 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