Editor's note:
SearchDomino.com is pleased to present tips featuring excerpts from THE VIEW articles on a monthly basis. You can read the full article in recent or upcoming issues of THE VIEW. This week's tip was excerpted from article in the November/December issue of THE VIEW entitled "Policy-Based User Management in Notes/Domino 6," which provides comprehensive information on the settings you can control using policies, plus guidance on how to organize and use policies effectively.
Notes/Domino 6 introduces policy-based management, a powerful feature that enables administrators to centrally define, organize, and control hundreds more user settings than they could in previous releases – including settings that must be made before first-time users connect to their home servers. There are five types of policy settings documents: Registration, Setup, Desktop, Security, and Archiving. The settings for desktop configuration, security, and archiving mail files are dynamic -- when an administrator changes a preference in one of these categories, it takes effect almost immediately. The next time a user authenticates with their home server, the Notes client's dynamic configuration process verifies whether any of the policy settings have changed on the server since the client last retrieved them. If
To continue reading for free, register below or login
To read more you must become a member of SearchDomino.com
');
// -->

any settings have changed, the client pulls the newer settings from the server.
There are two flavors of policy documents: organizational and explicit. Organization policies allow you to associate groups of settings with any subset of a named hierarchy (such as ABC Corp., Sales/ABC Corp., and so on). All members of the specified organization or organizational unit automatically inherit the associated settings. Explicit policies enable the administrator to customize settings for different users across organizational lines. These policies are assigned in users' Person documents.
Given the range of control now possible, implementing policy-based management requires a structured approach to create a maintainable set of policies. Before you create your first policy settings document, we suggest that you create a planning document. Start with the organizational hierarchy and apply the settings for each of the five categories to the organizational levels. Follow these guidelines:
A word of caution – don't forget to disable setup profiles in Person documents when you upgrade your clients. Make this a step in your upgrade plan.
About the authors:
Ted Niblett is a product manager at IBM/Lotus Software. Debbie Lynd is director of content for THE VIEW Conferences and Seminars.