Deleting a Notes® roaming user
You can delete a roaming user in Domino® Administrator just as you would delete any user name. When you delete a roaming user, multiple administration requests are generated.
Delete Person in Domino® Directory
Triggered by: Choosing in the Domino® Directory (or clicking Delete Person) and choosing to delay deletion of the name from the Domino® Directory.
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: The Administration Process removes the name from the Domino® Directory, except from other people's Person documents, and posts the Delete in Person documents request. If you have created a termination group and set up the administration process to add deleted users to that group, the name is added to that group.
Delete in Person Documents
Triggered by: Completion of a Delete 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 Domino® Directory.
Result: The Administration Process removes the name from other people's Person documents in the Domino® Directory.
Delete in Access Control Lists
Triggered by: Choosing to immediately delete all occurrences of the name from the Domino® Directory when initiating the Delete action or the completion of a Delete in Address Book request (if you chose to delay deletion of the name from the Domino® Directory).
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 deletes the name from the ACLs of databases for which it is an administration server.
Delete in Reader/Author fields
Triggered by: Completion of a Delete in Access Control Lists request on the administration server for the Domino® Directory (if you chose to immediately delete occurrences of the name from the Domino® Directory) or completion of a Delete in Person documents request (if you chose to delay deletion of the name from the Domino® Directory.
Carried out on: All servers in the domain.
Carried out: According to the Delayed Request settings for the Administration Process in the Server document. (Hourglass icon displays.)
Result: Each server in the domain deletes the name from 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. The server scans the databases for shared agents signed by the deleted person and for Private Design Elements (folders, views, agents) signed by the deleted person. Shared agents found are reported in the request's Response document. If Private Design Elements are found an Approve deletion of Private Design Elements administration request is posted.
Get Mail File Information for Deletion
This is generated once, to begin the deletion of the user's mail file.
Triggered by: Completion of the Delete in Access Control List request on the administration server for the Domino® Directory (if you chose to immediately delete all occurrences of the name) or completion of the Delete in Domino Directory request (if you chose to delay deleting the name from the Domino® Directory). You must also have specified to delete the mail file in which you chose to delete the person. You must have selected the option to delete the person's mail file.
Carried out on: The user's mail server.
Carried out: According to the Interval setting in the Administration Process section of the Server document.
Result: An Approve Mail File Deletion request is generated and appears on the Pending Administrator Approval view of the Administration Requests database.
Get Replica Information for Deletion
This is generated three times, once for each of these files: journal.nsf, bookmark.nsf and names.nsf.
Triggered by: This request is generated upon completion of the Delete in Access Control List administration request (if you chose to immediately delete all occurrences of the name) or completion of the Delete in Domino Directory request (if you chose to delay deleting the name from the Domino® Directory).
Carried out on: Server specified as the roaming server, which is the server on which the roaming files are stored.
Carried out: Immediately
Result: An Approve File Deletion request is generated and appears on the Pending Administrator Approval view of the Administration Requests database.
Approve Mail File Deletion
This is generated once.
Triggered by: Completion of the Get Mail File for Deletion request.
Carried out on: The user's home server.
Carried out: When you manually approve or reject this request.
Result: If you approve the request, the Administration Process creates a Request Mail File Deletion request.
Approve Replica Deletion
This is generated three times.
Triggered by: Completion of the Get Replica Information for Deletion request.
Carried out on: Server specified as the roaming server, that is, the server on which the roaming files are stored.
Carried out: When you manually approve or reject this request.
Result: If you approve the request, the Administration Process creates a Request Replica Deletion request.
Request Mail File Deletion
Triggered by: Approving the Approve Mail File Deletion request.
Carried out on: The user's home server.
Carried out: Immediately
Result: Posts a Delete Mail File request.
Request Replica Deletion
This request is generated three times, once for each of these files: journal.nsf, bookmark.nsf and names.nsf.
Triggered by: Approving the Approve Replica Deletion request.
Carried out on: The administration server for the Domino® Directory.
Carried out: Immediately
Result: Posts a Delete Replica request.
Delete Mail File
Triggered by: Completion of the Request Mail File Deletion request.
Carried out on: The user's home mail server.
Carried out: According to the Interval setting for the Administration Process in the Server document.
Result: The Administration Process verifies that the administrator who approved the deletion has at least Author with Delete documents access to the Domino® Directory. Then the Administration Process deletes the file
Delete Replica
This request is generated three times, once for each of these files: journal.nsf, bookmark.nsf and names.nsf.
Triggered by: Completion of the Request Replica Deletion request.
Carried out on: Server specified as the roaming server, which is the server on which the roaming files are stored.
Carried out: According to the Interval setting for the Administration Process in the Server document.
Result: The Administration Process verifies that the administrator who approved the deletion has at least Author with Delete documents access to the Domino® Directory. The Administration Process deletes the file.
If the user has created Private Design Elements, the Approve Deletion of Private Design Elements, Request to Delete Private Design Elements, and Delete Private Design Elements requests are generated and processed.
The administration requests that locate and delete replicas are repeated until all replicas of roaming user files are deleted. These requests are the Get Replica Information for Deletion, Approve Replica for Deletion, Request Replica Deletion and Delete Replicarequests.