Product DocsMenu

Desktop Integration Package Deployment Overview

The Desktop Integration Package (DIP) installs the Desktop Searchbar and the Outlook Sidebar on end-user computers. The DIP can also allow end-users to configure which folders and files should be crawled from their computer to be added to the unified index (see Desktop Integration Package).

Notes:

  • The DIP works together with the Desktop connector to allow indexing of files stored on end-user computers. If it is not already done, before deploying the DIP, you must create and configure a Desktop connector source (see Desktop Connector).

  • The DIP can be deployed on Windows 8 or 7 end-user computers.
    CES 7.0.4897+ (December 2012) Support for Windows 8.

  • With Outlook 2007 and up, for Windows systems, the outlook:// protocol used by the email result links in Coveo search interfaces (other than the Coveo Outlook Sidebar) is disabled by default. When you want users to be able to open email search results from these search interfaces directly in Outlook, if not already done, enable the protocol on all workstations for example using GPO (see Shortcuts and the Missing Outlook:// Protocol).

  • The Desktop Integration Package currently does not support screen resolutions above 1920 x 1080 in which case the Outlook Sidebar appears too small.

The Desktop Searchbar and the Outlook Sidebar bring Coveo search a keystroke or a click away from where end-users work. These useful Coveo access points often help end-users to more quickly adopt the Coveo solution. The DIP is available to all Coveo implementations. For these reasons, it is recommended to deploy the DIP within your organization.

As a Coveo administrator, you need to download, distribute, install, and maintain updates of the Desktop Integration Package on the end-user desktop and laptop computers within your organization.

The following sections present the available DIP deployment methods.

Group-Policy Object method

In a Microsoft Windows Active Directory environment, this method consists in creating and configuring a Group Policy Object (GPO) to automatically manage the DIP distribution, installation, and updates on selected end-user computers (see Creating a DIP Deployment Group Policy Object).

This is the recommended method as it offers many advantages.

Pros:

  • Controls exactly on which computer the DIP is installed.

  • Controls which DIP features are enabled.

  • Can pre-configure standard local folders to index.

  • Automatically deploys the DIP initial version and updates.

  • Contributes to maximize the usage and adoption of the Coveo solution.

Cons:

  • Needs Active Directory environment and permissions.

  • More complex configuration.

Login script method

This method consists in creating and using a login script to install the DIP when it is not already installed on the computer (see Deploying the Desktop Integration Package Using a Login Script).

Pros:

  • Simple to configure

  • Automatically deploys the DIP initial version.

Cons:

  • Still need GPO if you want to control which DIP features are enabled.

Manual distribution method

This method consists in making the DIP installer available to your end-users and rely on them to install and configure the DIP (see Manually Deploying the Desktop Integration Package).

Pros:

  • No configuration, only need to inform end-users of the availability of the DIP installer.

Cons:

  • Relies on end-user to install the DIP.

  • Cannot control which DIP features are enabled.

  • Each user must configure folders to index from scratch.

  • Need to inform and rely on end-users to install updated version of the DIP.

What's Next?

Make DIP updates available for an easy deployment (see Automatically Updating the DIP on All Computers).

People who viewed this topic also viewed