A Transend Corporation White Paper

A Transend Corporation 225 Emerson Street Palo Alto, CA 94301 (650) 324-5370 www.transend.com

Technical Reference Preparing GroupWise for Migration

Copyright August 27, 2010 by Transend Corporation Authored by John E. Hieb

Scenario Guide: Preparing Novell GroupWise for Migration

Table of Contents Section 1. Introduction ...... 1 Section 2. Basic Requirements ...... 2 Section 3. Preparing Novell GroupWise Server for Migration ...... 3 3-1-1 Enabling the IMAP protocol ...... 3 Section 4. Preparing the Workstation for Migration ...... 5 Section 5. Setting GroupWise Admin Permissions ...... 6 5-1-1 Proxy Access ...... 6 5-1-2 Trusted Mode ...... 8

ii Scenario Guide: Preparing Novell GroupWise for Migration

Section 1. Introduction

This technical reference gives you an overview on how to prepare your Novell GroupWise server and workstation for Migration. The goal of this document is not to include every possible configuration. Instead, the goal is to introduce you to the common setup items so that you can adjust as needed.

Page 1 of 10 Scenario Guide: Preparing Novell GroupWise for Migration

Section 2. Basic Requirements

The following list contains the basic requirements for migrating from or to Novell GroupWise.  The GroupWise Server must be version 5.5 or above (You need version 6.5 or greater to take advantage of Trusted Mode).  The workstation performing the migration must have the Novell Client installed. For Trusted Mode, you must be logged in with the Administrative account granted access to all of the user accounts.  The IMAP4 Protocol must be enabled so that live message data can be migrated through this protocol. You may use the GroupWise Client API; however, it is strongly recommended that you use the IMAP4 protocol when migrating live .  In some cases, when you are migrating between Microsoft Exchange and Novell GroupWise you will need two migration workstations. One workstation solely for the GroupWise API and GroupWise connections and another workstation solely for and Exchange connections. This is because the GroupWise and Outlook clients use similar mapi32.dll files, and they often conflict.  GroupWise archives must belong to active accounts or they will not migrate. If you will be migrating from multiple GroupWise archives then it is recommended that those archives are centralized in a share. Note You may use the OST/PST (non-Mapi) conversion choice when migrating from Microsoft Outlook OST or PST files. This conversion choice does not require Microsoft Outlook.

Page 2 of 10 Scenario Guide: Preparing Novell GroupWise for Migration

Section 3. Preparing Novell GroupWise Server for Migration

The following subsections are introductions on how to enable the IMAP protocol on your GroupWise Server. In many cases, the IMAP4 protocol is already enabled. Please contact your Netware Administrator for any other requirements you may need. Transend technical support cannot assist you in changing your Netware and GroupWise settings.

3-1-1 Enabling the IMAP protocol

1. Log into the workstation where ConsoleOne is installed 2. Start ConsoleOne 3. Select your GroupWise system 4. Select the Post Office Agents from the Toolbar 5. Select the Properties of the Post Office Agent

6. Select the Agent Settings from the GroupWise tab 7. Select the Checkbox to Enable IMAP if it is not already enabled

Page 3 of 10 Scenario Guide: Preparing Novell GroupWise for Migration

8. If the settings do not take effect right way then you may need to restart the Post Office Agent (POA), or restart your GroupWise server.

Page 4 of 10 Scenario Guide: Preparing Novell GroupWise for Migration

Section 4. Preparing the Workstation for Migration

Review the following items when preparing your workstation for migration. In some cases people have been able to have a successful migration without loading the Novell Client, and without using multiple workstations for a migration. Each project is different, and some GroupWise and Windows environments have their own unique challenges. Use the following information as a guide. If you run into technical difficulty with Windows, Netware, GroupWise, or Exchange/Outlook then we will first refer you to these steps.

1. Use XP, Vista, or Windows 7 to migrate email data. You may also use Windows 2003 or 2008 Server software; however, we do not recommend that you migrate email data on the same system as the email server software.

2. Install the Novell Client Software onto the workstation performing the migration. Ensure you log into Netware using the correct Tree, Context, and Server required for the GroupWise email system you are migrating. 3. The Novell is required to migrate Address Books, Calendars, Tasks, and GroupWise archives. It is recommended you use the IMAP4 protocol to migrate messages. 4. If you are migrating to or from Microsoft Outlook and Exchange, and if the workstation will have Novell GroupWise and Microsoft Outlook email client loaded onto it then Outlook must be the default email client for Windows. Also, make sure the Novell GroupWise profile is the default profile for Microsoft Outlook.

Page 5 of 10 Scenario Guide: Preparing Novell GroupWise for Migration

Section 5. Setting GroupWise Admin Permissions

You must have permission to migrate GroupWise user accounts, and there are three different ways to access user accounts for migration. They are: 1. Provide the user ID and password for each user 2. Give the account performing the migration Proxy access to each user account. Proxy access is normally granted by the user. Often, the Admin will give Proxy access to a GroupWise admin account during account migration. 3. Use Trusted Mode if you are running GroupWise version 6.5 or higher. Trusted Mode allows you to perform migrations for users without having to know each user password. You must have admin permission on the GroupWise server in order to use Trusted Mode. A user ID is still required.

5-1-1 Proxy Access

It is recommended that you use Trusted Mode instead of Proxy Access because it is much easier. If you cannot use Trusted Mode or Proxy Access then you must provide the username and password for each user.

GroupWise has a feature allowing one user to access email for another user. This is called Proxy Access. It is used when logging into GroupWise using the GroupWise email client API. More information can be found on Proxy Access in the GroupWise documentation. Proxy access allows User A to grant access rights to User B, so that User B may read or create email for User A.

If Proxy access has been given to the Admin performing the email migration then the Admin account will be able to convert email for users without knowing their password. It is recommended that you use Trusted Mode (see above), but if you are using a version of GroupWise older than 6.5 then Trusted Mode is not an option. In that case, use Proxy Access or provide the user password.

Use the GroupWise email client to give Proxy access to another user. The following procedures show how to give another user Proxy access to your account: 1. Start Novell GroupWise and Select Tools from the Toolbar 2. Select Options 3. Click on the Security Icon 4. Select the Proxy Access Tab

Page 6 of 10 Scenario Guide: Preparing Novell GroupWise for Migration

5. Enter the name of the person who you wish to grant Proxy access in the text box, or choose the Address Book Icon and locate the user. 6. At a minimum, give the user Read access Rights to , Appointments, Reminder Notes, and Tasks. 7. Press Apply and then OK To Perform a Proxy login using Transend Migrator modify the syntax of the GroupWise User field. Instead of using a single User ID, enter “UserB for UserA”, where UserB is the person who has been granted Proxy rights, and “UserA” is the person who owns the . The password required will be that of UserB. In batch mode, this syntax is used for the “FromDatabase” field. The following screen shot is an example of using a Proxy account with the single of Transend Migrator.

Page 7 of 10 Scenario Guide: Preparing Novell GroupWise for Migration

In batch mode, you would use the ToDatabase or FromDatabase keywords to specify the source or destination account, and this is also where you would enter in the Proxy information. Example: FromDatabase = jjones for jsnuffy ToDatabase = jjones for jsnuffy

5-1-2 Trusted Mode

Perform the following steps to configure Transend Migrator as a Trusted application. This procedure requires Netware Admin access to the GroupWise email server.

1. Download the Transend Trusted package from www.transend.com/ftp/gwtrustd.zip. This package contains two files, gwtrustd.exe and gwtapp.dll. 2. Place gwtrustd.exe in the same installation directory as Transend Migrator, and place gwtapp.dll into a directory on your system path, for example C:\Windows\System32. 3. Log into the Novell Network using the Novell Client as the GroupWise administrator. 4. Map a drive to the location of where the GroupWise domain and post office can be found (See Windows Help for how to Map a Drive for your version of Windows). The Trusted application requires a mapped drive and it needs to know where the domain files are located.

Page 8 of 10 Scenario Guide: Preparing Novell GroupWise for Migration

5. Open a Command Prompt by going into the Windows Start | Accessories program group or by using the Start | Run command. Change directories so that the current directory is the Transend Migrator installation directory.

Type in the following command to change directories:

CD\”Program Files\Transend Migrator”

6. Type in GWTRUSTD.EXE and press the Enter key

7. Press Y to continue or N to quit 8. Enter the name of the Trusted Application or press the Enter key to accept the default name of Transend Migrator. If you will be setting up more than one migration workstation then you will have to go through these procedures on each workstation, and you must provide a unique name for the Trusted Application. 9. This utility will ask you for the path to the GroupWise domain directory (This is the directory in which you can find the files gwdom.dc and gwpo.dc). 10. Enter a TCP address if you want Transend Migrator to be run from only the specified location. Normally, this option is not used. 11. When it completes successfully Transend Migrator will be a Trusted application. It creates inside the Transend Migrator installation directory the file gwappkey.dat, which contains the key information that Transend Migrator uses to enable Trusted mode.

Page 9 of 10 Scenario Guide: Preparing Novell GroupWise for Migration

At this point you can run Transend Migrator as a Trusted application; however, you must tell Transend Migrator that it is in Trusted mode by using one of the following switches:

Criteria Switch

When using the GroupWise Client API /trusted

When using the IMAP4 Protocol /gwtrusted

The switches are enabled by setting the program options in the graphical user interface of Transend Migrator, or by adding the switch to the command line.

Page 10 of 10