Configuring auto-processing of rename requests

You can configure the Administration Process to automatically process rename requests for users who have Notes IDs in the vault. This feature avoids the need for a user to authenticate with a Domino server from the Notes client to kick off rename processing.

About this task

This feature, introduced in V12.0.1, is targeted for HCL iNotes and HCL Verse users. In Domino 12.0 and earlier versions, when the name of an iNotes user or Verse user changed, the user had to use the Notes client to authenticate with a Domino server to trigger the name change processing. V12.0.1 avoids this requirement by using a new database Admin Q (or "Admin Quick") (adminq.nsf) to watch for and process rename requests automatically.

To enable the feature, set the following notes.ini setting on the administration server for the domain:


The following optional notes.ini settings are available. All must be set on the administration server for the domain.
  • ADMINQ_POLLING_SECS=<seconds>. Use this to change how frequently AdminP checks adminq.nsf for "Needs Processing" requests. Default is 3600 seconds (one hour).
  • ADMINQ_WEB_ONLY=0. Use to apply the feature to Notes client users, too. By default, the feature applies only to iNotes and Verse users.
  • DEBUG_ADMINQ_RENAME=1. Use to enable debugging for this feature.


When auto processing of rename requests is enabled, the following steps occur automatically.
  1. The Administration Process (AdminP) creates the database "Admin Q" (adminq.nsf) from the adminq.ntf template.
  2. When the "Delete Obsolete Change Requests" request runs each night, AdminP searches the Domino directory for unexpired "Initiate Rename in Domino Directory" requests. These requests are generated immediately after a rename request and indicate that the user whose name is being changed has not authenticated with Domino from the Notes client to kick off the rename processing.
  3. When AdminP finds an unexpired "Initiate Rename in Domino Directory" request, it creates an entry for the user being renamed in the adminq database and sets its state to "Needs Processing."
  4. A new AdminP thread looks every hour for "Needs Processing" requests. When it finds one, it updates the associated user's ID in the ID vault. This step is equivalent to the user logging in with the Notes client and causing the ID file to synchronize with the ID vault.
  5. After the ID is updated in the ID vault, AdminP changes the state of the entry in adminq.nsf to "Processed." "Processed" entries are purged every eight days. If the ID update fails, the entry is updated with error information, retried, and purged after 90 days.
  6. AdminP generates a "Rename Person in Domino Directory" request to kick off the usual rename request flow.