You can not do what you want as a general rule. In the case of products such as Host Intrusion Prevention (HIPS) IPS policy that have "slotted" policy design, you can make multiple assignment of policies at different branches. They do not behave the same as Microsoft Group policy that supercede each other. The policies are combined following the rules of the product policy design.
Policies that are not slotted can only have policy assignments that replace the policy of the parent once inheritance is broken.
In ePO 4.6 you can also assign policy via policy assignment rules and tags which can be quite flexible to get specific policy assigned to computer without changing the policy on ePO branch/group.
Thanks for confirming my thoughts. I find it interesting that a Product Enhancement Request I loaded about 12 months ago was closed as 'already in product'.
Policy assignment rules wont help with what I want unfortunately, as it still means having the same 'common' settings applied to mulitple policies. So then when maintaining those common settings you need to do so with multiple policies...
As a person who looks after alot more than just ePO, this is a big pain in the butt, due to the extra management overhead...
I feel your pain. I have implemented common generic policies at My Organization for just that reason. I can not maintain multiple policies when the same updates have to be applied to many policies.
I have made some suggestions as well, but they are too involved to type them here and do them any justice in terms of completeness and clarity.
They will again be raised at Focus once I get to the right person.