Deployment Guide

Deploying Copernic Desktop Search on a network

This section briefly explains the suggested steps to follow when a network administrator wants to deploy Copernic Desktop Search to his network.  For a completed guide, refer to the CDS - Deployment Guide.pdf in the MSI installation package.

Please note that the setup described below explains the way that CDS is meant to be deployed and the way Copernic will offer most support for. However, in the case of single installs where no network deployment is used, it is not required to use the deployment methodology described below.

Recommended Deployment Methodology

Group Policy Objects (GPO)

Group Policy Objects (GPO) allow network administrators to manage software from a single point and publish configuration changes and updates to their users. Multiple policies are available to configure options, indexing and search behavior. A possible use of Group Policies is to force a configuration to a group of users. This way, only the network administrator could modify this configuration.

Administrators can use Group Policy to apply one or more configurations to targeted computers by using the administrative template file (.adm or .admx files) which provides the available policy settings. CDS supports machine based group policies as well as user based policies.

Copernic Desktop Search comes with multiple GPOs. Please refer to document named CDS - GPO documentation.pdf in the MSI installation package.

Policies States

Enterprise default settings may be forced to computers in order to preserve a homogenous environment. When such settings are pushed, if the user tries to change the setting, the setting is not visible or is unavailable.

Policies have 3 possible states when previewed in the group policy administration system:

    • Enabled
    • Disabled
    • Not Configured

Enabled and Disabled may have various effect, depending on the policy that is being set.  As for Not Configured, this state means that the policy will be reverted back to its default value.

Policies Location

When a policy is set, a key is created in the registry. Policies can be set per user or per computer through the active directory.

Policies that are set per computer are created under the following section of the registry:

    • HKLM\SOFTWARE\Policies\Copernic\DesktopSearch

Policies that are set per user are created under the following section of the registry:

    • HKCU\SOFTWARE\Policies\Copernic\DesktopSearch

If no policy is applied, the associated key will not be created in the registry.

Return to top

Setting up the ADMX file and GPOs

Adding the ADMX template

Copy the .admx file in C:\Windows\PolicyDefinitions, the english adml file in C:\Windows\PolicyDefinitions\en-US, german adml file in C:\Windows\PolicyDefinitions\de-DE.

NOTE: For legacy adm template, see the CDS - Deployment Guide.pdf document.

Setting up the organization unit

An organizational unit is a group of users and/or computers to which GPOs (Group Policy Objects) will be assigned for specific software. In order to create an organizational unit, follow these steps:

    • Log on to the domain controller.
    • Open the active directory software (such as Microsoft management console).
    • Create a new organizational unit (Right click on domain root > new > organizational unit) or use one already existing.
    • Right click on the GPO folder and select properties from the drop down list.
    • Once the properties open, select the GPO tab then click on new and give it a name.

Adding users to the group

Return to the active directory console (should still be open) and add the desired USER/COMPUTER to the group. Right click on the query-based distribution group then new > user or new > computer. This will set to which user/computer the package and GPOs will be pushed. This operation can also be performed with a drag and drop from the computer and/or user list.

Configuring GPO settings

From the distribution group’s properties window, select the new GPO group and click on EDIT, this will open a new window named Group Policy Object Editor from where you will be able to handle the GPOs and the package.

You can find the new template named Copernic Desktop Search under the Administration Templates category in both computer or user configuration categories.

Before adding CDS package, you may want to set some GPO settings like adding the license fike or serial key. Please refer to document named CDS - GPO documentation.pdf in the MSI installation package for more information.

Adding the package

The package will be pushed to any user/computer previously set. (See step Adding users to the group). To do so right click on Software settings > Software Installation. Then click on new > Package. Once done, browse and select the package you want to push via GPO.

After selecting the package, select the Advanced method then click ok. Selecting Assigned will automatically install the package when it is pushed, while Advanced allows applying modifications to the deployment, such as changing the software language.

In order to customize the language of CDS:

    • Select the Modifications tab and click on Add.
    • Select the .mst file corresponding to the language desired and click Open.
    • You may click on OK to close the properties window, the process is complete and users should have CDS installed upon restarting their computer.

After installation

After these steps are completed, Copernic Desktop Search is installed and configured like desired through the GPO settings. The user will not have to do anything and will get the same configuration as all users added in step Adding users to the group.

Return to top