HCL-DOM-AADM-12 Questions and Answers

All requests for the Administration Process are stored in the Administration Requests database (admin4.nsf) . When an administrator performs a task (like deleting a user), a "request" document is created in this database. The AdminP task on each server in the domain periodically checks this database to see if there are tasks it needs to perform, such as updating local database ACLs or deleting local replicas.

Before running the HCL Domino installer on a Linux platform, the administrator must ensure that all required system libraries are pre-installed . Domino relies on specific OS-level packages (such as libcap, glibc, and libstdc++) to function correctly. If these dependencies are missing, the installation may fail, or server tasks may not launch properly after configuration.

=======

All Domino Policies —including Desktop, Security, Mail, and Archive settings—are stored within the Domino Directory (names.nsf) on the administration server. The directory contains the Policy documents and their associated Policy Settings documents. These policies are then distributed throughout the domain via the standard replication of the names.nsf file to other servers, where they are applied to users and groups during the authentication or login process.

=======

During the initial configuration of a Domino server, the setup utility prepares the Domino Directory by creating or modifying core documents. These include the Server document , which identifies the server and its specific network/security settings , and the Configuration Settings document , which is used to manage settings for tasks like mail routing and MIME across one or more servers in the domain.

=======

After the physical installation of the Domino binaries (the "program files") is complete, the server is not yet functional. The administrator must run the Server Setup Utility . This utility (which can be run via a graphical interface or through a web browser in recent versions) guides the administrator through naming the server, establishing the organization, setting up the first administrator, and choosing which initial services (like HTTP or SMTP) to enable.

=======

In HCL Domino, the registration process is the primary way to establish a user's identity within the domain. When an administrator uses the Domino Administrator Client to register a person, the system generates a Person document in the Domino Directory (names.nsf), which contains the user's public key and configuration. Simultaneously, it creates a Notes ID file , which stores the user's private key required for authentication and encryption. While a mail file is often created as part of this workflow, the document and ID file are the fundamental identity components.

=======

The notes.ini file is the primary configuration file for an HCL Domino server. During the initial setup and configuration process, the Domino utility automatically updates this file with environment-specific settings , such as the server's name, the path to the data directory, and the specific tasks to be loaded at startup. It serves as the master checklist for how the server behaves every time it boots.

=======

To enable the Domino Attachment and Object Service (DAOS) , an administrator must first enable it in the Server document (under the DAOS tab) by specifying a base path and the minimum attachment size. Once the server-level setting is active, the administrator must then enable DAOS on individual databases and run the compact -c -daos on command. This process converts the internal database structure to move attachments into the DAOS repository.

=======

While a server has many identifiers (like an IP or Hostname), the Server ID is the unique security file that defines the server's identity within the Domino domain. This file contains the server's private key and is created during the registration process. The Server ID allows the server to authenticate with other servers and clients, ensuring it is a trusted member of the hierarchical organization.

=======

Domino Domain Monitoring (DDM) provides a centralized collection and display of server events across an entire domain. It uses "probes" to check various subsystems (like Mail, Security, or Replication). When a probe finds an issue, it generates a report in the ddm.nsf database, allowing administrators to monitor the health of multiple servers from a single interface.

=======

The Administration Process (AdminP) handles user renames in several stages. After the user accepts the name change in their Notes client, AdminP triggers a series of requests. The specific request responsible for searching through every database on the server and changing the user's old name to the new name in the Access Control List is the Rename in ACL request. This ensures the user retains their permissions under their new identity.

=======

Domino Domain Monitoring (DDM) is the primary tool for proactive alerting within a Domino environment. By configuring event generators in DDM, administrators can set specific thresholds for server health, mail routing delays, and security events. When these thresholds are met, DDM generates an alert in the ddm.nsf database, which can then be configured to send notifications (such as emails) to administrators, allowing them to resolve issues before they impact end users.

In a complex environment where users are spread across multiple Domino domains or external LDAP directories, a single local Domino Directory is insufficient for authentication. The Directory Assistance database acts as a pointer that tells the Domino server where to look for user credentials when they are not found in the primary local directory (names.nsf). This allows for authentication and name lookups across an entire organization, regardless of which domain the user belongs to.

=======

The Domino Attachment and Object Service (DAOS) stores attachments separately from NSF files. When documents are deleted, the associated attachment files (.NLO) are not immediately removed from the storage. To reclaim this physical disk space, an administrator must:

Issue the tell daosmgr prune command : This identifies and deletes attachment files that are no longer referenced by any database and have exceeded the deferral interval.

Issue the tell daosmgr resync command : This synchronizes the DAOS catalog (daoscat.nsf) with the physical files on disk to ensure the repository is accurate.

=======

The Silent Install method is used to automate the installation of Domino binaries across one or many servers without requiring a person to manually click through the graphical interface. This is achieved by using a "response file" that contains all the necessary installation parameters. It is highly efficient for large-scale deployments or for installing Domino on remote servers where a graphical display (GUI) may not be available.

=======

The Server > Status tab in the Domino Administrator Client is the central monitoring hub. It provides a real-time view of all active server tasks (like the Router, AdminP, or HTTP), allows administrators to see the current status of those tasks, and provides access to the server console for tracking system events and performance metrics directly.

=======