Roaming user considerations

When configuring Notes® roaming users, be aware of the list of concerns and limitations listed here. In addition, see the roaming user considerations in the HCL Support Site.

• Enabling and re-enabling roaming user status on the fly in poor connectivity environments

  Users working with a slow Internet connection can temporarily disable their roaming status to more quickly access a target Notes® application, view, or document, including their Mail inbox. Roaming user status can also be set to remain disabled or be re-enabled at subsequent Notes® start-up. See article Disabling and re-enabling Notes roaming user status on the fly for details.

• File server roaming is not supported with the Notes® client basic configuration

  The file server roaming feature is not supported with Notes® client basic configuration or with a configuration that includes both the Notes® client basic and standard configurations. If your configuration includes clients with Notes® basic and other clients with Notes® standard configuration, only Domino® server roaming can be used in that configuration. File server roaming is supported only with the Notes® client standard configuration.

• Notes® opens tabs for nonexistent applications

  When a roaming user creates and opens a local database or a Symphony® document on one computer, the tabs for those applications roam to the second computer via replication on client shutdown. If the local database or Symphony® document does not exist on the second computer, the fields on the tab are empty or a dialog box displays asking you to choose the server. This is a display-related issue only.

• Downgrade from roaming user on second client generates request to update roaming user state

  When a user is upgraded to file server roaming on multiple computers by applying a roaming policy, a subsequent downgrade from roaming produces another administration process request to update the roaming user state in the Person document for every roamed computer. After the first request is processed, that is, the roaming state in the Person document is updated, the Person document is not updated again.

• Roaming rollout suggestions:
  Some rollout best practices are as follows:

  • Roll-out users progressively
  • Know that enabling roaming could have an immediate load on servers. Assigning a large set of users or groups to a roaming policy can result an immediate load on the roaming server.
  • Only re-enable roaming after roaming has been disabled on all of the user's computers
  • In the case of File Server roaming, ensure all user computers can access the targeted file server using the correct credentials or going though a firewall.
• Roaming server and home server names must match Domino® server name

  he roaming system expects the roaming server and the user's home server computer name (network name) to be the same as the Domino® server name. If this is not done, roaming users will encounter an error message when attempting to enable the second computer for roaming.