Migrator for Notes to Exchange 4.15.2 - Administration Guide

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 to 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 to 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 for message attributes since they are already used, although they may be used to map Notes contact attributes to Exchange.

A custom property can be unnamed or named. If it is unnamed, you must select a 16-bit integer TargetProperty in the range 0x0001 to 0x7FFF that is not already in use by MAPI. If it is named, you can select any property-set GUID. If you select a property set that is already in use, you must choose a 32-bit integer or string ID that is 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-").

How do I customize the placeholder message that the Data Migration Wizard substitutes for encrypted messages?

Since the Data Migration Wizard does not migrate encrypted messages, it will substitute placeholder messages for encrypted messages in your users’ Exchange mailboxes. The Self-Service Desktop Migrator will then replace the placeholder messages with the real messages as it de-crypts and migrates them.

You can customize the content of this placeholder message by creating a simple text file of the content, and then editing the Global Default Settings to specify the use and location of the file. The message can be a simple notification, or may include instructions for launching and running the Self-Service Desktop Migrator to migrate the encrypted message bodies. For information about customizing the user interface of the Self-Service Desktop Migrator, see How to customize the SSDM (in the Migrator for Notes to Exchange Scenarios Guide).

After you create the text file, edit the Global Default Settings (see How do I add or edit program parameters?):

Then use Notepad or some other text editor to open the notesdtapp.ini file, set the same two parameter values in the [General] section of that file, and save the changes to notesdtapp.ini.

How do I customize the placeholder message that the Data Migration Wizard substitutes for filtered attachments?

The Data Migration Wizard does not migrate encrypted messages or their attachments, so it substitutes placeholder messages for the filtered attachments in your users’ Exchange mailboxes. The Self-Service Desktop Migrator can then replace the placeholder messages with the corresponding attachments as it de-crypts and migrates the associated messages.

You can customize the content of this placeholder message by creating a simple text file of the content, and then editing the Global Default Settings to specify the use and location of the file. The message can be a simple notification, or may include instructions for launching and running the Self-Service Desktop Migrator to migrate the encrypted message bodies. For information about customizing the user interface of the Self-Service Desktop Migrator, see How to customize the SSDM (in the Migrator for Notes to Exchange Scenarios Guide).

After you create the text file, edit the Global Default Settings (see How do I add or edit program parameters?):

Then use Notepad or some other text editor to open the notesdtapp.ini file, set the same two parameter values in the [General] section of that file, and save the changes to notesdtapp.ini.

How do I create or edit a template for personalized user-notification emails?

The Data Migration Wizard can generate personalized ("mail-merge") notification emails to end users to inform them of their migration and provide useful information to help them in their transition. The wizard lets you send either or both of:

These options were originally developed to facilitate notification emails to users at the time of migration, but the feature can also be used to send personalized emails to users before or after they are migrated. You can use such pre- and post-migration notifications to announce an upcoming migration, explain the implications to end users, and tell them what they can expect and what will be expected of them. To send pre/post-migration emails like this you can use the same process explained below to create or edit a template, and then use the Data Migration Wizard to only send the messages (and not mailbox-enable users or migrate user data). See How do I send pre- or post-migration notification emails to end users? for more information.

As in any mail-merge process, the template files contain variables that are replaced with actual values as each user’s email is created. The wizard merges a template file with per-user variable values drawn from the collection’s data table (in the SQL database), and/or with environment or system variables. (Actually the wizard draws the per-user values from an INI file, but the INI-file values are in turn drawn from the SQL database and are rewritten, per user, as each user is processed.)

Migrator for Notes to Exchange installs with three standard template files:

The Data Migration Wizard prompts you to specify a template file for each merged email you want to send. You can choose one of the standard templates listed above, or create and use your own templates. You can also edit any of the template files to add or delete or modify content to better suit your needs.

A mail-merge template file must conform to these specifications:

A variable specification in a mail-merge template is enclosed within a pair of dollar signs, like this: $VarSpec$. (Also see the default templates, installed with the applications, to see how variables are used within a template file.)

A template may contain any combination of INI variables, environment variables, and system variables. Environment and system variables characterize the wizard’s operating environment—the current date and time, for example— and are not unique per user. An INI variable is so named because its value is drawn from the associated INI file that the wizard consults as it processes the users in a collection. The wizard generates this "scratch" INI file at the start of every program run by copying parameter values from the wizard’s Task Parameters. The [User] section of the INI file contains only a single user’s data, drawn from the collection data table elsewhere in the SQL database, but this per-user data is rewritten to the INI file prior to the processing of each user so that the correct values are available to the wizard for each user processed. The wizard can therefore consult the [User] section of the INI file for per-user values when generating a notification email.