Migrator for GroupWise 4.7.1 - Administration Guide

Use a text editor to open the attrs.csv template, and save the open copy under the new name customattrs.csv. Make sure you save customattrs.csv as a unicode (not ANSI) file, in the folder(s) noted above, and delete any data rows that may appear in the copy.

Enter a data row for each GroupWise custom attribute you want to migrate, as follows:

•

ID: Name of the custom attribute—a unique string that distinguishes this row’s custom attribute from all others in the file.


	NOTE: Caution: If any data row(s) remain in the original attrs.csv file, make sure that no ID value in customattrs.csv is the same as any ID value in attrs.csv. Custom attributes will not migrate correctly if any ID value appears in both files.

•

SourceProperty: Name of an attribute that has been added to a GroupWise mail message, to be migrated to a property on an Exchange message.

•

TargetPropertySet: The GUID for the target property set, which must be one of these values:

•

PS_PUBLIC_STRINGS

•

PS_MAPI

•

{hhhhhhhh-hhhh-hhhh-hhhh-hhhhhhhhhhhh}

... where each 'h' is a hexadecimal char, with letters uppercased.

If TargetPropertySet is PS_PUBLIC_STRINGS or PS_MAPI, the familiar GUID for the set named will be substituted for the string provided.

TargetPropertySet can be left blank, but in that case TargetProperty (see below) must be an integer property ID in the range 0x0000-0x7FFF.

•

TargetProperty: Name of the corresponding MAPI property in Exchange. A hexadecimal user-property value will be created in Exchange on each migrated mail message with the GroupWise property, which will hold the value. The hexadecimal values of the created properties will be reported in the log (search for "custom attr" in the log file).

If TargetPropertySet (above) is left blank, this TargetProperty value must be specified as a 16-bit integer in the range 0x0000- 0x7FFF that is not already defined for some other MAPI property.

•

TargetPropertyType: The data type of the MAPI property, which must logically correspond to the data type used in GroupWise. Valid values are:

STRING MV_STRING SYSTIME BOOLEAN LONG

Also, "PT_" may be prepended to any of the five types above, so valid values include PT_STRING, PT_MV_STRING, etc.

Save and close the updated customattrs.csv file.

For example, a typical customattrs.csv file might look something like this:

Troubleshooting problems in migrating GroupWise custom attributes

You can use Microsoft’s MfcMapi.exe utility to view the property and its value, if they have been created. (The utility is a free download from Microsoft; Google- search for "mfcmapi" and visit the www.microsoft.com/downloads link.) Most problems in migrating custom attributes can be diagnosed by these quick tests:

•

Verify that the target property specified in the customattrs.csv file does not already exist, and that the target property is in the correct format. (See About MAPI Properties below for more information.)

•

Verify that the customattrs.csv file is UNICODE, not ANSI.

•

Verify that the last line in the customattrs.csv file is followed by a line feed and carriage return (achieved by positioning the cursor at the end of the last line and pressing Enter).

•

If any data row(s) remain in the original attrs.csv file, make sure that no ID value in customattrs.csv is the same as any ID value in attrs.csv. Custom attributes will not migrate correctly if any ID value appears in both files.

About MAPI properties

A named property's name is a property-set GUID and an ID that is either a 32-bit integer or a string. A 16-bit integer alias in the range 0x8000–0xFFFF is assigned to the named property by MAPI. That alias is mailbox-specific.

An unnamed property's name is a 16-bit integer in the range 0x0001–0x7FFF. That 16-bit integer is valid in all mailboxes. Examples of unnamed properties are 0x0070 (i.e., PR_CONVERSATION_TOPIC) and 0x6656, both of which happen to be used by MAPI. So these two examples cannot be used as target property values since they are already used.

A custom property can be unnamed or named. If it is unnamed, you must select a 16-bit integer TargetProperty in the range 0x0001–0x7FFF that is not already used by MAPI. If it is named, you can select any property-set GUID. If you select a property set already in use, you must choose a 32-bit integer or string ID not already in use in that property set. If you select a brand new property-set GUID, you need not worry about IDs already in use because there will not be any.

If you want named custom properties, Quest recommends you use the PS_PUBLIC_STRINGS property-set GUID (PS_PUBLIC_STRINGS being an alias for {00020329-0000-0000-C000-000000000046}), and use string IDs with a prefix that is unique to your application (like "Quest-").

Prepare the UsersToMigrate.csv for mailbox-enabling (conditional)

This section applies only if the AD/Exchange environment is configured for a resource forest and a user forest, with corresponding user accounts. In that case, you must configure the global default settings in gwmigapp.ini, in:

\Program Files\Quest\Migrator for GroupWise (for a 32-bit OS); or

\Program Files (x86)\Quest\Migrator for GroupWise (for a 64-bit OS)

Then, prepare (or verify) the values in a column of the exported directory data for the Batch Migrator to properly associate the resource accounts with the user accounts and properly enable mailboxes.

Before you begin, you must determine which column in the UsersToMigrate.csv will correspond to which AD attribute for the Batch Migrator to match corresponding user accounts in the resource forest and user forest. The column (AdSearchCol) and attribute (AdAttribute) are both specified in the [ActiveDirectory2] section of the program parameters in gwmigapp.ini:

•

AdSearchCol: The column in the UsersToMigrate.csv that contains values the program should search for each particular AdAttribute value to match corresponding user accounts in the resource forest and user forest. The column specified here and its per-user values must exist before the Batch Migrator is run.


	IMPORTANT: In the current Migrator for GroupWise version, the AdSearchCol parameter value must be set to SearchKey2 (the default value for this parameter) for the mailbox-enabling process to succeed.

•

AdAttribute: The AD attribute whose values the program should read in the AdSearchCol column of UsersToMigrate.csv, to match corresponding user accounts in the resource and user forests. For example:

[ActiveDirectory2]
AdSearchCol=SearchKey2
AdAttribute=userPrincipalName

... tells the Batch Migrator to match AD objects with users such that the value of each AD object's userPrincipalName attribute matches the value of the corresponding user's SearchKey2 column in UsersToMigrate.csv.


	NOTE: You can also reuse the SearchKey2 column to form the forwarding addresses. For more information, see 6: Specify Source-to-Target Mail Forwarding Domain.

To configure the program parameters:

Edit the parameter settings in the gwmigapp.ini file using a text editor, such as Notepad.

In the [ActiveDirectory2] section, set the appropriate parameter value for AdAttribute, as described above.

Close Notepad. The next time you run Migrator for GroupWise it will use this setting.

If you need to enter or edit the AdSearchCol column values:

•

Use Microsoft Excel to enter or edit the contents of the column you have designated as the AdSearchCol column in your UsersToMigrate.csv.