Domino policy is a powerful mechanism that allow administrators remotely push settings to users and standardize various parts of Lotus Notes. With the help of Domino policies, you can define rules for new user registration, mail file settings, security and roaming settings, and push Lotus Notes settings that can be enabled by default. Administrator can also lock certain settings if they do not want users to modify them.
You can apply policies to the entire organization, a particular organization unit, or even specific users or group of users. You can also use policy to set initial values of certain user settings but allows user to change them, or set and lock certain setting values. If policies are deployed in an organization and setting documents are properly filled, you will have a standardized environment. A standardized environment can result in less help desk calls.
There is a difference in managing the setting for the devices through a Lotus Domino policy document as opposed to the Device Settings in LotusTraveler.nsf interface. The settings made in LotusTraveler.nsf will take effect quicker (on the next device synchronization with the Lotus Notes Traveler server) than the Lotus Domino policies. The reason is that the Lotus Domino policies are maintained in the user's individual mail database file on the Lotus Domino mail server. To apply these settings to the mail database for the user, the entire Domino domain tree must be traversed to apply the policy to the selected group. This is then applied to the users that are included in the policy.
For debugging and troubleshooting purposes, it is important to know that policies are in place so that there is no confusion between was is being done based on the policy as opposed to what is being done in the Device Settings in LotusTraveler.nsf. The Lotus Domino policy settings have priority over the settings made in the Device Settings on LotusTraveler.nsf.
If you implement locking setting, it will work for new phones that installed Lotus Notes Traveler client after setting is implemented. If you want to force locking setting for new phone, you must reset Lotus Traveler device status, but deleting Lotus Traveler device entry with console command on Lotus Traveler server. These commands are:
- tell traveler security delete <device ID or * for all devices> <user ID>
- tell traveler delete <device ID or * for all devices> <user ID>
You can have default policy document that has Lotus Traveler Settings document for all users. If you have complicated environment, you can have explicit policy for certain group of users. It is better when there is organization policy, and user is affected at least by one policy document. If all the settings are the same for all users, it is advantageous to use the Device Settings in LotusTraveler.nsf as opposed to a Lotus Domino policy.
This is an example of how to add a Lotus Domino policy:
- From the Domino administrator navigate to the Dynamic Policies and select Add Policy.
- Select a new Lotus Traveler policy.
- Enter a policy name.
- Apply any settings that you want for this policy to implement in the remaining tabs.
- Finally, select Save and Close.
If the Lotus Domino or Lotus Traveler environment is split in several domains you might be required to deploy and maintain setting of Lotus Traveler policies in every domain.
For more information about the policy and setting documents, such as locking and inheritance of settings from parent or to child, see