Chat now with support
Chat with Support

Migrator for GroupWise 4.7.1 - 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

Migrating from a cached GroupWise mailbox

The SSDM will access the GroupWise client in whatever mode the client was last run. To migrate from a cached mailbox, the user must first login to the GroupWise client in cached mailbox mode, then close the client and start MFG's SSDM.

Did it work?

To verify an SSDM run for any given user, check the user’s Outlook folders to see if his/her mail migrated as it should have, and to see if the user is now receiving new mail in his/her Exchange mailbox.

If a user does not appear to be migrated (after running the SSDM)

The next section of this chapter explains how to make some of the SSDM’s screen displays "silent"—that is, invisible to the end user. In that case, ordinarily the gwdtapp.ini file is further modified to provide to the program whatever information the "silent" screen would otherwise collect from the user. But if the program can’t find that information in the .ini file, and if the screen that ordinarily collects it has been hidden, the function will fail and the user’s data will not be fully migrated. This is a likely cause of any failed or incomplete single-user migration if the gwdtapp.ini file has been modified to make one or more screens "silent."

Customizing the SSDM

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. For example, if an administrator intends to migrate users’ server mail and address books in batches using Admin-Driven Batch Migrator and only use Self Service Desktop Migrator for local archives, SSDM can be customized to migrate only archives and not offer the additional options that are ordinarily offered in the program.

These program customizations are optional, accomplished by manipulating certain parameters in the gwdtapp.ini file, as described in the topics below:

If you leave those parameters at their default values, the Desktop Migrator simply runs in its default mode, displaying all screens and all options.

Some elements of the SSDM program flow can also be controlled by command-line switches, appended to the program command when the Desktop Migrator is executed. These command-line switches, and how they interact with pertinent INI-file parameters, are described at the end of this chapter, in the topic Command-line switches for running the SSDM in silent mode.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating