Migrator for GroupWise 4.7 - Program Parameters Reference Guide

Each line specifies a folder, by name, to be excluded from the migration. Upon installation, gwdtapp.ini contains these Filter[#] parameters by default:

You can add to this list to define more folders to be excluded. The digits appended to parameter key names need not appear in numerical order, but must in aggregate form an uninterrupted numerical sequence and must include Filter0.

The JUNK parameter value is a keyword that tells the program to create a folder named Junk E-mail, which will prevent Outlook 2003 from automatically creating its own Junk E-mail folder upon start-up. For example:

Determines whether the program will copy ACL information to Exchange during the migration. By default (ACLs=1) the SSDM will copy ACL information and will set folder permissions in Exchange.

Determines whether the corresponding migration option will be visible to the user on the Specify Data for Migration screen. The default AppDoesXxxx=1 makes the option visible. AppDoesXxxx=0 makes the option invisible (unavailable to the user) on the screen, and also:

Note that these parameters do not set the marked-vs-unmarked status of the corresponding checkboxes, although checkbox status can be controlled by the MigrateXxxxxx parameters. The SSDM chapter of the MFG Scenarios Guide (see Customizing the SSDM) explains how this parameter relates to others used to customize the SSDM.

See [General] ArchiveDestServerArchive below.

The ArchiveDest parameter specifies whether Archives should be migrated to the target server (ArchiveDest=server), or to a PST file (ArchiveDest=pst). The only valid values are pst (the default) or server.

If ArchiveDest=server, the SSDM then reads another boolean parameter (ArchiveDestServerArchive=<#>) to determine whether Archives should be sent to the user's server-mail mailbox (0) or to a personal-archive mailbox (1):

The default is ArchiveDestServerArchive=0, so that Archives will be migrated to the user's server-mail mailbox.

The Exchange personal-archives feature, available only in Exchange 2010 and later (including Office 365), lets a user keep archived items in a separate mailbox where they are more secure and accessible than in PST files. The ArchiveDestServerArchive parameter is ignored when migrating to an Exchange target where the personal archives feature is not available.

The boolean ArchiveDestServerArchive parameter is relevant only if ArchiveDest=server. If ArchiveDest=pst then the ArchiveDestServerArchive parameter is ignored.

Enables or disables date filtering, which lets you limit the items migrated by date: no earlier than, no later than, or both. The feature is disabled (0) by default—i.e., the date-filtering options are not presented to the user. Note: To use date filters with the SSDM, you may need to register the mscal.ocx file.

Specifies the number of additional times (valid range is 0–99 inclusive) to attempt to migrate an attachment if the first attempt fails. For example, AttachmentRetryCount=3 tells the SSDM that, if an attachment fails to migrate, the program should retry the migration three more times before giving up.

Determines whether the SSDM will migrate message Categories (color differentiation of messages within a folder, at the user's designation). The feature is enabled by default, but can be disabled by DoCategories=0. If the GroupWise source Category color does not exactly match one of Outlook's 25 standard colors, MFG will assign it to the closest matching color. Note: This feature requires GroupWise 6.5.7 or later on the admin's migration workstation.

Tells the SSDM to migrate (1) or not migrate (0) contacts' notes when migrating PABs. The option is off (0) by default. This feature is also available for the Admin-Driven Batch Migrator, where it is enabled/disabled (independently) by the same parameter in gwmigapp.ini.

Specifies how much detail the program will include in its run logs. Valid values are single-digit integers in the range 0–3 inclusive. The default LogLevel=1 is suitable for most routine production runs. If you are having trouble and want to diagnose a problem, set the value to 3 (verbose): LogLevel=3

The name of the single folder to which the program will merge multiple address books, if you want to migrate them to a folder other than the default Contacts folder. For example:

This parameter is ignored if MergeAddressBooks=0 and no address-book value is specified for the MergeAddressBookList parameter.

Tells the program to merge the contents of the named address book(s) into the single Contacts folder, or into a single folder as named by the MergeAddressBookFolder parameter (see above). Address-book name values are both case- sensitive and space-sensitive. You may specify two or more by using semicolons to separate the folder names in the list.

This parameter will be ignored if MergeAddressBooks=1, which tells the program to migrate all address books into a single folder (as described below). By default the program will migrate different address books to different folders, one folder per address book.

... tells the program to merge the contents of all migrated address books into the single Contacts folder, or into a single folder as named by the MergeAddressBookFolder parameter. By default the program will migrate different address books to different folders, one folder per address book.

... tells the program to migrate archives if the Specify Data for Migration screen does not appear, or sets the associated checkbox in that screen to be marked by default. A value of 0 tells the program to not migrate archives, or sets the associated checkbox to be unmarked by default. This parameter is ignored if AppDoesArch=0. The most common use of this parameter is to provide the necessary entry value when the program is configured to hide the Specify Data screen. The SSDM chapter of the MFG Scenarios Guide (see Customizing the SSDM) explains how this parameter relates to others used to customize the SSDM.

MigrateFreqContacts=1 tells the program to migrate Frequent Contacts if the Specify Data for Migration screen does not appear, or sets the associated checkbox in that screen to be marked by default. A value of 0 tells the program to not migrate Frequent Contacts, or sets the associated checkbox to be unmarked by default. The most common use of this parameter is to provide the necessary entry value when the program is configured to hide the Specify Data screen. The SSDM chapter of the MFG Scenarios Guide (see Customizing the SSDM) explains how this parameter relates to other parameters used to customize the SSDM.

MigratePAB=1 tells the program to migrate PABs if the Specify Data for Migration screen does not appear, or sets the associated checkbox in that screen to be marked by default. If MigratePAB=0 (default) the program will not migrate PABs, or will set the associated checkbox to be unmarked by default. This parameter is ignored if AppDoesPabs=0. This parameter is most commonly used to provide the necessary entry value when SSDM is configured to hide the Specify Data screen. The SSDM chapter of the MFG Scenarios Guide (see Customizing the SSDM) explains how this parameter relates to others used to customize the SSDM.

MigrateServerMail=1 tells the program to migrate server mail if the Specify Data for Migration screen does not appear, or sets the associated checkbox in that screen to be marked by default. A value of 0 tells the program to not migrate server mail, or sets the associated checkbox to be unmarked by default. This parameter is ignored if AppDoesMail=0. The most common use of this parameter is to provide the necessary entry value when the program is configured to hide the Specify Data screen. The SSDM chapter of the MFG Scenarios Guide (see Customizing the SSDM) explains how this parameter relates to other parameters used to customize the SSDM.

See [General] PABDestServerArchive below.

The PABDest parameter specifies whether PABs should be migrated to the target server (PABDest=server), or to a PST file (PABDest=pst). The only valid values are pst (the default) or server.

If PABDest=server, the SSDM then reads a separate boolean parameter (PABDestServerArchive=<#>) to determine whether PABs should be sent to the user's server-mail mailbox (0) or to a personal-archive mailbox (1):

The default is PABDestServerArchive=0, so that PABs will be migrated to the user's server-mail mailbox.

Personal archives is a feature only in Exchange 2010 and later, including Office 365, that lets a user keep archived items in a separate mailbox—where they are more secure and accessible than in PST files. The PABDestServerArchive parameter is ignored when migrating to a non-Office 365 hosted-Exchange environment, where personal archives are not available.

The boolean PABDestServerArchive parameter is relevant only if PABDest=server. If PABDest=pst then the PABDestServerArchive parameter is ignored.

The program needs this SelectedProfile parameter only if more than one eligible profile will be found on any user’s workstation. The SSDM chapter of the MFG Scenarios Guide (see Customizing the SSDM) explains how this parameter relates to other parameters used to customize the SSDM.

Specifies the destination folder (path) for the user’s migrated archive. The <path> is specified as a full UNC or mapped-drive path (without filename) relative to the user’s computer. For example:

The default is the Outlook default directory, which the program can determine from its operating environment. This parameter is therefore necessary only if you want users’ migrated archives to go somewhere other than the Outlook default directory. The SSDM chapter of the MFG Scenarios Guide (see Customizing the SSDM) explains how this parameter relates to others used to customize the SSDM.

See ServerMailDestServerArchive below.

The ServerMailDest parameter specifies whether ServerMail should be migrated to the target server (ServerMailDest=server), or to a PST file (ServerMailDest=pst). The only valid values are pst (the default) or server.

If ServerMailDest=server, the SSDM then reads a separate boolean parameter (ServerMailDestServer­Archive=<#>) to determine whether ServerMail should go to the user's server-mail mailbox (0) or to a personal-archive mailbox (1):

The default is ServerMailDestServerArchive=0, so that ServerMail will be migrated to the user's server-mail mailbox.

Personal archives is a feature in Exchange 2010 and Office 365 (only) that lets a user keep archived items in a separate mailbox—where they are more secure and accessible than PST files. The ServerMailDestServerArchive parameter is ignored when migrating to a non-Office 365 hosted- Exchange environment, where the personal archives feature is not available.

Note that the boolean ServerMailDestServerArchive parameter is relevant only if ServerMailDest=server. If ServerMailDest=pst then the ServerMailDestServerArchive parameter is ignored.

Determines whether the program will use large PSTs. By default (1) the program will use large PSTs if possible. Note: A setting of UseLargePsts=1 will not force Unicode PSTs if Outlook 2003 is not installed. The program cannot create PSTs without the proper MAPI components (from Outlook 2003) in place.