Move person's name in hierarchy

Triggered by: Choosing Actions - Rename Person then Request Move to New Certifier in the Domino Directory or by choosing People - Rename from the tools pane of the Domino Administrator.

Carried out on: The server from which you choose Actions - Complete Move.

Carried out: When you choose Actions - Complete Move, in the Name Move Requests view of the Administration Requests database, to move a person's name to another hierarchy.

Result: Approves the move and triggers the "Initiate rename in Domino Directory" request.

Triggered by: Choosing a rename action.

Carried out on: The administration server for the Domino Directory.

Carried out: According to the "Interval" setting for the Administration Process in the Server document.

Result: Adds the new name, certificate, and change request to the user's Person document. Prompts the user to accept the new name upon next server authentication.

Note By default, the new name is accepted automatically upon next server authentication.

Triggered by: Person accessing a server and accepting the new name.

Carried out on: The administration server for the Domino Directory.

Carried out: According to the "Interval" setting for the Administration Process in the Server document.

Result: Updates the person's name in the Domino Directory -- except for Person documents other than those belonging to the user. Posts the "Rename in Person documents" and the "Rename person in Unread Lists" administration requests.

Triggered by: Completion of the "Rename person in Domino Directory" request.

Carried out on: The administration server for the Domino Directory.

Carried out: According to the "Execute once a day requests at" setting for the Administration Process in the Server document.

Result: Updates the user's name if it appears in Domino Directory Person documents. For example, if the user is an administrator, the name may appear in the Owner or Administrator field of another user's Person document.

Triggered by: Completion of the "Rename person in Domino Directory" request.

Carried out on: Each server in the domain.

Carried out: According to the "Execute once a day requests at" setting for the Administration Process in the Server document.

Result: Each server in the domain examines every database on the server and updates the person's name in any unread lists.

Triggered by: Completion of the "Rename person in Domino Directory" request.

Carried out on: Each server in the domain.

Carried out: According to the "Interval" setting for the Administration Process in the Server document.

Result: Each server in the domain updates the person's name in ACLs of databases for which it is an administration server. In Domino 6 only, also updates the name in shared folders, views, agents and forms.

Triggered by: Completion of the "Rename in Access Control Lists" request on the administration server for the Domino Directory.

Carried out on: Each server in the domain.

Carried out: According to the "Delayed Request Settings" on the Server Tasks -- Administration Process tab in the Server document.

Result: Each server in the domain updates the person's name is in shared Design Elements of databases for which it is an administration server. Private design elements are not renamed.

Triggered by: Completion of the "Rename person in Domino Directory" request.

Carried out on: The person's home server.

Carried out: Immediately

Result: The person's name is changed in the Calendaring and Scheduling Free Time Database.

Triggered by: Completion of the "Rename person in Free Time Database" request.

Carried out on: The person's home server.

Carried out: Immediately

Result: The person's name is changed in their mail file's Calendar Profile and appointment documents. If the person's common name was changed and the common name is in the title of the mail file, the mail file title changes to reflect the new name. If the person is the "chair person" of any future meetings, the name is changed in those appointment documents.

Triggered by: Completion of the "Rename in Person documents" request on the administration server for the Domino Directory.

Carried out on: Each server in the domain.

Carried out: According to the "Delayed Request" setting for the Administration Process in the Server document.

Result: Each server in the domain updates the person's name in Reader / Author fields of databases for which it is an administration server and that have the advanced ACL option "Modify all Reader / Author fields" selected.

Triggered by: Expiration of the period in which a person can accept a new name, by default 21 days. When you rename the person, you can change the expiration period.

Carried out on: The administration server for the Domino Directory.

Carried out: According to the "Execute once a day requests at" setting for the Administration Process in the Server document.

Result: The Administration Process deletes the word "Pending" from the Change Request field from the Person document.

If the Domino server and the Notes client are both Notes Domino 6.0 or more recent, the user is not prompted to accept the name change, unless the user has requested to be prompted to accept. (To be prompted to accept a name change, the user must set that preference using the Security settings in the Notes client.

See also

Rename person - name change refused
Rename person - Cross domain administration request
Managing users
Rename Web user
Approve person's name change request
Administration process requests

Glossary