gwmigapp.ini [General] section
Tells the program whether to migrate the ACLs of shared-access folders when MigrateEmptyFolders=0
(in the [GroupWise] section, telling the program to not migrate empty folders). If MigrateEmptyFolders=1
, the ACLs are migrated and any ACLRootVisibleOnly
parameter is ignored. The program will migrate shared-folder ACLs by default (ACLRootVisibleOnly=1
), but you can disable the feature by ACLRootVisibleOnly=0
tells the program to not copy ACL information to Exchange during the migration. By default (1) the program will
copy ACL information and will set folder permissions in Exchange.
enables the BPOS features in the Batch Migrator, and adds BPOS-D
to the drop-down list of eligible migration targets. This feature is off (0) by default.
Sets the inactivity timeout limit, by number of minutes, if the timeout feature is enabled by DoInactivityTimer=1
(see separate parameter above in this same [General] section). The inactivity timeout feature tells the program to abort a process if it receives no response from the destination server for longer than a specified number of minutes following a data transmission. For example, InactivityTimeoutMinutes=60
tells the program to set the timeout threshold at 60 minutes (1 hour).
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 (see above). By default the program migrates different address books to different folders, one folder per address book.
tells the program to run in Silent mode — to use the configuration options provided during a previous session and run without user input.
tells the program to migrate all data into a single pst
file per user. The default is 1, so data is migrated into multiple pst
Determines whether the Admin-Driven Batch Migrator will migrate message Categories
—color differentiation of messages within a folder, at the user's designation. The feature is enabled (DoCategories=1
) 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.
gwmigapp.ini [GroupWise] section
tells the program to not migrate HTML message bodies. By default (ExportHTML=1
) the program will migrate HTML message bodies.
tells the program to migrate RTF message bodies. By default (ExportRTF=0
) the program will not migrate RTF message bodies.
This parameter corresponds to a GUI element in the Directory Exporter: the GroupWise Soap Server URL
field in the GroupWise System Information
screen. The value specifies the location of the GroupWise SOAP web service. This parameter is optional, but will help resolve a duplicate-meetings issue that can occur in some scenarios in some environments where Quest CMG coexistence product is also deployed. When a GroupWise user creates a meeting in GroupWise, and then changes it (or changes one instance of a recurring series) after he/she is migrated, the invitees' calendars may show duplicate instances unless the SOAP service is enabled and its URL is specified. This solution works only for GroupWise 8 and later (not for GroupWise 7).
These four Login
parameters let you delay the program’s login to GroupWise:
Number of seconds (0
≤ x ≤ 9999) to wait between login attempts, if LoginAttempts
> 1. For example: LoginRetryWait=10
tells the program to migrate documents and document references as attachments. By default, documents and document references do not migrate. Note that if any of these documents are GroupWise hidden messages, you must also set [GroupWise] MigrateHiddenMsg=1
(see below) if you want to migrate the hidden messages.
tells the program to not migrate empty folders. By default, the program will migrate all folders regardless of whether they contain any items. Note:
, the program migrates ACLs by default unless AclRootVisibleOnly=0
(in the [General] section).
tells the program to migrate empty shared folders, if MigrateEmptyFolders=0
(which tells the program to not
migrate other empty folders). For example:
... tells the program to migrate empty shared folders, but to not
migrate other (non-shared) empty folders. By default (MigrateEmptySharedFolders=0
), empty shared folders are not migrated. If MigrateEmptyFolders=1
(the default), the program ignores this MigrateEmptySharedFolders
parameter and migrates all empty folders.
tells the program to migrate GroupWise hidden messages that occur as Document References in mail folders. This feature is associated with a check box (Migrate Document References in mail folders by migrating a copy of the document
) on the Specify Data for Migration
screen of the program. If that check box is marked, and if the documents to be migrated are GroupWise hidden messages, the hidden messages will be migrated only if MigrateHiddenMsg=1
tells the program to migrate the My Subject field of an appointment from GroupWise, and use it as the appointment subject in the target.
tells the program to migrate the My Subject field of a document from GroupWise, and use it as the document subject in the target.
tells the program to migrate the My Subject field of an email from GroupWise, and use it as the email subject in the target.
tells the program to migrate the My Subject field of a note from GroupWise, and use it as the note subject in the target.
tells the program to migrate the My Subject field of a phone message from GroupWise, and use it as the message subject in the target.
tells the program to migrate the My Subject field of a task from GroupWise, and use it as the task subject in the target.
, the program looks at the due-date property to determine whether it is an all-day event (due-date property is set to 0), or a task (due-date property is set to anything other than
tells the program to migrate an independent copy of each shared folder to each user to whom the source folder was shared. By default the program migrates only a single copy of each shared folder to the user who owned it in GroupWise, and sets ACL permissions on that folder for other users to whom the GroupWise folder was shared.
tells the program to migrate an independent copy of each shared PAB to each user to whom the source PAB was shared. By default the program migrates only a single copy of each shared PAB to the user who owned it in GroupWise, and sets ACL permissions on that PAB for other users to whom the GroupWise PAB was shared.
Associates a particular GroupWise Post Office/domain with its corresponding IPaddress:port
. These parameters support unambiguous GroupWise-to-Exchange mail forwarding for two users sharing the same name and Object ID, but residing in different Post Offices and different domains. You can configure as many of these parameters as necessary to associate a unique IPaddress:port
with each GW Post Office/domain. For example, if:
tells the program to migrate users' proxy rights along with the users' other account information. Prior to version 3.1, the program migrated proxy rights by default. As of version 3.1, the default is to not
migrate proxy rights (ProxyAccountRights=0
parameter, in the [Exchange] section, does the same thing for errors that occur between MFG and Exchange.)
tells the program to not try to count messages by folder, but instead just count all messages. If SkipCountByFolder=0
the program counts by folder and then by message to work around a bug in the GroupWise API that limits the folder count to 8191 messages. If a folder contains more than 8191 messages, then the program will automatically switch methods. If the program crashes when estimating the number of messages to be migrated, setting this parameter value to 1 will probably preempt the crash.
tells the program to not use Novell's Trusted Application API feature to automatically register itself as a trusted application, so it can migrate GroupWise user data without user passwords or proxy authorization. By default, the program will use the Trusted Application API feature (UseTrustedAPI=1
gwmigapp.ini [Outlook] section
gwmigapp.ini [PowerShell] section
Specifies how long (in seconds) MFG will hold open an idle remote PowerShell connection before closing it. The default IdleConnectionTimeoutSeconds=30
will be 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
would tell 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.