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

adobjmerge.ini [ErrorsToWarn] section

adobjmerge.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.

adobjmerge.ini [General] section

EnableBPOS=1 enables the BPOS features in the AD Object Merge tool, and adds BPOS-D to the drop-down list of eligible migration targets. EnableBPOS=1 also tells the AD Object Merge Tool to display the Specify BPOS-D Identification Attributes screen, unless ShowBPOSIDAttrs=0 (as explained for ShowBPOSIDAttrs=<#> below).
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).
adobjmerge.ini [General] ShowBPOSIDAttrs=<#>
Determines whether the AD Object Merge tool will display the Specify BPOS-D Identification Attributes screen when EnableBPOS=1 (see above). This parameter permits selection of BPOS-D as the migration target but without showing the Specify BPOS-D Identification Attributes screen (ShowBPOSIDAttrs=0), in which case all settings on that screen remain at their defaults. Note that this parameter is ignored (irrelevant) if EnableBPOS=0.
Tells the program where it will find the user-list csv file, generated by the Directory Exporter, that specifies the users whose accounts the AD Object Merge Tool will merge in its current or next run. The <path> must be specified as a full UNC path including filename. For example:

adobjmerge.ini [PowerShell] section

adobjmerge.ini [PowerShell] IdleConnectionTimeoutSeconds=<##>
Specifies how long (in seconds) MFG will hold open an idle remote PowerShell connection before closing it. The default IdleConnectionTimeoutSeconds=30 is suitable for most environments. Note that this feature applies only to the duration of an idle state during a connection. Each command execution resets this timer to zero, so a series of commands with only short idle periods between commands could keep the connection open indefinitely. IdleConnectionTimeoutSeconds=0 tells MFG to not wait (wait 0 seconds) for a second command after a first, so every PowerShell connection would close immediately after only one command.
... where R is the number of simultaneous runspaces allowed by your tenant (typically 9), and S is the number of migration servers you will use. For example, if your limit is 9 runspaces and you intend to use one migration server, then MaxPowerShellConnections=8 = (9-1)/1. Or for a 9-runspace limit with 2 migration machines: MaxPowerShellConnections=4 = (9-1)/2. The default MaxPowerShellConnections=0 is interpreted as "no limit," effectively turning off this limiting feature.

gwdirapp.ini (Directory Exporter)

The gwdirapp.ini has the following sections:

Related Documents