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:
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 9.0.0 |
Information |
| 7.0.0 | Supported | Perform a direct upgrade to Version 9.0.0. |
| 8.0.0 | Not Supported | Perform a direct upgrade to
Version 10.0.0. Click here for more details. |
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.
| 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. 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:
|
| 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. |
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 - Outlook Add-In.