Mimecast for Outlook - Roaming Profiles

This article contains information on using Mimecast for Outlook with roaming profiles, the impact of not using roaming profiles, transitioning from a central SQL server, and compatibility with SQL databases in multi-user environments. It also explains how roaming or server-side profile folder synchronization can affect Mimecast for Outlook authentication (including Single Sign-On (SSO)), and where key cache and log files are stored.

The following are included

• Authentication tokens.
• Message cache.
• Personal user settings.
• Roaming user profiles must be in use.
• The ..\AppData\Roaming folder must be included as part of this profile.
• Roaming profiles must be redirected to a network share. Mimecast for Outlook may be deployed without the use of the Configuration Tool if no customizations are required.
• If your environment uses server-side user profile folders or synchronization of application data (for example, a server path such as \\ServerName\UserProfiles\<username>), ensure that synchronization of the Mimecast application folder within the roaming profile (for example, %userprofile%\AppData\Roaming\Mimecast) is enabled and working. Failed or incomplete sync of this folder can affect cached authentication data and SSO behavior.

User Experience if Roaming Profiles Aren't Used

Mimecast strongly recommends operating within the outlined support requirements. The guidance below is provided as information regarding the consequences of operating outside the requirements.

Should Administrators deploy Mimecast for Outlook in a multi-user environment without deploying a centralized SQL database, where roaming user profiles are not in place, the following will be experienced:

• The cached authentication tokens will no longer be present, causing users to re-authenticate each time a new session is started.
• Personal user settings will be cleared.
• Active Large File Send uploads will be lost between sessions. These will not be listed in the Large File Send Manager.

Moving Away from Using a Central SQL Server

As the new deployment won't have access to the data stored in the SQL database, the cached authentication token won't be present. As such, users will be required to re-authenticate the first time they access Mimecast for Outlook. Personal settings (e.g. setting sort orders and view widths) will also be cleared.

Using an SQL Database With Roaming Profiles?

Mimecast for Outlook maintains backward compatibility. As such it can be used with an SQL Database if you are using roaming profiles. Deploy and configure Mimecast for Outlook by referring to Installing in a Multi User Environment.

Mimecast for Outlook Cache and Log Locations

In environments using roaming profiles or server-side profile folders, it may be necessary to review or reset cached authentication data and collect logs for troubleshooting.

• Cache and authentication files: Stored in the user’s roaming profile at %userprofile%\AppData\Roaming\Mimecast. To reset authentication, the following files are typically removed:

  • msw.s3db
  • mfo-<user>@<domain>.key

  Before removing these files, ensure Microsoft Outlook is closed and the msddsk.exe process is stopped.

• Log files: Mimecast for Outlook logs are located at %ProgramData%\Mimecast\Logs. Collect the most recent logs from this folder if further troubleshooting or support review is required.