Hey Leute,
ich habe gerade ein paar neue Server R2 installiert und habe auf allen diesen Server folgende Warnung in den Logs:
Kann es sein das meine GPO's irgendwie die ursprünglich aus einer Server 2003 Domäne kommen nicht kompatible sind mit meinen R2 Fileservern?
Die Anleitung im Log bring mich leider nicht richtig weiter.
Danke euch
Log Name: Application
Source: SceCli
Date: 17.09.2012 13:24:45
Event ID: 1202
Task Category: None
Level: Warning
Keywords: Classic
User: N/A
Computer: test.de
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="2012-09-17T11:24:45.000000000Z" />
<EventRecordID>1485</EventRecordID>
<Channel>Application</Channel>
<Computer>test.de</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 -> 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.</Data>
</EventData>
</Event>
Event ID SceCli 1202
