We use cookies on our website to ensure we provide you with the best experience on our website. By using our website, you agree to the use of cookies for analytics and personalized content.This website uses cookies. More Information
It seems like your browser didn't download the required fonts. Please revise your security settings and try again.

Barracuda Email Security Gateway

Barracuda Outlook Add-In Deployment Guide 5.x

  • Last updated on

Note that the language for installation instructions is determined by your Microsoft Office installation locale. Supported languages for the add-in include:

  • English
  • Spanish (continental)
  • French
  • Japanese
  • Dutch
  • Italian
  • Chinese
  • Polish
  • German

Step 1: Install the Barracuda Email Security Gateway Outlook Add-In Deployment Kit

  1. Log into your Barracuda Email Security Gateway as an administrator.
  2. Navigate to USERS > User Features.
  3. Download the Outlook Add-In Deployment Kit.
  4. Extract the contents somewhere easily accessible. It should contain:
    1. Installer for the add-in for Outlook 64-bit (BsfOutlookAddIn-version_x64.msi) for Outlook 2010 and 2013.
    2. Installer for the add-in for all other versions of Outlook (BsfOutlookAddIn-version_x86.msi).
    3. The administrator module for the add-in (Barracuda Email Security Gateway Outlook Add-In version.adm).
  5. Move (or copy) the file ending in .adm to your local %systemroot%\inf, directory. Typically, this will be: C:\Windows.
  6. Copy the .msi file(s) to a location that is accessible by your user.

    If you do not already have a network share for GPO software deployment, you'll need to create one. The share should be accessible from all the machines that the software will be deployed to. The permissions for the share should give read access to the "Everyone" group, and the permissions for the underlying NTFS folder should give read access to the "Authenticated Users" group. The software will be installed by the machines themselves rather than by users, and machines are not members of the "Everyone" group, so this modification to the default permissions is required.

  7. Open the GPO Editor for whichever organization will be using the add-in (e.g. the default domain policy).
  8. Either edit the default policy or create a new policy object, then link it to the desired container; for example, the particular OU containing the computers on which the add-in will be installed.
  9. Expand User Configuration.
  10. Right-click on Administrative Templates, select All Tasks, then Add/Remove Templates.
  11. Navigate to %systemroot%\inf, select Barracuda Email Security Gateway Outlook Add-In<version#>.adm, and press Add….

Step 2: Configure the Add-In

  1. While still in the GPO Editor, go to User Configuration\Administrative Templates and expand the Barracuda node that should now be visible.
  2. Click on Email Security Gateway.
  3. Click on Barracuda Email Security Gateway Outlook Add-In version.
  4. Configure settings as required. For an explanation of the available settings, click the Explain tab of the policy.

Step 3: Deploy the MSI

  1. Start the Group Policy Editor for the domain for which you'll be installing the add-in.
  2. Either edit the default policy or create a new policy object, then link it to the desired container; for example, the particular OU containing the computers of users that should have the add-in. Please note that the software deployment policy must be for computers, not users.
  3. Navigate to Computer Configuration/Software Settings/Software Installation.
  4. Right-click on Software Installation and select New/Package…. Enter the UNC path to the MSI located in the shared folder.
  5. Click OK.

Support for Outlook 64-bit (2010 and 2013)

If you have both 32-bit and 64-bit machines in your environment, but none of the 64-bit machines are running Outlook 64-bit, then the x86 version of the MSI is the recommended version to use and is what is deployed by default to all 32-bit as well as 64-bit machines. However, if there are some 64-bit machines that do have Outlook 64-bit installed, then there are 3 possible scenarios:

Scenario 1: Every 64-bit machine in your environment has Outlook 64-bit installed. In this case, perform all of the following steps:

    1. Go the deployment tab for the 32-bit package.
    2. Click the Advanced… button, and uncheck the Make this 32-bit x86 application available to Win64 machines option.
    3. Repeat steps 3.1 - 3.5 for the 64-bit MSI.

The 32-bit MSI will now be deployed only to 32-bit machines, while the
64-bit MSI will be deployed only to 64-bit machines.

Scenario 2: Some 64-bit machines in your environment have Outlook 64-bit installed while others have the 32-bit versions of various other Outlook versions on them, and Outlook was installed through a GPO. In this case, perform all of the following steps:

    1. Apply the policy you created in the above steps to only those computers that were targeted for the installation of 32-bit Outlook.
    2. Repeat steps 3.1 - 3.5 for the 64-bit MSI, and apply this second policy to only those computers that were targeted for the installation of Outlook 64-bit.

The 64-bit MSI will only be installed on those computers with Outlook 64-bit installed, while the 32-bit add-in will be installed for all other computers to which the policy has been applied.

Scenario 3: The 64-bit machines in your environment have a mixture of Outlook 2010 and 2013 64-bit and other 32-bit versions of Outlook installed, but there are no existing AD containers that specify which of those computers have Outlook 64-bit on them. In this case, perform only one of the following steps:

    1. Manually create and populate these AD containers and then perform the steps in Scenario #2 above.
    2. Consider installing Outlook 2010 32-bit on all computers (unless you have users that require the 64-bit capabilities of Office 64-bit)
    3. Manually install the correct version of the add-in on each of the machines.
    4. Allow your users to install the correct version of the add-in installer for themselves (they must have administrative privileges on their computers).

Step 4: Testing

  1. Remember that Group Policy updates can take several minutes to post. You can run
    gpupdate /force
    to perform an immediate update.
  2. Restart a computer that is joined to the domain.
  3. The add-in should be installed when you log in, and the policies you have configured should be applied.

Step 5: Troubleshooting

  1. A common cause of failure is the user and/or the user's computer does not have adequate access to the share location. Verify that that all access and network privileges have been configured appropriately.
  2. Additional error messages may be found in the Event Log on the domain computer.
  3. If the Event Log has no useful information, consider enabling verbose logging and restarting the computer.
  4. Additional information on fixing Group Policy issues can be found here: http://technet.microsoft.com/en-us/library/cc775423.aspxh

 

Last updated on