Hi, I created a new OU and put my computer in that OU. I then created
a new policy (made no changes, just a new policy) and blocked
inheritance. I have rebooted, and ran gpupdate /force, but the error
message about the computer not updating always gives the wrong policy
name. I made justa blank new policy becaus i am having strange problems
on my PC services where I get access denied, and I can't even do simple
things like ping; yet, the NIC still runs and I'm on the network.

In other words, my new policy generated a long GUID (or whatever it is)

in sysvol for my OU that I created the policy for. But, when I use
gpupdate /force (and have waited for latency issues and so on) the
error gives the long guid looking identifier for the default policy.
It never uses the policy for the OU the machine is in.


Any ideas on how to make this work? Thank you.


I am using vista rc1, 5600. What happened was the default policy
stopped working for some reason with Vista and kept many services from
working, thus my attempt to get them back by isolating the PC in a new
OU, blocking inheritance. Thanks again.

jm wrote:
> Hi, I created a new OU and put my computer in that OU. I then created
> a new policy (made no changes, just a new policy) and blocked
> inheritance. I have rebooted, and ran gpupdate /force, but the error
> message about the computer not updating always gives the wrong policy
> name. I made justa blank new policy becaus i am having strange problems
> on my PC services where I get access denied, and I can't even do simple
> things like ping; yet, the NIC still runs and I'm on the network.
>
> In other words, my new policy generated a long GUID (or whatever it is)
>
> in sysvol for my OU that I created the policy for. But, when I use
> gpupdate /force (and have waited for latency issues and so on) the
> error gives the long guid looking identifier for the default policy.
> It never uses the policy for the OU the machine is in.
>
>
> Any ideas on how to make this work? Thank you.
>
>
> I am using vista rc1, 5600. What happened was the default policy
> stopped working for some reason with Vista and kept many services from
> working, thus my attempt to get them back by isolating the PC in a new
> OU, blocking inheritance. Thanks again.

I eventually got it to work by moving to the new OU and allowing an
override on the default policy for the forest. It allowed me to
update, but didn't allow me the privileges. Base Filtering Engine, for
example, saying that it can't find a procedure. Maybe RC1 is the
problems.