To move a roaming user's files, from the Domino Administrator choose People & Groups, People - Tools - Move.
If the destination server to which you are moving the roaming user files is not in the Local domain, the "Promote new roaming server's access" request is generated as the second request in the series. Otherwise, the "Promote New Roaming Server's Access" is not generated.
Move roaming files administration requests
Check Roaming Server's Access
Carried out on: The server on which the user's roaming files reside.
Carried out: Immediately
Result: Checks for a Connection document between the old and new roaming servers and sets up the ACLs so that the old and new roaming servers have Manager access.
This administration request is generated if the server to which you are moving the user's files does not have access to the roaming files.
Carried out on: The administration server of the Domino Directory.
Carried out: Immediately.
Result: Sets up the ACLs to give the old and new roaming servers Manager access. Posts a "Create Roaming User's replica" administration request. Changes the administration server of the roaming files to the destination roaming server.
This request is generated one time. It creates three replicas, one for journal.nsf, one for bookmark.nsf, and one for names.nsf.
Carried out on: User's roaming server.
Result: Pushes the three databases to the new replicas on the destination server. Posts the "Monitor roaming server's field in Person record" request.
Carried out on: Destination server to which the roaming user files are being moved.
Result: Recognizes the update to the Person record and posts the "Replace roaming server's field in Person record request.
Carried out on: Administration server for the Domino Directory only.
Result: New roaming server information is added to the Roaming Server field on the Basics tab of the Person document.
This request is generated three times, once each for journal.nsf, bookmark.nsf, and names.nsf.
Carried out on: The original roaming server.
Result: Pushes the last set of changes to the new Roaming Server. Initiates the "Get Replica Information for Deletion" administration request.
Carried out: According to the "Interval" setting in the Administration Process section of the Server document.
Result: Gathers the replica ID of each of the roaming files and posts the "Approve replica deletion" administration request.
Carried out on: Any server.
Carried out: According to the administrator's discretion, that is, when the administrator approves the deletion.
Result: Posts the "Request replica deletion" administration request.
Result: Posts the "Delete replica" administration request.
Carried out on: Deletes the replicas on the old roaming server.
Result: The replicas are deleted from the old roaming server.
Check mail server's access
Carried out on: Home server for the mail file as designated in the Person document.
Result: Checks for a Connection document between the old and new mail file servers, and sets up the ACL to provide the old and new mail servers with Manager access. Posts the "Create new mail file replica" request.
Carried out on: The administration server for the mail file.
Result: Creates a replica copy of the old mail file on the new mail server. Posts the "Add new mail file fields" administration request.
Carried out on: The administration server for the Domino Directory.
Result: Creates a "New mail file" field and an "Old mail file" field in the Person document. Posts the "Monitor new mail file fields" request.
Carried out on: The new mail server.
Carried out: When the router recognizes the new mail server for the mail file.
Result: Verifies that new fields are added to the Person document on the new mail server and that the router can route mail to the new server. Posts the "Replace mail file fields" administration request.
Result: New mail server information is added to the fields. Removes "New" fields from the Person document. Places "Old Mail File" and "Old Mail Server" fields in the Person document. The server sets a flag in the Person document to update the client.
Carried out on: The home mail server.
Result: Pushes the last set of changes and mail to the new mail file. Posts the "Get mail file information for deletion" administration request.
Carried out on: The old mail server.
Result: Locates the replica ID of the mail file and posts the "Approve mail file deletion" administration request.
Carried out: When you manually approve or reject the request in the administration requests database.
Result: Posts the "Request file deletion" administration request.
Result: Posts the "Delete mail file" administration request.
Carried out on: The original mail server.
Result: The old mail file is deleted from the original mail server.