Chat now with support
Chat with Support

Migrator for GroupWise 4.7 - Scenarios Guide

About this guide Scenarios overview Migration to a proprietary Exchange target
Pre-migration preparations Batch migration process Post-migration activities
Migration to Office 365
Migration to Office 365 Pre-migration preparations Batch migration process Post-migration activities
SSDM (per-desktop) migration

Why and when to use the SSDM

Batch migrations and per-desktop migrations are performed using different migration engines, both included with Migrator for GroupWise. This chapter describes administrator planning and deployment of Migrator for GroupWise’s per-desktop Self Service Desktop Migrator (SSDM). For batch migration (multiple users at a time, performed by an administrator), see the Batch Migration sections of the preceding chapters: Migration to a proprietary Exchange target and Migration to Office 365.

The SSDM is used by an end user, or by an administrator on behalf of an end user, to extract a single user’s GroupWise data and migrate it to Exchange. Depending on your circumstances and preferences, you may choose to migrate some or all of your users one at a time, from each user’s desktop, using the SSDM. For example, some administrators prefer the per-desktop tool to migrate user archives when the archives reside on users’ individual workstations, where that option seems easier than prepping the user-list .csv file with per-user values for the locations of all the local archives.

Migrator for GroupWise’s SSDM provides a distributed migration option, which runs in memory on the user’s workstation. SSDM runs from a share, offers an optional Silent Mode to minimize end user interaction, and does not install anything locally. These features can eliminate the need for desktop visits by the admin during or after the migration, although an admin can run the SSDM at user desktops if he/she chooses, perhaps selectively for only some users. The per-desktop migration option can be used for a portion of the migration (e.g., for local archives) or to migrate all of a user’s data: the Exchange mailbox, PST files, or both.

Migrator for GroupWise’s Self Service Desktop Migrator is intuitive enough that many end users will be able to run it in interactive mode. However, some migration admins prefer to have more control over the migration options and minimize end user interaction. This can be accomplished by customizing the SSDM configuration, in advance, to enforce settings and eliminate choices and screens in accordance with a particular migration strategy. These customization options are fully described in the Customizing the SSDM section later in this chapter.

Before running the SSDM

Verify all of the Pre-Migration Preparations are complete before the first desktop migration is performed (see the Pre-Migration Preparations sections of the preceding chapters: Migration to a proprietary Exchange target or Migration to Office 365). The pre-migration tasks are performed just once prior to the data migration. Also, an update of the CSV data files may be necessary if any users have joined or left the organization since the last run of the Directory Exporter.

* 
IMPORTANT: Important Notes About the SSDM:
•
Verify that all users have access to the share containing gwdtapp.exe (the SSDM program file) and the AddressTranslation.csv and AddressTransla- tion.bin files. SSDM requires access to the address translation files, generated by the Migrator for GroupWise Directory Exporter, to convert addresses in messages, address books, and calendar content.
•
The SSDM cannot migrate archives if the GroupWise client is running in cached mode. If your users will be migrating archives, they should verify they are not running in cached mode before starting the SSDM.
•
When a Quest license key is updated, Migrator for GroupWise's Directory Exporter must be re-run to register the updated license with the SSDM.

If you want to run the SSDM with App-V

The SSDM must be sequenced in with the Outlook virtual application package. The SSDM cannot be sequenced separately, nor can it access a local Outlook install directly. The GroupWise client must be installed locally or also sequenced in with the Outlook package.

Also, you must edit the OSD file for gwdtapp.exe. Find:

<VM VALUE="Win32">
<SUBSYSTEM VALUE="windows"/>
</VM>

... and change the parameter value from windows to console.

Distribution of SSDM program and user communications

Before users can run the SSDM, they will need access to the program directory. The most common methods of distribution are:

•
Share the directory that is created during the Migrator for GroupWise installation and updated by the Directory Exporter.
•
Copy the contents of this directory to another location and share the new location. If the AddressTranslation.csv and AddressTranslation.bin files have been updated by Directory Exporter, you must also copy these files to the new directory.
•
Burn the contents of the end-user directory to a CD. Remember, if the AddressTranslation.csv and AddressTranslation.bin files have been updated, any such CD must be replaced with a new version containing the updated versions of those files.
•
Modify users’ login scripts to automatically launch the SSDM. In this case the SSDM program and address-translation data files still must be accessible to end users, as noted above.

You must tell your users where the SSDM program file is, and provide operating instructions for how to run it. Typically, an administrator will send an email to migrating users with a link to the SSDM program—at some network location accessible to all users—so each user can simply click the link in the email to launch the program.

If users will run SSDM in interactive mode, you should also include a copy of the Self Service Desktop Migrator User Guide (in PDF format), which explains how to operate the per-desktop program from the end user’s point of view. You may either copy the PDF file to a public-access folder and link to it from the same email that announces the SSDM program to your users, or simply add it to the email as an attachment.

Related Documents