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.
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?):
• |
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: |
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.
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?):
• |
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: |
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.
• |
"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 intercepted by any forwarding rules that would re-route them to Exchange.) |
• |
"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. |
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.
Migrator for Notes to Exchange installs with three standard template files:
• |
ybm_template.html: for delivery to users’ Notes mailboxes immediately after migration, when migrating to a local Exchange 2010 or later server, or to a hosted-Exchange environment other than Office 365. |
• |
ynma_template.html: for delivery to users’ Notes mailboxes immediately after migration, when migrating to Office 365. |
• |
wte_template.html: for delivery to users’ Outlook mailboxes immediately after migration, when migrating to any target type. |
A mail-merge template file must conform to these specifications:
• |
A template file may contain UNICODE, UTF-8 or ANSI characters. UTF-16 is not supported. If an HTML tag specifying charset is included in the file, the charset will be sent with each email. |
• |
Maximum length of any single line in the file (after any merge variables are expanded) is 512 bytes, or 256 UNICODE characters. Any line that exceeds this limit will be omitted from the merged email. This may vary from user to user, as variables in the form are replaced with user-specific values. |
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.)
© ALL RIGHTS RESERVED. Feedback 使用条款 隐私 Cookie Preference Center