shldbgolfn
asked on
GPO on Server 2003
I have multiple issue with my terminal server. Below is the first:
Server 2003 Standard x64
Service Pack 2
Current on updates
Part of small SBS 2008 domain
This is a terminal Server
I keep getting Application Event ID 1202 (Warning) - see below for event text.
After running through the instructions in the event description, I discovered that the (Domain) GPO is the Log on as a Batch File user right. The GPO includes the local machine Administrator account for an application server within the domain. (It also includes a couple of other domain and machine admin accounts, but the error is tied to a single account - Server3\Administrator)
Again, the Event error is appearing in the terminal server (Server2) only.
The other machines are not generating this Event ID, only the Terminal Server machine is. Apparently, that is the only machine that cannot reconcile the SID.
I have removed the account from the GPO and put it back and the events start again.
Any suggestions?
Event ID 1202:
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
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.
For more information, see Help and Support Center at
Server 2003 Standard x64
Service Pack 2
Current on updates
Part of small SBS 2008 domain
This is a terminal Server
I keep getting Application Event ID 1202 (Warning) - see below for event text.
After running through the instructions in the event description, I discovered that the (Domain) GPO is the Log on as a Batch File user right. The GPO includes the local machine Administrator account for an application server within the domain. (It also includes a couple of other domain and machine admin accounts, but the error is tied to a single account - Server3\Administrator)
Again, the Event error is appearing in the terminal server (Server2) only.
The other machines are not generating this Event ID, only the Terminal Server machine is. Apparently, that is the only machine that cannot reconcile the SID.
I have removed the account from the GPO and put it back and the events start again.
Any suggestions?
Event ID 1202:
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
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.
For more information, see Help and Support Center at
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
Correction to the original description - the other 2003 server in the domain is also generating the same error event. The 2008 servers are not. Seems to indicate that just 2003 os not being able to reconcile the account.
ASKER
Though this seems like a work around that might have caused other issues, it turns out the permission was no longer needed. Therefore this solution worked. Thanks.
ASKER