Re: Group Policy Loopback Not Applying

Ace,

I've done some more work and found that all comptuer based GPOs are not
applying after doing a sysprep and rejoining the domain. Even with a
different computer name. The even stranger things is that it appears to be
just in this particular OU. If I move the computer to a different OU,
computer policies apply just fine.

The only thing I can think of is that the particular OU that the loopback
policy is applied to is set to block policy inheritance from the parent OU.
This is also generating some weird results when running a "gpresult" on the
computer in question. Under the Computer Settings area, there is a section
called: "The following GPOs were not applied because they were filtered out".
It appears as though any other computer based GPOs are filtered because of
an "unknown reason" and the group policy with the loopback is listed, but not
under the filtered area. I wish I could attach a screen shot, it would be
much clearer to explain with a picture. I hope this makes sense and might
help trigger an idea of how to solve this mystery.

Thanks again!

Thomas

"Ace Fekay [Microsoft Certified Trainer]" wrote:

In news:0C2E68C3-8189-4056-8816-E565BD0AB2D6@xxxxxxxxxxxxx,
Thomas <Thomas@xxxxxxxxxxxxxxxxxxxxxxxxx>, posted the following:
Thank you Ace and Meinolf for your quick response.

The computer account in question was definitely located in the
correct OU. In fact I tested the OU membership/policies by moving
another computer into that OU and found the loopback policy worked as
designed.

I ran a RSOP from the GPMC and it processed without any errors. I
also checked in the result of the RSOP and found the user policies
that are supposed to be applied from the computer loopback policy
were applied successfully.

In addition, I took the advice of Meinolf, and removed the problem
computer from the domain, then deleted the computer accounts. Forced
a sync with our two Windown 2003 domain controllers. At this time I
figured I would run sysprep again (to generate new SIDs). I copied
the latest sysprep files (which I downloaded from:
http://www.microsoft.com/DOWNLOADS/details.aspx?familyid=673A1019-8E3E-4BE0-AC31-70DD21B5AFA7&displaylang=en)
to the local drive in "C:\sysprep" folder. I ran sysprep, took an
image (in case it worked), and brought the computer back up, joined
the domain, placed the computer in the correct OU, restarted, forced
gpupdate, restarted. Still nothing.

The weird thing is that the user and computer GPOs are applying. In
fact, the computer is receiving GP from the "PD Laptop User Policy -
Computer" which is where the loopback is turned on. For whatever
reason, the user portion of that GPO is not looping back to the user
settings on this particular computer.

This computer was working just fine with the loopback policy before I
ran sysprep.

Any other ideas?

Thanks again for your time, it is most appreciated!

Thomas

Actually it has got me stumped, because this just works, well, normally in
all cases that I've used. Therefore, I haven;t seen this problem at all. May
there be something in a batch file running making a change, a security
setting being applied, etc?

Ace


.

Relevant Pages

  • Re: Group Policy Loopback Not Applying
    ... policy is applied to is set to block policy inheritance from the parent OU. ... "The following GPOs were not applied because they were filtered out". ... another computer into that OU and found the loopback policy worked as ... figured I would run sysprep again. ...
    (microsoft.public.windows.server.active_directory)
  • Re: At this point, Im wondering if GPOs even work?
    ... what is set in a policy does not bubble up into the user interface. ... Pop-up Blocker" box on one and checked it on the other. ... ensured no GPOs nor local policy were superseding my Test GPO ... Config (so why do these settings even exist in Computer Config if they ...
    (microsoft.public.windows.group_policy)
  • Re: Domain Security policy
    ... The group policy does'nt apply to the user pc even thought i logoff and login ... I would suggest to design your OU structure to reflect your ... GPOs set. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Authentication issue preventing Group Policy from applying to
    ... Linking a GPO to a container other than the one where the ... or the one for the Computer when the policy was for Users ... >>What are the permissions on the GPOs? ... > and the policy is set to apply to Authenticated Users. ...
    (microsoft.public.win2000.active_directory)
  • Sysprep 2.0 Local Group and Local Group Policy
    ... this group doesn't give rights to the same location though. ... > Ok I have setup a group policy for the machine following article Q274478. ... > I sysprep the machine using sysprep 2.0, minisetup, pnp. ...
    (microsoft.public.windowsxp.security_admin)