Rename person - Cross domain administration request
You can use the Administration Process to rename (upgrade) a flat user name to a hierarchical user name, change the person's common name, or move a user to new organizational hierarchy.
Rename person - outbound (source) domain
The following requests are generated on the outbound (source) domain.
Initiate® rename in Domino® Directory
Triggered by: Selecting the person, and choosing Domino® Administrator, and then choosing Upgrade to Hierarchical.
on the tools pane in theCarried 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: Writes the Change Request and new public key to the Domino® Directory.
Rename person in Domino® Directory
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 in Person documents. Recognizes the Cross Domain Configuration Document and checks for appropriate signatures and access. Mails the request to the inbound domain. Posts the Rename in Access Control List, Rename in unread list, and the Rename in Free Time database requests.
Rename in Person document
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 name in Domino® Directory Person documents. Posts the Rename in Reader / Author Fields administration request.
Rename in Access Control List
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.
Rename in Free Time database
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. Posts the Rename in Calendar entries and Profile administration request.
Rename in unread list
Triggered by: Completion of the Initiate rename in Domino Directory request.
Carried out on: Every server in the domain.
Carried out: According to the Execute once a day requests at setting for the Administration Process in the Domino® Directory.
Result: If an Unread List is located for the old name, the Unread List is then stored with the person's new name.
Rename person in calendar entries and profiles in mail file
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. The name is also changed if it exists in the Chair field of future meeting invitations.
Rename in Reader / Author fields
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 Readers and Authors fields of databases for which it is an administration server and that have the advanced ACL option Modify all Readers and Authors fields selected.
Rename person - Inbound (destination) domain
The following requests are generated on the inbound domain.
Rename person in Domino® Directory
Triggered by: Receipt of the request from the outbound domain.
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 in Person documents. Posts a Rename in Person document request.
Rename in Person documents
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 name in Domino® Directory Person documents.
Rename in Access Control List
Triggered by: Completion of the Rename person in Domino Directoryrequest.
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.
Rename in unread lists
Triggered by: Completion of the Rename person in Domino Directory request.
Carried out on: Every server in the domain.
Carried out: According to the Execute once a day requests at setting in the Administration Process section of the Server document.
Result: If an Unread List for the old name is found in the database, a copy of the Unread List is stored with the new name. Each server in the domain examines every database on the server and updates the person's name in any unread lists.
Rename in Reader/Author fields
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 Readers and Authors fields of databases for which it is an administration server and that have the advanced ACL option Modify all Readers and Authors fields selected.