Chat now with support
Chat with Support

Migrator for GroupWise 4.7 - Release Notes

Known issues

MFG may add multiple entries to the proxy access list for the same user with the same access rights, or cannot remove an entry from the list when setting or removing proxy for GroupWise client 12.0.4. In this case, other versions of GroupWise client are recommended to avoid this issue.

704756

When the Source SMTP Domain is different from the Target SMTP Domain, MFG cannot resolve the email address in ACLs in Office 365 GAL for contacts or users in Office 365 that do not have a secondary proxy address with the Source SMTP domain. Office 365 should be configured to generate appropriate secondary SMTP addresses with the Source SMTP domain.

586882

System requirements

Supported GroupWise source environments

Novell GroupWise version 6.0–7.0.4, or 8.0.0–8.0.3, GroupWise 2012 to SP4 (12.0.1 through 12.0.4), GroupWise 2014, and GroupWise 18

Configuration requirements

An admin account must be defined with admin rights to the GroupWise server and the ability to add trusted API keys.

If GroupWise Internet Addressing is not enabled, GroupWise Internet Agent LDAP Service must be configured to automate the creation of the Address Translation Table. See: http://support.novell.com/docs/Tids/Solutions/10007372.html

Required for ACL migration

ACL migration is supported only from a GW 2012 source. A GroupWise 6, 7 or 8 source requires [General] ACLs=0 in MFG’s gwmigapp.ini and/or gwdtapp.ini.

Supported target environments

Recommended throttling policy for proprietary Exchange

The following action is not applicable to Exchange 2013 and above.

To migrate mailboxes to an on-premises Exchange, Quest recommends setting a throttling policy on Exchange similar to the typical throttling settings used for Blackberry and/or Cisco Unity. The optimum throttling value varies, but start by setting RCAPercentTimeInAD=200, and then adjust to suit your local environment.

Apply this new policy to the user account that serves as the intermediary between Exchange and Groupwise—typically called something like GWMigrate. You can also apply this policy to the migration workstation's computer account—typically called GWMigrateServer or something similar. For example, to set RCAPercentTimeInAD to 200 for these sample account names, you would execute this PowerShell command on the Exchange server:

$b = Get-ThrottlingPolicy "Groupwise Throttling Policy";

Set-Mailbox GWMigrateServer$ -ThrottlingPolicy $b;

Set-Mailbox GWMigrate -ThrottlingPolicy $b;

Stop and start the Exchange Transport Service to activate the updated settings.

Requirements

If your AD is configured for a resource forest and a user forest:

Operating system

NOTE:  

* For Windows Server 2016, 2012 R2, 2012, 2008 R2 or 2008, or Windows 10, 8.1, 8 or 7: ACL migration is supported only from a GW 2012 source. A GroupWise 6, 7 or 8 source requires [General] ACLs=0 in MFG’s gwmigapp.ini.

** Windows Vista Caution: Heap corruption may occur (rarely) when using MFG running on Windows Vista to migrate ACLs. If this becomes a problem in your environment, set [General] ACLs=0 in MFG’s gwmigapp.ini.

*** In Windows Server 2016 and Windows 10, currently you will be prompted to enter the Administrator user name and password of your target Exchange after you click Next on the Select Destination Exchange Server screen in Administrator-Driven Batch Migrator.

Workstation hardware

Must be a separate machine from the Exchange server, but a member of the same domain as AD and Exchange.

May be a virtual machine, but a dedicated "actual" machine will likely yield better migration performance.

Minimum hardware requirements:

Recommended for improved performance, especially for high-volume migrations:

Order of installation

A migration requires an unusual combination of tools, developed by different vendors, all installed on this single migration server, and the combination can cause compatibility problems on some machines. To minimize these conflicts, Quest recommends that you install the applications in this particular order:

Antivirus software

Prior to running any Quest admin application: Any antivirus software must be configured to not scan the Quest program files directory or %temp% directory, or may be simply turned off (and may be restored after the program runs). If an antivirus scan misinterprets an MFG temporary file as a threat, it will try to "clean" the file, which will generate an error when the MFG program call fails.

Required for all Exchange targets, including Office 365

get-executionpolicy | set-executionpolicy unrestricted

Required Outlook client on MFG admin server

Outlook 2016, 2013, 2010, 2007 or 2003 (32-bit versions only) must be installed. The Admin Account Pooling Utility requires Outlook 2016, 2013, 2010 or 2007 (not 2003). For an Exchange 2016 or 2013 target, Microsoft requires the Outlook client be one of:

The Outlook profile for the migration:

When the Outlook profile uses MAPI over HTTP in a migration to a local Exchange:

Outlook Anywhere may be used as the required Outlook client on the admin workstation, but if migrating to a proprietary Exchange target:

Required for Admin Account Pooling feature (for O365 target; see Admin Guide chapter 6)

MFG’s Account Pool Utility uses Microsoft Office 365 cmdlets to issue commands to Office 365, and these cmdlets must be installed before MFG can use account pooling. Note these requirements before you can install the cmdlets:

The installer adds the program to your Start menu, and adds a shortcut to your desktop.

Required for migration from GroupWise 7.x to Windows XP SP2 or later

GroupWise versions 7.x are incompatible with the DEP (Data Execution Prevention) security feature in Windows XP SP2 and later versions, so MFG's admin components can run only if the GroupWise app is added to Windows’ DEP list of exceptions (on the admin workstation). Otherwise, when MFG tries to call a GroupWise function, MFG will crash and report a C++ runtime error.

Back on the DEP tab, click OK to save these changes.

Operating system

NOTE:  

* For Windows Server 2016, 2012 R2, 2012, 2008 R2 or 2008, or Windows 10, 8.1, 8 or 7: ACL migration is supported only from a GW 2012 source. A GroupWise 6, 7 or 8 source requires [General] ACLs=0 in MFG’s gwdtapp.ini.

** Windows Vista Caution: Heap corruption may occur (rarely) when using MFG running on Windows Vista to migrate ACLs. If this becomes a problem in your environment, set [General] ACLs=0 in MFG’s gwdtapp.ini.

Other requirements

GroupWise client version 6.0 - 7.0.4, or 8.0.0 - 8.0.3, or GroupWise 2012.

Outlook 2016, 2013, 2010, 2007 or 2003 (32-bit versions only) must be installed. For an Exchange 2016 or 2013 target, Microsoft requires the Outlook client be one of:

Upgrade and compatibility

There is no need to uninstall a previous 4.x version before installing a new version. The upgrade installation and setup 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 MFG 3.x to MFG 4.7.

This process will rebuild the MFG Address Translation Table, but the program’s configuration and .csv files are preserved.

Product licensing

Migrator for GroupWise is a metered-use product that requires the application of a valid license key. Quest sells license keys for particular numbers of users to be migrated. When the limit is reached the software continues to function nominally for users that have already been migrated, but will not migrate additional users. The same license is used for all product functions for a particular user. That is, when any feature of any MFG component is applied to a particular user, then all features of all components can be applied to the same user under the same license. Moreover, users can be re-migrated (if necessary) using the original license; remigration does not require an additional license.

You can obtain your first or a subsequent license key by contacting a Quest Software sales representative. For either a trial or perpetual license, the key takes the form of a file GroupWiseMgrEX_4-###-#####.asc (where ###-##### represents your unique license number) attached to an email sent to you from Quest Licensing.

The product will install without a license key, but will prompt you to apply a license key the first time you try to run the software. You will be prompted to find and specify the license key file that Quest provided.

An Evaluation (or Trial) License is intended to let you try the MFG software in your own environment, with your own data, to help you determine whether MFG’s capabilities are suitable to your needs. Under an Evaluation/Trial license, therefore, the program stamps a "MIGRATION EVALUATION" prefix into the Subject of every migrated message, and also imposes these limitations:

Related Documents