Windows Messaging System to GroupWise Migration Tool
====================================================
Version: 1.0
Date: 03/18/1998
Author: Scott Lewis
Support: Limited support is available from the author by
email at slewis@novell.com


WMS2GW.EXE is a tool for accessing Windows Messaging System (WMS) messages
from .PST files and generating GroupWise API Gateway input files.

System Requirements:
====================
The API gateway processes these files and imports the mail into the
GroupWise users' mailboxes.

MSMAPI32.OCX needs to be in the \WINDOWS\SYSTEM directory and needs to 
be properly registered. If you are running WMS, the OCX should be there.
If WMS2GW.EXE quits with an error that says a class wasn't registered, run 
the included TREGSVR as follows:

TREGSVR MSMAPI32.OCX <Enter>


A GroupWise API Gateway must be installed, configured and working.
The API Gateway is available from developer.novell.com as a free download
to registered developers (no charge but an electronic application must be
filled out). Users MUST HAVE RIGHTS to the API Gateway's API_IN and ATT_IN
directories. These rights must include WRITE. An alternative is to make a
fake API gateway directory structure somewhere and then have an administrator
move the files to the real directories later on. Make sure you copy or move
the ATT_IN directory BEFORE the API_IN directory if you choose this approach.

The user that will be migrated must exist in GroupWise before using this
tool. If they do not exist, the API gateway will log errors and either
delete their messages or move them to the GWPROB directory. Normally it is
a good idea to name the GroupWise users the same as they were named in WMS.
If the usernames need to be changed, make sure the users know their new
email userIDs before they run WMS2GW.EXE as they will need to supply a
GroupWise userID to it.

In the directory that WMS2GW.EXE is run from there should be a text file
called WMS2GW.PRM. This file needs three lines of text as follows:

h:\grpwise\gw5dom\wpgate\api41
gw5dom
gw5po

where the first line is the path to the API Gateway directory, the second
line is the domain name, and the third line is the post office name.

If you are using this for more than one post office or domain, either make
it available to one post office at a time or create more than one directory
to run WMS2GW from and copy it to those directories and give them each an
appropriate WMS2GW.PRM file.


Usage:
======
Each user should run WMS2GW.EXE on a machine that has a MAPI profile that
can access their WMS message store. Typically the machine that they normally
run WMS on is the best choice. When WMS2GW.EXE starts, they'll need to
choose the right MAPI profile (distributing WMS2GW.EXE before installing
GroupWise might make this easier as there will usually only be one profile).
They will then login to WMS (password will be required if it isn't saved).
Next, the user enters their GroupWise userID into WMS2GW.EXE's Username field.
Finally, the user clicks on the Convert button to process their inbox.

WMS2GW.EXE will accept a GroupWise userID on the command line for the
username. By deploying this tool with ZEN Works, you can extract the
GroupWise userID from NDS automatically and eliminate a possible chance for
user error in the migration. If a name is found on the command line,
WMS2GW.EXE will change the username field to read-only so the user cannot
change it and import messages to someone else's mailbox.

WMS2GW.EXE doesn't understand folders as Microsoft's MAPI Controls for Visual 
Basic do not expose the folders. Only the inbox will be migrated. Move messages
in accordance with this limitation.

Most problems can be solved by uninstalling and re-installing Windows Messaging.

Usernames containing spaces should be enclosed in double quotes
(ie. "Scott Lewis").

You may want to create user instructions from the following template. Change
the sample wording to match your specific configuration.

Instructions for migrating Windows Messaging System Messages to GroupWise
=========================================================================

1) Delete old messages that you no longer require.

2) Run WMS2GW.EXE on your workstation.

3) Signon to WMS by selecting the MSMAIL profile.

4) Enter your password, if required.

5) In WMS2GW.EXE, enter your GroupWise userID in the Username field.
   Your username in GroupWise is the same as your username was in WMS.

6) Click the Convert button. Depending on how much mail you have, how many
   attachments are on your messages and how many other users are migrating
   at the same time, your messages should show up as imported messages in
   GroupWise within a few minutes.


