Chat now with support
Chat with Support

Migrator for GroupWise 4.7 - Administration Guide

About this guide AddProxy utility Directory Exporter AD Object Merge Tool Administrator-Driven Batch Migrator
Why and when to use the Admin-Driven Batch Migrator Before running the Admin-Driven Batch Migrator ... Online search feature Per-screen instructions and application notes Did it work? Remember to distribute any user .pst files
The Log Viewer Office 365 Admin Account Pool Utility Discovery utility

16: Specify GroupWise Information

This screen appears only if the Migrate archives option was marked in screen #14: Specify Data for Migration. Use the Browse button to locate and specify the root directory for your users' GroupWise archive files (or just type the value into the text box), and click Next.

Archive root directory: The top-level directory where user archives reside. Any archives to be migrated must be in this directory or its subdirectories. If other locations (e.g., a different disk drive) also contain archives, you must either rerun this program for each archive location, or run the Self Service Desktop Migrator program from each user’s desktop (or have your users run it).
NOTE: If you specify an Archive root directory here, and user archives are in diverse directory subtrees under the root, Migrator for GroupWise will search all subfolders under the root until it finds the archive it needs, and will repeat that search for every user. To speed up that process, leave this Archive root directory field empty, but then specify each user's subfolder path in the user-list .csv file, in the Archives column. The optional Archives column can be used like this to limit the volume of data the program must scan to find each user's archive, by specifying a subset of a larger shared directory structure. Multiple paths can be designated by separating them with a pipe ( | ) character. Examples:

17: Specify GroupWise Login Information

This screen appears only if the Migrate users option was marked on screen #2: Select Operations, or if the Set forwarding or Remove forwarding option was marked in screen #4: Select GroupWise Administrative Operations.

Specify the Login method (if necessary), and GroupWise PostOffice Path (if you want to access GroupWise via direct mode—see below), and click Next. If the GroupWise source is version 6.5 or higher and you are not setting or removing GroupWise mail-forwarding in this program run, the Login method will not apply and will appear grayed-out. For more information about this circumstance, see the topic Method of Access to GroupWise User Data, in chapter 3 of the Migrator for GroupWise Pre-Migration Planning Guide.

Login method (if offered): Select the appropriate option to indicate how the program should access users’ GroupWise accounts:
Use proxy account: Tells the program to rely on proxy rights for access to users' accounts.
For GroupWise 6.5 or higher: This option is available only if Migrator for GroupWise will set or remove GroupWise mail-forwarding in this program run. Enter the GroupWise user ID, Password, and the associated Email address in either GroupWise or SMTP format. For example:
For GroupWise 6.0: Enter the GroupWise user ID and Password of the admin account that has been granted proxy rights for these migrating users' accounts. The Email address field does not apply and therefore does not appear. The proxy rights must already be established before this program run; the AddProxy Utility can automate the process of obtaining proxy rights.
Use user passwords: Option available only when the GroupWise source is version 6.0, and will be grayed-out when the source is version 6.5 or higher. It tells the program to access users’ GroupWise data by logging into their accounts individually. If you opted to Set user password (in screen #4: Select GroupWise Administrative Operations), the program will use the passwords specified in screen #7: Specify GroupWise Passwords. If you did not opt to Set user password, the program will use the passwords in the Password column of the user-list .csv file.
Note that this option will appear grayed-out (unavailable) if you have not told the program to reset user passwords, or if the program finds no Password column in your user-list .csv file. (In this case, the program would have no way of knowing user passwords, and therefore would be unable to access accounts by passwords.)
Direct connection (optional) / GroupWise PostOffice path: This option lets you tell the program to access the GroupWise server via direct mode rather than via client-server mode, since direct mode is usually faster. If you leave this text box blank, the program will default to whichever mode was last used to connect to the GroupWise server. Otherwise, to require direct-mode access: Type your GroupWise PostOffice path into the text box, or use the Browse button to locate and specify your GroupWise PostOffice path.
NOTE: If necessary you can use the NetWare Administrator program, NWAdmin or ConsoleOne, to find the GroupWise PostOffice path: From the Tools menu, select GroupWise View ..., and then in the folder tree expand the branch for the GroupWise domain name. Right-click on the PostOffice name, and select Details. The displayed value for UNC Path is your GroupWise PostOffice path.

18: Specify Destinations for Migrated Data

This screen appears only if the Migrate users option was marked in screen #2: Select Operations. Specify the desired target location for each category of migrated data, and click Next.

Archives: Archive data can be migrated to a personal folder (.pst) file or a server-based mailbox. The default: a .pst file.
Address books: Address book data can be migrated to a personal folder (.pst) file or a server-based mailbox (the default).
Server-based data: Server-based data can be migrated to a personal folder (.pst file) or a server-based mailbox. The default: server-based mailbox.

19: Specify How To Migrate Shared Information

This screen appears only if your entries on earlier screens indicate that you intend to migrate shared folders, shared address books or proxy/delegate rights. Enter the requested information to indicate your preferences for the migration of shared items and proxy/delegate rights, and click Next.

A shared folder or address book in GroupWise can be migrated either to its owner (only) in Exchange, or to all of the users to whom the item was shared in GroupWise. The Migrator for GroupWise Pre-Migration Planning Guide (see the Migrating Shared Folders topic in chapter 3) explains how Migrator for GroupWise maps shared folders to Outlook.

For Shared Folders, choose to migrate shared folders either for each user or only for the owner (mutually exclusive):

Migrate a separate copy ... for each user having access rights: Tells the program to migrate a separate copy of the shared item for every user who had access to it in GroupWise.
If you choose to migrate to each user that has access rights, the program will migrate a complete copy for each user, and the multiple copies will become independent of one another upon migration. That is, any changes made to such a copy by User A will apply only to User A's copy, and not to User B's or any other user's independent copy.
Migrate ... only for the owner (single copy migrated): Tells the program to migrate only a single copy of the item, to the user who owned it in GroupWise. If you do choose to migrate only for the owner, you may also (optionally):
Define ACLs on the Exchange server using the shared folder permissions: Tells the program to read the GroupWise ACL for each shared item, and recreate it in Exchange, so that the migrated item will be re-shared with the same users who had access to it in GroupWise.
NOTE: The program will ignore a checkmark here if [GroupWise] MigrateEmptyFolders=0 and [General] ACLRootVisibleOnly=0 (in gwmigapp.ini).
Also, if you choose to migrate only for the owner, you may:
Post a message informing users how to access their shared folders: A checkbox that tells the program to post a message in each folder that was shared, explaining how to open the shared item in Exchange. If you select this feature, you can (optionally):
Message body: This button opens the associated RTF template file for editing, using whatever application is associated with RTF files (usually Microsoft Word) on your desktop. The template filename is SharedFolderNotificationTemplate.rtf. If you edit the template, be sure to save it as an RTF file—not as a Word doc file or any other file type.

For Shared Address Books, choose to migrated shared address books either for each user or only for the owner (mutually exclusive):

Migrate a separate copy ... for each user having access rights: Tells the program to migrate a separate copy of the shared item for every user who had access to it in GroupWise.
NOTE: If you choose to migrate to each user that has access rights, the program will migrate a complete copy for each user, and the multiple copies will become independent of one another upon migration. That is, any changes made to such a copy by User A will apply only to User A's copy, and not to User B's or any other user's independent copy.
Migrate ... only for the owner (single copy migrated): Tells the program to migrate only a single copy of the item, to the user who owned it in GroupWise. If you do choose to migrate only for the owner, you may also (optionally):
Define ACL on the Exchange Server: Tells the program to read the GroupWise ACL for each shared item, and recreate it in Exchange, so that the migrated item will be re-shared with the same users who had access to it in GroupWise.
NOTE: The program will ignore a checkmark here if [GroupWise] MigrateEmptyFolders=0 and [General] ACLRootVisibleOnly=0 (in gwmigapp.ini).
Post a message informing users how to access their shared PABs: Tells the program to post a message in the folder that was shared, explaining how to open the shared item in Exchange. If you select this feature, you can (optionally):
Message body: This button opens the associated RTF template file for editing, using whatever application is associated with RTF files (usually Microsoft Word) on your desktop. The template filename is SharedPabNotificationTemplate.rtf. If you edit the template, be sure to save it as an RTF file—not as a Word doc/docx file or any other file type.

For proxy/delegate access rights, you may:

Message body: This button opens the associated RTF template file for editing, using whatever application is associated with RTF files (usually Microsoft Word) on your desktop. The template filename is DelegateACLNotificationTemplate.rtf. If you edit the template, be sure to save it as an RTF file—not as a Word doc file or any other file type.
Related Documents