How do you stop top-level policies from forcing inheritance to child groups? I have the 'Force inheritance of settings in child policies' unchecked, as well as 'force inheritance in child groups' unchecked under 'Managed Computers' properties, but all my child groups are being forced to use the top-level policies (and they are configured to NOT inherit).

Same thing goes for tasks...I really need to be able to apply separate settings for different servers, but the "locked" policies and tasks refuse to let me modify how they are applied.

Any ideas?

hi, in the parent policy, unlock the setting (the lock icon) in any configuration that you dont want the child to inherent.

hi, forget about the earlier post.
what you can do is
- on the parent policy, make sure the "force inheritance of settings in child policies" is UNCHECKED
- on the child policy, make sure the "inherit settings from parent policy" is UNCHECKED
now your child will not inherit from parent

Thanks for the reply Chan GG.

That's exactly how I have the policies configured, which is what is confusing me.

Top level policy has "force inheritance of settings in child policies" UNCHECKED.

When I right-click on a child group--Policies folder and check "View--Inherited Policies," It displays the top-level policy (actually is displays ALL of my policies, and they're all set to not force inheritance) with a lock over the icon. Also, trying to edit the inherited policy, the "Advanced" link is grayed out, so I can't uncheck "inherit settings from parent policy."

Maybe the new Admin Kit configuration is what is confusing me, but I would think that if I had the top-level policy configured to NOT force inheritance to child policies, then that policy would not even be displayed in the child policy, which isn't the case.

Am I doing this wrong? Should I be unlocking settings at the top that I don't want to filter down, and then creating a new child policy with locks on the features that I DO want?

Thanks for the help.

hi, my opinion. if most of the configuration is the same for parent and child, stick with lock/unlocked technique. this is because if you need to change a common setting, you only need to change at the parent.
however, if most of the configuration are different between parent and child, use the "inherent from parent" and "force inherent" setting. are you still having problem with "inherent from parent"? is working fine in my adminkit 8...

Yeah, still having problems. No matter how I configure the policies, they'are always applied to child groups, and they're always locked.

I keep my Workstation policies and tasks locked at the top level, since these are universally applied across multiple domains. For servers, however, I have different requirements depending on what it's function is. In the previous version I would apply a top-level policy so it would catch everything, but then I would have a seperate child that doesn't inherit any settings, and a seperate policy for that child group only. Doesn't look like I can do that here, or at least I should be able to, it's just not working right.

Quick question if you could check for me please:

In your configuration, if you have a top-level policy that is configured to NOT force inheritance on child groups, does that policy simple NOT show up at all in the child policy?

Remember to right-click on the child group--Policies folder and check "View--Inherited Policies." If you can't see the inherited policy, then I have a problem and need to open a support case.

Thanks again.

Hello,

Just in case, from the help file :

Hi jthomas27,

Now I am more clear on your situation. Yes, if you select view inherented policy, those inherented policy cannot be changed since they are basically your parent policies.
If your parent-child policy is going to be very different
- uncheck "force inheritance of settings in child policies" in the parent policy
- copy and parent policy and paste to child policy. Then make the necessary changes in the child policy

Hope this help.