Remote Upgrades - MSI Packages Using Active Directory Group Policies

Click on a link below to go to a specific section of the software upgrade:

The procedure on this page describes the steps involved in upgrading the following DataArchiver components in a non-clustered environment using Active Directory Group Policy Objects (GPOs) to remote the upgrade MSI package out to remote clients. An MSI package can be pushed out using full interface mode. After the remote upgrade is complete, you can use the load an ADM template available in the Resource Pack to override Registry settings for the remote upgrade of Outlook Add-In. (See Tools and Utilities for more information.)
  • Data Classification Enabler
  • DataArchiver Outlook Add-In
  • File Share Archiver Client

This procedure provides steps for upgrading each of these components individually.

If multiple components are installed on a computer, then ensure that all applicable components are selected for upgrade. In such a situation, the upgrade sequence may vary. Refer to the appropriate procedures for upgrade requirements and steps specific to the component.

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

Supported Upgrade Paths

The following table provides a list of supported upgrade paths for the current software version. If the version currently installed on your computer is not listed here, contact your software provider for more information.

Installed Version

Upgrade to Version 8.0.0

Information
     
6.1.0 Supported Perform a direct upgrade to Version 8.0.0.
     
7.0.0 Supported Perform a direct upgrade to Version 8.0.0.

Upgrade Requirements
Review the following before upgrading the software:

General

  • Review the Upgrade Strategy before upgrading the software.
  • Verify that no jobs are in progress or scheduled to occur while the software is being upgraded on the client. If jobs are scheduled, either perform the upgrade at another time or disable all jobs in the client using the Activity Control tab from the Client Computer Properties dialog box in the CommCell Console.

    Once the upgrade is completed, you can enable the jobs from this dialog box.

  • Verify that the CommServe computer is accessible and all services on the CommServe and the MediaAgent in which you wish to perform the upgrade are running.
  • Verify that the SQL Server instance used by the CommServe is running on the CommServe computer.
  • Verify that all applications (CommCell Console, Service Control Manager) are closed.
  • Close all applications and disable any programs that run automatically, including antivirus, screen savers and system utilities. Some programs, including antivirus software, may be running as a service. Stop and disable all non-essential services before you begin. You can re-enable them after the upgrade.
  • The files and folders associated with CommCell components should not be opened by other applications (for example, Windows Explorer, FTP, etc.) on this computer or from other computers during the upgrade.
  • Verify that you have the software installation disc that is appropriate to the destination computer’s operating system.

    Make sure that you have the latest software installation disc before you start to install the software. If you are not sure, contact your software provider.

Agent Specific

  • Install the MSI version 3.1 Package available through Windows Updates from Microsoft Corporation.

  • If you have previously installed an MSI package from a disc, you must upgrade the software using the software installation disc from the current release. Conversely, if you have previously installed an MSI package remotely, you must upgrade the software remotely using the MSI package for the current release.

  • Note that during the Outlook Add-In upgrade process, the software automatically installs the Visual C++ Redistributable and JRE packages. For more information, see System Requirements - Exchange Mailbox Archiver Agent.

Before You Begin
  • Ensure that you are logged on to the computer as a local Administrator or as a member of the local Administrators group on that computer.

Upgrade Procedure
1. Uninstall the previous version then 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.

Note: 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. If you have already created a GPO that was used for installing the previous version of this software, then select that GPO and skip to Step 7. Otherwise, create a new GPO for upgrading your MSI package and give this GPO a descriptive name.
6. While the 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 upgrading 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).

Note: 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 Advanced published or assigned then perform the following tasks from the resulting Properties dialog box:
  • Click 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.
  • Select the appropriate entry in the Package to upgrade display pane, then click Add.
  • From the Add Upgrade Package dialog box, select the option corresponding to Package can upgrade over the existing package, then click OK.
  • From the Upgrades tab, click OK. The installation package (.msi file) is now added to the group policy.
10. If you are using a previously existing GPO that already has the requisite permissions, then skip the remaining steps and continue on to the Post-Upgrade Considerations section. Otherwise, continue on with this procedure.

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-Upgrade Considerations

General

  • Install post-release updates or Service Packs that may have been release after the release of the software.
  • 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.

Agent Specific

  • To customize Registry settings and override the upgrade 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, 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.

  • We strongly recommend upgrading the Outlook Add-In, and any agents that support it, to the same release version as the CommServe. Otherwise, the Outlook Add-In functionality will be limited or unavailable. For more information, see Backward Compatibility - DataArchiver Outlook Add-In.

The File Archiver for Windows Agent and the File Share Archiver Agent has been merged in this release. For detailed information on the impact of this merge, see Merge Impact of File Archiver for Windows/File Share Archiver Agents in Upgrade Overview.