Mimecast for Outlook - Installing with SCCM

Updated

This article contains information on deploying Mimecast for Outlook using SCCM, including prerequisites, packaging the .MSI and .NET Framework, adding packages to distribution points, monitoring distribution, and step-by-step installation on client devices.

Knowledge of implementing via SCCM is essential before installing Mimecast for Outlook using the steps below.

Prerequisites

Read Prerequisites.

Installation Notes

  • Mimecast for Outlook has not been exhaustively tested with all other third-party applications.
  • Mimecast cannot guarantee compatibility with all Microsoft Outlook add-ons.
  • The Mimecast for Outlook installer automatically upgrades over previous versions. There is no need to uninstall older versions.
  • Ensure that a support version of Microsoft .NET Framework is installed on all workstations.
  • Microsoft Outlook must be closed for the installation to be successful.

Deploying Mimecast for Outlook Using SCCM

When deploying software using SCCM, the following steps must be completed:

  1. Packaging the .MSI software.
  2. Packaging the .NET framework.
  3. Adding the packages to the distribution points.
  4. Install Mimecast for Outlook on the client workstations.

The steps in the sections below assume that both the distribution points and installation clients have been configured. Although the major steps have been outlined, not all fields and options have been detailed.

Packaging the Mimecast for Outlook .MSI

Packaging the Mimecast for Outlook .MSI ensures the file is added to the SCCM database. Once there, it is available to be deployed to the client workstations.

You can package the Mimecast for Outlook .MSI, by using the following steps:

  1. Open the SCCM Console.
  2. Click on the Software Library tab.
  3. Navigate to Application Management | Applications and right click this option.
  4. Click on Create Application.
  5. Select the Automatically Detect Information About This Application From Installation Files option.
  6. Select the Windows Install option from the Application Type drop down.
  7. Set the Location by browsing to the Mimecast for Outlook MSI. This step imports the file into the SCCM database.

    When browsing to the .MSI file, ensure you use the full Universal Naming Convention (UNC) path of the shared installer package.

  8. Click on Next.
  9. Change the Name, General Information, and Installation Command fields as required.
  10. Click Next to complete the packaging of the Mimecast for Outlook .MSI into the SCCM database.

Packaging the .NET Framework

Packaging the .NET framework ensures the file is added to the SCCM database. Once there, it is available to be deployed to the client workstations.

You can package the .NET Framework, by using the following steps:

  1. Open the SCCM Console.
  2. Click on the Software Library tab.
  3. Navigate to Application Management | Applications and right click this option.
  4. Click on Create Application.
  5. Select the Manually Specify the Application Information option. This is required because the software is an .EXE file.
  6. Provide any other application detail (e.g. Name, Comments, Manufacturer).
  7. Leave the default values on the Application Catalog page.
  8. Click on Next.
  9. Click on Add.
  10. Select to Manually specify the deployment type information.
  11. Click on Next.
  12. Enter a Name and Description for the deployment type (e.g. Standard Install).
  13. Click on Next.
  14. Select the .NET Framework execution in the Content Location field by browsing for the file.
  15. Click on Next.
  16. Specify the command to run in the Installation Program field (e.g. "dotNetFx40_Full_x86_x64.exe").

    You can add the following switches to the install script:
    • To run a silent install - add /q
    • To prevent machines from restarted - add /norestart
    • To display the progress bar during installation - add /qb

  17. Click on Next.
    Platform Type Settings
    x86

    • Setting Type: File System
    • Type: File
    • Path:  %windir%\microsoft.net\framework\v4.0.30319\
    setupcache\extended
    • File or Folder Name: 1025
    x64

    • Setting Type: File System
    • Type: File
    • Path: %windir%\microsoft.net\framework64\v4.0.30319\
    setupcache\extended
    • File or Folder Name: 1025

    Click the Add Clause button. This allows you to add a clause needs to ensure that the .Net Framework and Mimecast for Outlook .MSI are installed. The best method is to use the File System Setting Type and Folder type. These are more consistent to verify .NET Framework's presence.

    The clause must be added twice to ensure that both x86 and x64 platforms are covered.

    The 1025 folder is a folder found in the locations above when .NET Framework 4 Extended has been installed.
    If this folder does not exist, SCCM will push .NET Framework 4 Extended as the prerequisite, prior to installing Mimecast for Outlook.

  18. Click on OK once the clauses have been added.
  19. Click on Next. The User Experience dialog is displayed.
  20. Complete the dialog as follows:
    Field / Option Description
    Installation Behavior Select the "Install for System" option.
    Logon Requirement Defines if the user needs to be logged on before installing the software.
    Installation Program Visibility Select the "Normal" option.
    Allow users to view and interact with the program installation Select this option.
  21. Click on OK to save your configuration settings.
  22. Click on OK to exit the application package properties.

Adding the Packages to the Distribution Points

To make the software available for install, it needs to be uploaded to the distribution point/s. This ensures that the software is moved to a server in the local region for the client workstations.

You can add the packages to the Distribution Points, by using the following steps:

  1. Right click the Application you've created.
  2. Click the Distribute Content menu item.
  3. Click Next until you see the "Content Destination" menu.
  4. Click the Add - Distribution Point Group menu item.
  5. Select the Distribution Location which applies.
  6. Click on OK. The locations are added to the list of Content Destination points.
  7. Click on Next.
  8. Click on Next to progress through the distribution of the software.
  9. Click on Next to complete the wizard.
  10. Click on Close to complete the distribution of the applications.

Monitoring the Software Distribution

You can monitor the software distribution, by using the following steps:

  1. Click the Monitoring tab.
  2. Go to Distribution Status - Content Status. This view displays all application packages and shows the status of whether they have been uploaded to the distribution points.

Installing Mimecast for Outlook

Once the software has been packaged and distributed to the distribution points, it can be installed on the client devices. Devices are grouped together in collections, based on either devices or users.

You can install the software, by using the following steps:

  1. Navigate to Assets and Compliance | Device Collections OR User Collections.
  2. Either:
    • Right click the Collection you wish to deploy the application to.
    • Right click the Application you wish to deploy, and click the Deploy - Application menu item.

      To add an individual machine, right click it and choose to add the machine to a new collection. This will only allow that machine to receive the application.

  1. Click the Browse button In the General dialog to select the appropriate Collection (or Software).
  2. Click on Next. The Content dialog displays the available Distribution Points.
  3. Click on Next. The Deployment Settings dialog is displayed.
  4. Specify how the software will be deployed:
    • Action: Set the software to Install.
    • Purpose: Provides options to install the software when the user chooses to (Available) or to install without the user's authorization (Required).
  1. Click on Next. The Scheduling dialog is displayed.
  2. Specify the i when the software should be installed, or if deploying immediately click Next.
  3. Select which User Notifications should be sent out.
  4. Click on Next.
  5. Configure if you wish to be alerted when the software installation fails.
  6. Click on Next through the Summary dialog.
  7. Click on Close, once you have navigated through the Progress and Completion dialogs.

Mimecast for Outlook is now installed on the workstation. The user will be prompted to close Microsoft Outlook if it is open, and if the appropriate switch is used in the Deployment Type Wizard as described above, a progress bar is displayed. Once the installation has been completed, Microsoft Outlook is automatically started.

To download the user settings as defined in the Application Settings definition, and start using Mimecast for Outlook, the client needs to authenticate with Mimecast.

Related to

Was this article helpful?
1 out of 2 found this helpful

Comments

0 comments

Please sign in to leave a comment.