What pre-migration preparations are required to migrate items having any foreign characters successfully? Does Groupwise Migrator for Exchange support single-byte or double-byte character set migration?
Please ensure that all multi-language pre-requisitesare met on the migration machine. Also, test with a single user first to verify that GroupWise items with foreign characters are migrated successfully.
Perform these steps when migrating items having any double-byte (such as Chinese, Korean, or Japanese) characters.
If the GroupWise Migrator is also going to be used to to create Exchange Mailboxes, Groups or running the Object Merge tool, Groupwise Migrator will require access to a US English versions the Powershell cmdlets (local install of EN-US tools for Exchange 2007; access to an EN-US version of an Exchange server for 2010 remote Powershell).
From the Release Notes:
This section contains information about installing and operating this product in non-English or non-ASCII configurations, such as those needed by customers outside the USA. This section does not replace the materials about supported platforms and configurations found elsewhere in the product documentation.
The platforms and configurations supported in this release may use any time zone, single-byte character encoding, language, or locale configuration to operate this product. Multibyte encodings (such as those used for the Chinese, Japanese, or Korean languages) may work appropriately but have not been tested and this product should be used with caution in those environments.
The migration server must be installed and operated on a machine where the code page associated with the runtime locale is identical to the encoding for each mailbox being migrated. The Groupwise APIs used to retrieve the data do not support retrieval of data from outside the current code page. For example, if the migration server were configured on a German machine (which uses code page 1252) and used to migrate a mailbox containing Polish data (which uses code page 1250), data would be lost during the migration.
The Exchange server which is a target for the migration may be in any locale, as that interface uses the Unicode character set.