About MAPI properties
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?
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 iface 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?):
-
In the [General] section, set UseFilteredBodyMsg=1, and set an appropriate parameter value for
BodyLostDueToEncryptionMsg (the full path and filename of the customized text file). For example:
[General] UseFilteredBodyMsg=1
BodyLostDueToEncryptionMsg=c:\temp\replace.txt
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?
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 iface 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?):
-
In the [General] section, set UseFilteredAttachmentMsg=1, and set a suitable parameter value for
AttachmentLostDueToEncryptionMsg (the full path and filename of the customized text file). Example:
[General] UseFilteredAttachmentMsg=1
AttachmentLostDueToEncryptionMsg=c:\temp\replace2.txt
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?
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 can also generate migration summary emails to administrators to keep them apprised of migration status.
The wizard lets you send the following messages:
-
"You’ve been migrated" messages to Notes mailboxes: Generates a personalized mail-merge email to the Notes mailbox of every user in the collection, notifying them of their migration to the Exchange server. (The wizard inserts these messages directly into the users’ Notes mailboxes, so they are not icepted by any forwarding rules that would re-route them to Exchange.)
This email typically explains to the user that he or she has been migrated to Exchange, and should use the Outlook client for all future email and calendar activities. The email also typically provides each user’s new Outlook login credentials, and any other special instructions or tips that may be helpful.
-
"Welcome to Exchange" messages to Exchange mailboxes: Generates a personalized mail-merge email to the Exchange mailbox of every user in this collection, welcoming him or her to the Exchange environment and the Outlook client, and typically including information (or a link) to orient users to their new tools.
-
Send "Migration summary" messages to administrators: Generates a personalized mail-merge email to all the SMTP addresses that are specified in the Recipient SMTP address text box. The email provides the migration summary and often includes an attachment containing logs of the migration statistics for each user in the collection. The email message might also include an attachment that contains a log of deferred Notes emails to be sent at a future date and time by Domino.
The first two options were 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, use the process for creating or editing a template described in this section, and use the Data Migration Wizard only to 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? on page 331 for more information.
The third option can be used to provide migration summary information to administrators and migration teams. An email attachment can provide detailed migration status information for each user in a collection. Another attachment can provide a list of Notes emails that were scheduled to be sent by Domino at a future date and time.
As in any mail-merge process, the template files contain variables that are replaced with values as each 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. (The wizard draws the per-user values from an INI file, but the INI-file values are drawn from the SQL database and are rewritten, per user, as each user is processed.)
Migrator for Notes to Exchange installs with the following standard template files:
-
ybm_template.html: for delivery to users’ Notes mailboxes immediately after migration when migrating to an on-premises Exchange server, or to a hosted Exchange environment other than Microsoft 365.
-
ynma_template.html: for delivery to users’ Notes mailboxes immediately after migration when migrating to Microsoft 365.
-
migration_summary_template.html: for delivery to the specified SMTP addresses of the administrators who should receive migration summary emails.
-
wte_template.html: for delivery to users’ Outlook mailboxes immediately after migration when migrating to any target type.
-
ada_template.html: for delivery to users' Notes mailboxes when migrating to on-premises Exchange. Tells the users that their AD accounts have been created and provides account information and passwords.
-
o365_pwreset.html: for delivery to user's Notes mailboxes when migrating to Microsoft 365. Tells the users that their Microsoft 365 account passwords have been reset.
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, or you can 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.
