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. You can search in Google for "mfcmapi" and visit the www.microsoft.com/downloads link.) Most problems in migrating custom attributes can be diagnosed by these quick tests:
• |
Verify the target property specified in the customattrs.tsv file does not already exist, and that the target property is in the correct format. See About MAPI properties below for more information about this. |
• |
Verify that the customattrs.tsv file is UNICODE, not ANSI. |
• |
Verify that the last line in the customattrs.tsv file is followed by a line feed and carriage return (achieved by positioning the cursor at the end of the last line and pressing E). |
• |
If any data rows remain in the original attrs.tsv file, ensure that no ID value in customattrs.tsv is the same as any ID value in attrs.tsv. Custom attributes will not migrate correctly if any ID value appears in both files. |
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 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: |
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 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: |
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.
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Termini di utilizzo Privacy Cookie Preference Center