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.
Configuring directory services
This section describes how to plan, set up, and use HCL Domino® directory services.
Directory Sync
Directory Sync allows you to sync people and group data from an external LDAP directory into the Domino® directory. Currently data from Active Directory can be synced.
Active Directory password synchronization
WARNING: This feature impacts your Active Directory domain controller configuration; proceed only with a working backup of your domain controller. See further details in this topic.
Configuring password synchronization
To configure password synchronization, complete all of the steps in this section.
4. Configuring Request Processor servers
Configure settings for Request Processor servers in the Server document and in a Configuration Settings document in the Domino directory.

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.
  - 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.
    - The Domino® Directory
      The Domino® Directory, which some previous releases referred to as the Public Address Book or Name and Address Book, is a database that Domino creates automatically on every server. The Domino Directory is a directory of information about users, servers, and groups, as well as custom entries you may add. Registering users and servers in a domain automatically creates corresponding Person documents and Server documents in the Domino Directory for the domain. These documents contain detailed information about each user and server.
    - The LDAP service
      Lightweight Directory Access Protocol (LDAP) is a standard Internet protocol for searching and managing entries in a directory, where an entry has one or more attributes associated with a distinguished name. A distinguished name -- for example, cn=Phyllis Spera,ou=Sales,ou=East,o=Renovations -- is a name that identifies an entry within a directory tree.
    - LDAP schema
      A directory entry contains information about a particular entity, or object -- for example, a person or a group -- and is associated with a distinguished name. An LDAP schema is a set of rules that define what can be stored as entries in an LDAP directory. Each LDAP directory has a default schema, which organizations can customize, or "extend," by adding elements to it. The elements of a schema are attributes, syntaxes, and object classes. LDAP directory servers provide the ability to enforce the schema to ensure that directory changes made using LDAP operations conform to it.
    - ldapsearch utility
      Domino® and Notes® provide a command-line search utility, LDAPSEARCH.EXE, that you use to search entries in any LDAP directory. The ldapsearch utility connects to a directory server and returns results that match search criteria you specify. It is available on Domino server and Notes client platforms.
    - Directory assistance
      Directory assistance allows a server to look up information in a directory other than a local primary Domino® Directory (NAMES.NSF).
    - Directory Sync
      Directory Sync allows you to sync people and group data from an external LDAP directory into the Domino® directory. Currently data from Active Directory can be synced.
      - Configuring Directory Sync
        Complete the following steps to configure Directory Sync.
      - Creating a Directory Assistance document enabled for Directory Sync
        The first step to configure Directory Sync is creating a Directory Sync-enabled Directory Assistance document in the directory assistance database.
      - Creating a Directory Sync Configuration document
        After you create a Directory Assistance document that is enabled for Directory Sync, create a Directory Sync Configuration document in the Domino® directory. You use this document to select Directory Sync configuration options and then to enable Directory Sync.
      - Active Directory password synchronization
        WARNING: This feature impacts your Active Directory domain controller configuration; proceed only with a working backup of your domain controller. See further details in this topic.
        Password synchronization components
        The process of password synchronization involves components on the Active Directory domain controller and components on servers in the Domino domain.
        Password synchronization process flow
        Here are the steps that are taken to push a Windows user's new password in Active Directory to the HTTP password field in a Person document and to the Notes ID in the ID vault.
        Configuring password synchronization
        To configure password synchronization, complete all of the steps in this section.
        1. Creating a Directory Assistance database and document for password synchronization
        Create a new Directory Assistance database and a document in it to enable the Domino password filter on the Active Directory domain controller to look up user information in the Domino directory.
        2. Registering Request Creator servers
        Register a new Domino server to function as a password change Request Creator for each Active Directory domain controller from which you synchronize passwords.
        3. Configuring Request Creator servers
        Configure settings for Request Creator servers in the Server document and in a Configuration Settings document in the Domino directory.
        4. Configuring Request Processor servers
        Configure settings for Request Processor servers in the Server document and in a Configuration Settings document in the Domino directory.
        5. Replicating the directory and restarting servers
        After you've configured the Request Creator and Request Processor servers, replicate the Domino directory to the Request Processor servers and then restart them.
        6. Installing Active Directory Password Sync on a domain controller
        To install Domino Active Directory Password Sync, use the Domino Windows 64-bit server installer on the Active Directory domain controller.
        Password synchronization statistics: domain controller
        The following statistics for the domain controller are available.
      - Renaming Domino® users when their names change in Active Directory
        When you use Directory Sync and the common name of a registered Domino® user changes in Active Directory, follow this procedure to change the name in the Domino directory Person document, too.
      - Registering Active Directory users in Domino®
        When you use Directory Sync, you can register Active Directory users in Domino® to create mail files and Notes® IDs for them.
      - Deleting users and groups
        When users or groups are deleted in Active Directory, they are also deleted in the Domino® directory when a full resync is done. One exception is that Active Directory users who are registered in Domino through user registration are not deleted from Domino.
      - Changing the Directory Sync configuration
        To change the Directory Sync configuration, disable Directory Sync, edit the Directory Sync Configuration document, and then enable Directory Sync again.
      - Resyncing all data
        You can resync all of the Active Directory data.
      - Monitoring Directory Sync
        Use the following methods to monitor Directory Sync, in addition to monitoring the output of Directory Sync (Dirsync) at the server console and in log.nsf.
    - Directory catalogs
      A directory catalog is an optional directory database that typically contains information aggregated from multiple Domino® directories. Clients and servers can use a directory catalog to look up mail addresses and other information about the people, groups, mail-in databases, and resources throughout an organization, regardless of the number of Domino domains and Domino Directories the organization uses.
    - Extended ACL
      An extended access control list (ACL) is an optional directory access-control feature available for a directory created from the PUBNAMES.NTF template -- a Domino® Directory or an extended directory catalog. An extended ACL is tied to the database ACL, and you access it through the Access Control List dialog box using a Notes® or Domino Administrator client.
  - 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.

4. Configuring Request Processor servers

Configure settings for Request Processor servers in the Server document and in a Configuration Settings document in the Domino directory.

About this task

Complete this procedure for each Request Processor server in the Domino domain.

Request Creators and Request Processors can share the same Configuration Settings document or use separate ones. If they use separate ones, best practice is to use the same Active Directory Password Sync settings.

Procedure

Identify the server as a Request Processor in its Server document:
1. Open the Server document for the Request Processor in the Domino directory.
2. Select the Server Tasks - > > Active Directory Password Sync tab.
3. In the Password Sync processing role field, select Request Processor.
4. Optional: in the Password Sync requests database path and filename field, optionally specify a path and file name for the Active Directory Password Change Request database on this server. If you leave this blank, the database is created in the data directory with the file name adpwsync.nsf.
Open the Configuration Settings document in the Domino directory that the Request Processor uses and select the Active Directory Password Sync tab.

Complete the Global settings:

Setting	Description
Domino password types to sync	Select one of the following options: Select Notes ID to sync only passwords for Notes IDs in the ID vault HTTP Password to sync only HTTP passwords in the directory HTTP and Notes ID to sync both types of passwords. Note: To sync passwords to Notes IDs, the Request Processor servers require password reset authority to the ID vault.
Request expiration time (minutes)	Specify the amount of times in minutes after a request is created to allow the request to be processed. When the period expires, requests are deleted. Default is 365 minutes.
Request storage database managers	Specify the users who can access the Password Change Request database.

Note: The Global Settings settings also apply to Request Creator servers that use the same Configuration Settings document.