The effective policy provides a synopsis of the settings and policies that are associated with a user or group. This feature allows you to view all the inherited and enforced settings based on the policies that apply to the user or group. In other words, if there are multiple organizational policies, the synopsis will show the hierarchical view of policies and settings for the selected users.
Using the Policy Synopsis function of the Domino Administrator client, you view the effect policy. The Policy Synopsis can produce two types of reports - Summary Only and Detailed. These reports are, by default, stored in the policy log database (policysyn.nsf). Each time the synopsis is run, the report is logged in the database.
The summary report provides a list of the policies assigned to the selected user. The detailed report shows all policies and settings for the user. The following steps outline how to produce a policy synopsis and to display the effective policy for a person listed in the Domino Directory.
Step 1. Launch the Domino Administrator client.
Step 2. Navigate to the People & Groups tab.
Step 3. Select the People view.
Step 4. Select one or more users or groups from the Directory.
Step 5. Locate the People navigation pane along the right side of the Domino Administrator client and select the Policy Synopsis action (Figure 23). The "Policy Synopsis" dialog appears.
Figure 23. The Policy Synopsis action is located in the right pane in the People action menu.
Step 6. Select the report -- either Summary Only or Detailed (Figure 24).
Figure 24. In the Policy Synopsis dialog, you can select to generate the summary or detailed effective policy report for a particular user.
With the Summary Only option, Domino will generate a hierarchical synopsis of the policies that apply to the user. The Detailed option, on the other hand, enables you to refine the report.
Using the Detailed option, you can select which settings documents should be included in the report, such as Archive, Desktop, Mail, Registration, Setup, or Activities, along with a number of additional settings. One or more of the settings document can be included in the detailed report.
Step 7. (Optional) All synopsis reports are stored in a database on the Domino server. By default, reports will be appended to the database. However, you can optionally change the setting such that new reports overwrite previous reports.
Step 8. Click OK to generate the effective policy for the selected user(s). Domino generates the synopsis report and automatically launches the policy report database.
The new report will appear as a document in the database. To view the synopsis, simply select and open the document.
Also note that a separate report document will be generated for each person selected from the Directory. So if you select 100 persons to be included in the synopsis report, Domino will generate 100 separate documents. Each document will contain the unique effective policy for the individual user.
|Note: Generating policy synopsis reports can take time to generate from the Domino Administrator client. The response time will depend on the number of users selected from the Directory, server performance, and so on.|
Survival guide for Lotus Notes and Domino Administrators
Part 1: What are policies?
Part 2: How are policies implemented?
Part 3: What settings documents?
Part 4: What is a policy architecture?
Part 5: Creating settings and policy documents
Part 6: Creating policy documents
Part 7: Registering a new user using an explicit policy
Part 8: Assigning an explicit policy to an existing user
Part 9: Using exception policies
Part 10: Viewing your policy settings
| This chapter is an excerpt from the book, Survival Guide for Lotus Notes and Domino Administrators, authored by Mark Elliott, published by IBM Press, March 2009, ISBN 0137153317, Copyright 2009 by International Business Machines Corporation. All rights reserved. For more info, please visit the publisher site. Safari Books Online subscribers can also access the book at safari.com.
Click here for the chapter download.
This was first published in October 2009