Red X on a GPO in RSOP

I am noticing when I run rsop.lmsc I get warning symbols for Computer and  User section.

When I go to "Properties" to see what's going on and click on Computer Properties, I show this first initial message in the tab:

comp props
I went further into RSOP.MSC to Computer Configuration\Windows Settings\Security Settings\Local Policies\User Rights Assignment and saw a red X on Log on as a service GPO.
Log on as a service
I'm not sure what is causing the error or how to trace from there.

I'm also showing red X's in many other GPOs but there aren't any explanations as to why or how to resolve.
garryshapeAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
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.

JohnBusiness Consultant (Owner)Commented:
Have you installed the snap-in properly?

https://support.microsoft.com/en-ca/kb/323276

And are you using Server 2008 or 2008 R2?

(I just ran it in Windows 8 and only have Server 2012 at my disposal).
garryshapeAuthor Commented:
it is 2008 r2 I'm running rsop from Windows 7 on my local system
JohnBusiness Consultant (Owner)Commented:
Did you install the Microsoft Administration Tools for Server 2008 on your Windows 7 machine?

Here is a link to the tools

https://www.microsoft.com/en-us/download/details.aspx?id=7887
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

garryshapeAuthor Commented:
I think so, I tried to download and install just now and got:
Update for Windows (KB958830) is already installed on this computer.
JohnBusiness Consultant (Owner)Commented:
Follow the article above all the way down.

1. You can only have one copy of SAT on the computer at one time. Perhaps uninstall the package, restart and install the current download again.

2. You need to enable the feature you want in Windows Features (in Programs and Features).
garryshapeAuthor Commented:
I already have RSAT tools installed and the feature enabled
JohnBusiness Consultant (Owner)Commented:
I am not sure why they do not work. Have you tried RSOP directory on the server?
JohnBusiness Consultant (Owner)Commented:
You ARE using Windows 7 Pro or higher ?   Yes?   And you used the x86 or x64 install package for your system?
garryshapeAuthor Commented:
Yes I have all the tools that come from the RSAT install/features. Have Group Policy Management, Active Directory, all that stuff.
The issue I have here is tracing GPO issues that I am finding via rsop.msc
JohnBusiness Consultant (Owner)Commented:
There is a Hotfix available for this issue

https://support.microsoft.com/en-us/kb/2575866

Here is a general article on avoiding conflicts with GPO

http://www.techrepublic.com/article/solutionbase-check-group-policy-assignment-with-rsop/5165777/

Here is an EE Solution (although older and for Server 2003)

http://www.experts-exchange.com/Security/Misc/Q_21982476.html

Please let us know. Thanks
garryshapeAuthor Commented:
The event log has a corresponding error:

Log Name:      Application
Source:        SceCli
Date:          6/20/2015 9:31:47 PM
Event ID:      1202
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      PC0477.domain.com
Description:
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.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="SceCli" />
    <EventID Qualifiers="32768">1202</EventID>
    <Level>3</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2015-06-21T02:31:47.000000000Z" />
    <EventRecordID>36663</EventRecordID>
    <Channel>Application</Channel>
    <Computer>PC0477.domain.com</Computer>
    <Security />
  </System>
  <EventData>
    <Data>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 -&gt; Run -&gt; 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 -&gt; Run -&gt; 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.</Data>
  </EventData>
</Event>
garryshapeAuthor Commented:
I run the command:

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

Open in new window


And get output:

---------- C:\WINDOWS\SECURITY\LOGS\WINLOGON.LOG
        Cannot find IIS_WGP.
        Cannot find MSSQL$MICROSOFT##WID.

But I do see IIS_WGP in Active Directory. Hmmm....
garryshapeAuthor Commented:
Oh wait, no it's not. There's an IIS_WPG in AD, but not an IIS_WGP. lol. I guess somebody messed with something. Very strange, let me check further.
garryshapeAuthor Commented:
Ok yeah I traced it down to two accounts not existing in AD. I guess one was a typo and the other was a past account.
It would appear that this GPO doesn't validate names/groups typed in unless you "browse" for a name, so that is likely the case.
Will SzymkowskiSenior Solution ArchitectCommented:
The only time you need to care about errors in RSOP.msc is when they are actually on the Computer Configuration or User Configuration directly. If you see warning on Computer or User Configure this are not something to worry about.

A red X on Computer or User confiugration means the entire computer or user configuration is not applying any policies for several possible reasons.

- computer trust relationships
- in compatible software being applied to the computer using gpo
- corrupt gpo
etc...

Will.

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
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 2008

From novice to tech pro — start learning today.