Migration of GroupWise mailboxes to Exchange may not successfully transfer Hebrew characters

During migration of mailboxes from Novell GroupWise to Exchange 2000/2003 using GroupWise connector on the Novell side, mailboxes with Hebrew characters may not successfully duplicate the content of some messages / folders.
A common problem is that Hebrew characters are transferred as " * " or " ? ", instead of regular Hebrew fonts.

The GroupWise connector on the Novell side has limitations in transferring Hebrew characters.
Since Novell is using an old API with an old ASCII table the Hebrew characters are transferring as " * "
(on the Novell API gateway "API_OUT" before they transfer to the Microsoft side ) and back as " ? ".

There are few workarounds to overcome the GroupWise connector limitations on the Novell side:

Use the migration wizard in two steps:

a. Export each mailbox to PST.

b. Import the PST into the Exchange.

Note: You will need to customize some of the other issues like (See the "More information" section):�
���������������During migration of contacts you may need to change the fields in GroupWise to match the correct fields in Outlook.
�������������� You can also run a script that can automatically save and import the calendar file .sc2 .

Moving from Novell GroupWise to Exchange Server
�
http://www.microsoft.com/exchange/techinfo/interop/GroupWise.asp

Microsoft corporation and/or its respective suppliers make no representations about the suitability, reliability, or accuracy of the information and related graphics contained herein. All such information and related graphics are provided "as is" without warranty of any kind. Microsoft and/or its respective suppliers hereby disclaim all warranties and conditions with regard to this information and related graphics, including all implied warranties and conditions of merchantability, fitness for a particular purpose, workmanlike effort, title and non-infringement. You specifically agree that in no event shall Microsoft and/or its suppliers be liable for any direct, indirect, punitive, incidental, special, consequential damages or any damages whatsoever including, without limitation, damages for loss of use, data or profits, arising out of or in any way connected with the use of or inability to use the information and related graphics contained herein, whether based on contract, tort, negligence, strict liability or otherwise, even if Microsoft or any of its suppliers has been advised of the possibility of damages.