Chat now with support
Chat with Support

Migrator for GroupWise 4.7.1 - Quick Start Guide

Upgrade considerations

There is no need to uninstall a previous 4.x version before installing a new version. The upgrade installation and setup from a 4.x version are fully automated, and will preserve any data already migrated, so you may simply resume the migration process from wherever you left off with the previous version.

There is no direct upgrade path from Migrator for GroupWise 3.x to Migrator for GroupWise 4.7.1.

Uninstall Migrator for GroupWise 3.x. Use Windows’ Add/Remove Programs feature in the Control Panel.

This will rebuild the Migrator for GroupWise Address Translation Table, but will preserve the program’s configuration and .csv files.

Before you install the software

For Migrator for GroupWise to work correctly with the GroupWise and Outlook software, the non-Quest applications should be installed on the administrator’s migration server in the order as specified in the Requirement specifications above. If these applications are already installed before you install the Quest software, and you then experience problems accessing GroupWise address books, the most likely cause will be the installation sequence. To solve the problem, uninstall these other applications and then reinstall them in the order specified above.

Installing Migrator for GroupWise

Download the Migrator for GroupWise zip folder from the website, and extract all files into an installation folder. Then run Autorun.exe from the installation folder.
Or: You could instead simply insert a Migrator for GroupWise product CD/DVD, which runs the Autorun utility automatically.
Windows then launches the Autorun utility, where you can browse product information including the Prerequisites and all Migrator for GroupWise Documentation before installing the product.
Verify that your environment conforms to the System requirements specified in the Migrator for GroupWise Quick Start Guide. Several of the required third-party components may be downloaded from links on the Autorun Prerequisites tab.
Select the Quest Migrator for GroupWise product name, and click Next.
Review the Welcome screen and click Next.
... see Specifying antivirus software for the Migrator for GroupWise Prerequisites Checker below for information about how to specify an alternate antivirus checker.
NOTE: The checker can also be run independently from your Windows Start menu, in the Quest | Migrator for GroupWise group. The Prerequisites Checker log file is written to %SystemDrive%\ProgramData\Quest\.
Click Finish from the last screen to complete the installation.
When you are finished browsing other Autorun tabs, click the Close box ([X] in the top-right corner of the window) to close the Autorun utility.

Specifying antivirus software for the Migrator for GroupWise Prerequisites Checker

Among other tests, the Prerequisites Checker will test the status of any antivirus software that may be running on the migration server. The wizard is configured to look for four popular antivirus products: System Center Endpoint Protection, Avast!, AVG Antivirus, and Symantec Antivirus. If you use another antivirus product, you can tell the Prerequisites Checker to add it to the list (to be checked) by adding it to the wizard's configuration file (\Prerequisite Checker\ConfigFile\CheckerManager.config, in the MFG installation folder). To do this:

Open the CheckerManager.config configuration file in a text editor.
Find <Section Name="AVSChecker"> in CheckerManager.config.
Within the AVSChecker section, find these parameters:
<Key Name="ProgramNames" ...> lists the names of antivirus programs the wizard will check, separated by semicolons (;). The names will appear in the wizard's results exactly as they are listed here.
<Key Name="ProcessNames" ...> lists the names of antivirus program processes that are associated with the ProgramNames listed above, separated by semicolons (;).
Add the name of its corresponding process to the <Key Name="ProcessNames" ...> list. Important: The ProcessNames in this list must appear in the same order as their associated ProgramNames in the ProgramNames list above. The wizard associates the first ProcessName in the list with the first ProgramName, and associates the second with the second, and the third with the third, etc.
Save and close the CheckerManager.config configuration file.

For example, the default configuration appears like this:

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating