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 (AD Object Merge Utility)

The adobjmerge.ini has the following sections:

adobjmerge.ini [ActiveDirectory] section

adobjmerge.ini [ActiveDirectory] AllowUpdateOfAttributes=<#>
... would prevent the update of AD attribute values with data from the source csv file. By default (AllowUpdateOfAttributes=1), the program will overwrite any values in AD that differ from the corresponding attribute values in the source.
adobjmerge.ini [ActiveDirectory] AlwaysUseOldExchDn=<#>
AlwaysUseOldExchDn=1 (the default) tells the program to always use the old legacy Exchange distinguished name (DN) for mail forwarding, so that free/busy lookups will be directed to the Exchange server (rather than to GroupWise). This feature is useful when objects were synchronized into AD by Quest CMG Directory Connector or Microsoft's Connector, and you want free/busy lookups to work for existing Outlook 2003 users after GW users migrate, and you don't mind Outlook 2003's auto-complete feature presenting long, cryptic user names. To use this feature:
Set AlwaysUseOldExchDn=1 in the [ActiveDirectory] sections of both gwmigapp.ini and adobjmerge.ini, and
Set RemoveSrcAddresses=1 in the [ActiveDirectory] section of gwmigapp.ini.
The feature can be disabled by AlwaysUseOldExchDn=0, which is appropriate if objects were synched into AD by some method other than CMG's Directory Connector or Microsoft's Connector, or if you don't care about free/busy lookups for Outlook 2003 users, or if you will simply force all Outlook 2003 clients to refresh their caches, or if you prefer the shorter, “friendlier” names in Outlook 2003's auto-complete feature.
Each Attr<#> parameter specifies a Contact attribute whose values the AD Object Merge Tool will merge into the corresponding AD security object record, when the program merges the Contact into the object and deletes the Contact. You may define one or more Attr<#> parameters to specify one or multiple attributes whose data you want to carry into the merged object records. For example:
The digit(s) appended to an Attr<#> key name differentiate one parameter from another. Multiple Attr<#> parameters need not appear in numerical order, but must in aggregate form an uninterrupted numerical sequence beginning with Attr0.
adobjmerge.ini [ActiveDirectory] CmgExcludeFromDirSync=extensionAttribute<##>
The parameter defaults to extensionAttribute15, which is suitable as long as your organization is not already using extensionAttribute15 for some other purpose. If you are already using extensionAttribute15 (and are using the CMG Directory Connector), change the parameter value to some other unused AD attribute (within the range 1–14). Note that this parameter can be set only if SetCmgExcludeAttr=1 (see notes for SetCmgExcludeAttr=, also in this [ActiveDirectory] section).
adobjmerge.ini [ActiveDirectory] CreateUserNameFrom=<#>
Tells the AD Object Merge tool whether to use the values from TargetAddress (CreateUserNameFrom=1) or NDSUserName (CreateUserNameFrom=2) when updating the SAMAccountName attribute values in AD security objects. The SAMAccountName is updated only if ReplaceExistingUserName=1; the CreateUserNameFrom parameter is ignored if ReplaceExistingUserName=0.
adobjmerge.ini [ActiveDirectory] CustomAttr[#]=<AttributeName>
Each CustomAttr[#] parameter in adobjmerge.ini specifies a particular attribute in Active Directory to receive the values of a particular GroupWise custom attribute when the AD Object Merge Tool provisions objects into AD. Example:
You may define as many as 20 custom attributes, CustomAttr1 through CustomAttr20, but every attribute defined in adobjmerge.ini must correspond to an existing column in the csv data files.
Another set of CustomAttr[#] parameters (in gwdirapp.ini) tells MFG's Directory Exporter what data columns to create in the csv files for custom GroupWise attributes, so the Directory Exporter can then populate those columns with the correct data. In short, the CustomAttr[#] parameters in gwdirapp.ini map GroupWise custom attributes to particular columns in the csv data files, while the CustomAttr[#] parameters in adobjmerge.ini map those columns in the csv files to particular AD attributes.
Determines whether users newly created by the AD Object Merge Tool (if ProvisionUsers=1) should be logon-enabled. By default (0), any such newly created users are not logon-enabled.
adobjmerge.ini [ActiveDirectory] MailEnableAttempts=<#>
adobjmerge.ini [ActiveDirectory] MailEnableRetryWaitSeconds=<##>
Determines the value that MFG's AD Object Merge Tool will assign to the AD mAPIRecipient property if UseMapiRecipientFlag=1 (elsewhere in this same [ActiveDirectory] section). If UseMapiRecipientFlag=0, the program will ignore this MapiRecipientFlag= parameter and leave the AD property at its <not set> default. For example:
... (the default) tells the Merge Tool to set the AD mAPIRecipient property to TRUE, while a value of 0 tells the program to set the property to FALSE. Note: If UseMapiRecipientFlag=1 and Provision Users if not found is selected, the AD Object Merge Tool will set AD's mAPIRecipient to FALSE. See the UseMapiRecipientFlag parameter below for more information about this feature.
IMPORTANT: The same two parameters must also be set to the same values in the [ActiveDirectory] section of gwmigapp.ini, so the Batch Migrator can correctly set the mAPIRecipient when that program is run to mailbox-enable users.
adobjmerge.ini [ActiveDirectory] MergeContactAttribWins=<#>
Determines which of two methods the AD Object Merge Tool will use to find a contact when merging: by the SMTP address (MergeFindbySMTP=1), or the default method (MergeFindbySMTP=0) of finding a contact by its GroupWise source address. The value of this parameter also sets defaults for two other related parameters in this [ActiveDirectory] section (see below):
If MergeFindbySMTP=1:
If MergeFindbySMTP=0:
adobjmerge.ini [ActiveDirectory] ReplaceExistingUserName=<#>
Tells the AD Object Merge tool whether to update AD security objects' SAM­AccountName attribute values. When this feature is enabled (ReplaceExisting­UserName=1), the CreateUserNameFrom parameter (see separate listing above, also in this [ActiveDirectory] section) tells the program whether to use the TargetAddress (CreateUserNameFrom=1) or NDSUserName (CreateUserNameFrom=2) to update the SAMAccountName.
adobjmerge.ini [ActiveDirectory] MergeReqImportedFrom=<#>
adobjmerge.ini [ActiveDirectory] MergeReqProxyAddress=<#>
Tells the AD Object Merge tool whether to copy X500 addresses into their corresponding AD user objects. For example MergeX500=1 tells the program to merge X500 addresses into the AD user objects. By default (MergeX500=0) the program will not merge X500 addresses.
Determines whether the AD Object Merge Tool will create a new mail-enabled security object in AD when none is found by the program to correspond with a user in the UsersToMerge.csv file. Such new objects will be created in the container specified by the UserContainer parameter, also in this [ActiveDirectory] section. By default (0), the program will not create such objects.
Note that these PSRetry parameters can also be set in gwmigapp.ini.
Sets the interval (in seconds) between retry attempts when the program will retry data transmissions to Active Directory due to errors in prior attempts. This PSRetryWait parameter is used in conjunction with PSRetryAttempts to control retries of transmissions to AD, as described above for the PSRetryAttempts parameter. The default is 15 seconds for migration to a proprietary Exchange, or 40 seconds for migration to Office 365.
Determines whether the AD Object Merge tool will populate the extension attribute designated by the CmgExcludeFromDirSync parameter (also in this [Active Directory] section), which in turn specifies the AD attribute that will determine when merged and mailbox-enabled objects should synchronize back into GroupWise. This SetCmgExcludeAttr parameter is set to 1 (on) by default, but you can set SetCmgExcludeAttr=0 to tell the program to not set (to ignore) the CmgExcludeFromDirSync= parameter.
Determines how the program will set the Exchange option to Automatically update e-mail addresses based on e-mail address policy. (The Automatically update... feature is an Exchange feature, offered as a check box in the Exchange Management Console, on the E-Mail Addresses tab of the Data Properties for each mailbox.) This MFG SetRecipPolicy parameter specifies whether MFG should automatically enable or disable that Exchange feature for the AD objects in a designated user group. For example:
... tells MFG to enable the Exchange auto-update feature (mark the Exchange check box) for the AD objects after processing. If SetRecipPolicy=0, the program disables the Exchange auto-updating feature (unmarks the Exchange check box). The default is 1 for any target type, including Office 365. Note: When mailbox-enabling, make sure that this setting for SetRecipPolicy=<#> matches the setting in gwmigapp.ini for [Exchange] EmailAddressPolicyEnabled=<#>.
adobjmerge.ini [ActiveDirectory] SetUserAccountControl=<#>
Tells the program whether to set the userAccountControl attribute value in Active Directory. If:
… then the program will set the userAccountControl attribute value to the integer value specified by the UserAccountControl= parameter (also in this [ActiveDirectory] section). By default (SetUserAccountControl=0), the UserAccountControl parameter is ignored.
Determines whether the program must find contacts—as was required prior to the 3.1 release when it was revised to accommodate the Migrator for NDS. For each user listed in the UsersToMerge.csv file, if SyncObjRequired=0 (default) and no corresponding contact is found, the program simply merges the SourceAddress from UsersToMerge.csv into the AD security object, to mail-enable the object. But if SyncObjRequired=1, then the program will mail-enable an object only if it finds a corresponding contact.
adobjmerge.ini [ActiveDirectory] UseMapiRecipientFlag=<#>
Determines whether MFG's AD Object Merge Tool will set the AD mapiRecipient property according to the MapiRecipientFlag parameter value (also in this [ActiveDirectory] section). If UseMapiRecipientFlag=0, the program will leave the AD property at its <not set> default. But if:
... (the default), the program will set the AD property according to the MapiRecipientFlag parameter value. Note: If UseMapiRecipientFlag=1 and Provision Users if not found is selected, the AD Object Merge Tool will set AD's mapiRecipient to FALSE. See the MapiRecipientFlag parameter above for more information about this feature.
IMPORTANT: The same two parameters must also be set to the same values in the [ActiveDirectory] section of the gwmigapp.ini file, so that the Admin-Driven Batch Migrator can correctly set the mapiRecipient property when that program is run to mailbox-enable users.
adobjmerge.ini [ActiveDirectory] UserAccountControl=<###>
Assigns the integer value to the userAccountControl attribute value in Active Directory, but only if this feature is enabled by SetUserAccountControl=1, also in this [ActiveDirectory] section. If SetUserAccountControl=1 and this User­AccountControl parameter is unspecified, its value defaults to 512 (NORMAL_ ACCOUNT). If SetUserAccountControl=0, this UserAccountControl parameter is ignored.
... will put all new users in the Users container. The designated container must already exist. This UserContainer parameter is required if ProvisionUsers=1.

adobjmerge.ini [ActiveDirectory2] section

adobjmerge.ini [ErrorsToIgnore] section

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