Installing Mimecast for Outlook in a Multi User Environment

Document created by user.oxriBaJeN4 Employee on Sep 16, 2015Last modified by user.oxriBaJeN4 Employee on Oct 11, 2016
Version 8Show Document
  • View in full screen mode

This article outlines the considerations, guidance and steps to install Mimecast for Outlook in a multi-user environment (e.g. Terminal Services or Citrix).

 

For multi-user environments, instead of installing the Mimecast for Outlook application on the user's workstation, it is installed on the Citrix or Terminal Server. This allows multiple users to access the application. In these instances, a Microsoft SQL server or MySQL server may be required as a backend to store add-in data if persistent user profiles are not used.

For further information, and to check if you require a central SQL database, review the SQL Databases and Mimecast for Outlook article.

 

Prerequisites

 

For multi-user environments, the following applications prerequisites should be considered:

  • Read the Mimecast for Outlook: Prerequisites article.
  • Read the Mimecast for Outlook Configuration Tool article for more information on configuring the available settings.
  • The Mimecast for Outlook MSI package must be downloaded.
  • SQL Sever (if required):
    • Microsoft SQL Server 2008 or later to be installed. SQL Express is not supported.
    • or MySQL Community Server 5.6.21 or later to be installed.
  • Mixed Authentication mode (SQL & Windows Authentication) implemented.
  • LAN connectivity from the terminal server to the SQL Server is required.
  • The Configuration Tool requires the full version of the Microsoft .NET Framework 4.0 or later.
  • The "Allow Automatic Failover" option in the Continuity section of the Application Settings must be disabled.

 

MySQL Community Server guidance

The use of a MySQL server may not be required. First review the following article before proceeding: SQL Databases and Mimecast for Outlook.

 

Microsoft SQL Server Guidance

 

Create the Microsoft SQL Server Database

The use of a Microsoft SQL server may not be required. First review the following article before proceeding: SQL Databases and Mimecast for Outlook. 

Database upgrades are handled automatically. Customers should use the SQL Settings area of the Configuration Tool to connect to their database and create a custom MSI.

Prior to the installation of the Mimecast for Outlook application, a database needs to be created on the SQL server, and the Mimecast for Outlook MSI installer must be customized by the Mimecast for Outlook Configuration Tool to include the SQL specific connection string.

  1. Open the Mimecast for Outlook Configuration Tool.
  2. Click the File | Open menu item to load the Mimecast for Outlook installation MSI.
  3. Navigate to the SQL Settings section of the tool where the following settings need to be completed:

    Option
    Description
    Data SourceENTER IP ADDRESS OR HOSTNAME OF SQL SERVER HERE
    Initial Catalogmimecast-mso
    User IDENTER SQL USER ID HERE
    PasswordENTER SQL USER PASSWORD HERE
    Pool Size300

    Use the default Pool Size setting, unless instructed otherwise by Mimecast Support.

    Admin user IDEnter the account with Administrator database permissions
    Admin PasswordENTER DATABASE ADMINISTRATOR PASSWORD HERE
    Create DatabaseInitiates the database creation process:

    Test Connection

    (Should be used AFTER the database has been created)

    Tests the connection to the SQL Server:
  4. Click the File | Save As menu item to save a custom MSI installer containing the SQL Connection string to the database that has just been created. This is the installer that should be deployed into the multi user environment.

 

System Processes

 

For standalone installations, Mimecast for Outlook uses a user process called msddsk.exe. This simplifies deployments, as system based proxy settings are applied to Mimecast for Outlook traffic in the context of the logged in user. For multi tenant environments (e.g.Terminal Services / Citrix farms) this process is switched to a per machine process running as the Local System account (msdsrv.exe). In these environments, users share the resource.

2 people found this helpful

Attachments

    Outcomes