Had one of those “duh” moments today and wanted to pass along.
Simple scenario - I’m working with a customer on deploying widgets. We have Widget A that needs to be deployed to ALL users, and we have Widget B that only needs to be deployed to some.
We created an explicit policy that pushes down Widget A, and a dynamic policy to push down widget B to those people who need it (and they get it by being in the group the policy is assigned to).
NOBODY ever got Widget B.
And, it wasn’t until talking with IBM support that I realized what the problem was (and then had the “Duh” moment).
You can’t have two policy documents that BOTH are pushing down widgets to the same user. Any given user can only get widget “instructions” from one policy.
I kept thinking that this would be “additive” - that is, I kept thinking that some users would get BOTH widgets. But, Notes saw the two policies as being conflicting - and so it went into the usual policy precedence mode, and the explicit policy won out over the dynamic policy (which, in turn, would have won out over an Organizational policy).
So, lesson learned.
You cannot have TWO different policy documents, both telling your Notes client what widgets to pick up. You can only have one …
So, we are reworking things and will have a couple different policy documents - but Widget A will be in both of them, and Widget B in the second …
There’s a great document in the Lotus Wiki that helps explain how the policy precedence works:
http://www-10.lotus.com/ldd/dominowiki.nsf/dx/domino-policy-precedence-explained
Just thought I would pass this along …
- r