Home
Administering
This documentation provides information about the administration tools for managing and monitoring servers and databases.
Managing servers
Manage Domino® servers by performing any of these tasks.
Collecting diagnostic information after a server or client crash
The automatic diagnostic collection tool collects diagnostic data after server and client crashes and sends the collected data to a mail-in database when the server or client restarts. You can then use the collected data to determine the cause of the crash.
Enabling the Fault Analyzer task on the server
You can complete this task at the same time that you set up automatic diagnostic data collection. Use the Server Configuration document to set up automatic diagnostic data collection on the server and to enable or disable Fault Analyses.

Administering
This documentation provides information about the administration tools for managing and monitoring servers and databases.
- Administration tools
  Topics in this section describe the tools you can use to administer a Domino® server.
- Managing users
  The Administration Process helps you manage users by automating many of the associated administrative tasks. For example, if you rename a user, the Administration Process automates changing the name throughout databases in the Notes® domain by generating and carrying out a series of requests, which are posted in the Administration Requests database.
- Monitoring servers
  This section describes how to use the tools and features that help you monitor a Domino® system.
- Managing servers
  Manage Domino® servers by performing any of these tasks.
  - Changing the server administrator
    If the name of the former administrator is explicitly listed in the access control list (ACL) for the Domino® Directory, delete the name of the former administrator from the ACL. Add the name of the new administrator and assign the administrator Manager access.
  - Setting and managing passwords for the server console
    Set server console passwords to protect against unauthorized use of the server console.
  - Decommissioning a Domain Search server
    If you want the server that creates full-text indexes of the Domino® domain to resume duty as a regular Domino server, remove it from the appropriate group in the Domino Directory, edit its Server document, and then delete some files from its directory structure.
  - Decommissioning a server
    You use the Decommission Server Analysis tool when you are consolidating existing servers and/or permanently removing a server from service. Whether you are combining two servers into one server or renaming a server, the result is the same -- the old server name is replaced with the new server name.
  - Deleting a server name
    You can use the Administration Process to delete references to a server from the Domino® Directory, and from database ACLs and Extended ACLs. The Administration Process automatically deletes mail-in database documents and cross-certificate documents as necessary during the Delete Server process.
  - Dropping user sessions on a server
    Dropping user sessions from a server may be useful when you need to make a database or server temporarily unavailable to correct a problem; users can reconnect after you are ready. You can drop one user session or all user sessions for the current database, or selected user sessions, from the server.
  - Finding a server name in the domain with the Domino® Administrator
    You can search for a server name in the domain and then view a log that includes document links and directory links to each occurrence of the server name.
  - Recertifying a server ID
    Use the original certifier to recertify a server ID that has a certificate that is about to expire.
  - Uninstalling a Domino® partitioned server
    You can remove all server partitions from a computer or you can remove just one server partition.
  - Reinstalling or moving a Domino® server from one computer to another
    Use this procedure to reinstall a server if an error occurs and the installer does not complete during the install of an incremental installer, or if the Domino® server is crashing and troubleshooting does not reveal the root cause.
  - Transaction logging
    Domino® transaction logging captures changes made to a database and writes them to a transaction log. The logged transactions are then written to disk in a batch, either when resources are available or when scheduled.
  - Installing and running NSD as a Microsoft™ Windows™ service
    Installing and running NSD as a Microsoft Windows service is no longer available as of Domino 10.
  - Setting up a Fault Reports database
    The Notes/Domino Fault Reports database stores data that is collected at the time of a server crash. Data is collected from both the client and the server and can then be used to measure client reliability and determine the areas where problems exist.
  - Client and server diagnostics
    Use these tasks to perform client and server diagnostics to collect diagnostic information after a server or client crash.
  - Collecting diagnostic information after a server or client crash
    The automatic diagnostic collection tool collects diagnostic data after server and client crashes and sends the collected data to a mail-in database when the server or client restarts. You can then use the collected data to determine the cause of the crash.
    - Writing status bar history to a log file
      You can use the NOTES.INI setting LOGSTATUSBAR=1 to enable logging of status bar messages to the local log file, LOG.NSF. You can then use the information that is written to the log file to assist you when troubleshooting problems.
    - Setting up automatic diagnostic data collection on clients
      Use the desktop policy settings document to set up automatic diagnostic data collection on clients.
    - Setting up automatic diagnostic data collection on the server
      Use the Server Configuration document to set up automatic diagnostic data collection on the server. You can also enable or disable Fault Analyses from this same tab in the Server Configuration Settings document.
    - Enabling the Fault Analyzer task on the server
      You can complete this task at the same time that you set up automatic diagnostic data collection. Use the Server Configuration document to set up automatic diagnostic data collection on the server and to enable or disable Fault Analyses.
  - Using the IBM_TECHNICAL_SUPPORT directory
    The IBM_TECHNICAL_SUPPORT database contains data that has been collected using the Domino® Configuration Collector and the Automatic Diagnostic Data Collection tool. It also includes system information files and documents that have been exported from the Domino Directory and saved as .dxl documents using the Save command entered at the Domino server console.
  - The Domino® server log file (LOG.NSF)
    Every Domino® server has a log file (LOG.NSF) that reports all server activity and provides detailed information about databases and users on the server. The log file is created automatically when you start a server for the first time.
  - Controlling the size of the log file
    By default, the log file (LOG.NSF) records information about the Domino® system.
  - The Domino® Web server log (DOMLOG.NSF)
    You can log your server activity and Web server requests to the Domino® Web server log (DOMLOG.NSF) database. This option may be preferable if you want to create views and view data in different ways.
  - Using console log mirroring
    Console log mirroring causes a new server thread to be created which monitors all messages written to the Console Log file and duplicates these messages into another file. When this new file is filled, the thread closes the mirrored file and creates a new file into which subsequent messages are written. You can delete the closed mirrored files at your discretion.
  - Using the Domino® Configuration Tuner to evaluate server settings
    The Domino® Configuration Tuner (DCT) evaluates server settings according to a growing catalog of best practices. All servers in a single domain can be evaluated together. DCT generates reports that explain the issues DCT uncovers, suggests mitigations, and provides references to supporting publications.
  - Activity Logging
    You use activity logging to collect information about the activity in your enterprise. You can use this information to charge users for the amount they use your system, monitor usage, conduct resource planning, and determine if clustering would improve the efficiency of your system.
  - Managing a cluster
    After you have set up a cluster, you can perform tasks to manage it.
- Managing databases
  Topics in this section describe how to set up and manage Domino® databases.

Enabling the Fault Analyzer task on the server

You can complete this task at the same time that you set up automatic diagnostic data collection. Use the Server Configuration document to set up automatic diagnostic data collection on the server and to enable or disable Fault Analyses.

Procedure

From the Domino® Administrator, click the Configuration tab.
Click Server > Configurations.
Select the Server Configuration document you want to edit and click Edit Configuration.

Click the Diagnostics tab and then complete these fields.

Table 1. Fault Analyzer task options
Field	Action
Run Fault Analyzer on Fault databases on this server	Choose one: Yes -- Enables the Fault Analyzer task on this server. No -- Disables the Fault Analyzer task on this server.
Run Fault Analyzer on	Choose one: All mail-in databases on this server -- Fault Analyzer runs on all mail-in database on this server. Fault Report documents may be posted to any mail-in database on the server. Specific mail-in database -- Specify the mail-in database on which you want Fault Analyzer to run. Fault Reports documents will be posted to this database.
Databases to run Fault Analyzer against?	Specify the databases against which you want Fault Analyzer to run. The Fault Analyzer task searches these database for Fault Report documents and determines whether the stack matches a crash that has already been seen by a user or server at that customer site.
Remove attachments for duplicate faults	If Fault Analyzer locates duplicate fault reports, the new crash is reported as a response to the original crash and attachments are either removed from the response document to save space in the database, or they are saved with the response document. Choose one: Yes -- Attachments are removed from the response document to save space in the database No -- Attachments are saved with the response document.

Click Save and Close.