SQL Databases and Mimecast for Outlook

Document created by user.2oEIBdeQKn Expert on Jan 4, 2016Last modified by user.2oEIBdeQKn Expert on Jan 5, 2017
Version 7Show Document
  • View in full screen mode

From Mimecast for Outlook v6.2 Administrators can decide whether to utilize a SQL database with Mimecast for Outlook in multi user environments. Previous versions of Mimecast for Outlook required a centralized SQL database when deployed in environments such as Terminal Services and Citrix. This SQL database stored end user data including:

  • Authentication tokens.
  • Message cache.
  • Personal user settings.

 

From v6.2 Mimecast for Outlook changes the way end user data is stored. These changes allow for Mimecast for Outlook to be operated without the requirement for a central SQL database, when the prerequisites outlined below are met:

  • 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.

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 reauthenticate 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 following theInstalling Mimecast for Outlook in a multi-user environment page.

Attachments

    Outcomes