Security policies were propagated with warning. 0x534 : No mapping between account names and security IDs was done.

I have just installed a new Domain Controller running windows Server 2012 R2, I am getting plagued by Event 1202 warnings Security policies were propagated with warning. 0x534 : No mapping between account names and security IDs was done
I have identified the account causing the issue, its SQLAgent$SQLEXPRESS. The problem is this is an account that was on the old server and no longer exists on the new one as we don’t have this instance of SQL.

In RSOP its showing as been used in

Adjust memory quotas for process
Bypass traverse checking
Replace a process level token

But when I look in the local security police it’s not in any of these, I have tried installing that instance of SQL and removing it but I am still getting the warning every few minutes
miller75Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Walter PadrónCommented:
You must check in your local policies User Rights Assignment at Administrative Tools / Local Security Policy / Local Policies  and manually remove the deleted account.

Best regards
miller75Author Commented:
I have looked though all the Local Security Policy's and SQLAgent$SQLEXPRESS doesn't appear in any. There are a lot of entries begining with S-1-5-80- and a long string of numbers , could it be one of these?
Thanks
Walter PadrónCommented:
When an account or group is deleted the object no longer exists thats why you see the UID.
And yes is one of these.

Also check all GPO's until you deleted all unknown references.

Best regards
The 7 Worst Nightmares of a Sysadmin

Fear not! To defend your business’ IT systems we’re going to shine a light on the seven most sinister terrors that haunt sysadmins. That way you can be sure there’s nothing in your stack waiting to go bump in the night.

miller75Author Commented:
Is there any way to identify which
miller75Author Commented:
I have checked the entries with psgetsid and they don't relate to SQLAgent$SQLEXPRESS
Walter PadrónCommented:
You don't have any way to identify which one because these user objects don't exist anymore

Every time you find and UID (S-x-xxxxx...), check it with psgetsid if no valid account is returned then you can safely delete the UID from your GPO policy. Some times you found the name and not the UID, also check the security filter section of your GPO

Check the Default  Domain Policy and the Default Domain Controllers Policy probably you find the offending account there.

Best regards

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
miller75Author Commented:
Spot on, it was in the Default Domain Controllers Policy

Thanks
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2012

From novice to tech pro — start learning today.