This article contains information on Mimecast for Outlook deployment options, including standalone installation, group policy, managed deployment, and multi-user environments, with advantages, disadvantages, and configuration steps for each method.
Mimecast for Outlook supports deployment in both standalone and multi-user environments.
Standalone Installation
Mimecast for Outlook can be downloaded and installed directly on the user's workstation. You can also create a network installation point, and copy the installer onto the network share. You can Install Standalone or Install with SCCM.
| Advantages | Disadvantages |
|---|---|
|
|
Group Policy
Administrators can use Group Policy scripts to deploy Mimecast for Outlook to many workstations.
| Advantages | Disadvantages |
|---|---|
|
|
Managed Deployment
Mimecast for Outlook can be deployed to many workstations at the same time using a centralized deployment tool (e.g. Install with SCCM or Microsoft InTune).
Mimecast does not provide direct assistance for deployments through third-party management tools, and any installation issues with these methods would require contacting Microsoft support.
| Advantages | Disadvantages |
|---|---|
|
|
Multi User Environments
Mimecast for Outlook can be deployed to multi-user environments (e.g. Citrix, Terminal Services). This reduces the administrative overhead of Mimecast for Outlook deployment. An SQL server is required as a backend to store the end user's profiles.
AppV is not supported for use with Mimecast for Outlook.
| Advantages | Disadvantages |
|---|---|
|
|
Comments
Please sign in to leave a comment.