Home
Configuring
Use this information to configure your network, users, servers (including Web servers), directory services, security, messaging, widgets and live text, and server clusters.
Configuring users and servers
Topics in this section describe how to set up users and servers.
Policies
Use Domino® policy settings to control how users work with Notes®. A policy is a document that identifies a collection of individual policy settings. Policy settings documents define a set of defaults that apply to the users and groups to which the policy is assigned. You can change policy settings and they will be automatically applied to the assigned users and groups.
Creating policies
Creating a policy is a two-step process. If you create an organizational policy, it automatically applies when you register users. If you create an explicit policy, you assign it manually during user registration, in the Person document or by using the Policy Assignment tool.
Creating a Desktop Settings document
Use the Desktop Settings document to establish or make changes to a user's HCL Notes® desktop environment including setting up a default home page, customizing the user's Welcome page, upgrading the mail template, enabling automatic diagnostic data collection for client crashes, controlling Widgets and Live Text options, and specifying how and when Notes client Smart Upgrade runs.
Specifying Smart Upgrade settings for a desktop policy
Use the Smart Upgrade tab of the Desktop Settings document to specify if and how users of the policy will use the Notes® Smart Upgrade feature.

Configuring
Use this information to configure your network, users, servers (including Web servers), directory services, security, messaging, widgets and live text, and server clusters.
- Configuring a network
  This section presents the planning concepts and setup procedures necessary for a successful HCL Domino® deployment over a network. It provides information on network protocols from a Domino perspective but does not attempt to provide general network information.
- Configuring users and servers
  Topics in this section describe how to set up users and servers.
  - Understanding the Server document
    The Server document is set up when you register a server. It contains many of the settings that define how your server operates.
  - Policies
    Use Domino® policy settings to control how users work with Notes®. A policy is a document that identifies a collection of individual policy settings. Policy settings documents define a set of defaults that apply to the users and groups to which the policy is assigned. You can change policy settings and they will be automatically applied to the assigned users and groups.
    - Organizational and explicit policies
      There are two types of policies: organizational and explicit. Understanding the differences between the types helps you plan the implementation.
    - Understanding policy hierarchy and effective policy
      The effective policy for a user is a set of derived policy settings that are dynamically calculated at the time the policy is executed. The field values in an effective policy can originate from many different policy settings documents associated with the policy documents that apply to the user. Users may have a combination of policy settings that include values set at their OU level, values set with an explicit policy -- including values assigned to groups the user is a member of -- and settings inherited from a parent policy. The resolution of those settings determines the effective policy for each user.
    - Assigning dynamic policies
      Before you register and set up users, plan and create policies. Then, during user registration, assign the policies.
    - Understanding the How to Apply setting for a policy
      The policy settings documents contain a How to Apply setting that enables you to uniformly control how and when users can modify the individual field values in these documents and when the field values cannot be modified by end users. The How to Apply feature provides a central location, the policy settings document, from which you can set, and optionally, lock down policy settings. This feature is especially useful for implementing company procedures and increasing security. The How to Apply setting is available in all policy settings documents.
    - Assigning NOTES.INI or location document settings using a desktop policy
      Assign custom NOTES.INI settings or Locations settings using the Custom Settings tab of the Desktop Settings document.
    - Assigning Eclipse preference settings using a desktop policy
      You can use a Desktop Settings document to add or remove Eclipse preferences used by Notes® or other Expeditor client application.
    - Configuring administrative settings for deploying Eclipse-based plug-ins
      You can centrally control various aspects of the Eclipse-based plug-ins that you deploy to HCL Notes® and non-Notes users.
    - Extending policy settings to HCL iNotes® and HCL Notes® profile documents
      You can customize the mail policy settings document and push new or customized settings to the profile document specified in the $Profiles field.
    - Creating policies
      Creating a policy is a two-step process. If you create an organizational policy, it automatically applies when you register users. If you create an explicit policy, you assign it manually during user registration, in the Person document or by using the Policy Assignment tool.
      - Creating a Connections settings document
        Create a Connections Settings policy document to define a user's HCL Connections™ server and assigned port, and whether the user names, passwords, and activities data are to be encrypted with SSL.
      - Creating a Desktop Settings document
        Use the Desktop Settings document to establish or make changes to a user's HCL Notes® desktop environment including setting up a default home page, customizing the user's Welcome page, upgrading the mail template, enabling automatic diagnostic data collection for client crashes, controlling Widgets and Live Text options, and specifying how and when Notes client Smart Upgrade runs.
        Specifying Basic settings for a desktop policy
        Create the Desktop Settings document and then use the Basics tab to specify general options for users of the policy, including options for homepage/welcome page, location, server, mail template information, calendaring and scheduling, and menus.
        Specifying Smart Upgrade settings for a desktop policy
        Use the Smart Upgrade tab of the Desktop Settings document to specify if and how users of the policy will use the Notes® Smart Upgrade feature.
        Specifying Application settings for a desktop policy
        Use the Applications tab of the Desktop Settings document to specify how Notes® and Domino® applications will be created and managed for users of the policy.
        Specifying Widget settings for a desktop policy
        Use the Widgets tab of the Desktop Settings document to control access to Widgets and Live Text for users of the policy.
        Specifying Dial-Up, Account, and Name Server settings for a desktop policy
        Use the Dial-Up Connections, Accounts, and Name Servers tabs of the Desktop Settings document to specify those details for users of the policy.
        Specifying TLS settings for a desktop policy
        Use the TLS tab of the Desktop Settings document to manage Transport Layer Security (TLS) behavior for users of the policy.
        Specifying Applet Security settings for a desktop policy
        Use the Applet Security tab of the Desktop Settings document to specify access to Java™ applets for users of the policy.
        Specifying Proxy server settings for a desktop policy
        Use the Proxies tab of the Desktop Settings document to determine whether users of the policy will access the Internet through a proxy server, and to specify settings for each of several types of proxies.
        Specifying Mail settings for a desktop policy
        Use the Mail tab of the Desktop Settings document to specify mail and mail quota settings, as well as managed mail replica settings, for users of the policy.
        Specifying Preferences for a desktop policy
        Use the Preferences tab of the Desktop Settings document, and all its sub-tabs, to specify client preferences for users of the policy.
        Specifying Diagnostic settings for a desktop policy
        Use the Diagnostics tab of the Desktop Settings document to specify methods of automatically collecting diagnostic data from users of the policy.
        Specifying Custom Settings for a desktop policy
        Use the Custom Settings tab of the Desktop Settings document to push supplied or custom settings to users of the policy.
        Saving a desktop policy
        Saving a Desktop PolicySettings document is the first stage of putting the policy into effect.
        Understanding the desktop policy settings document
        Use a desktop policy settings document to control the user's workspace. Desktop settings are enforced the first time a user logs in to iNotes® and runs setup. After the initial setup, you can use them to update the user's desktop settings. Users receive updates to the settings when any of the policy settings change, and then the desktop policy settings are enforced the next time users authenticate with their home server.
      - Creating a Traveler policy settings document
        Use the Traveler Policy Settings document to define HCL Traveler preferences for synchronizing HCL Domino® users' mail database data with their mobile handheld devices. You can synchronize Email, Calendar, To-Do, Contacts and Notebook data. Push technology is used to deliver updates to the device as they occur in real time.
      - Creating a Roaming Settings document
        Use the Roaming Settings document to enable file server roaming for registered HCL Notes® users, standard configuration. When you enable file server roaming for a Notes end user, the user's files and applications that roam reside on a file server.
      - Creating a mail policy settings document
        Use the mail policy settings document to establish or make changes to a user's HCL Notes® mail, calendar and schedule functions.
      - Creating a Registration Policy Settings document
        Use a Registration Policy Settings document to populate desired default settings when registering new users. If you use an organizational policy, when you register users with the corresponding certifier ID, that policy is automatically applied. If you use an explicit policy, you select the policy during registration.
      - Creating a Setup Policy Settings document
        In previous releases of HCL Domino®, a Setup Policy Settings document was used to define the default look and content of the user workspace, to modify user Location documents, and to create Connection documents for dial-up (pass-through) connections that simplify server connections. Instead, in this release, use a Desktop Policy Settings document for these purposes.
      - Creating an archiving policy settings document
        To set up mail file archiving, you use both Archiving Policy Settings documents and Archive Criteria Settings documents. The Archiving Policy Settings document allows you to specify archiving policy parameters -- or not specify parameters -- as well as to specify whether HCL Notes® users can archive mail databases, and whether they can set or modify archive settings. The Archiving Policy Settings document can make use of one or more archive criteria settings documents.
      - Creating a security policy settings document
        A security policy settings document allows you to manage HCL Notes® and Internet passwords, configure customized password polices for your organization, set up key rollover, manage administration ECLs, push trusted cross-certificates to clients, and configure an ID vault. You can also configure settings for signed plug-ins and the home portal server for composite applications.
      - Creating a policy document
        When you create a policy, you use a Policy document to specify which policy settings documents to include. You can create policy settings documents before you create the policy document, or you can create them while you create the Policy document.
      - Creating a child policy document
        When you create a child policy, you use a Policy document to specify which policy settings documents to include.
    - Managing policies
      To manage policies, you can perform any of the tasks listed in the related topics.
  - Defining default settings for Notes® user registration
    Before you register new Notes® users, you can specify default settings that apply to all users. Default settings simplify user registration and ensure user settings consistency. You can define many default settings, such as what mail server users have or what certifier ID to use for user registration. You can also specify a default workstation execution control list (ECL) to protect data from unauthorized workstation access.
  - Using groups
    Groups are lists of users, groups, and servers that have common traits. They are useful for mailing lists and access control lists. Using groups can simplify administration tasks.
  - Replicas
    You can make a database available to users in different locations, on different networks, or in different time zones, by creating replicas of the database.
  - Calendars and scheduling
    The calendar and scheduling features allow users to check the free time of other users, schedule meetings with them, and reserve resources, such as conference rooms and equipment.
  - Editing the notes.ini file
    The Domino and Notes notes.ini files contain the settings required for the server and client to operate correctly. If you modify or add settings in a notes.ini file, do so cautiously and never edit the file directly with a text editor.
  - Configuring directory services
    This section describes how to plan, set up, and use HCL Domino® directory services.
  - Configuring messaging
    This section provides an overview of messaging and describes how to set up mail routing, how to set up and customize mail servers, and how to track mail.
  - Configuring iNotes®
    HCL iNotes® provides HCL Notes® users with browser-based access to Notes mail and to Notes calendar and scheduling features. Administrators specify mail policy and security policy settings as well as notes.ini file settings to complete the full implementation of HCL iNotes.
  - Configuring Web servers
    This section describes how to set up the HCL Domino® Web server, and the Domino Web Navigator.
  - Setting up a cluster
    Setting up a cluster includes the tasks of creating and verifying that it is working correctly, and then setting up user access, mail, replications, size quotas, directory assistance, roaming, web navigation, and use of a private LAN in the cluster.
  - Configuring Widgets and Live Text
    Widgets and Live Text enables end users to see and act on Live Text in supported documents, including HCL Notes® mail, using XML extensions (widgets) created specifically for their use.
  - Domain Search
    Notes® client and Web users can use Domain Search to search an entire Domino® domain for database documents, files, and attachments that match a search query.

Specifying Smart Upgrade settings for a desktop policy

Use the Smart Upgrade tab of the Desktop Settings document to specify if and how users of the policy will use the Notes® Smart Upgrade feature.

Procedure

Complete the following fields on the Smart Upgrade tab:

Table 1. Smart Upgrade fields and actions
Field	Action
Deploy version	If you use Smart Upgrade, enter the Notes® version to which you want users to upgrade.
Upgrade deadline	If you use Smart Upgrade, use `mm/dd/yyyy` format to enter the date by which users must upgrade. If users to do not upgrade by this date, the upgrade happens automatically.
Remind me every hour after "upgrade deadline" has passed	Check this field if you want to send an hourly reminder to users who have not updated their clients by the deadline set in the field Upgrade deadline.
Mail-in Database for Smart Upgrade reports:	By default, the name of the mail-in database for Smart Upgrade appears. If a Smart Upgrade mail-in database name is not displayed but one exists, you can specify one. This field is required to enable Smart Upgrade Tracking for the users or groups in policy settings document. If a Smart Upgrade mail-in database does not exist, you must create one.
Remove Smart Upgrade tracking files after a specified number of days:	Choose one: Yes -- Automatically deletes the Smart Upgrade tracking files when the specified time period for maintaining files is exceeded and the Notes® Client is restarted. When the field appears, enter the number of days. No -- Maintains the Smart Upgrade tracking files after the specified time for maintaining the files is exceeded. The files are not deleted.
Number of days to keep Smart Upgrade Tracking files	Enter the number of days to keep the Smart Upgrade Tracking log files. The default is 365 days. Log files are stored in the user's Notes® client data directory: data\IBM_TECHNICAL_SUPPORT\Smart Upgrade