If my intent is to use a packaged driver and to customize it by adding my
own packages to it, what's the best ("correct"?) way to replace pre-
packaged functionality?

I'll use Google Apps as an example here. The default packages include two
Subscriber Placement rules:

NOVLGGLEORGU-sub-pp_Placement (from Google Apps Organizational Units

NOVLGGLEBCFG-sub-pp_DefaultPlacement (from Google Apps Configuration)

For one reason or another, assume that neither of these meets my needs.

Looking at them, it looks like I could:

Use the GCV "User Placement Settings" and set it to "No Placement". That
would keep the NOVLGGLEORGU-sub-pp_Placement rule from doing anything.

Create a "NIU Google Apps Customizations" package.
Add a policy to the Subscriber Placement rule, linkage set to weight 250.
In this policy, implement whatever crazy scheme we've come up with here
that needs to be done.

By setting the weight, I can put it after NOVLGGLEORGU-sub-pp_Placement
and before NOVLGGLEBCFG-sub-pp_DefaultPlacement, so the result should be
that my custom placement is what we get. This should work.

But if the driver I'm customizing isn't as nicely designed as this one,
or if what I need to do conflicts with what the packaged version wants to
do, I can see how this wouldn't work in all cases.

Is there a way, in my package installation, to unlink policies from
somebody else's package? If NOVLGGLEORGU-sub-pp_Placement wasn't easily
bypassed with a GCV, can I unlink it from the driver and link in my own
replacement? (I know I can unlink NOVLGGLEORGU-sub-pp_Placement in the
driver in Designer.)

David Gersic dgersic_@_niu.edu
Knowledge Partner http://forums.netiq.com

Please post questions in the forums. No support provided via email.
If you find this post helpful, please click on the star below.