When the Outlook Add-In is installed, end users can access their archived emails directly from the Outlook application. ContentStore Email Viewer, which is included with Outlook Add-In, allows end users to access emails that have been content indexed.
Where to Install
-
Outlook Add-In can be installed on the end user's computer that has Outlook 2007 SP2 or later installed. However, the ContentStore Email Viewer plug-in is only supported by Outlook 2010 or later.
-
If you have Outlook 2007 SP2 installed and you want to install Outlook Add-In, follow the instructions mentioned in the following KB articles:
Before You Begin
-
For the CommCell environment:
-
A Web Server and the Web Console must be installed.
-
The Web Console computer must belong to the same domain as the computers where Outlook Add-in with ContentStore will be installed (end-users' domain).
-
The Proxy Server for ContentStore must be installed on the Web Console machine. The Proxy Server for ContentStore is required to retrieve content indexing data using the Web Server.
-
Compliance Search must be installed in your environment and on the Web Server that the proxy server is pointing to. Installing Compliance Search provides you with access to the Search Admin page, which you can use to configure preferences and settings for the ContentStore Email Viewer.
For information about the settings you can configure from the Search Admin page, see Compliance Search Advanced Configuration - Search Preferences.
For information about installing Compliance Search, see Deployment - Compliance Search.
-
If you use OnePass for Exchange Mailbox (Classic), then content indexing must be configured and performed on your archived email data.
-
Configure the recall services. See Configure Recall Services.
Note
After you configure the recall services, you must perform an incremental backup of the archived data to update the recall URL properties of the archived email messages.
-
-
The following are installed on the end-user computer when the executable file is used to install Outlook Add-In:
-
Visual Studio Tools for Office
-
A custom Java Runtime Environment (JRE) for ContentStore is installed on the client automatically by the software. The ContentStore JRE can be installed alongside other JRE versions that are present on the end-user's computer.
-
Installation
The software can be installed using one of the following methods:
-
Method 1: Log On Script through Active Directory
Use this procedure to mass deploy Outlook Add-in to end users.
Use this procedure to allow users to download the installation file from a local network.
Method 1: Log On Script through Active Directory
-
On the Active Directory Server, log on using an account with Domain Administrator privileges and open the Group Policy Management Console (GPMC).
For instructions, see the Microsoft TechNet article, Open the GPMC.
-
Create a new Group Policy Object (GPO) named Outlook_Addin_ContentStore.
For instructions, see the Microsoft TechNet article, Create and Edit a Group Policy Object.
-
Assign a new User Logon Script to the GPO, and then add the location of the Outlook Add-In application as a script.
For instructions, see the Microsoft TechNet article, Assign User Logon Scripts.
-
Instruct all end users to restart their computers.
The Outlook Add-In installation is complete after the computers are restarted.
Method 2: Host the Installation File on an Internal Network
If your end user computers have no Internet connection, you should host the installation file on a location on your local network. You must download the Outlook Add-In installer and create a new installer that uses local paths to install Outlook Add-In, Java Runtime Environment, Visual Studio Tools for Office, and .NET Framework.
-
Use a third-party tool, such as 7-Zip, to extract the contents of OutlookAddinWithContentStore.exe into a new folder.
The extracted folder contains the following files:
-
CvInstaller.exe: the installation file for Outlook Add-In with ContentStore
-
CvInstaller.ini: a preconfigured template file that includes the default locations of the software in the package.
-
-
From the command prompt, type the following command to download the installer package to a local location:
CvInstaller.exe /DOWNLOAD DownloadPath
-
Replace DownloadPath with the full path to the download.
For example: C:\OutlookAddinWithContentStore
Folders for X32 and X64 appear at the specified download path and contain the following files:
-
OutlookAddinClient.msi (both x86 and x64)
-
All prerequisite packages
-
-
Right-click CvInstaller.ini, and then click Edit.
-
Customize the CvInstaller.ini file according to your needs:
-
For Custom JRE: change the existing path to the local path where the custom JRE installation file is located
For example, change the following text:
X64="http://downloadcenter.commvault.com/CVDownloadCenter/11.0/outlook/OutlookAddinPreReq/CvJRE/CvJREx64.exe"to
x64="\\localhost\download\CvJREx64.exe" -
For .NET framework: change the existing path to a local path where .NET framework installation file is located.
For example, change the following text:
X64="http://downloadcenter.commvault.com/CVDownloadCenter/11.0/outlook/OutlookAddinPreReq/netframework/dotnetfx40_full_x86_x64.exe"to
x64="\\localhost\download\dotnetfx40_full_x86_x64.exe" -
For Visual Studio Tools for Office: change the existing path to a local path where .VSTO installation file is located.
For example, change the following text:
X64="http://downloadcenter.commvault.com/CVDownloadCenter/11.0/outlook/OutlookAddinPreReq/VSTO/x64/vstor40_x64.exe"to
x64="\\localhost\download\vstor40_x64.exe" -
For Outlook Add-In: change the existing path to the local path where the Outlookaddin.msi file is located
For example, change the following text:
X64="http://downloadcenter.commvault.com/CVDownloadCenter/11.0/outlook/December_2015/OutlookAddinClient_x64_11_12152015.msi"to
x64="\\localhost\download\OutlookAddinClient_x64_11_1215201.msi"
-
-
Save and close the CvInstaller.ini file.
-
Use a third-party tool, such as 7-Zip, to create a self-extracting executable that includes CvInstaller.exe and CvInstaller.ini.
-
Save the executable file to a location on your internal network.