Note that the language for installation instructions is determined by your Microsoft Office installation locale. Supported languages for the add-in include:
- Spanish (continental)
Step 1: Install the Barracuda Email Security Gateway Outlook Add-In Deployment Kit
- Log into your Barracuda Email Security Gateway as an administrator.
- Navigate to USERS > User Features.
- Download the Outlook Add-In Deployment Kit.
- Extract the contents somewhere easily accessible. It should contain:
- Installer for the add-in for Outlook 64-bit (BsfOutlookAddIn-version_x64.msi) for Outlook 2010 and 2013.
- Installer for the add-in for all other versions of Outlook (BsfOutlookAddIn-version_x86.msi).
- The administrator module for the add-in (Barracuda Email Security Gateway Outlook Add-In version.adm).
- Move (or copy) the file ending in .adm to your local %systemroot%\inf, directory. Typically, this will be: C:\Windows.
Copy the .msi file(s) to a location that is accessible by your user.
- Open the GPO Editor for whichever organization will be using the add-in (e.g. the default domain policy).
- 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.
- Expand User Configuration.
- Right-click on Administrative Templates, select All Tasks, then Add/Remove Templates.
- Navigate to %systemroot%\inf, select Barracuda Email Security Gateway Outlook Add-In<version#>.adm, and press Add….
Step 2: Configure the Add-In
- While still in the GPO Editor, go to User Configuration\Administrative Templates and expand the Barracuda node that should now be visible.
- Click on Email Security Gateway.
- Click on Barracuda Email Security Gateway Outlook Add-In version.
- Configure settings as required. For an explanation of the available settings, click the Explain tab of the policy.
Step 3: Deploy the MSI
- Start the Group Policy Editor for the domain for which you'll be installing the add-in.
- 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.
- Navigate to Computer Configuration/Software Settings/Software Installation.
- Right-click on Software Installation and select New/Package…. Enter the UNC path to the MSI located in the shared folder.
- 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:
- Go the deployment tab for the 32-bit package.
- Click the Advanced… button, and uncheck the Make this 32-bit x86 application available to Win64 machines option.
- 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:
- Apply the policy you created in the above steps to only those computers that were targeted for the installation of 32-bit Outlook.
- 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:
- Manually create and populate these AD containers and then perform the steps in Scenario #2 above.
- Consider installing Outlook 2010 32-bit on all computers (unless you have users that require the 64-bit capabilities of Office 64-bit)
- Manually install the correct version of the add-in on each of the machines.
- 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
- Remember that Group Policy updates can take several minutes to post. You can run
to perform an immediate update.
- Restart a computer that is joined to the domain.
- The add-in should be installed when you log in, and the policies you have configured should be applied.
Step 5: Troubleshooting
- 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.
- Additional error messages may be found in the Event Log on the domain computer.
- If the Event Log has no useful information, consider enabling verbose logging and restarting the computer.
- Additional information on fixing Group Policy issues can be found here: http://technet.microsoft.com/en-us/library/cc775423.aspxh