Remote Installs - MSI Packages Using Active Directory Group Policies

Table of Contents

Install Requirements

Install Procedure

Post-Install Considerations

Install Requirements
For several agents or components, you can use Active Directory Group Policy Objects (GPOs) to remote the installation out to remote clients. An MSI package can be pushed out using full interface mode. After the remote installation is complete, you can use the load an ADM template available in the Resource Pack to override Registry settings for the remote installation of Outlook Add-In. (See Resource Pack for more information.)

This remote install type is supported by the following:

  • Outlook Add-In
  • Lotus Notes Client Add-In
  • File Share Archiver Client
  • Workstation Backup Agent

Verify that the computer in which you wish to install the software satisfies the requirements specified in the following, as appropriate:

The following procedure describes the steps involved in installing the supported agent or component. If you choose to install multiple components simultaneously, refer to the appropriate procedures for installation requirements and steps specific to the component. Also, keep in mind that when installing the Outlook Add-In for use only with the Exchange Mailbox iDataAgent, certain tasks and steps in this procedure may not apply, as they are specific to migration archiving-related functions. For example, the OFL Configuration section can be skipped when installing Outlook Add-In with the Exchange Mailbox iDataAgent.

In order to use the Outlook Add-In component, you must install one of the supported agents (Exchange Mailbox Archiver Agent, Exchange Public Folder Archiver Agent, Exchange Mailbox iDataAgent). For procedures on installing these agents, see:

In order to use the Lotus Notes Client Add-In, you must install the Domino Mailbox Archiver Agent on the Domino server. See Deployment - Exchange Agents for procedures on installing the Domino Mailbox Archiver Agent.

In order to use the File Share Archiver Client component, you must install the File Archiver for Windows Agent. See Getting Started - Windows File Archiver Agent Deployment for procedures on installing the File Archiver for Windows Agent. Do not install the File Share Archiver Client and the File Archiver for Windows Agent on the same computer. Note that configurations utilizing an FPolicy or Celerra instance to perform the recalls do not require the File Share Archiver Client software. For more information, see Instances - File Archiver. 

If you are remote installing the software following its removal via Add/Remove Programs (i.e., if you are reinstalling the software under this scenario), you cannot use the same Group Policy Object (GPO) to reinstall the software. See Article 872969 in the Microsoft Knowledge Base for a workaround. By following the steps in this article, the software will be reinstalled on the affected computers the next time these computers are rebooted.

Review the following Install Requirements before installing the software:

General

  • Review Install Considerations before installing the software.
  • This version of the software is intended to be installed in a CommCell with the latest version of CommServe and MediaAgent(s).
  • Close all applications and disable any programs that run automatically, including anti-virus, screen savers and operating system utilities. Some of the programs, including many anti-virus programs, may be running as a service. Stop and disable such services before you begin. You can re-enable them after the installation.
  • Verify that you have the software installation disc that is appropriate to the destination computer’s operating system.

Lotus Notes Client Add-In

  • For the Lotus Notes Client Add-In installations, the szLotusNotesServerName registry key must be created on the client computer and configured with the fully qualified host name of the Domino Server prior to installing the software.

Workstation Backup Agent

  • For the Workstation Backup Agent installations, the szCommServeIPHostName registry key must be created on the client computer and configured with the fully qualified host name of the CommServe computer, prior to installing the software.
  • If the client computer is behind a firewall, you can configure CommCell communications across the firewall by creating the following registry keys with appropriate values, on the client computer:
  • Optionally, to create Replication Sets upon installation, create the szRepSetPolicyName registry with the appropriate Replication Policy name.
  • If you wish to install Workstation Backup Agent to any instance, create the bAllowMultiInstances registry key with the value set to '1', on the client computer. By default the software installs to instance001.

Install Procedure
1. Create a folder to hold the MSI package to be pushed out. Share the folder with the appropriate permissions to allow the users and computers to read and run these files.
2. From the software installation disc, navigate to the appropriate MSI package, and copy the MSI package files to the folder you created in the previous step.
3. From a Windows 2000 computer in the domain, log on as a domain administrator. Then start the Active Directory Users and Computers snap-in.

NOTES

  • You can apply group policies to domains, sites, and organizational units (OUs).
4. From the Active Directory Users and Computers snap-in, click the OU container to which you want to link the Group Policy Object (GPO). Right-click that container, click Properties, and then click the Group Policy tab.
5. Create a new GPO for installing your MSI package. Give this GPO a descriptive name.
6. While the new GPO is selected, click Edit. This starts the Group Policy snap-in and allows you to edit this GPO.
7. Open and right-click Software Installation under Computer Configuration in the GPO. Then click New Package.
8. You are prompted for the path to the Windows Installer file (.msi) for this package. View the network location that contains the Windows Installer file, click the file, and then click Open. Click the installation package (.msi file).

NOTES

  • You must specify the location of the installation package as a UNC path by typing its location in the File Name edit box. For example: \\Peach\msi\Exchange_DM_Client.msi.
9. Click the desired deployment method based on your requirements.
  • Click Advanced published or assigned if you wish to do the following from the resulting Properties dialog box:
    • Specify a "declared upgrade". This causes the new installation package to install as an upgrade over a previous version of the installation package that has already been installed. In such a case, use the Upgrades tab. If a group policy object already contains an installation package, and if a newer version of the package is added to the group policy object, the Upgrades tab may automatically detect the relationship between the packages. However, if the upgrade relationship is not automatically detected, you can manually add this information under the Upgrades tab. If an upgrade relationship has been established between different versions of a package, and when the group policy deploys the newly added package, the older package will be uninstalled first and then the newly added package will be installed.

      Click OK when you are finished. The installation package (.msi file) is now added to the group policy.

  • Click Assigned and OK to add the installation package (.msi file) to the group policy.
10. From the Active Directory Users and Computers snap-in, click the container to which you linked your GPO. Right-click that container, click Properties, and then click the Group Policy tab.
11. Click your GPO and then click Properties.
12. Click the Security tab and then remove Authenticated Users from the list.
13. Click Add. Then select the security group to which you plan to have this policy applied in order to add it to the list.
14. Select your security group and then give the group READ and Apply Group Policy permissions.

Post-Install Considerations

General

  • Install post-release updates or Service Packs that may have been released after the release of the software. If you are installing a Service Pack, verify and ensure that it is the same version as the one installed in the CommServe.
  • Changes to a GPO are not immediately imposed upon the target computers but are applied in accordance with the currently valid group-policy refresh interval. You can use the Secedit.exe command-line tool to impose GPO settings upon a target computer immediately. See Article 227302 in the Microsoft Knowledge Base for more information.
  • You can override the stub file port number by using the EVMGRC_REMOTE_PORT_OVERRIDE registry key.  Use this key when the port number changes. Keep in mind that using this key defeats the benefit of being able to recall data using different port numbers for multiple Agents.

Agent Specific

Exchange Archiver Agents

  • To customize registry settings and override the installation default settings for Outlook Add-In, follow the README file instructions for the CVOutlookAddin.adm Template available in the Resource Pack.
  • Before using the Outlook Add-In for use with Exchange Mailbox Archiver or Exchange Public Folder Archiver, ensure that the Organizational Forms Library has been set up and configured for special forms. See OFL Configuration for more information.

  • Before using the Outlook Add-In, ensure that the port number used by the Client Event Manager Service is properly configured. Typically, the install program configures this automatically; however, when using custom port numbers you will need to make sure that the port number configured on the Exchange Server under the nEVMGRCPORT registry key matches the port number configured on the Outlook client under registry key nEvMgrCPortNumber. This requirement also applies to multi-instance installs, in which case, you will need to locate the nEVMGRCPORT registry key under the appropriate instance on the Exchange Server. For general information on port number requirements, see Network TCP Port Requirements.

Domino Mailbox Archiver Agent

  • Once the Lotus Notes Client Add-In is installed, the Windows user accessing the Lotus Notes application must be given Full Control permission in the LotusNotesDMClient registry key.
  • To customize registry key settings to configure the Lotus Notes Client Add-In installation, follow the README file instructions for the LNDMAddin.adm Template available in the Resource Pack.

Back to Top