Link to home
Create AccountLog in
Avatar of ManieyaK_
ManieyaK_Flag for United States of America

asked on

GPO not changing registry key values

We're trying to push out registry changes to the following keys,
HKLM\SOFTWARE\Microsoft\Internet Explorer\Main\FeatureControl\FEATURE_ENABLE_PRINT_DISCLOSURE_FIX\iexplore.exe
HKLM\SOFTWARE\Wow6432Node\Microsoft\Internet Explorer\MAIN\FeatureControl\FEATURE_ENABLE_PRINT_DISCLOSURE_FIX\iexlore.exe

Current value of iexplore = 0 we need to change the value to 1 and make it stick.  We've created a GPO specifically for registry modifications, made the changes, all the logs show policy updated successfully, but no change in value.  We've tried the the following "Actions" when attempting this change, "Replace, Change, Update, & Create)  Making the change in Computer Configuration\Preferences\Registry  <--- this is where we added the keys to be updated, we set the permissions in the following location >> Computer Configuration>Policies>Security Settings>Registry.  After looking in Windows Event Logs there are a ton of failure audits in Security Log, under task category "Registry"  for the following account,
Security ID >> NETWORK SERVICE
Account Name >> ServerName$

Another entry in event log in Application Log we got the following message,

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.

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------Ran FIND /I "Cannot find"  %SYSTEMROOT%\Security\Logs\winlogon.log with the following result,
------------C:\WINDOWS\SECURITY\LOGS\WINLOGON.LOG--------------------
Cannot find WebDevelopers.
Warning 2: The system cannot find the file specified.
                 Cannot find WebDevlopers.
Warning 2: The system cannot find the file specified.
                 Cannot find WebDevlopers.
Warning 2: The system cannot find the file specified.
                 Cannot find WebDevlopers.
Warning 2: The system cannot find the file specified.
                 Cannot find WebDevlopers.
Warning 2: The system cannot find the file specified.
                 Cannot find WebDevlopers.
Warning 2: The system cannot find the file specified.
                 Cannot find WebDevlopers.
Warning 2: The system cannot find the file specified.
                 Cannot find WebDevlopers.
Warning 2: The system cannot find the file specified.
                 Cannot find WebDevlopers.
Warning 2: The system cannot find the file specified.
                 Cannot find WebDevlopers.
Warning 2: The system cannot find the file specified.
                 Cannot find WebDevlopers.
Warning 2: The system cannot find the file specified.
Warning 2: The system cannot find the file specified.
Warning 2: The system cannot find the file specified.
Warning 2: The system cannot find the file specified.
Warning 2: The system cannot find the file specified.
Warning 2: The system cannot find the file specified.
Warning 2: The system cannot find the file specified.
Warning 2: The system cannot find the file specified.
Warning 2: The system cannot find the file specified.
Warning 2: The system cannot find the file specified.
Warning 2: The system cannot find the file specified.
Warning 2: The system cannot find the file specified.

-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Ran rsop, found policy with red x the policy with the red x was located >> Computer Configuration>Windows Settings>Security Settings>Local Policies>User Rights Assignment>"Allow log on through Remote Desktop Services with the following user account Administrators, & WebDevlopers.

WebDevlopers account or group doesn't exist any where within our ORG.

Running Server 2008 R2
Avatar of Mahesh
Mahesh
Flag of India image

where did you applied this policy?

On OU containing computers or users?

policy should be applied on Ou containing computers..

GP preferences works with system account
ASKER CERTIFIED SOLUTION
Avatar of Steve Knight
Steve Knight
Flag of United Kingdom of Great Britain and Northern Ireland image

Link to home
membership
Create an account to see this answer
Signing up is free. No credit card required.
Create Account
Avatar of ManieyaK_

ASKER

So I applied the policy to an OU specifically for Severs,  no users.  GPRESULT /z show N/A under applied Group Policy Objects.  Removing the key altogether, it doesn't come back, only if value is changed it will change the value back.
I was running under local account didn't realize.  Now it shows GPO applied but not the one in question.
Ok so it is applied to the ou the computer is in, set in computer policy and rsop shows it but gpresult does not?
Not sure if its related or not but there are a ton on audit failures for SID S-1-5-18 (Local System Account).  I'm not sure why that is.   The GPO is Link, & Enforced but it simply won't apply to this machine.  I even put the machine name in the security settings for the GPO, it doesn't show anywhere as being applied, or even that the system is linked to that GPO.
If it applies to another computer account in the same ou ok then it sounds like an issue with the domain connectivity on that machine - check DNS settings on network cards and remove / add back to domain if needed.
Did you solve this then?
Yeah so the issue was a GPO in a higher OU was being enforced which was set to the incorrect value.  Removed the GPO we created to modify the value, updated GPO that was causing the issue.  Issue has been resolved.

Steve, thanks for the comments.