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.
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.
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:
|
Also, you must edit the OSD file for gwdtapp.exe. Find:
... and change the parameter value from windows to console.
• |
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. |
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.
© 2021 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy