Blog

Domino policy management needs to grow up


Tags :


UPDATE: This is a discussion Gabriella started and we agreed on and I took an interest on making a diagram to make it clear

While working with a large policy deployment I finally reached the breaking point in trying to unravel large spaghetti policy topologies.  There is no simple viewer for a user and the synopsis tool makes the work just as hard.  Since the data is stored in the Domino directory for what policy is assigned to the user as well as what information is stored in what policy, extracting the data should be simple for a viewer approach.  Here is what we have now compared to a mockup of what we should have.  Keep in mind that the first image does not exist, it only represents what you have to do to even map policies in the first place.  The second image is a simplified approach of what we should get back when selecting a user and requesting for active policy settings.

Image:Domino policy management needs to grow up
With this approach, we know what should be applied to users.  It is a starting point to seeing how the client should be behaving based on the deployed policy set.  Unfortunately, we cannot even get that far most of the time, even with the hidden ($Policies) view in the local names.nsf on the client.  Thoughts?