Changes to roaming user functionality in Notes/Domino 8.5
Lotus Notes and Domino 8.5 bring about some changes to the Roaming user functionality which are cited in the technote, "Summary of changes to Roaming User functionality in Notes and Domino 8.5" (#1327275).
File server roaming
File server roaming is available starting in Notes/Domino 8.5 (Notes client standard configuration). To change a Notes client user to a file server roaming user, you create a Roaming settings policy document.
Refer to the technote Highlighting important information related to File Server Roaming in Notes and Domino 8.5 (#1329414) for information on file server roaming users.
Domino server roaming
When you (a Domino Administrator) change a Notes Client user from non-roaming to roaming, the Administration Process (AdminP) changes the user's status in their Person document from non-roaming to roaming. AdminP then creates a personal sub-directory for the roaming user. This personal sub-directory contains the roaming user's files and, by default, is placed in the \Data path on the Domino Server, unless you specify another location. You can optionally choose a separator character if you want to include one in the user's directory name.
You can use the Domino Administrator client to update a user from a non-roaming state to a roaming state by selecting the user and selecting People - Roaming from the Tools pane.
Detailed steps to change a non-roaming user to roaming:
1. In the Access Control List (ACL) of the Domino Directory ,ensure you have the following access:
- Editor with UserModifier access, or
- Author with Create documents role and UserModifier privilege
2. From the Domino Administrator, select the People & Groups tab.
3. Select one or more non-roaming user name(s).
4. From the Tools pane, select People - Roaming.
Note: If you selected a mixed group of roaming and non-roaming users, the Mixed Roaming Profile dialog box (shown below) appears and prompts you to select either roaming or non-roaming.
Select the option 'Assign Roaming Profiles to <n> Selected Users'. In this case, <n> is the number of non-roaming users selected.
5. The Domino Administrator client's Roaming Tool opens to the 'Assign Roaming User's dialog box.
In the 'Assign Roaming User's dialog box, complete the following fields:
*Please note: The Notes product help documentation contains the table above, and states in the table that you can optionally choose a separator character if you choose to change the default format of the "User's personal roaming folder" field. This is an incorrect statement.
6. Select OK. A message displays indicating the number of users successfully upgraded from non-roaming to roaming.
This procedure changes the user's status in their Person document from non-roaming to roaming. To verify that the change has been made:
1. From the Domino Administrator, select the People & Groups tab.
2. Select the user you promoted to roaming.
3. Click 'Edit Person' to open the user's Person document.
4. Click the Roaming tab. The 'User Can Roam' field should display "In Progress" or "Yes". The "In Progress" status displays until replication has occurred and all replicas of the user's files are updated.
When a user has been successfully set up to roam, a "blue globe" icon appears next to that user's name in the People view of the Domino Directory. If the upgrade is still "in progress" and awaiting the user's authentication with their roaming server in order to complete the upgrade, then a "grey hourglass" icon will appear next to the user's name in this view.
It should be noted here that if the roaming server is not the same as the primary server, then the AdminP requests to create replicas of roaming databases on the server for the user must be carried out on the roaming server and not the server initiating the AdminP requests. Therefore, these requests must be replicated via the Administration (Admin4.nsf) database to that server to be completed. Also, the status of these requests must then be replicated back via Admin4.nsf to the originating server for the upgrade procedure to continue. Because of this, a user may state that he/she is not seeing notification or prompt to upgrade immediately at his clients. If this is the case, the Domino Administrator should review the status of the AdminP requests on the servers in that user's environment.
The AdminP requests and results for an upgrade of a user to roaming are as follows, and can be viewed within Admin4.nsf in a view called "Requests\All Requests by Name":
Update Roaming User State in Person Document
(This is also known as Proxy Action 134.)
Update Client Information in the Person Record
(This is also known as Proxy Action 46.)
Create Roaming User's Replica Stubs
Update Roaming User Information in Person Record
Monitor Roaming Users Replica Stubs