• GroupWise Administrative Functions: • Remove forwarding
• Set forwarding • Set user password • Set user visibility
• Exchange Administrative Functions: • Set forwarding
• Remove forwarding
• Remove user free/busy forwarding to GroupWise • Other account creation and maintenance features
(available features depends on designated Exchange target type) • Migrate Users: Migrates user data—any combination of
server-based or archived mail, calendar data, or the trash folder, or personal address books—from GroupWise to Exchange.
• Provision Distribution Groups: Copies GroupWise public distribution lists (PDLs) into Active Directory.
When migrating Shared Addressbooks from Groupwise to Exchange, sometimes an error is logged indicating user accounts with permission to the shared mailboxes could not be located in Active Directory.
Another workaround would be to add the GroupWise style address to the proxy addresses of the user in AD, so that GroupWise Migrator would succeed when performing a search against the AD. However, in most cases, it is desirable to have populated the data correctly in the addresstranslation.csv so that address translations can be performed correctly.
Typically caused by:
• Running multiple actions at once, I.E Groupwise Functions and Migrate Users. • Corrupt MAPI Profiles on the Migration console.
• Mail client installation issues or order of installation.
• Network problems, including NDS tree connection issues.
See SOL12655 for more information on this particular error. https://support.quest.com/SolutionDetail.aspx?id=SOL12665
Install the correct codepage from the Regional and Settings within control panel. The warning can be harmless. In some circumstances the message will still migrate. For example , the message may have Internet content meaning that the content cannot be migrated because on migration NME/GME cannot re-load content from the Internet.
Abnormal termination of Software Power failures,
Server hardware problems, NICs, Hard Drives, memory etc. Backup software trying to backup open databases
Virus scanners scanning open databases,
User’s workstations accessing their mail via direct access – mapped drive (not client/server)
An interruption of a database transaction can cause corruption.
More information on GroupWise Check (GWCheck) is available on Novell's website: http://www.novell.com/documentation/gw6/gw6_admin/data/a3n60l6.html
GroupWise Trusted Application has not been generated correctly.
The GroupWise Trusted Application is created from the last wizard screen of the Quest GroupWise Migrator for Exchange tool (running under the credentials of a GroupWise Administrator).
- Upon a successful run, the GroupWise Trusted Application will return and add a line within the C:\Program Files\Quest Software\GroupWise Migrator for
Exchange\gwmigapp.ini file starting with TK= specifying the GroupWise Trusted Application key value similar to the following example:
[GroupWise]
DomainPath=\\cs-novell65-01\SYS\MAIL\DOMAIN
TK=<itu777eHhfglsAwbMwn9rD9Hj5elNkubxzD9tHQHi5el5jC8VZeDOZ9ZhkElYSy$yw EDtH$8lfVJzyu8VZn2tH98gNel72BrFFUk>
Note: This value
<itu777eHhfglsAwbMwn9rD9Hj5elNkubxzD9tHQHi5el5jC8VZeDOZ9ZhkElYSy$ywEDt H$8lfVJzyu8VZn2tH98gNel72BrFFUk> is returned from the GroupWise server as part of the GroupWise Trusted Application process.
- The GroupWise Trusted Application process then generates the hostname of the machine within the Tools | GroupWise System Operations -> | Trusted Applications... window of ConsoleOne that looks similar to the following:
QUESTGWMIGAPP-COMPUTERNAME
Throughput:
Key factors that can significantly affect the rate of data migration are: Data geography
Bandwidth
Migration workstation hardware (memory, number and speed of processors, and disk speed) Actual throughput rates for the batch-migration program vary widely with the interplay of all relevant factors, but customers typically report migration rates of 1 to 3GB per hour.
Rates as high as 20 GB per hour have been reported under optimal conditions with high-performance workstation hardware.
Resource Migration:
Resources are migrated and treated as regular Mailboxes. Groupwise Permissions:
As per the Requirement Specifications stated in the GroupWise Migrator for Exchange User Guide, the Novell account needs to be an admin account (or equivalent) having administrator rights to the GroupWise Server.
License Tracking:
GME 4.X and above is designed to consume license per mailbox migration. For instance, if you migrate a mailbox and set forwarding for the same user; one license will be consumed. If you perform the same process on a DIFFERENT object; a new license will be consumed. License are tracked separately on each migration console.
When troubleshooting Groupwise Migrator for Exchange Administrator Driven Batch Migrator, the temporary log file can be very valuable to help determine what the program is doing before the migration is kicked off.
Also remember to check the %temp% folder on the migration console to find additional log files for troubleshooting.
Verbose logging will capture much more detailed information about what the
program is doing during the migration and can help to provide valuable information on the environment and any specific errors which may be encountered.
The gwmigapp.ini file allows you to customize the settings used for the Administrator Driven Batch Migrator.
When needed, the Administrator Driven Batch Migrator settings may be customized with the switches which are outlined in the GME_INI_Reference.pdf file (Included with the installation). There are a lot of different switches that can be used for troubleshooting, some of the most common are:
MAPIErrorsToRetry=<########> MAPIRetryWait=<##>
MessageRetryCount=<#>
ServerMailResolveAttendees=<#> DoInactivityTimer=<#>
For more information on these settings please refer to the GME_INI_Reference.pdf
Before creating a service request. please exercise due diligence in testing the data or attempting to reproduce the issue in your lab environment if possiable. This will ensure a speedy reply and should help speed up the troubleshooting process.
Collect all pertinent data such as Logs, Screen Shots etc, provide a link to a share with this information in it.
Provide as much detail as possible to the case to ensure that support knows what has been attempted and where the issue stands.
Gather log files, screenshots, if necessary, to perform analysis
Webex sessions are also an extremely efficient way to gather information.
Make sure to note things such as:
Operating System / Hardware Quest Software versions
Outlook Client Version / Exchange Version Novell Client Version
Groupwise Client Version / Groupwise Version