This article contains information on using the Mimecast for Outlook Configuration Tool to modify settings before deployment, including amending MSI files, configuring SQL settings, proxy updates, and upgrading in multi-user environments.
The Mimecast for Outlook Configuration Tool allows you to modify specific Mimecast for Outlook settings before deployment to end users, and is located here.
The configuration tool can only be used for configuring SQL settings.
Amending the MSI fileYou can amend the standard MSI file using the Mimecast for Outlook Configuration Tool, by using the following steps:
Install and UpdateThis tab shows various settings specific to the installer to be modified.
CommunicationThis tab allows you to configure whether or not a Proxy Server is in use. Additional Proxy Server settings can also be defined.
|
Service Settings
This tab defines the service account to be used as part of the installation. It also allows specific file and log size limits to be set.
| Service Account | Use the Network Service Account | Specifies the Network Service account used for running the Mimecast service. |
| Use a Custom Account | Customize the user account used for running the Mimecast service. | |
| Service Files | Max Log File Size | Specifies the maximum log file size. |
| Data Cache | Specifies the configurable size cache. | |
| Log Path | Specifies the server path for the log files. | |
| Max Log Rolls | Specifies the number of files to which the logs will roll once they have reached the maximum file size. | |
| Log Level | This dictates the level of logging. The options are: None, Error, Info, or Debug (default is set to Notices, Warnings and Errors). | |
| Option | Description | |
SQL Settings
This tab should be used when implementing Mimecast for Outlook in a Citrix / Terminal Server or roaming profile multi-user environment.
| Option | Description |
|---|---|
| Database Provider | Specify the database type you provide, either SQL Server or MySQL. |
| Connector Location (MySQL Only) | Specify the location of your MySQL Connector/NET location. |
| Data Source | Specify the IP Address or the SQL Server Hostname. |
| Initial Catalog | Specify "mimecast-mso". |
| User ID | Specify the SQL userid. |
| Password | Specify the SQL user's password. |
| Pool Size | 300 - Use the default setting unless instructed otherwise by Mimecast Support. |
| Admin User ID | Specify the user with administrator database permissions. |
| Admin Password | Specify the password of the user with administrator database permissions. |
| Create Database (Should be used AFTER the connection has been tested) | Initiates the database creation process. |
| Test Connection | Tests the connection to the SQL Server. |
Mimecast for Outlook Configuration Tool Files
Once the MSI is modified and saved, two files are generated:
- The new MSI
- A file with an MCX extension. This change file stores all the modifications made from the default settings. This file should be retained, as it can be useful in the future (e.g. upgrades, recreating the MSI, and making changes to the user's configurations after deployment). Administrators can also view or change the MCX files in the Configuration tool. If you select View Change File, you can see a list of the changes made to the default MSI file. Alternatively, administrators can open the MSI file and apply the changes to that file or apply an MCX file directly by clicking on the File | Apply Change File menu item.
Upgrading Mimecast for Outlook in a Multi-User Environment
Ensure that every time you upgrade Mimecast for Outlook in a multi-user environment, you perform the following:
- Populate the SQL data in the Mimecast for Outlook Configuration Tool.
- Click the Create Database button. This validates if a database upgrade is required and completes the upgrade of the database version if needed. A log file is created in the configuration tool folder detailing completed actions.
Proxy Updates
If proxy settings are updated, a new custom MSI must be generated using the configuration tool. It is unnecessary to reinstall the full application, as only the settings.mcx file is affected. The file must be overwritten on the machines where the settings must be changed. Ensure that:
- The file name is settings.mcx
- msddsk.exe process is restarted or the machine rebooted for the new settings to take effect.
- The file path is similar to [Installation directory]\Mimecast\Mimecast Windows Service\]
Comments
Please sign in to leave a comment.