Chat now with support
Chat with Support

Migrator for GroupWise 4.7 - Program Parameters Reference Guide

Introduction Parameters for Administrator Components Parameters for the SSDM

gwdirapp.ini [Config] section

gwdirapp.ini [Config] MigrateUsersSample=<path>
Tells the program where to save the user-list csv file that will specify to the batch-migration program which user accounts to process in its current or next run. The <path> must be a full UNC path including filename. For example:
gwdirapp.ini [Config] UsersToMergePath=<path>
Tells the program where to save the user-list csv file that will specify to the AD Object Merge Tool which user accounts to merge in its current or next run. The <path> must be a full UNC path including filename. For example:
gwdirapp.ini [Config] dumpaliases=<#>
dumpaliases=1 tells the Directory Exporter to extract users’ aliases from GroupWise and insert them into the AddressTranslation.csv file, in the TargetAliases column. (While aliases are exported from GroupWise, nicknames are not. Alias and nickname are not the same data element. To export nicknames as well, see gwdirapp.ini [Config] dumpNicknameAliases=<#> ) Then, when the Admin-Driven Batch Migrator mailbox-enables users’ Exchange accounts, it can load the aliases into Active Directory. This feature is disabled (0) by default.
When dumpNicknameAliases is set to 1, Directory Exporter extracts users' nicknames from GroupWise, and insert them to the TargetAliases column in the AddressTranslation.csv file. When the Admin-Driven Batch Migrator mailbox-enables users' Exchange accounts, it can load the nicknames into Active Directory. This feature is disabled by default.
Note: To export nicknames, set both dumpaliases and dumpNicknameAliases to 1. That is, you will export the aliases as well when exporting the nicknames.
Determines which formats of GroupWise alias will be created for the TargetAliases column in the AddressTranslation.csv file.
Note: This parameter only works when the parameter dumpaliases is set to 1.

userid@domain

Mandatory

userid.postoffice.domain@domain

1

firstname@domain

2

lastname@domain

4

firstname.lastname@domain

8

lastname.firstname@domain

16

userid.postoffice@domain

32

domain.postoffice.userid@domain

64

postoffice.userid@domain

128

The value of the parameter TargetAliasFormatTypes should be the sum of all values of the alias formats you select. For example, if set to 6, the formats firstname@domain, lastname@domain and the mandatory one userid@domain are selected (as long as the first name and last name fields have been filled in GroupWise).
When multipleSMTPDomain is set to 1, users are allowed to enter their Primary Internet Domain for the TargetAddress attribute, and multiple Secondary Internet Domains (separated by comma) for the TargetAlias attribute.
Note: This parameter only works when the parameter dumpaliases is set to 1.
Determines which GroupType value the Directory Exporter will assign to all groups in its GroupsToProvision.txt file. The Admin-Driven Batch Migrator in turn reads the GroupType values in GroupsToProvision.txt to determine the types of groups to provision in Active Directory. The value is a three-letter string defined by the combination of two elements:
For example, the default setting GroupType=GDL signifies a Global Distribution List. Similarly, GroupType=LSG tells the program to set all GroupType values in GroupsToProvision.txt to LSG (Local Security Group).
After the Directory Exporter runs, you can edit GroupsToProvision.txt to change the GroupType setting for any one or more groups individually, and thereby provision groups of different types within a single run of the Admin-Driven Batch Migrator. But the Directory Exporter will initially set all of the GroupType values to whatever value is defined by this INI parameter.
gwdirapp.ini [Config] UseAdminAPI=<#>
Determines whether the program will use or ignore the Admin API. Ordinarily this is on (UseAdminAPI=1) by default, but UseAdminAPI=0 tells the program to not use the Admin API — for example, if you are not using NDS DN and suspect the Admin API may be causing errors.
gwdirapp.ini [Config] WorkerLimit=<####>

gwdirapp.ini [ErrorsToIgnore] section

gwdirapp.ini [ErrorsToIgnore] Error[#]=<[####-###-###-########]>
Each Error[#] parameter specifies a single particular runtime error that the program should ignore when documenting its activities and outcomes in its log file. Each parameter value:
The digit(s) appended to an Error[#] key name arbitrarily differentiate one parameter from another. Multiple Error[#] parameters need not appear in numerical order, need not form an uninterrupted numerical sequence, and need not begin at 0. But the program will read only Error[#] parameters whose differentiating digits are within the range 0–99 inclusive.

gwdirapp.ini [ErrorsToWarn] section

gwdirapp.ini [ErrorsToWarn] Error[#]=<[####-###-###-########]>
Each Error[#] parameter specifies a single particular runtime error that the program should change to a warning when documenting its activities and outcomes in its log file. Each parameter value:
The digit(s) appended to an Error[#] key name arbitrarily differentiate one parameter from another. Multiple Error[#] parameters need not appear in numerical order, need not form an uninterrupted numerical sequence, and need not begin at 0. But the program will read only Error[#] parameters whose differentiating digits are within the range 0–99 inclusive.

gwdirapp.ini [General] section

Tells the Directory Exporter to skip directory data for the designated <User>, used to bypass a user if his/her data generates an error in the export process, as reported in the Error Log Report. For the <User> value, enter the exact identifying text string as it appears in the Error Log Report (a display name value). You can enter multiple parameters to skip multiple <User>s—that is, enter a FilterUser0 parameter for the first user you want to skip, then FilterUser1 for the second, FilterUser2 for the third, and so forth. Example:
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 LogLevel=3 (verbose).
Related Documents