Chat now with support
Chat with Support

Binary Tree Migrator for Notes 20.12 - Release Notes

Release Notes

Binary Tree® Migrator for Notes 20.12

May 2021

These release notes provide information about the Binary Tree Migrator for Notes 20.12 release.

Topics:

 

About this release

Migrator for Notes is the most comprehensive software available for migrating from HCL Domino to Microsoft Exchange.

Migrator for Notes not only supports migrations to on-premises Microsoft Outlook and Exchange, but also to online versions of Microsoft Outlook and Hosted Exchange, including Office 365.

Migrator for Notes, part of Binary Tree’s suite of migration solutions that includes Directory Sync Pro and Notes Integration, offers unmatched data fidelity, migration management, and migration throughput.

Migrator for Notes 20.12 is a minor release, with new features and functionality. See New features and Enhancements.

New features

New features in Migrator for Notes:

  • The Migrate Unfiled Documents option has been added to the Migration Profile Options. This option determines if “unfiled” documents will be migrated. (54015)

  • To resolve formatting issues with the Sametime Chat history, the "Process Sametime history as" setting has been added to allow you to select the format as Rich Text or MIME. (75337)

  • The “Override existing license" option has been added to the Office 365 Settings page. This setting allows for overriding an existing license on accounts being processed, replacing the license with the new selection. (75965)

  • The "Copy Manager on Notification" setting has been added to the Message Template settings. Select this setting to send a copy of the message to the user’s manager. This setting is available only when Other Settings - Advanced features is enabled and the account being sent the notification has the Manager field competed in the Domino Directory. (76044)

  • New settings to Skip reprocessing users that have previously failed and to Reprocess successful matches have been added to the Email Repliability Matching settings. (76059)

  • Exchange Environment, Remote Azure AD Endpoint, and Azure AD Environment settings have been added to the User Provisioning Settings to handle connections for regional data centers. (76174)

See also:

Enhancements

The following is a list of enhancements implemented in Migrator for Notes.

Table 1. General enhancements

Enhancement

Issue ID

The two migration job log files have been combined into a single log file.

47509

For migrations that have repeated network errors, the migration of accounts is now automatically re-tried using the auto retry processing.

64665

Migration will now be terminated if the Name Translation process cannot connect to the source database.

65900

Updated email repliability to validate against canonical Notes name for accounts where there are multiple entries with the same common name.

75031

Migrations failures due to network errors have been added to re-queue processing.

75323

Unfiled processing has been updated to skip opening documents that are already in the migration history to allow for faster Unfiled checks.

75336

Passwords passed from the engine to the Outlook Agent are now hashed.

75385

The Outlook Agent has been updated to use the registry-stored account and password if not provided when called from engine.

75386

The User Provisioning Settings have been updated to hide settings that are not applicable to Office 365 migrations.

75952

Support for double-byte character set (DBCS) has been added for the following fields:

Rooms & Resources:

  • Room Label

  • Resource Label

  • Online Label

  • Location Detail Indicator

Migration profile:

  • Unfiled folder name

Other Settings:

  • Encrypted Items Migration (text)

75966

Updated Settings to include a configurable list of Notes system folders for use with the Fix Folders agent.

75967

Settings that are not applicable to Office 365 migration are hidden on the User Provisioning Settings screen.

76060

Support for double-byte character set (DBCS) for encrypted body message has been added.

76148

Resolved issues

The following is a list of issues addressed in this release.

Table 2. General resolved issues

Resolved Issue

Issue ID

An issue where migrated external meeting requests had the reply address set incorrectly has been resolved.

41515

An issue where migrations are incorrectly marked as successful when the Domino server runs out of space and cannot open source folders has been resolved.

52658

An issue where messages with the follow up flags set to high priority/low priority are migrated without the follow up flags has been resolved.

54900

An issue where the reply to and forwarded icons indicating that a message has been replied to or forwarded did not migrate has been resolved.

54901

An issue where address field values with leading spaces caused Name Translation Table lookups to fail has been resolved.

69928

An issue where the reply address was set incorrectly for migrated "on behalf of" messages has been resolved.

74131

Corrected a condition where a document causing a Notes out of memory error was not being skipped during the fault recovery migration.

76085

An issue where Modern Auth failed if LegacyExchangeDN was not found and terminated abnormally has been resolved.

76161

An issue where Modern Auth abnormally terminated if GetTopOfInformationStore fails has been resolved.

76162

An issue where initialization failed on Notes version 10.0 has been resolved.

76243

Corrected an issue where when using Modern Authentication, and targeting an Archive mailbox, Migrator for Notes failed to connect to the target archive mailbox.  Basic Authentication must remain enabled for Autodiscover, but Modern Authentication can be used for mailbox access.

76265

Known limitations

Most of the known limitations and issues of any migration process are due to feature inconsistencies between the source and target environments. Features that are available in the Notes environment cannot be migrated to a target environment that does not offer the same or comparable features. Other limitations are due to feature incompatibilities where similar features are available in both the source and target environments, but their implementations are so different that migration is impractical.

While every effort is made to determine the specific limitations of a migration process, so that these are available for planning, communications and support, it is possible that there may be unknown limitations. These can occur in particular with changes to source or target system versions and in the case of email migrations for any data generated by third party system changes. Where previously unknown limitations in the data migration are found these would be reviewed to determine if the item can be resolved and migrated but it should be noted that these may result in a new known limitation.

The following is a list of known limitations or issues, including those attributed to third-party products, known to exist at the time of this release.

Table 4. AWD\Configuration known limitations

Known limitation

Issue ID

The Store Password feature does not validate the password and will allow you to store an incorrect password without prompting for a valid password when "Get Server List" is clicked.

16596

Table 5. AWD\Migration Workstation known limitations

Known limitation

Issue ID

If more than one instance of Lotus Notes or Notes Migrator is installed on a migration workstation, you will be prompted for the Notes password for each migration.

16688

Table 6. Calendar Migration known limitations

Known limitation

Issue ID

"Description:" appears in the body of migrated calendar documents when viewed in Outlook Web Access.

16629

Attachments in migrated calendar entries may not appear in the same position as in Notes when viewed from Outlook.

16635

If an invitee of a migrated meeting is changed from Optional to Required, the invitee's name appears in both Optional and Required fields in OWA. This is not a problem in Outlook.

16650

Calendar entries with a repeat pattern of Every Other Year are not natively supported in Exchange and are migrated as Yearly entries.

16654

When the migration setting to add Room, Resource and Online Meeting Place information to the body of Calendar entries is selected, and there is no Room, Resource or Online Meeting Place in the calendar entry, "See Details Below" is still added to the Location field.

16655

Subjects of Repeat Calendar entries that have carriage returns will not be displayed properly in Outlook and OWA 2007.

16659

Rooms and Resources added or removed to a Notes repeat meeting after the meeting was created will appear properly on each occurrence of the migrated meeting, but not the meetings series.

16663

User values in the BCC field of a migrated calendar item will appear in the Resource field. This is because Exchange uses the BCC field for resources, so any names in the BCC field will be treated as a resource. If the location field is empty, Outlook will display the resources in the location field also (it assumes resources will be a room or online meeting place).

16669

If "Automatically adjust clock for daylight saving changes" on the "Date and Time Properties" dialog box is not checked, and/or the latest Microsoft DST patches have not been installed, multi-day calendar events that start in one Daylight Savings Time period and end it another will appear off by 1 hour during the Daylight Savings Time period in which they were not created.

16685

Migrated recurring calendar events, where invitees have been added or removed from single instances will not list the correct attendees on the Chair Person's calendar.  However, the invitees’ calendars are correct.

16713

A migration crash can occur with an excessive amount of data (over 50 entries) in the Location and Rooms fields.

16717

Enterprise Vault links in Domino calendar items are missing after migration.

16758

Migrated meeting invitations that are unread in Notes are not displayed in the OWA calendar until after they are viewed post migration. (21865)

21865

Calendar items that do not have a start or end date causes a migration failure.

44404

Notes calendar entries' High Importance property does not get migrated to O365. Migrated calendar entries will be migrated as Normal importance.

57585

Attachments in migrated calendar entries may not appear in the same position as in Notes when viewed from Outlook.

16635

Table 7. Calendar Migration\Anniversary known limitations

Known limitation

Issue ID

The Play Sound reminder option in Lotus Notes Calendar items does not migrate to Outlook.

16618

Lotus Notes Anniversaries with the 'Pencil In' option selected are migrated to Outlook with a Show As: Free, instead of Tentative.

16625

Reminder sound notification is not maintained on a non-repeating Anniversary after migration.

16653

A recurring anniversary series that has been modified will appear on the correct day(s), but the dates displayed in each occurrence reflect the original date.

16687

Location and Category fields are not migrated in Anniversaries.

16712

Birthday and Anniversary data for local contacts are not added to the Outlook Calendar.

45182

Table 8. Calendar Migration\Delegation known limitations

Known limitation

Issue ID

If an invitee delegates one or more instances of a repeating meeting to someone else and the chairperson then updates the meeting, the entire series will appear on the original invitee’s calendar post migration.

16798

Table 9. Calendar Migration\Meetings known limitations

Known limitation

Issue ID

Embedded images in calendar entries appear as attachments in migrated calendar documents.

16614

The chairperson of an unaccepted meeting appears in the Required field after migration.

16627

Responses from attendees added after the original invite is issued do not update the chair's calendar tracking status.

16675

With the setting "Process meetings with no end date using ICAL information" set to yes, meetings with no end date sent from Outlook to Notes do not migrate properly if updates/reschedules have been accepted in Lotus Notes.

16676

Changes to migrated meetings with Rooms and/or Resources are not updated in the Domino Resource Reservations database. Updates are not properly made in the Notes Rooms and Resources database if a one-time meeting or reoccurring meeting is cancelled in Outlook. Additionally, updates are not properly made in the Notes Rooms and Resources database or migrated Room and Resource mailbox if individual occurrences are cancelled or rescheduled in Outlook.

16698

If an occurrence of a migrated repeating meeting is changed by the migrated chair in Exchange, it does not appear correctly on the calendar of Invitees that were added after the original meeting was created.

16699

Required attendees and resource do not show up in a printer output of the meeting with a migrated meeting. Native meetings created in Outlook show this information in the printed output.

16741

Meetings and Appointments in Notes that have the choice "Mark Available" checked are listed as "Tentative”, instead of "Free”, when migrated to Exchange.

16757

A meeting identified as a repeating meeting, but contains no repeat pattern, will not migrate the remaining events if one of the events has been cancelled.  The meeting will be listed in the log as being skipped because it was cancelled, when in truth, only one of the occurrences was canceled.

16766

Unknown time zones display the incorrect time even though the meeting is on the calendar at the proper date and time.

16778

The Response Status is not cleared when a critical change (date/time/location) is made by the chair after the invitee has accepted the original meeting. When the chair invites, the invitee accepts, the chair changes the date, and then migration occurs, the migrated calendar event will contain the invitee response to the original invite, even though it is not invalid/obsolete due to the date change. The date change notice will migrate correctly, and later responses will correctly update the chair tracking. In the time between migration and the invitee responding to the change, the chair tracking will continue to show the invitee as accepted even though the change has been issued.

16791

If the entire series of a repeat meeting was rescheduled prior to migration, changes post migration will generate an NDR.

16813

If the chair of a meeting cancels an instance of a recurring meeting prior to migration by using the 'Delete' key, Domino deletes the child document from the database. Since the child document is missing, Notes Migrator will use the original pattern during migration, and the canceled meeting will appear on the calendar in Outlook.  To avoid this, the canceled meeting(s) instances should not be deleted from the source database.

16823

Executable (.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC) and consumable (.PST) attachments to calendar items are delayed when migrating. Items appear approximately 30 to 45 minutes after migration completes.

41359

When an all day, repeating event is rescheduled in Notes before migration, the reschedule dates are not applied in Outlook. The original all-day event dates are used except for the first booking in the series.

41856

Due to Exchange’s inability to process a large number of exceptions, during a migration, Notes Migrator will not create more than 200 exceptions for an event. Any exception beyond the first 200 will not be applied, and this may show as updates/reschedules/additions/cancels/etc. not appearing on the later occurrences.

37682

Table 10. Calendar Migration\Reminders known limitations

Known limitation

Issue ID

Tasks/ToDos, Notices (invites and updates) that have reminders and Messages that have a follow-up/reminder set will cause many past due pop-up reminders in outlook after they are migrated. Clicking the "dismiss all" button will resolve the issue.

16705

Because there is no equivalent in Outlook, Reminders migrate as appointments with the free time blocked out.

16771

Table 11. Contact Migration known limitations

Known limitation

Issue ID

Migration of personal NAB nested groups causes delivery failure for Nested Groups.

16594

Migrating Personal Groups with internal Notes users creates delivery failures due to lack of "EX" value in 'Type' field.

16597

The data in the Location field of contacts is not migrated.  The data in Address fields are not mapped properly and will appear differently between Outlook and Outlook Web Access.

16633

Embedded graphics in Migrated Contacts are not visible in OWA.

16637

The Home Address is migrated into both the Home and Business Address of Contacts.

16647

The data in the Location field on the Business tab of a Lotus Notes contact does not migrate to the PR_Office_Location field in Outlook as expected.

16651

The entire Business Address is migrated to the City field in a Contact.

16658

If the member of a Personal Mail Group was copied from the Domino Directory (into the Personal Address Book), the members have invalid SMTP addresses with a Domain of "@unk domain" after migration.

16660

The Country Codes of Personal Addresses are not migrated in Contacts.

16662

Embedded files in contacts do not migrate.

16695

The IM Address in contacts does not migrate to Exchange.

16745

The contact's SMTP email address does not get migrated to Exchange when the 'InternetAddress' field is NULL, but there is a value in the 'MailAddress' field.

16750

When Contacts with a photo are migrated to Exchange, the contact photo is migrated to the "Notes" field as an attachment without an extension and not the contact field in the Exchange contact document.

16756

When migrated to Exchange, the friendly email address format is incorrect and results in an email delivery failure when used.

16764

Personal Contact non-primary email fields with a canonical format do not get translated to an SMTP address.

16781

The Blog Site field in a Notes contact does not migrate because there is no corresponding field in Outlook.

16782

If both the "pager" field and "Mobile 2" field are entered for a contact, the Mobile 2 number is lost.

16839

Table 12. Delegation Permissions known limitations

Known limitation

Issue ID

In hybrid Exchange installations (containing Exchange on-prem and Office 365), delegation access can only be set for users on the same system. Office 365 users can set delegation access to the mailbox to other Office 365 users, but not to Exchange users. Exchange users can set delegation access to other Exchange accounts, but not to Office 365 users. Access delegation is not supported between Exchange on-prem users and Office 365 accounts.

16841,46138

The number of accounts or groups that can be excluded from the Delegate audit is limited to 200 entries.

29154

Table 13. Encrypted Items known limitations

Known limitation

Issue ID

If a Lotus Notes encrypted message is migrated with the parameter "Require decryption action and migrate into the body", but the document is not decrypted prior to migration, the recipient is duplicated in the To field. This will only occur the first time the recipient name is encountered. All subsequent messages will be migrated as expected.

16762

The decrypt agent introduced in version 3.5.1 does not set the encrypt field to 0 or remove it, so an audit run after the agent has been run still show documents as encrypted when they are not.

16814

For messages that are encrypted at the time of the migration, the From address is not translated and uses the address from the MIME header to stamp the message. Messages are migrated without the body due to encryption and the message is not able to be replied to since the From address has not been translated.

25661

An apostrophe (') in encrypted content body text does not correctly migrate.

29153

Table 6. Group Migrations known limitations

Known limitation

Issue ID

Domino Directory Group Migrations should be done using Directory Sync Pro.

34459

Table 14. Installation known limitations

Known limitation

Issue ID

File versions are not properly displayed in the C:\program files\binary tree\cmt for exchange\cmtmonitor\bin location.

29005

The .MSI installer does not check the workstation environment meets the minimum requirements and does not install the missing components needed for a successful migration.

27624

Migration workstations cannot be uninstalled if the Migration Control Center cannot be contacted.

32941

Table 15. Logging known limitations

Known limitation

Issue ID

Migration summary of contacts does not count group documents.

34362

Table 16. Mail Migration known limitations

Known limitation

Issue ID

The subjects of migrated messages are not appended with "[BinaryTree Evaluation Copy]" when using an evaluation copy and the user is migrated more than one time.

16611

Font size properties within a migrated message are not maintained if the font size in Lotus Notes is not the default size.

16612

The color of text bullets is black regardless of the color of the text and bullets in the source document.

16624

Although the type of message to migrate is set to 'Mail Only' in the Migration Settings, Phone Messages still migrate and do not contain the correct formatting.

16628

The recipient of a message sent to one's self appears in the CC: field instead of the To: field of migrated messages.

16631

The text "Follow Up" is not present in the gray follow-up banner of the migrated messages when viewed in OWA. If there is no date associated with a follow up flag in Notes, the date and time the message was sent will appear in the gray follow-up banner of the message.

16634

The Follow Flag reminder time is 12 hours ahead after migration when viewed from Outlook. It is displayed properly in OWA.

16646

An embedded graphic in a migrated mail item is displayed incorrectly when opening the browser window minimized in OWA.

16657

When migrating phone messages, the 'spiral notebook' graphic that appears at the top of the phone message in Lotus Notes is migrated as an attachment.

16704

Legacy Archive migration currently only supports 5 archives per user.

16709

Follow Up dates associated with Follow Up flags do not migrate if the time field is not set in Lotus Notes. Furthermore, Follow Up dates and times only migrate if the Alarm is set in Lotus Notes.

16724

The "Sent" field in a previewed Draft in Outlook displays the Migration Date instead of "None".

16726

Migrated draft messages are not editable. Unable to resume editing or send a migrated draft message.

16743

Some bullet types do not maintain the same format in migrated message bodies. This can impact all document types such as email, calendar, task and to-do.

16754

The following error during migration causes mail messages to not appear in destination mailbox: ! Error: Failed to save changes in MimeToMapi 0x80040305

16765

The bodies of messages containing winmail.dat files are not migrated, because they cannot be processed with MIME.

16777

Multiple attachments of the same type in a single message, stored in the message as V4 attachment types, are not migrated across. An EML attachment is added to the email (file contains no content).

16786

Reservation Doclinks sent from the Rooms and Resources database migrate as database links.

16793

When an Office 365 validation check is performed and the folder destinations do not exist, an OLE: Automation object error occurs.

16815

Tasks migrated to Exchange 2016 mailboxes do not have the PR_CONVERSATION_INDEX_TRACKING property; however, this does not appear to impact the functionality of the task.

16824

A migrated message with a follow up flag does not include the Priority Status (FollowUpStatus) if the FollowUpText field is populated.

18388

There is an issue migrating Notes email that is stored in a MIME CSS format where the message body is missing post migration.

25942

Draft messages are not migrated if both the source and target are non-English.

28157

SMTP addresses do not support double byte character sets.

33652

The source file or progress bar does not display correctly if the migration is run from a staged replica of the Domino mail file and used the additional database tab to supply the source information.

33993

Submitting a migration job using the Schedule Migration option results in the worker not updating the controller to complete the job.

44627

Responses to conversation threads that occur after the first pass migration are not added to the conversation during subsequent migrations.

45601

The Remove Migrated data functionality incorrectly selects IPM.Schedule message class items for removal when the profile is intended to only select/remove Mail items.

55414

Journal entries are migrated with the date that they are created in Notes, this does not use the Diary Date or Time Created for the journal fields.

67532

Lotus Notes stored forms and the content within the stored form may not be rendered properly after migration.

16794

Table 17. Mail Migration\Attachments known limitations

Known limitation

Issue ID

There is a 240-character limitation imposed by Lotus Notes on the full file/path name of an attachment. If this is exceeded, an error will occur and the mail message will not be migrated.

16690

There is a limit of 100MB for attachments if the Large Attachment processing is not enabled. If this is enabled there is a limit of 125MB for a single attachment and 150MB for all attachments on a message

16696

Attachments in contacts are not displayed in OWA 2013, therefore migrated attachments in contacts are not displayed in OWA. They do function as expected when using an Outlook client.

16761

Table 18. Mail Migration\Delivery Options known limitations

Known limitation

Issue ID

Mail "Return Receipt:" loses all information after migrating to Exchange.

16684

If an unread message with a read receipt request is migrated to Outlook before being read, the read receipt is not sent to the sender when read in Outlook.

18275

Table 19. Mail Migration\Rich Text known limitations

Known limitation

Issue ID

Bulleted lists with checkmarks, circles and squares are not migrated correctly and appear as filled in circles in Outlook.

16694

Migrations that contain double byte character sets may experience Rich Text formatting issues in the message body. The message content is migrated, but may not retain the font colors, bold, or indentations.

34322

Table 20. Mail Migration\Views/Folders known limitations

Known limitation

Issue ID

Any folder name containing the word "Rules" (case sensitive) is not migrated to Exchange, however, the documents will be migrated to the Unfiled folder.

16644

The Migration profile choice to "skip folder" will not work if the folder has a leading or trailing space.

16779

When migrating to a PST running an Outlook client in a language other than English, Calendar, Contacts and the drafts folder migrate in English instead of the language being used.

16787

Accented characters in an unfiled folder name is not migrated properly.

42996

The Outlook system folder’s RSS Feeds and Search Folders (or language-specific folder’s names for these) are not migrated or updated during the migration processing.

66926

Table 21. Mail-In db Migration known limitations

Known limitation

Issue ID

The Verify Database process does not report on mail-in databases.

16710

Migration of Mail-in databases with a ":" in the name is not supported, and the Mail-in database should be renamed prior to migration to remove the ":".

16730

Domino Database names containing special characters, such as "&", cause a migration status of "Migration terminated abnormally" even though the migration was successful.

16759

Table 22. Match Users known limitations

Known limitation

Issue ID

The 'Matches the selected users on the Exchange CAS server' setting does not function properly. You must use LDAP to match users prior to migrations.

16602

The Password field does not allow a space in the password when logging into the CAS Server administration ID in the Settings and Additional tab.

16604

Users that have SMTP addresses starting with 'con.', for example 'con.test@mydomain.com' cause PowerShell matching to fail.

16796

If re-matching user accounts after an account has been deleted in Office 365, the original matching information is incorrectly used.

28502

In Archive Migrator for Notes, if the archive documents generated need to be matched/re-matched, the Last Name field value will be updated for the first archive file. Documents for the second and forward will not be changed.

38119

Table 23. Migration Workstation known limitations

Known limitation

Issue ID

The migration of a user with an ampersand (&) within the first name or last name will not send logs to the Migration Control Center.

17621

Migrations workstations with a double byte character set language pack installed crashes when starting migrations.

26681

Table 24. MTCW known limitations

Known limitation

Issue ID

When updating either a single occurrence meeting or any part of a repeating meeting, if the chair changes the time zone of the update, it may not be applied to the existing meeting, but may instead create a new entry on the calendar.

34256

Table 25. Name Translation known limitations

Known limitation

Issue ID

Contact group (Distribution List) will translate to LegacyExchangeDN if matching SMTP address exists in source 'Full Name' field. Outlook Distribution Lists cannot contain LegacyExchangeDN. This will cause email delivery failures.

16784

Table 26. Notes Migrator.nsf known limitations

Known limitation

Issue ID

When clicking the 'Migrate Users' action, in an empty Migrate view, the 'Select Migration Priority' dialog is launched instead of receiving the following error: "To run this agent you must have at least 1 document selected".

16616

The "Run Replica Comparison" agent does not function when a custom replication formula is used.

16819

Chinese character archives cannot be opened from the open link in the CMT Person Document.

33433

If an invalid password is entered in the Autodiscover Password setting, the Autodiscover process will prompt for a password when the migration begins. You must enter a valid password, check the box to remember these credentials and click OK for the migration to proceed. If you do not check the box to remember these credentials, the migration will end and not complete.

38838

Table 27. Notes Migrator.nsf\Configuration Settings known limitations

Known limitation

Issue ID

When configuring migration of user for future time, you see "migration status is set to error for user XX: migratecmtuser failed in the status bar at the button of the Lotus Notes client; however, the user will migrate.

16600

Changing a migration to a “Migrate Now (high priority)” does not queue the user on the next available migration workstation; only use the default selection: "Add to migration queue (normal priority)”.

16691

The "Past and Present Domino Domains" setting is limited to 255 characters.

18385

Separators, other than commas, in the list of Past and Present Domino Domains entered in the Email Repliability settings are not converted to commas.

39586

LDAP validation and processing will not complete if an AD Domain Controller GPO is set with “Domain controller: LDAP server signing requirements” set to “Require Signing”.

40768

Calendar items created from migrated data will not be removed by the Remove Migrated Data function.

48487

Table 28. Notes Migrator.nsf\Message Templates known limitations

Known limitation

Issue ID

The error message, "You do not have the permission to send the message on behalf of the specified user" appears when attempting to send a migrated draft message.

16636

When "receiving unencrypted mail, encrypt before storing in your mailfile:" is selected in the Person document (in the Domino Directory), the decrypt button will not decrypt these encrypted messages.

16740

Migration Message Templates that contain Notes buttons are not available if an end user views the email in iNotes (web mail). This limitation applies to all button email templates in Notes Migrator. The email buttons can only be processed in the full Notes client.

54536

Table 29. Notes Migrator.nsf\Migration Profiles known limitations

Known limitation

Issue ID

Attempting to Set Migration Profile when there are no documents selected, does not produce an error.

16642

Advanced settings in a Migration Profile disappear after Profile Refresh, if the profile is deleted from the UI, and not the back-end. The Advance Settings are still stored in the back-end but are not displayed in the UI. To work around this issue, enter the missing values and resave the document.

16785

When modifying a Migration Profile’s Migration Options, from the initially selected "Message of type" option with the 'Mail', 'Task', 'Calendar' or 'Contacts' checkboxes selected, to the "All message types" option, without unchecking the selected checkboxes, the migration will migrate the items which were initially selected, not all message types. The checkboxes must be unchecked prior to changing to the 'All message types' option.

45859

Table 30. Notes Migrator.nsf\Post-Migration Actions known limitations

Known limitation

Issue ID

The "Set Reader Access for Users mailfile" does not properly report the success and failed to process correctly.

16599

The "Set Reader Access" post migration action incorrectly reports no success when agent completes.

16811

Migrated data does not get removed when using a date range. 

29156

The Set Full Access button agent reports a PowerShell error when the Full Access delegation permissions are run on accounts that have been mail box enabled in Office 365 if there are two or more accounts that have the same Display Name attribute.

Error: The operation couldn't be performed because 'Account Name' matches multiple entries.

40699

Table 31. Notes Migrator.nsf\Pre-Migration Actions known limitations

Known limitation

Issue ID

A Mail Rules message doesn't show the Message Log under the Notes Migrator user document which prevents the migration administrator from verifying the rules message was sent to the selected user(s).

16640

When using the combined notification template for end users in the Notes Migrator database, there is no way to prevent execution alerts from being displayed to the end users.

16666

Unable to provision a user if any of the shortnames in the Notes Migrator person document are in firstname.lastname format, regardless of whether the value is single or multiple.

16746

CAS Server matching returns an erroneous message when it can't find a match for a user due to non-matching SMTP addresses between the source and destination objects.

16763

Verify Mail DB (Audit Mail file) does not support clustered mail servers.

16772

The Name Translation Table CSVDE matching option does not support the matching of the German o ( ö ) character and Greek Alphabet characters (Έλληνες χρήστη1). To work around this issue, use one of the other match options.

16788

Mail-in DB's or Rooms & Resources cannot be provisioned to Office 365. This must be manually performed.

16802

Set Full Admin access fails when the users name contains a "$" character.

16805

Private folders are not included in the Pre-Migration Mail File Audit.

22747

Table 32. Notes Migrator.nsf\Progress Summary known limitations

Known limitation

Issue ID

Scheduled migrations produced error in Notes status bar.

16667

Table 33. Rooms and Resources known limitations

Known limitation

Issue ID

The database template specified in the Rooms & Resource settings must be present on the Target server specified in the same settings document, or an error will display that the database template cannot be found.

16508

Room and Resources don't display on a migrated calendar entry on the scheduling tab.

16606

Leading and trailing spaces are trimmed in values of Room Label, Resource Label, Online Label, Location Detail Indicator, and Room Resource Separator Settings Fields.

16661

Recurring meetings in the Domino rooms and resources application are stored as individual documents for each instance and are migrated as such. These require direct management in Outlook for changes post migration. Additionally, modifications to recurring meetings in rooms and resources will not migrate instance changes correctly. 

16715

Room and Resources Migration will not load the worker on the controller if no other workers are registered.  You will encounter the error: "C:\program files\binarytree\cmt for exchange\cmt_migrationworker.exe could not be started.  Please confirm that CMT is Installed correctly and the settings doc reflects the correct install path."

28448

Room import fails when the room has quotes in the name.

38359

 

 

Table 34. To-Do Migration known limitations

Known limitation

Issue ID

Completing a migrated Task will send a notification to the SendTo user when the Task is created using the "Copy into new..." button in Lotus Notes. No notification should be sent.

16598

Text bullets appear as asterisks ("*") post migration when viewed from Outlook Web Access (only).

16613

Embedded graphics in Lotus Notes Tasks are migrated as attachments.

16619

Lotus Notes Tasks created by a delegate appear in Outlook with the delegate as the Owner, instead of 'Delegate (Sent on behalf of mail file owner)'.

16621

Migrated Tasks containing Notes links have an extraneous .gif attachment for each link.

16622

Read/Unread status is not maintained on migrated Tasks when using Outlook Web Access.

16623

Unaccepted To Do notices in Lotus Notes do not migrate to Exchange.

16632

Repeating tasks (to-do's) do not migrate to the correct dates.

16693

Assigned Tasks (To-Do's) are migrated as Task calendar events, not as Task Requests. The migrated Task will only be displayed in the To-Do's not in the Inbox.

16697

Yearly and Custom recurring Tasks become Weekly Tasks after migration.

16702

When migrated assigned tasks are completed the person who created the task and assigned it to someone else does not get the notification that it was completed. 

16706

The Task Owner name displays the ExchangeLegacyDN rather than the Display Name. This is a cosmetic issue only and there is no loss in functionality.

46929

Task assignees (Required, Optional, FYI) are not migrated to Outlook.

46986

System requirements

Refer to the Binary Tree Migrator for Notes 20.12 Requirements (http://support.quest.com/technical-documents/binary-tree-migrator-for-notes/20.12/requirements) for system requirements.

Product licensing

A valid license is required for Binary Tree Migrator for Notes.

To obtain licenses, see information on this page https://www.quest.com/company/contact-us.aspx or contact the sales team at sales@quest.com

Upgrade and installation instructions

Refer to the Binary Tree Migrator for Notes 20.12 Installation and Configuration Guide (http://support.quest.com/technical-documents/binary-tree-migrator-for-notes/20.12/installation-and-configuration-guide) for installation instructions.

More resources

Additional information is available from the following:

Globalization

This section contains information about installing and operating this product in non-English configurations, such as those needed by customers outside of North America. This section does not replace the materials about supported platforms and configurations found elsewhere in the product documentation.

 

This release is Unicode-enabled and supports any character set. In this release, all product components should be configured to use the same or compatible character encodings and should be installed to use the same locale and regional options. This release is targeted to support operations in the following regions: North America, Western Europe and Latin America, Central and Eastern Europe, Far-East Asia, Japan. It supports bidirectional writing (Arabic and Hebrew). The release supports Complex Script (Central Asia – India, Thailand).

About us

Quest creates software solutions that make the benefits of new technology real in an increasingly complex IT landscape. From database and systems management, to Active Directory and Office 365 management, and cyber security resilience, Quest helps customers solve their next IT challenge now. Around the globe, more than 130,000 companies and 95% of the Fortune 500 count on Quest to deliver proactive management and monitoring for the next enterprise initiative, find the next solution for complex Microsoft challenges and stay ahead of the next threat. Quest Software. Where next meets now. For more information, visit www.quest.com.

Technical support resources

Technical support is available to Quest customers with a valid maintenance contract and customers who have trial versions. You can access the Quest Support Portal at https://support.quest.com.

The Support Portal provides self-help tools you can use to solve problems quickly and independently, 24 hours a day, 365 days a year. The Support Portal enables you to:

  • Submit and manage a Service Request

  • View Knowledge Base articles

  • Sign up for product notifications

  • Download software and technical documentation

  • View how-to-videos

  • Engage in community discussions

  • Chat with support engineers online

  • View services to assist you with your product.

© 2021 Quest Software Inc.
ALL RIGHTS RESERVED.

This guide contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchaser’s personal use without the written permission of Quest Software Inc.

The information in this document is provided in connection with Quest Software products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest Software products. EXCEPT AS SET FORTH IN THE TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST SOFTWARE ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST SOFTWARE BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST SOFTWARE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest Software makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. Quest Software does not make any commitment to update the information contained in this document.

If you have any questions regarding your potential use of this material, contact:

Quest Software Inc.

Attn: LEGAL Dept

4 Polaris Way

Aliso Viejo, CA 92656

Refer to our Web site (https://www.quest.com) for regional and international office information.

Patents

Quest Software is proud of our advanced technology.  Patents and pending patents may apply to this product. For the most current information about applicable patents for this product, please visit our website at https://www.quest.com/legal.

Trademarks

Quest, the Quest logo, and Join the Innovation are trademarks and registered trademarks of Quest Software Inc. For a complete list of Quest marks, visit https://www.quest.com/legal/trademark-information.aspx.  All other trademarks and registered trademarks are property of their respective owners.

Legend

CAUTION: A CAUTION icon indicates potential damage to hardware or loss of data if instructions are not followed.

 

IMPORTANT, NOTE, TIP, MOBILE, or VIDEO: An information icon indicates supporting information.

About this release

Binary Tree® Migrator for Notes 20.12

Release Notes

May 2021

These release notes provide information about the Binary Tree Migrator for Notes 20.12 release.

Topics:

 

Migrator for Notes is the most comprehensive software available for migrating from HCL Domino to Microsoft Exchange.

Migrator for Notes not only supports migrations to on-premises Microsoft Outlook and Exchange, but also to online versions of Microsoft Outlook and Hosted Exchange, including Office 365.

Migrator for Notes, part of Binary Tree’s suite of migration solutions that includes Directory Sync Pro and Notes Integration, offers unmatched data fidelity, migration management, and migration throughput.

Migrator for Notes 20.12 is a minor release, with new features and functionality. See New features and Enhancements.

New features

New features in Migrator for Notes:

  • The Migrate Unfiled Documents option has been added to the Migration Profile Options. This option determines if “unfiled” documents will be migrated. (54015)

  • To resolve formatting issues with the Sametime Chat history, the "Process Sametime history as" setting has been added to allow you to select the format as Rich Text or MIME. (75337)

  • The “Override existing license" option has been added to the Office 365 Settings page. This setting allows for overriding an existing license on accounts being processed, replacing the license with the new selection. (75965)

  • The "Copy Manager on Notification" setting has been added to the Message Template settings. Select this setting to send a copy of the message to the user’s manager. This setting is available only when Other Settings - Advanced features is enabled and the account being sent the notification has the Manager field competed in the Domino Directory. (76044)

  • New settings to Skip reprocessing users that have previously failed and to Reprocess successful matches have been added to the Email Repliability Matching settings. (76059)

  • Exchange Environment, Remote Azure AD Endpoint, and Azure AD Environment settings have been added to the User Provisioning Settings to handle connections for regional data centers. (76174)

See also:

Enhancements

The following is a list of enhancements implemented in Migrator for Notes.

Table 1. General enhancements

Enhancement

Issue ID

The two migration job log files have been combined into a single log file.

47509

For migrations that have repeated network errors, the migration of accounts is now automatically re-tried using the auto retry processing.

64665

Migration will now be terminated if the Name Translation process cannot connect to the source database.

65900

Updated email repliability to validate against canonical Notes name for accounts where there are multiple entries with the same common name.

75031

Migrations failures due to network errors have been added to re-queue processing.

75323

Unfiled processing has been updated to skip opening documents that are already in the migration history to allow for faster Unfiled checks.

75336

Passwords passed from the engine to the Outlook Agent are now hashed.

75385

The Outlook Agent has been updated to use the registry-stored account and password if not provided when called from engine.

75386

The User Provisioning Settings have been updated to hide settings that are not applicable to Office 365 migrations.

75952

Support for double-byte character set (DBCS) has been added for the following fields:

Rooms & Resources:

  • Room Label

  • Resource Label

  • Online Label

  • Location Detail Indicator

Migration profile:

  • Unfiled folder name

Other Settings:

  • Encrypted Items Migration (text)

75966

Updated Settings to include a configurable list of Notes system folders for use with the Fix Folders agent.

75967

Settings that are not applicable to Office 365 migration are hidden on the User Provisioning Settings screen.

76060

Support for double-byte character set (DBCS) for encrypted body message has been added.

76148

Resolved issues

The following is a list of issues addressed in this release.

Table 2. General resolved issues

Resolved Issue

Issue ID

An issue where migrated external meeting requests had the reply address set incorrectly has been resolved.

41515

An issue where migrations are incorrectly marked as successful when the Domino server runs out of space and cannot open source folders has been resolved.

52658

An issue where messages with the follow up flags set to high priority/low priority are migrated without the follow up flags has been resolved.

54900

An issue where the reply to and forwarded icons indicating that a message has been replied to or forwarded did not migrate has been resolved.

54901

An issue where address field values with leading spaces caused Name Translation Table lookups to fail has been resolved.

69928

An issue where the reply address was set incorrectly for migrated "on behalf of" messages has been resolved.

74131

Corrected a condition where a document causing a Notes out of memory error was not being skipped during the fault recovery migration.

76085

An issue where Modern Auth failed if LegacyExchangeDN was not found and terminated abnormally has been resolved.

76161

An issue where Modern Auth abnormally terminated if GetTopOfInformationStore fails has been resolved.

76162

An issue where initialization failed on Notes version 10.0 has been resolved.

76243

Corrected an issue where when using Modern Authentication, and targeting an Archive mailbox, Migrator for Notes failed to connect to the target archive mailbox.  Basic Authentication must remain enabled for Autodiscover, but Modern Authentication can be used for mailbox access.

76265

Known limitations

Most of the known limitations and issues of any migration process are due to feature inconsistencies between the source and target environments. Features that are available in the Notes environment cannot be migrated to a target environment that does not offer the same or comparable features. Other limitations are due to feature incompatibilities where similar features are available in both the source and target environments, but their implementations are so different that migration is impractical.

While every effort is made to determine the specific limitations of a migration process, so that these are available for planning, communications and support, it is possible that there may be unknown limitations. These can occur in particular with changes to source or target system versions and in the case of email migrations for any data generated by third party system changes. Where previously unknown limitations in the data migration are found these would be reviewed to determine if the item can be resolved and migrated but it should be noted that these may result in a new known limitation.

The following is a list of known limitations or issues, including those attributed to third-party products, known to exist at the time of this release.

Table 4. AWD\Configuration known limitations

Known limitation

Issue ID

The Store Password feature does not validate the password and will allow you to store an incorrect password without prompting for a valid password when "Get Server List" is clicked.

16596

Table 5. AWD\Migration Workstation known limitations

Known limitation

Issue ID

If more than one instance of Lotus Notes or Notes Migrator is installed on a migration workstation, you will be prompted for the Notes password for each migration.

16688

Table 6. Calendar Migration known limitations

Known limitation

Issue ID

"Description:" appears in the body of migrated calendar documents when viewed in Outlook Web Access.

16629

Attachments in migrated calendar entries may not appear in the same position as in Notes when viewed from Outlook.

16635

If an invitee of a migrated meeting is changed from Optional to Required, the invitee's name appears in both Optional and Required fields in OWA. This is not a problem in Outlook.

16650

Calendar entries with a repeat pattern of Every Other Year are not natively supported in Exchange and are migrated as Yearly entries.

16654

When the migration setting to add Room, Resource and Online Meeting Place information to the body of Calendar entries is selected, and there is no Room, Resource or Online Meeting Place in the calendar entry, "See Details Below" is still added to the Location field.

16655

Subjects of Repeat Calendar entries that have carriage returns will not be displayed properly in Outlook and OWA 2007.

16659

Rooms and Resources added or removed to a Notes repeat meeting after the meeting was created will appear properly on each occurrence of the migrated meeting, but not the meetings series.

16663

User values in the BCC field of a migrated calendar item will appear in the Resource field. This is because Exchange uses the BCC field for resources, so any names in the BCC field will be treated as a resource. If the location field is empty, Outlook will display the resources in the location field also (it assumes resources will be a room or online meeting place).

16669

If "Automatically adjust clock for daylight saving changes" on the "Date and Time Properties" dialog box is not checked, and/or the latest Microsoft DST patches have not been installed, multi-day calendar events that start in one Daylight Savings Time period and end it another will appear off by 1 hour during the Daylight Savings Time period in which they were not created.

16685

Migrated recurring calendar events, where invitees have been added or removed from single instances will not list the correct attendees on the Chair Person's calendar.  However, the invitees’ calendars are correct.

16713

A migration crash can occur with an excessive amount of data (over 50 entries) in the Location and Rooms fields.

16717

Enterprise Vault links in Domino calendar items are missing after migration.

16758

Migrated meeting invitations that are unread in Notes are not displayed in the OWA calendar until after they are viewed post migration. (21865)

21865

Calendar items that do not have a start or end date causes a migration failure.

44404

Notes calendar entries' High Importance property does not get migrated to O365. Migrated calendar entries will be migrated as Normal importance.

57585

Attachments in migrated calendar entries may not appear in the same position as in Notes when viewed from Outlook.

16635

Table 7. Calendar Migration\Anniversary known limitations

Known limitation

Issue ID

The Play Sound reminder option in Lotus Notes Calendar items does not migrate to Outlook.

16618

Lotus Notes Anniversaries with the 'Pencil In' option selected are migrated to Outlook with a Show As: Free, instead of Tentative.

16625

Reminder sound notification is not maintained on a non-repeating Anniversary after migration.

16653

A recurring anniversary series that has been modified will appear on the correct day(s), but the dates displayed in each occurrence reflect the original date.

16687

Location and Category fields are not migrated in Anniversaries.

16712

Birthday and Anniversary data for local contacts are not added to the Outlook Calendar.

45182

Table 8. Calendar Migration\Delegation known limitations

Known limitation

Issue ID

If an invitee delegates one or more instances of a repeating meeting to someone else and the chairperson then updates the meeting, the entire series will appear on the original invitee’s calendar post migration.

16798

Table 9. Calendar Migration\Meetings known limitations

Known limitation

Issue ID

Embedded images in calendar entries appear as attachments in migrated calendar documents.

16614

The chairperson of an unaccepted meeting appears in the Required field after migration.

16627

Responses from attendees added after the original invite is issued do not update the chair's calendar tracking status.

16675

With the setting "Process meetings with no end date using ICAL information" set to yes, meetings with no end date sent from Outlook to Notes do not migrate properly if updates/reschedules have been accepted in Lotus Notes.

16676

Changes to migrated meetings with Rooms and/or Resources are not updated in the Domino Resource Reservations database. Updates are not properly made in the Notes Rooms and Resources database if a one-time meeting or reoccurring meeting is cancelled in Outlook. Additionally, updates are not properly made in the Notes Rooms and Resources database or migrated Room and Resource mailbox if individual occurrences are cancelled or rescheduled in Outlook.

16698

If an occurrence of a migrated repeating meeting is changed by the migrated chair in Exchange, it does not appear correctly on the calendar of Invitees that were added after the original meeting was created.

16699

Required attendees and resource do not show up in a printer output of the meeting with a migrated meeting. Native meetings created in Outlook show this information in the printed output.

16741

Meetings and Appointments in Notes that have the choice "Mark Available" checked are listed as "Tentative”, instead of "Free”, when migrated to Exchange.

16757

A meeting identified as a repeating meeting, but contains no repeat pattern, will not migrate the remaining events if one of the events has been cancelled.  The meeting will be listed in the log as being skipped because it was cancelled, when in truth, only one of the occurrences was canceled.

16766

Unknown time zones display the incorrect time even though the meeting is on the calendar at the proper date and time.

16778

The Response Status is not cleared when a critical change (date/time/location) is made by the chair after the invitee has accepted the original meeting. When the chair invites, the invitee accepts, the chair changes the date, and then migration occurs, the migrated calendar event will contain the invitee response to the original invite, even though it is not invalid/obsolete due to the date change. The date change notice will migrate correctly, and later responses will correctly update the chair tracking. In the time between migration and the invitee responding to the change, the chair tracking will continue to show the invitee as accepted even though the change has been issued.

16791

If the entire series of a repeat meeting was rescheduled prior to migration, changes post migration will generate an NDR.

16813

If the chair of a meeting cancels an instance of a recurring meeting prior to migration by using the 'Delete' key, Domino deletes the child document from the database. Since the child document is missing, Notes Migrator will use the original pattern during migration, and the canceled meeting will appear on the calendar in Outlook.  To avoid this, the canceled meeting(s) instances should not be deleted from the source database.

16823

Executable (.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC) and consumable (.PST) attachments to calendar items are delayed when migrating. Items appear approximately 30 to 45 minutes after migration completes.

41359

When an all day, repeating event is rescheduled in Notes before migration, the reschedule dates are not applied in Outlook. The original all-day event dates are used except for the first booking in the series.

41856

Due to Exchange’s inability to process a large number of exceptions, during a migration, Notes Migrator will not create more than 200 exceptions for an event. Any exception beyond the first 200 will not be applied, and this may show as updates/reschedules/additions/cancels/etc. not appearing on the later occurrences.

37682

Table 10. Calendar Migration\Reminders known limitations

Known limitation

Issue ID

Tasks/ToDos, Notices (invites and updates) that have reminders and Messages that have a follow-up/reminder set will cause many past due pop-up reminders in outlook after they are migrated. Clicking the "dismiss all" button will resolve the issue.

16705

Because there is no equivalent in Outlook, Reminders migrate as appointments with the free time blocked out.

16771

Table 11. Contact Migration known limitations

Known limitation

Issue ID

Migration of personal NAB nested groups causes delivery failure for Nested Groups.

16594

Migrating Personal Groups with internal Notes users creates delivery failures due to lack of "EX" value in 'Type' field.

16597

The data in the Location field of contacts is not migrated.  The data in Address fields are not mapped properly and will appear differently between Outlook and Outlook Web Access.

16633

Embedded graphics in Migrated Contacts are not visible in OWA.

16637

The Home Address is migrated into both the Home and Business Address of Contacts.

16647

The data in the Location field on the Business tab of a Lotus Notes contact does not migrate to the PR_Office_Location field in Outlook as expected.

16651

The entire Business Address is migrated to the City field in a Contact.

16658

If the member of a Personal Mail Group was copied from the Domino Directory (into the Personal Address Book), the members have invalid SMTP addresses with a Domain of "@unk domain" after migration.

16660

The Country Codes of Personal Addresses are not migrated in Contacts.

16662

Embedded files in contacts do not migrate.

16695

The IM Address in contacts does not migrate to Exchange.

16745

The contact's SMTP email address does not get migrated to Exchange when the 'InternetAddress' field is NULL, but there is a value in the 'MailAddress' field.

16750

When Contacts with a photo are migrated to Exchange, the contact photo is migrated to the "Notes" field as an attachment without an extension and not the contact field in the Exchange contact document.

16756

When migrated to Exchange, the friendly email address format is incorrect and results in an email delivery failure when used.

16764

Personal Contact non-primary email fields with a canonical format do not get translated to an SMTP address.

16781

The Blog Site field in a Notes contact does not migrate because there is no corresponding field in Outlook.

16782

If both the "pager" field and "Mobile 2" field are entered for a contact, the Mobile 2 number is lost.

16839

Table 12. Delegation Permissions known limitations

Known limitation

Issue ID

In hybrid Exchange installations (containing Exchange on-prem and Office 365), delegation access can only be set for users on the same system. Office 365 users can set delegation access to the mailbox to other Office 365 users, but not to Exchange users. Exchange users can set delegation access to other Exchange accounts, but not to Office 365 users. Access delegation is not supported between Exchange on-prem users and Office 365 accounts.

16841,46138

The number of accounts or groups that can be excluded from the Delegate audit is limited to 200 entries.

29154

Table 13. Encrypted Items known limitations

Known limitation

Issue ID

If a Lotus Notes encrypted message is migrated with the parameter "Require decryption action and migrate into the body", but the document is not decrypted prior to migration, the recipient is duplicated in the To field. This will only occur the first time the recipient name is encountered. All subsequent messages will be migrated as expected.

16762

The decrypt agent introduced in version 3.5.1 does not set the encrypt field to 0 or remove it, so an audit run after the agent has been run still show documents as encrypted when they are not.

16814

For messages that are encrypted at the time of the migration, the From address is not translated and uses the address from the MIME header to stamp the message. Messages are migrated without the body due to encryption and the message is not able to be replied to since the From address has not been translated.

25661

An apostrophe (') in encrypted content body text does not correctly migrate.

29153

Table 6. Group Migrations known limitations

Known limitation

Issue ID

Domino Directory Group Migrations should be done using Directory Sync Pro.

34459

Table 14. Installation known limitations

Known limitation

Issue ID

File versions are not properly displayed in the C:\program files\binary tree\cmt for exchange\cmtmonitor\bin location.

29005

The .MSI installer does not check the workstation environment meets the minimum requirements and does not install the missing components needed for a successful migration.

27624

Migration workstations cannot be uninstalled if the Migration Control Center cannot be contacted.

32941

Table 15. Logging known limitations

Known limitation

Issue ID

Migration summary of contacts does not count group documents.

34362

Table 16. Mail Migration known limitations

Known limitation

Issue ID

The subjects of migrated messages are not appended with "[BinaryTree Evaluation Copy]" when using an evaluation copy and the user is migrated more than one time.

16611

Font size properties within a migrated message are not maintained if the font size in Lotus Notes is not the default size.

16612

The color of text bullets is black regardless of the color of the text and bullets in the source document.

16624

Although the type of message to migrate is set to 'Mail Only' in the Migration Settings, Phone Messages still migrate and do not contain the correct formatting.

16628

The recipient of a message sent to one's self appears in the CC: field instead of the To: field of migrated messages.

16631

The text "Follow Up" is not present in the gray follow-up banner of the migrated messages when viewed in OWA. If there is no date associated with a follow up flag in Notes, the date and time the message was sent will appear in the gray follow-up banner of the message.

16634

The Follow Flag reminder time is 12 hours ahead after migration when viewed from Outlook. It is displayed properly in OWA.

16646

An embedded graphic in a migrated mail item is displayed incorrectly when opening the browser window minimized in OWA.

16657

When migrating phone messages, the 'spiral notebook' graphic that appears at the top of the phone message in Lotus Notes is migrated as an attachment.

16704

Legacy Archive migration currently only supports 5 archives per user.

16709

Follow Up dates associated with Follow Up flags do not migrate if the time field is not set in Lotus Notes. Furthermore, Follow Up dates and times only migrate if the Alarm is set in Lotus Notes.

16724

The "Sent" field in a previewed Draft in Outlook displays the Migration Date instead of "None".

16726

Migrated draft messages are not editable. Unable to resume editing or send a migrated draft message.

16743

Some bullet types do not maintain the same format in migrated message bodies. This can impact all document types such as email, calendar, task and to-do.

16754

The following error during migration causes mail messages to not appear in destination mailbox: ! Error: Failed to save changes in MimeToMapi 0x80040305

16765

The bodies of messages containing winmail.dat files are not migrated, because they cannot be processed with MIME.

16777

Multiple attachments of the same type in a single message, stored in the message as V4 attachment types, are not migrated across. An EML attachment is added to the email (file contains no content).

16786

Reservation Doclinks sent from the Rooms and Resources database migrate as database links.

16793

When an Office 365 validation check is performed and the folder destinations do not exist, an OLE: Automation object error occurs.

16815

Tasks migrated to Exchange 2016 mailboxes do not have the PR_CONVERSATION_INDEX_TRACKING property; however, this does not appear to impact the functionality of the task.

16824

A migrated message with a follow up flag does not include the Priority Status (FollowUpStatus) if the FollowUpText field is populated.

18388

There is an issue migrating Notes email that is stored in a MIME CSS format where the message body is missing post migration.

25942

Draft messages are not migrated if both the source and target are non-English.

28157

SMTP addresses do not support double byte character sets.

33652

The source file or progress bar does not display correctly if the migration is run from a staged replica of the Domino mail file and used the additional database tab to supply the source information.

33993

Submitting a migration job using the Schedule Migration option results in the worker not updating the controller to complete the job.

44627

Responses to conversation threads that occur after the first pass migration are not added to the conversation during subsequent migrations.

45601

The Remove Migrated data functionality incorrectly selects IPM.Schedule message class items for removal when the profile is intended to only select/remove Mail items.

55414

Journal entries are migrated with the date that they are created in Notes, this does not use the Diary Date or Time Created for the journal fields.

67532

Lotus Notes stored forms and the content within the stored form may not be rendered properly after migration.

16794

Table 17. Mail Migration\Attachments known limitations

Known limitation

Issue ID

There is a 240-character limitation imposed by Lotus Notes on the full file/path name of an attachment. If this is exceeded, an error will occur and the mail message will not be migrated.

16690

There is a limit of 100MB for attachments if the Large Attachment processing is not enabled. If this is enabled there is a limit of 125MB for a single attachment and 150MB for all attachments on a message

16696

Attachments in contacts are not displayed in OWA 2013, therefore migrated attachments in contacts are not displayed in OWA. They do function as expected when using an Outlook client.

16761

Table 18. Mail Migration\Delivery Options known limitations

Known limitation

Issue ID

Mail "Return Receipt:" loses all information after migrating to Exchange.

16684

If an unread message with a read receipt request is migrated to Outlook before being read, the read receipt is not sent to the sender when read in Outlook.

18275

Table 19. Mail Migration\Rich Text known limitations

Known limitation

Issue ID

Bulleted lists with checkmarks, circles and squares are not migrated correctly and appear as filled in circles in Outlook.

16694

Migrations that contain double byte character sets may experience Rich Text formatting issues in the message body. The message content is migrated, but may not retain the font colors, bold, or indentations.

34322

Table 20. Mail Migration\Views/Folders known limitations

Known limitation

Issue ID

Any folder name containing the word "Rules" (case sensitive) is not migrated to Exchange, however, the documents will be migrated to the Unfiled folder.

16644

The Migration profile choice to "skip folder" will not work if the folder has a leading or trailing space.

16779

When migrating to a PST running an Outlook client in a language other than English, Calendar, Contacts and the drafts folder migrate in English instead of the language being used.

16787

Accented characters in an unfiled folder name is not migrated properly.

42996

The Outlook system folder’s RSS Feeds and Search Folders (or language-specific folder’s names for these) are not migrated or updated during the migration processing.

66926

Table 21. Mail-In db Migration known limitations

Known limitation

Issue ID

The Verify Database process does not report on mail-in databases.

16710

Migration of Mail-in databases with a ":" in the name is not supported, and the Mail-in database should be renamed prior to migration to remove the ":".

16730

Domino Database names containing special characters, such as "&", cause a migration status of "Migration terminated abnormally" even though the migration was successful.

16759

Table 22. Match Users known limitations

Known limitation

Issue ID

The 'Matches the selected users on the Exchange CAS server' setting does not function properly. You must use LDAP to match users prior to migrations.

16602

The Password field does not allow a space in the password when logging into the CAS Server administration ID in the Settings and Additional tab.

16604

Users that have SMTP addresses starting with 'con.', for example 'con.test@mydomain.com' cause PowerShell matching to fail.

16796

If re-matching user accounts after an account has been deleted in Office 365, the original matching information is incorrectly used.

28502

In Archive Migrator for Notes, if the archive documents generated need to be matched/re-matched, the Last Name field value will be updated for the first archive file. Documents for the second and forward will not be changed.

38119

Table 23. Migration Workstation known limitations

Known limitation

Issue ID

The migration of a user with an ampersand (&) within the first name or last name will not send logs to the Migration Control Center.

17621

Migrations workstations with a double byte character set language pack installed crashes when starting migrations.

26681

Table 24. MTCW known limitations

Known limitation

Issue ID

When updating either a single occurrence meeting or any part of a repeating meeting, if the chair changes the time zone of the update, it may not be applied to the existing meeting, but may instead create a new entry on the calendar.

34256

Table 25. Name Translation known limitations

Known limitation

Issue ID

Contact group (Distribution List) will translate to LegacyExchangeDN if matching SMTP address exists in source 'Full Name' field. Outlook Distribution Lists cannot contain LegacyExchangeDN. This will cause email delivery failures.

16784

Table 26. Notes Migrator.nsf known limitations

Known limitation

Issue ID

When clicking the 'Migrate Users' action, in an empty Migrate view, the 'Select Migration Priority' dialog is launched instead of receiving the following error: "To run this agent you must have at least 1 document selected".

16616

The "Run Replica Comparison" agent does not function when a custom replication formula is used.

16819

Chinese character archives cannot be opened from the open link in the CMT Person Document.

33433

If an invalid password is entered in the Autodiscover Password setting, the Autodiscover process will prompt for a password when the migration begins. You must enter a valid password, check the box to remember these credentials and click OK for the migration to proceed. If you do not check the box to remember these credentials, the migration will end and not complete.

38838

Table 27. Notes Migrator.nsf\Configuration Settings known limitations

Known limitation

Issue ID

When configuring migration of user for future time, you see "migration status is set to error for user XX: migratecmtuser failed in the status bar at the button of the Lotus Notes client; however, the user will migrate.

16600

Changing a migration to a “Migrate Now (high priority)” does not queue the user on the next available migration workstation; only use the default selection: "Add to migration queue (normal priority)”.

16691

The "Past and Present Domino Domains" setting is limited to 255 characters.

18385

Separators, other than commas, in the list of Past and Present Domino Domains entered in the Email Repliability settings are not converted to commas.

39586

LDAP validation and processing will not complete if an AD Domain Controller GPO is set with “Domain controller: LDAP server signing requirements” set to “Require Signing”.

40768

Calendar items created from migrated data will not be removed by the Remove Migrated Data function.

48487

Table 28. Notes Migrator.nsf\Message Templates known limitations

Known limitation

Issue ID

The error message, "You do not have the permission to send the message on behalf of the specified user" appears when attempting to send a migrated draft message.

16636

When "receiving unencrypted mail, encrypt before storing in your mailfile:" is selected in the Person document (in the Domino Directory), the decrypt button will not decrypt these encrypted messages.

16740

Migration Message Templates that contain Notes buttons are not available if an end user views the email in iNotes (web mail). This limitation applies to all button email templates in Notes Migrator. The email buttons can only be processed in the full Notes client.

54536

Table 29. Notes Migrator.nsf\Migration Profiles known limitations

Known limitation

Issue ID

Attempting to Set Migration Profile when there are no documents selected, does not produce an error.

16642

Advanced settings in a Migration Profile disappear after Profile Refresh, if the profile is deleted from the UI, and not the back-end. The Advance Settings are still stored in the back-end but are not displayed in the UI. To work around this issue, enter the missing values and resave the document.

16785

When modifying a Migration Profile’s Migration Options, from the initially selected "Message of type" option with the 'Mail', 'Task', 'Calendar' or 'Contacts' checkboxes selected, to the "All message types" option, without unchecking the selected checkboxes, the migration will migrate the items which were initially selected, not all message types. The checkboxes must be unchecked prior to changing to the 'All message types' option.

45859

Table 30. Notes Migrator.nsf\Post-Migration Actions known limitations

Known limitation

Issue ID

The "Set Reader Access for Users mailfile" does not properly report the success and failed to process correctly.

16599

The "Set Reader Access" post migration action incorrectly reports no success when agent completes.

16811

Migrated data does not get removed when using a date range. 

29156

The Set Full Access button agent reports a PowerShell error when the Full Access delegation permissions are run on accounts that have been mail box enabled in Office 365 if there are two or more accounts that have the same Display Name attribute.

Error: The operation couldn't be performed because 'Account Name' matches multiple entries.

40699

Table 31. Notes Migrator.nsf\Pre-Migration Actions known limitations

Known limitation

Issue ID

A Mail Rules message doesn't show the Message Log under the Notes Migrator user document which prevents the migration administrator from verifying the rules message was sent to the selected user(s).

16640

When using the combined notification template for end users in the Notes Migrator database, there is no way to prevent execution alerts from being displayed to the end users.

16666

Unable to provision a user if any of the shortnames in the Notes Migrator person document are in firstname.lastname format, regardless of whether the value is single or multiple.

16746

CAS Server matching returns an erroneous message when it can't find a match for a user due to non-matching SMTP addresses between the source and destination objects.

16763

Verify Mail DB (Audit Mail file) does not support clustered mail servers.

16772

The Name Translation Table CSVDE matching option does not support the matching of the German o ( ö ) character and Greek Alphabet characters (Έλληνες χρήστη1). To work around this issue, use one of the other match options.

16788

Mail-in DB's or Rooms & Resources cannot be provisioned to Office 365. This must be manually performed.

16802

Set Full Admin access fails when the users name contains a "$" character.

16805

Private folders are not included in the Pre-Migration Mail File Audit.

22747

Table 32. Notes Migrator.nsf\Progress Summary known limitations

Known limitation

Issue ID

Scheduled migrations produced error in Notes status bar.

16667

Table 33. Rooms and Resources known limitations

Known limitation

Issue ID

The database template specified in the Rooms & Resource settings must be present on the Target server specified in the same settings document, or an error will display that the database template cannot be found.

16508

Room and Resources don't display on a migrated calendar entry on the scheduling tab.

16606

Leading and trailing spaces are trimmed in values of Room Label, Resource Label, Online Label, Location Detail Indicator, and Room Resource Separator Settings Fields.

16661

Recurring meetings in the Domino rooms and resources application are stored as individual documents for each instance and are migrated as such. These require direct management in Outlook for changes post migration. Additionally, modifications to recurring meetings in rooms and resources will not migrate instance changes correctly. 

16715

Room and Resources Migration will not load the worker on the controller if no other workers are registered.  You will encounter the error: "C:\program files\binarytree\cmt for exchange\cmt_migrationworker.exe could not be started.  Please confirm that CMT is Installed correctly and the settings doc reflects the correct install path."

28448

Room import fails when the room has quotes in the name.

38359

 

 

Table 34. To-Do Migration known limitations

Known limitation

Issue ID

Completing a migrated Task will send a notification to the SendTo user when the Task is created using the "Copy into new..." button in Lotus Notes. No notification should be sent.

16598

Text bullets appear as asterisks ("*") post migration when viewed from Outlook Web Access (only).

16613

Embedded graphics in Lotus Notes Tasks are migrated as attachments.

16619

Lotus Notes Tasks created by a delegate appear in Outlook with the delegate as the Owner, instead of 'Delegate (Sent on behalf of mail file owner)'.

16621

Migrated Tasks containing Notes links have an extraneous .gif attachment for each link.

16622

Read/Unread status is not maintained on migrated Tasks when using Outlook Web Access.

16623

Unaccepted To Do notices in Lotus Notes do not migrate to Exchange.

16632

Repeating tasks (to-do's) do not migrate to the correct dates.

16693

Assigned Tasks (To-Do's) are migrated as Task calendar events, not as Task Requests. The migrated Task will only be displayed in the To-Do's not in the Inbox.

16697

Yearly and Custom recurring Tasks become Weekly Tasks after migration.

16702

When migrated assigned tasks are completed the person who created the task and assigned it to someone else does not get the notification that it was completed. 

16706

The Task Owner name displays the ExchangeLegacyDN rather than the Display Name. This is a cosmetic issue only and there is no loss in functionality.

46929

Task assignees (Required, Optional, FYI) are not migrated to Outlook.

46986

System requirements

Refer to the Binary Tree Migrator for Notes 20.12 Requirements (http://support.quest.com/technical-documents/binary-tree-migrator-for-notes/20.12/requirements) for system requirements.

Product licensing

A valid license is required for Binary Tree Migrator for Notes.

To obtain licenses, see information on this page https://www.quest.com/company/contact-us.aspx or contact the sales team at sales@quest.com

Upgrade and installation instructions

Refer to the Binary Tree Migrator for Notes 20.12 Installation and Configuration Guide (http://support.quest.com/technical-documents/binary-tree-migrator-for-notes/20.12/installation-and-configuration-guide) for installation instructions.

More resources

Additional information is available from the following:

Globalization

This section contains information about installing and operating this product in non-English configurations, such as those needed by customers outside of North America. This section does not replace the materials about supported platforms and configurations found elsewhere in the product documentation.

 

This release is Unicode-enabled and supports any character set. In this release, all product components should be configured to use the same or compatible character encodings and should be installed to use the same locale and regional options. This release is targeted to support operations in the following regions: North America, Western Europe and Latin America, Central and Eastern Europe, Far-East Asia, Japan. It supports bidirectional writing (Arabic and Hebrew). The release supports Complex Script (Central Asia – India, Thailand).

About us

Quest creates software solutions that make the benefits of new technology real in an increasingly complex IT landscape. From database and systems management, to Active Directory and Office 365 management, and cyber security resilience, Quest helps customers solve their next IT challenge now. Around the globe, more than 130,000 companies and 95% of the Fortune 500 count on Quest to deliver proactive management and monitoring for the next enterprise initiative, find the next solution for complex Microsoft challenges and stay ahead of the next threat. Quest Software. Where next meets now. For more information, visit www.quest.com.

Technical support resources

Technical support is available to Quest customers with a valid maintenance contract and customers who have trial versions. You can access the Quest Support Portal at https://support.quest.com.

The Support Portal provides self-help tools you can use to solve problems quickly and independently, 24 hours a day, 365 days a year. The Support Portal enables you to:

  • Submit and manage a Service Request

  • View Knowledge Base articles

  • Sign up for product notifications

  • Download software and technical documentation

  • View how-to-videos

  • Engage in community discussions

  • Chat with support engineers online

  • View services to assist you with your product.

© 2021 Quest Software Inc.
ALL RIGHTS RESERVED.

This guide contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchaser’s personal use without the written permission of Quest Software Inc.

The information in this document is provided in connection with Quest Software products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest Software products. EXCEPT AS SET FORTH IN THE TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST SOFTWARE ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST SOFTWARE BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST SOFTWARE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest Software makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. Quest Software does not make any commitment to update the information contained in this document.

If you have any questions regarding your potential use of this material, contact:

Quest Software Inc.

Attn: LEGAL Dept

4 Polaris Way

Aliso Viejo, CA 92656

Refer to our Web site (https://www.quest.com) for regional and international office information.

Patents

Quest Software is proud of our advanced technology.  Patents and pending patents may apply to this product. For the most current information about applicable patents for this product, please visit our website at https://www.quest.com/legal.

Trademarks

Quest, the Quest logo, and Join the Innovation are trademarks and registered trademarks of Quest Software Inc. For a complete list of Quest marks, visit https://www.quest.com/legal/trademark-information.aspx.  All other trademarks and registered trademarks are property of their respective owners.

Legend

CAUTION: A CAUTION icon indicates potential damage to hardware or loss of data if instructions are not followed.

 

IMPORTANT, NOTE, TIP, MOBILE, or VIDEO: An information icon indicates supporting information.

New features

Binary Tree® Migrator for Notes 20.12

Release Notes

May 2021

These release notes provide information about the Binary Tree Migrator for Notes 20.12 release.

Topics:

 

About this release

Migrator for Notes is the most comprehensive software available for migrating from HCL Domino to Microsoft Exchange.

Migrator for Notes not only supports migrations to on-premises Microsoft Outlook and Exchange, but also to online versions of Microsoft Outlook and Hosted Exchange, including Office 365.

Migrator for Notes, part of Binary Tree’s suite of migration solutions that includes Directory Sync Pro and Notes Integration, offers unmatched data fidelity, migration management, and migration throughput.

Migrator for Notes 20.12 is a minor release, with new features and functionality. See New features and Enhancements.

New features in Migrator for Notes:

  • The Migrate Unfiled Documents option has been added to the Migration Profile Options. This option determines if “unfiled” documents will be migrated. (54015)

  • To resolve formatting issues with the Sametime Chat history, the "Process Sametime history as" setting has been added to allow you to select the format as Rich Text or MIME. (75337)

  • The “Override existing license" option has been added to the Office 365 Settings page. This setting allows for overriding an existing license on accounts being processed, replacing the license with the new selection. (75965)

  • The "Copy Manager on Notification" setting has been added to the Message Template settings. Select this setting to send a copy of the message to the user’s manager. This setting is available only when Other Settings - Advanced features is enabled and the account being sent the notification has the Manager field competed in the Domino Directory. (76044)

  • New settings to Skip reprocessing users that have previously failed and to Reprocess successful matches have been added to the Email Repliability Matching settings. (76059)

  • Exchange Environment, Remote Azure AD Endpoint, and Azure AD Environment settings have been added to the User Provisioning Settings to handle connections for regional data centers. (76174)

See also:

Enhancements

The following is a list of enhancements implemented in Migrator for Notes.

Table 1. General enhancements

Enhancement

Issue ID

The two migration job log files have been combined into a single log file.

47509

For migrations that have repeated network errors, the migration of accounts is now automatically re-tried using the auto retry processing.

64665

Migration will now be terminated if the Name Translation process cannot connect to the source database.

65900

Updated email repliability to validate against canonical Notes name for accounts where there are multiple entries with the same common name.

75031

Migrations failures due to network errors have been added to re-queue processing.

75323

Unfiled processing has been updated to skip opening documents that are already in the migration history to allow for faster Unfiled checks.

75336

Passwords passed from the engine to the Outlook Agent are now hashed.

75385

The Outlook Agent has been updated to use the registry-stored account and password if not provided when called from engine.

75386

The User Provisioning Settings have been updated to hide settings that are not applicable to Office 365 migrations.

75952

Support for double-byte character set (DBCS) has been added for the following fields:

Rooms & Resources:

  • Room Label

  • Resource Label

  • Online Label

  • Location Detail Indicator

Migration profile:

  • Unfiled folder name

Other Settings:

  • Encrypted Items Migration (text)

75966

Updated Settings to include a configurable list of Notes system folders for use with the Fix Folders agent.

75967

Settings that are not applicable to Office 365 migration are hidden on the User Provisioning Settings screen.

76060

Support for double-byte character set (DBCS) for encrypted body message has been added.

76148

Resolved issues

The following is a list of issues addressed in this release.

Table 2. General resolved issues

Resolved Issue

Issue ID

An issue where migrated external meeting requests had the reply address set incorrectly has been resolved.

41515

An issue where migrations are incorrectly marked as successful when the Domino server runs out of space and cannot open source folders has been resolved.

52658

An issue where messages with the follow up flags set to high priority/low priority are migrated without the follow up flags has been resolved.

54900

An issue where the reply to and forwarded icons indicating that a message has been replied to or forwarded did not migrate has been resolved.

54901

An issue where address field values with leading spaces caused Name Translation Table lookups to fail has been resolved.

69928

An issue where the reply address was set incorrectly for migrated "on behalf of" messages has been resolved.

74131

Corrected a condition where a document causing a Notes out of memory error was not being skipped during the fault recovery migration.

76085

An issue where Modern Auth failed if LegacyExchangeDN was not found and terminated abnormally has been resolved.

76161

An issue where Modern Auth abnormally terminated if GetTopOfInformationStore fails has been resolved.

76162

An issue where initialization failed on Notes version 10.0 has been resolved.

76243

Corrected an issue where when using Modern Authentication, and targeting an Archive mailbox, Migrator for Notes failed to connect to the target archive mailbox.  Basic Authentication must remain enabled for Autodiscover, but Modern Authentication can be used for mailbox access.

76265

Known limitations

Most of the known limitations and issues of any migration process are due to feature inconsistencies between the source and target environments. Features that are available in the Notes environment cannot be migrated to a target environment that does not offer the same or comparable features. Other limitations are due to feature incompatibilities where similar features are available in both the source and target environments, but their implementations are so different that migration is impractical.

While every effort is made to determine the specific limitations of a migration process, so that these are available for planning, communications and support, it is possible that there may be unknown limitations. These can occur in particular with changes to source or target system versions and in the case of email migrations for any data generated by third party system changes. Where previously unknown limitations in the data migration are found these would be reviewed to determine if the item can be resolved and migrated but it should be noted that these may result in a new known limitation.

The following is a list of known limitations or issues, including those attributed to third-party products, known to exist at the time of this release.

Table 4. AWD\Configuration known limitations

Known limitation

Issue ID

The Store Password feature does not validate the password and will allow you to store an incorrect password without prompting for a valid password when "Get Server List" is clicked.

16596

Table 5. AWD\Migration Workstation known limitations

Known limitation

Issue ID

If more than one instance of Lotus Notes or Notes Migrator is installed on a migration workstation, you will be prompted for the Notes password for each migration.

16688

Table 6. Calendar Migration known limitations

Known limitation

Issue ID

"Description:" appears in the body of migrated calendar documents when viewed in Outlook Web Access.

16629

Attachments in migrated calendar entries may not appear in the same position as in Notes when viewed from Outlook.

16635

If an invitee of a migrated meeting is changed from Optional to Required, the invitee's name appears in both Optional and Required fields in OWA. This is not a problem in Outlook.

16650

Calendar entries with a repeat pattern of Every Other Year are not natively supported in Exchange and are migrated as Yearly entries.

16654

When the migration setting to add Room, Resource and Online Meeting Place information to the body of Calendar entries is selected, and there is no Room, Resource or Online Meeting Place in the calendar entry, "See Details Below" is still added to the Location field.

16655

Subjects of Repeat Calendar entries that have carriage returns will not be displayed properly in Outlook and OWA 2007.

16659

Rooms and Resources added or removed to a Notes repeat meeting after the meeting was created will appear properly on each occurrence of the migrated meeting, but not the meetings series.

16663

User values in the BCC field of a migrated calendar item will appear in the Resource field. This is because Exchange uses the BCC field for resources, so any names in the BCC field will be treated as a resource. If the location field is empty, Outlook will display the resources in the location field also (it assumes resources will be a room or online meeting place).

16669

If "Automatically adjust clock for daylight saving changes" on the "Date and Time Properties" dialog box is not checked, and/or the latest Microsoft DST patches have not been installed, multi-day calendar events that start in one Daylight Savings Time period and end it another will appear off by 1 hour during the Daylight Savings Time period in which they were not created.

16685

Migrated recurring calendar events, where invitees have been added or removed from single instances will not list the correct attendees on the Chair Person's calendar.  However, the invitees’ calendars are correct.

16713

A migration crash can occur with an excessive amount of data (over 50 entries) in the Location and Rooms fields.

16717

Enterprise Vault links in Domino calendar items are missing after migration.

16758

Migrated meeting invitations that are unread in Notes are not displayed in the OWA calendar until after they are viewed post migration. (21865)

21865

Calendar items that do not have a start or end date causes a migration failure.

44404

Notes calendar entries' High Importance property does not get migrated to O365. Migrated calendar entries will be migrated as Normal importance.

57585

Attachments in migrated calendar entries may not appear in the same position as in Notes when viewed from Outlook.

16635

Table 7. Calendar Migration\Anniversary known limitations

Known limitation

Issue ID

The Play Sound reminder option in Lotus Notes Calendar items does not migrate to Outlook.

16618

Lotus Notes Anniversaries with the 'Pencil In' option selected are migrated to Outlook with a Show As: Free, instead of Tentative.

16625

Reminder sound notification is not maintained on a non-repeating Anniversary after migration.

16653

A recurring anniversary series that has been modified will appear on the correct day(s), but the dates displayed in each occurrence reflect the original date.

16687

Location and Category fields are not migrated in Anniversaries.

16712

Birthday and Anniversary data for local contacts are not added to the Outlook Calendar.

45182

Table 8. Calendar Migration\Delegation known limitations

Known limitation

Issue ID

If an invitee delegates one or more instances of a repeating meeting to someone else and the chairperson then updates the meeting, the entire series will appear on the original invitee’s calendar post migration.

16798

Table 9. Calendar Migration\Meetings known limitations

Known limitation

Issue ID

Embedded images in calendar entries appear as attachments in migrated calendar documents.

16614

The chairperson of an unaccepted meeting appears in the Required field after migration.

16627

Responses from attendees added after the original invite is issued do not update the chair's calendar tracking status.

16675

With the setting "Process meetings with no end date using ICAL information" set to yes, meetings with no end date sent from Outlook to Notes do not migrate properly if updates/reschedules have been accepted in Lotus Notes.

16676

Changes to migrated meetings with Rooms and/or Resources are not updated in the Domino Resource Reservations database. Updates are not properly made in the Notes Rooms and Resources database if a one-time meeting or reoccurring meeting is cancelled in Outlook. Additionally, updates are not properly made in the Notes Rooms and Resources database or migrated Room and Resource mailbox if individual occurrences are cancelled or rescheduled in Outlook.

16698

If an occurrence of a migrated repeating meeting is changed by the migrated chair in Exchange, it does not appear correctly on the calendar of Invitees that were added after the original meeting was created.

16699

Required attendees and resource do not show up in a printer output of the meeting with a migrated meeting. Native meetings created in Outlook show this information in the printed output.

16741

Meetings and Appointments in Notes that have the choice "Mark Available" checked are listed as "Tentative”, instead of "Free”, when migrated to Exchange.

16757

A meeting identified as a repeating meeting, but contains no repeat pattern, will not migrate the remaining events if one of the events has been cancelled.  The meeting will be listed in the log as being skipped because it was cancelled, when in truth, only one of the occurrences was canceled.

16766

Unknown time zones display the incorrect time even though the meeting is on the calendar at the proper date and time.

16778

The Response Status is not cleared when a critical change (date/time/location) is made by the chair after the invitee has accepted the original meeting. When the chair invites, the invitee accepts, the chair changes the date, and then migration occurs, the migrated calendar event will contain the invitee response to the original invite, even though it is not invalid/obsolete due to the date change. The date change notice will migrate correctly, and later responses will correctly update the chair tracking. In the time between migration and the invitee responding to the change, the chair tracking will continue to show the invitee as accepted even though the change has been issued.

16791

If the entire series of a repeat meeting was rescheduled prior to migration, changes post migration will generate an NDR.

16813

If the chair of a meeting cancels an instance of a recurring meeting prior to migration by using the 'Delete' key, Domino deletes the child document from the database. Since the child document is missing, Notes Migrator will use the original pattern during migration, and the canceled meeting will appear on the calendar in Outlook.  To avoid this, the canceled meeting(s) instances should not be deleted from the source database.

16823

Executable (.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC) and consumable (.PST) attachments to calendar items are delayed when migrating. Items appear approximately 30 to 45 minutes after migration completes.

41359

When an all day, repeating event is rescheduled in Notes before migration, the reschedule dates are not applied in Outlook. The original all-day event dates are used except for the first booking in the series.

41856

Due to Exchange’s inability to process a large number of exceptions, during a migration, Notes Migrator will not create more than 200 exceptions for an event. Any exception beyond the first 200 will not be applied, and this may show as updates/reschedules/additions/cancels/etc. not appearing on the later occurrences.

37682

Table 10. Calendar Migration\Reminders known limitations

Known limitation

Issue ID

Tasks/ToDos, Notices (invites and updates) that have reminders and Messages that have a follow-up/reminder set will cause many past due pop-up reminders in outlook after they are migrated. Clicking the "dismiss all" button will resolve the issue.

16705

Because there is no equivalent in Outlook, Reminders migrate as appointments with the free time blocked out.

16771

Table 11. Contact Migration known limitations

Known limitation

Issue ID

Migration of personal NAB nested groups causes delivery failure for Nested Groups.

16594

Migrating Personal Groups with internal Notes users creates delivery failures due to lack of "EX" value in 'Type' field.

16597

The data in the Location field of contacts is not migrated.  The data in Address fields are not mapped properly and will appear differently between Outlook and Outlook Web Access.

16633

Embedded graphics in Migrated Contacts are not visible in OWA.

16637

The Home Address is migrated into both the Home and Business Address of Contacts.

16647

The data in the Location field on the Business tab of a Lotus Notes contact does not migrate to the PR_Office_Location field in Outlook as expected.

16651

The entire Business Address is migrated to the City field in a Contact.

16658

If the member of a Personal Mail Group was copied from the Domino Directory (into the Personal Address Book), the members have invalid SMTP addresses with a Domain of "@unk domain" after migration.

16660

The Country Codes of Personal Addresses are not migrated in Contacts.

16662

Embedded files in contacts do not migrate.

16695

The IM Address in contacts does not migrate to Exchange.

16745

The contact's SMTP email address does not get migrated to Exchange when the 'InternetAddress' field is NULL, but there is a value in the 'MailAddress' field.

16750

When Contacts with a photo are migrated to Exchange, the contact photo is migrated to the "Notes" field as an attachment without an extension and not the contact field in the Exchange contact document.

16756

When migrated to Exchange, the friendly email address format is incorrect and results in an email delivery failure when used.

16764

Personal Contact non-primary email fields with a canonical format do not get translated to an SMTP address.

16781

The Blog Site field in a Notes contact does not migrate because there is no corresponding field in Outlook.

16782

If both the "pager" field and "Mobile 2" field are entered for a contact, the Mobile 2 number is lost.

16839

Table 12. Delegation Permissions known limitations

Known limitation

Issue ID

In hybrid Exchange installations (containing Exchange on-prem and Office 365), delegation access can only be set for users on the same system. Office 365 users can set delegation access to the mailbox to other Office 365 users, but not to Exchange users. Exchange users can set delegation access to other Exchange accounts, but not to Office 365 users. Access delegation is not supported between Exchange on-prem users and Office 365 accounts.

16841,46138

The number of accounts or groups that can be excluded from the Delegate audit is limited to 200 entries.

29154

Table 13. Encrypted Items known limitations

Known limitation

Issue ID

If a Lotus Notes encrypted message is migrated with the parameter "Require decryption action and migrate into the body", but the document is not decrypted prior to migration, the recipient is duplicated in the To field. This will only occur the first time the recipient name is encountered. All subsequent messages will be migrated as expected.

16762

The decrypt agent introduced in version 3.5.1 does not set the encrypt field to 0 or remove it, so an audit run after the agent has been run still show documents as encrypted when they are not.

16814

For messages that are encrypted at the time of the migration, the From address is not translated and uses the address from the MIME header to stamp the message. Messages are migrated without the body due to encryption and the message is not able to be replied to since the From address has not been translated.

25661

An apostrophe (') in encrypted content body text does not correctly migrate.

29153

Table 6. Group Migrations known limitations

Known limitation

Issue ID

Domino Directory Group Migrations should be done using Directory Sync Pro.

34459

Table 14. Installation known limitations

Known limitation

Issue ID

File versions are not properly displayed in the C:\program files\binary tree\cmt for exchange\cmtmonitor\bin location.

29005

The .MSI installer does not check the workstation environment meets the minimum requirements and does not install the missing components needed for a successful migration.

27624

Migration workstations cannot be uninstalled if the Migration Control Center cannot be contacted.

32941

Table 15. Logging known limitations

Known limitation

Issue ID

Migration summary of contacts does not count group documents.

34362

Table 16. Mail Migration known limitations

Known limitation

Issue ID

The subjects of migrated messages are not appended with "[BinaryTree Evaluation Copy]" when using an evaluation copy and the user is migrated more than one time.

16611

Font size properties within a migrated message are not maintained if the font size in Lotus Notes is not the default size.

16612

The color of text bullets is black regardless of the color of the text and bullets in the source document.

16624

Although the type of message to migrate is set to 'Mail Only' in the Migration Settings, Phone Messages still migrate and do not contain the correct formatting.

16628

The recipient of a message sent to one's self appears in the CC: field instead of the To: field of migrated messages.

16631

The text "Follow Up" is not present in the gray follow-up banner of the migrated messages when viewed in OWA. If there is no date associated with a follow up flag in Notes, the date and time the message was sent will appear in the gray follow-up banner of the message.

16634

The Follow Flag reminder time is 12 hours ahead after migration when viewed from Outlook. It is displayed properly in OWA.

16646

An embedded graphic in a migrated mail item is displayed incorrectly when opening the browser window minimized in OWA.

16657

When migrating phone messages, the 'spiral notebook' graphic that appears at the top of the phone message in Lotus Notes is migrated as an attachment.

16704

Legacy Archive migration currently only supports 5 archives per user.

16709

Follow Up dates associated with Follow Up flags do not migrate if the time field is not set in Lotus Notes. Furthermore, Follow Up dates and times only migrate if the Alarm is set in Lotus Notes.

16724

The "Sent" field in a previewed Draft in Outlook displays the Migration Date instead of "None".

16726

Migrated draft messages are not editable. Unable to resume editing or send a migrated draft message.

16743

Some bullet types do not maintain the same format in migrated message bodies. This can impact all document types such as email, calendar, task and to-do.

16754

The following error during migration causes mail messages to not appear in destination mailbox: ! Error: Failed to save changes in MimeToMapi 0x80040305

16765

The bodies of messages containing winmail.dat files are not migrated, because they cannot be processed with MIME.

16777

Multiple attachments of the same type in a single message, stored in the message as V4 attachment types, are not migrated across. An EML attachment is added to the email (file contains no content).

16786

Reservation Doclinks sent from the Rooms and Resources database migrate as database links.

16793

When an Office 365 validation check is performed and the folder destinations do not exist, an OLE: Automation object error occurs.

16815

Tasks migrated to Exchange 2016 mailboxes do not have the PR_CONVERSATION_INDEX_TRACKING property; however, this does not appear to impact the functionality of the task.

16824

A migrated message with a follow up flag does not include the Priority Status (FollowUpStatus) if the FollowUpText field is populated.

18388

There is an issue migrating Notes email that is stored in a MIME CSS format where the message body is missing post migration.

25942

Draft messages are not migrated if both the source and target are non-English.

28157

SMTP addresses do not support double byte character sets.

33652

The source file or progress bar does not display correctly if the migration is run from a staged replica of the Domino mail file and used the additional database tab to supply the source information.

33993

Submitting a migration job using the Schedule Migration option results in the worker not updating the controller to complete the job.

44627

Responses to conversation threads that occur after the first pass migration are not added to the conversation during subsequent migrations.

45601

The Remove Migrated data functionality incorrectly selects IPM.Schedule message class items for removal when the profile is intended to only select/remove Mail items.

55414

Journal entries are migrated with the date that they are created in Notes, this does not use the Diary Date or Time Created for the journal fields.

67532

Lotus Notes stored forms and the content within the stored form may not be rendered properly after migration.

16794

Table 17. Mail Migration\Attachments known limitations

Known limitation

Issue ID

There is a 240-character limitation imposed by Lotus Notes on the full file/path name of an attachment. If this is exceeded, an error will occur and the mail message will not be migrated.

16690

There is a limit of 100MB for attachments if the Large Attachment processing is not enabled. If this is enabled there is a limit of 125MB for a single attachment and 150MB for all attachments on a message

16696

Attachments in contacts are not displayed in OWA 2013, therefore migrated attachments in contacts are not displayed in OWA. They do function as expected when using an Outlook client.

16761

Table 18. Mail Migration\Delivery Options known limitations

Known limitation

Issue ID

Mail "Return Receipt:" loses all information after migrating to Exchange.

16684

If an unread message with a read receipt request is migrated to Outlook before being read, the read receipt is not sent to the sender when read in Outlook.

18275

Table 19. Mail Migration\Rich Text known limitations

Known limitation

Issue ID

Bulleted lists with checkmarks, circles and squares are not migrated correctly and appear as filled in circles in Outlook.

16694

Migrations that contain double byte character sets may experience Rich Text formatting issues in the message body. The message content is migrated, but may not retain the font colors, bold, or indentations.

34322

Table 20. Mail Migration\Views/Folders known limitations

Known limitation

Issue ID

Any folder name containing the word "Rules" (case sensitive) is not migrated to Exchange, however, the documents will be migrated to the Unfiled folder.

16644

The Migration profile choice to "skip folder" will not work if the folder has a leading or trailing space.

16779

When migrating to a PST running an Outlook client in a language other than English, Calendar, Contacts and the drafts folder migrate in English instead of the language being used.

16787

Accented characters in an unfiled folder name is not migrated properly.

42996

The Outlook system folder’s RSS Feeds and Search Folders (or language-specific folder’s names for these) are not migrated or updated during the migration processing.

66926

Table 21. Mail-In db Migration known limitations

Known limitation

Issue ID

The Verify Database process does not report on mail-in databases.

16710

Migration of Mail-in databases with a ":" in the name is not supported, and the Mail-in database should be renamed prior to migration to remove the ":".

16730

Domino Database names containing special characters, such as "&", cause a migration status of "Migration terminated abnormally" even though the migration was successful.

16759

Table 22. Match Users known limitations

Known limitation

Issue ID

The 'Matches the selected users on the Exchange CAS server' setting does not function properly. You must use LDAP to match users prior to migrations.

16602

The Password field does not allow a space in the password when logging into the CAS Server administration ID in the Settings and Additional tab.

16604

Users that have SMTP addresses starting with 'con.', for example 'con.test@mydomain.com' cause PowerShell matching to fail.

16796

If re-matching user accounts after an account has been deleted in Office 365, the original matching information is incorrectly used.

28502

In Archive Migrator for Notes, if the archive documents generated need to be matched/re-matched, the Last Name field value will be updated for the first archive file. Documents for the second and forward will not be changed.

38119

Table 23. Migration Workstation known limitations

Known limitation

Issue ID

The migration of a user with an ampersand (&) within the first name or last name will not send logs to the Migration Control Center.

17621

Migrations workstations with a double byte character set language pack installed crashes when starting migrations.

26681

Table 24. MTCW known limitations

Known limitation

Issue ID

When updating either a single occurrence meeting or any part of a repeating meeting, if the chair changes the time zone of the update, it may not be applied to the existing meeting, but may instead create a new entry on the calendar.

34256

Table 25. Name Translation known limitations

Known limitation

Issue ID

Contact group (Distribution List) will translate to LegacyExchangeDN if matching SMTP address exists in source 'Full Name' field. Outlook Distribution Lists cannot contain LegacyExchangeDN. This will cause email delivery failures.

16784

Table 26. Notes Migrator.nsf known limitations

Known limitation

Issue ID

When clicking the 'Migrate Users' action, in an empty Migrate view, the 'Select Migration Priority' dialog is launched instead of receiving the following error: "To run this agent you must have at least 1 document selected".

16616

The "Run Replica Comparison" agent does not function when a custom replication formula is used.

16819

Chinese character archives cannot be opened from the open link in the CMT Person Document.

33433

If an invalid password is entered in the Autodiscover Password setting, the Autodiscover process will prompt for a password when the migration begins. You must enter a valid password, check the box to remember these credentials and click OK for the migration to proceed. If you do not check the box to remember these credentials, the migration will end and not complete.

38838

Table 27. Notes Migrator.nsf\Configuration Settings known limitations

Known limitation

Issue ID

When configuring migration of user for future time, you see "migration status is set to error for user XX: migratecmtuser failed in the status bar at the button of the Lotus Notes client; however, the user will migrate.

16600

Changing a migration to a “Migrate Now (high priority)” does not queue the user on the next available migration workstation; only use the default selection: "Add to migration queue (normal priority)”.

16691

The "Past and Present Domino Domains" setting is limited to 255 characters.

18385

Separators, other than commas, in the list of Past and Present Domino Domains entered in the Email Repliability settings are not converted to commas.

39586

LDAP validation and processing will not complete if an AD Domain Controller GPO is set with “Domain controller: LDAP server signing requirements” set to “Require Signing”.

40768

Calendar items created from migrated data will not be removed by the Remove Migrated Data function.

48487

Table 28. Notes Migrator.nsf\Message Templates known limitations

Known limitation

Issue ID

The error message, "You do not have the permission to send the message on behalf of the specified user" appears when attempting to send a migrated draft message.

16636

When "receiving unencrypted mail, encrypt before storing in your mailfile:" is selected in the Person document (in the Domino Directory), the decrypt button will not decrypt these encrypted messages.

16740

Migration Message Templates that contain Notes buttons are not available if an end user views the email in iNotes (web mail). This limitation applies to all button email templates in Notes Migrator. The email buttons can only be processed in the full Notes client.

54536

Table 29. Notes Migrator.nsf\Migration Profiles known limitations

Known limitation

Issue ID

Attempting to Set Migration Profile when there are no documents selected, does not produce an error.

16642

Advanced settings in a Migration Profile disappear after Profile Refresh, if the profile is deleted from the UI, and not the back-end. The Advance Settings are still stored in the back-end but are not displayed in the UI. To work around this issue, enter the missing values and resave the document.

16785

When modifying a Migration Profile’s Migration Options, from the initially selected "Message of type" option with the 'Mail', 'Task', 'Calendar' or 'Contacts' checkboxes selected, to the "All message types" option, without unchecking the selected checkboxes, the migration will migrate the items which were initially selected, not all message types. The checkboxes must be unchecked prior to changing to the 'All message types' option.

45859

Table 30. Notes Migrator.nsf\Post-Migration Actions known limitations

Known limitation

Issue ID

The "Set Reader Access for Users mailfile" does not properly report the success and failed to process correctly.

16599

The "Set Reader Access" post migration action incorrectly reports no success when agent completes.

16811

Migrated data does not get removed when using a date range. 

29156

The Set Full Access button agent reports a PowerShell error when the Full Access delegation permissions are run on accounts that have been mail box enabled in Office 365 if there are two or more accounts that have the same Display Name attribute.

Error: The operation couldn't be performed because 'Account Name' matches multiple entries.

40699

Table 31. Notes Migrator.nsf\Pre-Migration Actions known limitations

Known limitation

Issue ID

A Mail Rules message doesn't show the Message Log under the Notes Migrator user document which prevents the migration administrator from verifying the rules message was sent to the selected user(s).

16640

When using the combined notification template for end users in the Notes Migrator database, there is no way to prevent execution alerts from being displayed to the end users.

16666

Unable to provision a user if any of the shortnames in the Notes Migrator person document are in firstname.lastname format, regardless of whether the value is single or multiple.

16746

CAS Server matching returns an erroneous message when it can't find a match for a user due to non-matching SMTP addresses between the source and destination objects.

16763

Verify Mail DB (Audit Mail file) does not support clustered mail servers.

16772

The Name Translation Table CSVDE matching option does not support the matching of the German o ( ö ) character and Greek Alphabet characters (Έλληνες χρήστη1). To work around this issue, use one of the other match options.

16788

Mail-in DB's or Rooms & Resources cannot be provisioned to Office 365. This must be manually performed.

16802

Set Full Admin access fails when the users name contains a "$" character.

16805

Private folders are not included in the Pre-Migration Mail File Audit.

22747

Table 32. Notes Migrator.nsf\Progress Summary known limitations

Known limitation

Issue ID

Scheduled migrations produced error in Notes status bar.

16667

Table 33. Rooms and Resources known limitations

Known limitation

Issue ID

The database template specified in the Rooms & Resource settings must be present on the Target server specified in the same settings document, or an error will display that the database template cannot be found.

16508

Room and Resources don't display on a migrated calendar entry on the scheduling tab.

16606

Leading and trailing spaces are trimmed in values of Room Label, Resource Label, Online Label, Location Detail Indicator, and Room Resource Separator Settings Fields.

16661

Recurring meetings in the Domino rooms and resources application are stored as individual documents for each instance and are migrated as such. These require direct management in Outlook for changes post migration. Additionally, modifications to recurring meetings in rooms and resources will not migrate instance changes correctly. 

16715

Room and Resources Migration will not load the worker on the controller if no other workers are registered.  You will encounter the error: "C:\program files\binarytree\cmt for exchange\cmt_migrationworker.exe could not be started.  Please confirm that CMT is Installed correctly and the settings doc reflects the correct install path."

28448

Room import fails when the room has quotes in the name.

38359

 

 

Table 34. To-Do Migration known limitations

Known limitation

Issue ID

Completing a migrated Task will send a notification to the SendTo user when the Task is created using the "Copy into new..." button in Lotus Notes. No notification should be sent.

16598

Text bullets appear as asterisks ("*") post migration when viewed from Outlook Web Access (only).

16613

Embedded graphics in Lotus Notes Tasks are migrated as attachments.

16619

Lotus Notes Tasks created by a delegate appear in Outlook with the delegate as the Owner, instead of 'Delegate (Sent on behalf of mail file owner)'.

16621

Migrated Tasks containing Notes links have an extraneous .gif attachment for each link.

16622

Read/Unread status is not maintained on migrated Tasks when using Outlook Web Access.

16623

Unaccepted To Do notices in Lotus Notes do not migrate to Exchange.

16632

Repeating tasks (to-do's) do not migrate to the correct dates.

16693

Assigned Tasks (To-Do's) are migrated as Task calendar events, not as Task Requests. The migrated Task will only be displayed in the To-Do's not in the Inbox.

16697

Yearly and Custom recurring Tasks become Weekly Tasks after migration.

16702

When migrated assigned tasks are completed the person who created the task and assigned it to someone else does not get the notification that it was completed. 

16706

The Task Owner name displays the ExchangeLegacyDN rather than the Display Name. This is a cosmetic issue only and there is no loss in functionality.

46929

Task assignees (Required, Optional, FYI) are not migrated to Outlook.

46986

System requirements

Refer to the Binary Tree Migrator for Notes 20.12 Requirements (http://support.quest.com/technical-documents/binary-tree-migrator-for-notes/20.12/requirements) for system requirements.

Product licensing

A valid license is required for Binary Tree Migrator for Notes.

To obtain licenses, see information on this page https://www.quest.com/company/contact-us.aspx or contact the sales team at sales@quest.com

Upgrade and installation instructions

Refer to the Binary Tree Migrator for Notes 20.12 Installation and Configuration Guide (http://support.quest.com/technical-documents/binary-tree-migrator-for-notes/20.12/installation-and-configuration-guide) for installation instructions.

More resources

Additional information is available from the following:

Globalization

This section contains information about installing and operating this product in non-English configurations, such as those needed by customers outside of North America. This section does not replace the materials about supported platforms and configurations found elsewhere in the product documentation.

 

This release is Unicode-enabled and supports any character set. In this release, all product components should be configured to use the same or compatible character encodings and should be installed to use the same locale and regional options. This release is targeted to support operations in the following regions: North America, Western Europe and Latin America, Central and Eastern Europe, Far-East Asia, Japan. It supports bidirectional writing (Arabic and Hebrew). The release supports Complex Script (Central Asia – India, Thailand).

About us

Quest creates software solutions that make the benefits of new technology real in an increasingly complex IT landscape. From database and systems management, to Active Directory and Office 365 management, and cyber security resilience, Quest helps customers solve their next IT challenge now. Around the globe, more than 130,000 companies and 95% of the Fortune 500 count on Quest to deliver proactive management and monitoring for the next enterprise initiative, find the next solution for complex Microsoft challenges and stay ahead of the next threat. Quest Software. Where next meets now. For more information, visit www.quest.com.

Technical support resources

Technical support is available to Quest customers with a valid maintenance contract and customers who have trial versions. You can access the Quest Support Portal at https://support.quest.com.

The Support Portal provides self-help tools you can use to solve problems quickly and independently, 24 hours a day, 365 days a year. The Support Portal enables you to:

  • Submit and manage a Service Request

  • View Knowledge Base articles

  • Sign up for product notifications

  • Download software and technical documentation

  • View how-to-videos

  • Engage in community discussions

  • Chat with support engineers online

  • View services to assist you with your product.

© 2021 Quest Software Inc.
ALL RIGHTS RESERVED.

This guide contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchaser’s personal use without the written permission of Quest Software Inc.

The information in this document is provided in connection with Quest Software products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest Software products. EXCEPT AS SET FORTH IN THE TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST SOFTWARE ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST SOFTWARE BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST SOFTWARE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest Software makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. Quest Software does not make any commitment to update the information contained in this document.

If you have any questions regarding your potential use of this material, contact:

Quest Software Inc.

Attn: LEGAL Dept

4 Polaris Way

Aliso Viejo, CA 92656

Refer to our Web site (https://www.quest.com) for regional and international office information.

Patents

Quest Software is proud of our advanced technology.  Patents and pending patents may apply to this product. For the most current information about applicable patents for this product, please visit our website at https://www.quest.com/legal.

Trademarks

Quest, the Quest logo, and Join the Innovation are trademarks and registered trademarks of Quest Software Inc. For a complete list of Quest marks, visit https://www.quest.com/legal/trademark-information.aspx.  All other trademarks and registered trademarks are property of their respective owners.

Legend

CAUTION: A CAUTION icon indicates potential damage to hardware or loss of data if instructions are not followed.

 

IMPORTANT, NOTE, TIP, MOBILE, or VIDEO: An information icon indicates supporting information.

Enhancements

Binary Tree® Migrator for Notes 20.12

Release Notes

May 2021

These release notes provide information about the Binary Tree Migrator for Notes 20.12 release.

Topics:

 

About this release

Migrator for Notes is the most comprehensive software available for migrating from HCL Domino to Microsoft Exchange.

Migrator for Notes not only supports migrations to on-premises Microsoft Outlook and Exchange, but also to online versions of Microsoft Outlook and Hosted Exchange, including Office 365.

Migrator for Notes, part of Binary Tree’s suite of migration solutions that includes Directory Sync Pro and Notes Integration, offers unmatched data fidelity, migration management, and migration throughput.

Migrator for Notes 20.12 is a minor release, with new features and functionality. See New features and Enhancements.

New features

New features in Migrator for Notes:

  • The Migrate Unfiled Documents option has been added to the Migration Profile Options. This option determines if “unfiled” documents will be migrated. (54015)

  • To resolve formatting issues with the Sametime Chat history, the "Process Sametime history as" setting has been added to allow you to select the format as Rich Text or MIME. (75337)

  • The “Override existing license" option has been added to the Office 365 Settings page. This setting allows for overriding an existing license on accounts being processed, replacing the license with the new selection. (75965)

  • The "Copy Manager on Notification" setting has been added to the Message Template settings. Select this setting to send a copy of the message to the user’s manager. This setting is available only when Other Settings - Advanced features is enabled and the account being sent the notification has the Manager field competed in the Domino Directory. (76044)

  • New settings to Skip reprocessing users that have previously failed and to Reprocess successful matches have been added to the Email Repliability Matching settings. (76059)

  • Exchange Environment, Remote Azure AD Endpoint, and Azure AD Environment settings have been added to the User Provisioning Settings to handle connections for regional data centers. (76174)

See also:

The following is a list of enhancements implemented in Migrator for Notes.

Table 1. General enhancements

Enhancement

Issue ID

The two migration job log files have been combined into a single log file.

47509

For migrations that have repeated network errors, the migration of accounts is now automatically re-tried using the auto retry processing.

64665

Migration will now be terminated if the Name Translation process cannot connect to the source database.

65900

Updated email repliability to validate against canonical Notes name for accounts where there are multiple entries with the same common name.

75031

Migrations failures due to network errors have been added to re-queue processing.

75323

Unfiled processing has been updated to skip opening documents that are already in the migration history to allow for faster Unfiled checks.

75336

Passwords passed from the engine to the Outlook Agent are now hashed.

75385

The Outlook Agent has been updated to use the registry-stored account and password if not provided when called from engine.

75386

The User Provisioning Settings have been updated to hide settings that are not applicable to Office 365 migrations.

75952

Support for double-byte character set (DBCS) has been added for the following fields:

Rooms & Resources:

  • Room Label

  • Resource Label

  • Online Label

  • Location Detail Indicator

Migration profile:

  • Unfiled folder name

Other Settings:

  • Encrypted Items Migration (text)

75966

Updated Settings to include a configurable list of Notes system folders for use with the Fix Folders agent.

75967

Settings that are not applicable to Office 365 migration are hidden on the User Provisioning Settings screen.

76060

Support for double-byte character set (DBCS) for encrypted body message has been added.

76148

Resolved issues

The following is a list of issues addressed in this release.

Table 2. General resolved issues

Resolved Issue

Issue ID

An issue where migrated external meeting requests had the reply address set incorrectly has been resolved.

41515

An issue where migrations are incorrectly marked as successful when the Domino server runs out of space and cannot open source folders has been resolved.

52658

An issue where messages with the follow up flags set to high priority/low priority are migrated without the follow up flags has been resolved.

54900

An issue where the reply to and forwarded icons indicating that a message has been replied to or forwarded did not migrate has been resolved.

54901

An issue where address field values with leading spaces caused Name Translation Table lookups to fail has been resolved.

69928

An issue where the reply address was set incorrectly for migrated "on behalf of" messages has been resolved.

74131

Corrected a condition where a document causing a Notes out of memory error was not being skipped during the fault recovery migration.

76085

An issue where Modern Auth failed if LegacyExchangeDN was not found and terminated abnormally has been resolved.

76161

An issue where Modern Auth abnormally terminated if GetTopOfInformationStore fails has been resolved.

76162

An issue where initialization failed on Notes version 10.0 has been resolved.

76243

Corrected an issue where when using Modern Authentication, and targeting an Archive mailbox, Migrator for Notes failed to connect to the target archive mailbox.  Basic Authentication must remain enabled for Autodiscover, but Modern Authentication can be used for mailbox access.

76265

Known limitations

Most of the known limitations and issues of any migration process are due to feature inconsistencies between the source and target environments. Features that are available in the Notes environment cannot be migrated to a target environment that does not offer the same or comparable features. Other limitations are due to feature incompatibilities where similar features are available in both the source and target environments, but their implementations are so different that migration is impractical.

While every effort is made to determine the specific limitations of a migration process, so that these are available for planning, communications and support, it is possible that there may be unknown limitations. These can occur in particular with changes to source or target system versions and in the case of email migrations for any data generated by third party system changes. Where previously unknown limitations in the data migration are found these would be reviewed to determine if the item can be resolved and migrated but it should be noted that these may result in a new known limitation.

The following is a list of known limitations or issues, including those attributed to third-party products, known to exist at the time of this release.

Table 4. AWD\Configuration known limitations

Known limitation

Issue ID

The Store Password feature does not validate the password and will allow you to store an incorrect password without prompting for a valid password when "Get Server List" is clicked.

16596

Table 5. AWD\Migration Workstation known limitations

Known limitation

Issue ID

If more than one instance of Lotus Notes or Notes Migrator is installed on a migration workstation, you will be prompted for the Notes password for each migration.

16688

Table 6. Calendar Migration known limitations

Known limitation

Issue ID

"Description:" appears in the body of migrated calendar documents when viewed in Outlook Web Access.

16629

Attachments in migrated calendar entries may not appear in the same position as in Notes when viewed from Outlook.

16635

If an invitee of a migrated meeting is changed from Optional to Required, the invitee's name appears in both Optional and Required fields in OWA. This is not a problem in Outlook.

16650

Calendar entries with a repeat pattern of Every Other Year are not natively supported in Exchange and are migrated as Yearly entries.

16654

When the migration setting to add Room, Resource and Online Meeting Place information to the body of Calendar entries is selected, and there is no Room, Resource or Online Meeting Place in the calendar entry, "See Details Below" is still added to the Location field.

16655

Subjects of Repeat Calendar entries that have carriage returns will not be displayed properly in Outlook and OWA 2007.

16659

Rooms and Resources added or removed to a Notes repeat meeting after the meeting was created will appear properly on each occurrence of the migrated meeting, but not the meetings series.

16663

User values in the BCC field of a migrated calendar item will appear in the Resource field. This is because Exchange uses the BCC field for resources, so any names in the BCC field will be treated as a resource. If the location field is empty, Outlook will display the resources in the location field also (it assumes resources will be a room or online meeting place).

16669

If "Automatically adjust clock for daylight saving changes" on the "Date and Time Properties" dialog box is not checked, and/or the latest Microsoft DST patches have not been installed, multi-day calendar events that start in one Daylight Savings Time period and end it another will appear off by 1 hour during the Daylight Savings Time period in which they were not created.

16685

Migrated recurring calendar events, where invitees have been added or removed from single instances will not list the correct attendees on the Chair Person's calendar.  However, the invitees’ calendars are correct.

16713

A migration crash can occur with an excessive amount of data (over 50 entries) in the Location and Rooms fields.

16717

Enterprise Vault links in Domino calendar items are missing after migration.

16758

Migrated meeting invitations that are unread in Notes are not displayed in the OWA calendar until after they are viewed post migration. (21865)

21865

Calendar items that do not have a start or end date causes a migration failure.

44404

Notes calendar entries' High Importance property does not get migrated to O365. Migrated calendar entries will be migrated as Normal importance.

57585

Attachments in migrated calendar entries may not appear in the same position as in Notes when viewed from Outlook.

16635

Table 7. Calendar Migration\Anniversary known limitations

Known limitation

Issue ID

The Play Sound reminder option in Lotus Notes Calendar items does not migrate to Outlook.

16618

Lotus Notes Anniversaries with the 'Pencil In' option selected are migrated to Outlook with a Show As: Free, instead of Tentative.

16625

Reminder sound notification is not maintained on a non-repeating Anniversary after migration.

16653

A recurring anniversary series that has been modified will appear on the correct day(s), but the dates displayed in each occurrence reflect the original date.

16687

Location and Category fields are not migrated in Anniversaries.

16712

Birthday and Anniversary data for local contacts are not added to the Outlook Calendar.

45182

Table 8. Calendar Migration\Delegation known limitations

Known limitation

Issue ID

If an invitee delegates one or more instances of a repeating meeting to someone else and the chairperson then updates the meeting, the entire series will appear on the original invitee’s calendar post migration.

16798

Table 9. Calendar Migration\Meetings known limitations

Known limitation

Issue ID

Embedded images in calendar entries appear as attachments in migrated calendar documents.

16614

The chairperson of an unaccepted meeting appears in the Required field after migration.

16627

Responses from attendees added after the original invite is issued do not update the chair's calendar tracking status.

16675

With the setting "Process meetings with no end date using ICAL information" set to yes, meetings with no end date sent from Outlook to Notes do not migrate properly if updates/reschedules have been accepted in Lotus Notes.

16676

Changes to migrated meetings with Rooms and/or Resources are not updated in the Domino Resource Reservations database. Updates are not properly made in the Notes Rooms and Resources database if a one-time meeting or reoccurring meeting is cancelled in Outlook. Additionally, updates are not properly made in the Notes Rooms and Resources database or migrated Room and Resource mailbox if individual occurrences are cancelled or rescheduled in Outlook.

16698

If an occurrence of a migrated repeating meeting is changed by the migrated chair in Exchange, it does not appear correctly on the calendar of Invitees that were added after the original meeting was created.

16699

Required attendees and resource do not show up in a printer output of the meeting with a migrated meeting. Native meetings created in Outlook show this information in the printed output.

16741

Meetings and Appointments in Notes that have the choice "Mark Available" checked are listed as "Tentative”, instead of "Free”, when migrated to Exchange.

16757

A meeting identified as a repeating meeting, but contains no repeat pattern, will not migrate the remaining events if one of the events has been cancelled.  The meeting will be listed in the log as being skipped because it was cancelled, when in truth, only one of the occurrences was canceled.

16766

Unknown time zones display the incorrect time even though the meeting is on the calendar at the proper date and time.

16778

The Response Status is not cleared when a critical change (date/time/location) is made by the chair after the invitee has accepted the original meeting. When the chair invites, the invitee accepts, the chair changes the date, and then migration occurs, the migrated calendar event will contain the invitee response to the original invite, even though it is not invalid/obsolete due to the date change. The date change notice will migrate correctly, and later responses will correctly update the chair tracking. In the time between migration and the invitee responding to the change, the chair tracking will continue to show the invitee as accepted even though the change has been issued.

16791

If the entire series of a repeat meeting was rescheduled prior to migration, changes post migration will generate an NDR.

16813

If the chair of a meeting cancels an instance of a recurring meeting prior to migration by using the 'Delete' key, Domino deletes the child document from the database. Since the child document is missing, Notes Migrator will use the original pattern during migration, and the canceled meeting will appear on the calendar in Outlook.  To avoid this, the canceled meeting(s) instances should not be deleted from the source database.

16823

Executable (.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC) and consumable (.PST) attachments to calendar items are delayed when migrating. Items appear approximately 30 to 45 minutes after migration completes.

41359

When an all day, repeating event is rescheduled in Notes before migration, the reschedule dates are not applied in Outlook. The original all-day event dates are used except for the first booking in the series.

41856

Due to Exchange’s inability to process a large number of exceptions, during a migration, Notes Migrator will not create more than 200 exceptions for an event. Any exception beyond the first 200 will not be applied, and this may show as updates/reschedules/additions/cancels/etc. not appearing on the later occurrences.

37682

Table 10. Calendar Migration\Reminders known limitations

Known limitation

Issue ID

Tasks/ToDos, Notices (invites and updates) that have reminders and Messages that have a follow-up/reminder set will cause many past due pop-up reminders in outlook after they are migrated. Clicking the "dismiss all" button will resolve the issue.

16705

Because there is no equivalent in Outlook, Reminders migrate as appointments with the free time blocked out.

16771

Table 11. Contact Migration known limitations

Known limitation

Issue ID

Migration of personal NAB nested groups causes delivery failure for Nested Groups.

16594

Migrating Personal Groups with internal Notes users creates delivery failures due to lack of "EX" value in 'Type' field.

16597

The data in the Location field of contacts is not migrated.  The data in Address fields are not mapped properly and will appear differently between Outlook and Outlook Web Access.

16633

Embedded graphics in Migrated Contacts are not visible in OWA.

16637

The Home Address is migrated into both the Home and Business Address of Contacts.

16647

The data in the Location field on the Business tab of a Lotus Notes contact does not migrate to the PR_Office_Location field in Outlook as expected.

16651

The entire Business Address is migrated to the City field in a Contact.

16658

If the member of a Personal Mail Group was copied from the Domino Directory (into the Personal Address Book), the members have invalid SMTP addresses with a Domain of "@unk domain" after migration.

16660

The Country Codes of Personal Addresses are not migrated in Contacts.

16662

Embedded files in contacts do not migrate.

16695

The IM Address in contacts does not migrate to Exchange.

16745

The contact's SMTP email address does not get migrated to Exchange when the 'InternetAddress' field is NULL, but there is a value in the 'MailAddress' field.

16750

When Contacts with a photo are migrated to Exchange, the contact photo is migrated to the "Notes" field as an attachment without an extension and not the contact field in the Exchange contact document.

16756

When migrated to Exchange, the friendly email address format is incorrect and results in an email delivery failure when used.

16764

Personal Contact non-primary email fields with a canonical format do not get translated to an SMTP address.

16781

The Blog Site field in a Notes contact does not migrate because there is no corresponding field in Outlook.

16782

If both the "pager" field and "Mobile 2" field are entered for a contact, the Mobile 2 number is lost.

16839

Table 12. Delegation Permissions known limitations

Known limitation

Issue ID

In hybrid Exchange installations (containing Exchange on-prem and Office 365), delegation access can only be set for users on the same system. Office 365 users can set delegation access to the mailbox to other Office 365 users, but not to Exchange users. Exchange users can set delegation access to other Exchange accounts, but not to Office 365 users. Access delegation is not supported between Exchange on-prem users and Office 365 accounts.

16841,46138

The number of accounts or groups that can be excluded from the Delegate audit is limited to 200 entries.

29154

Table 13. Encrypted Items known limitations

Known limitation

Issue ID

If a Lotus Notes encrypted message is migrated with the parameter "Require decryption action and migrate into the body", but the document is not decrypted prior to migration, the recipient is duplicated in the To field. This will only occur the first time the recipient name is encountered. All subsequent messages will be migrated as expected.

16762

The decrypt agent introduced in version 3.5.1 does not set the encrypt field to 0 or remove it, so an audit run after the agent has been run still show documents as encrypted when they are not.

16814

For messages that are encrypted at the time of the migration, the From address is not translated and uses the address from the MIME header to stamp the message. Messages are migrated without the body due to encryption and the message is not able to be replied to since the From address has not been translated.

25661

An apostrophe (') in encrypted content body text does not correctly migrate.

29153

Table 6. Group Migrations known limitations

Known limitation

Issue ID

Domino Directory Group Migrations should be done using Directory Sync Pro.

34459

Table 14. Installation known limitations

Known limitation

Issue ID

File versions are not properly displayed in the C:\program files\binary tree\cmt for exchange\cmtmonitor\bin location.

29005

The .MSI installer does not check the workstation environment meets the minimum requirements and does not install the missing components needed for a successful migration.

27624

Migration workstations cannot be uninstalled if the Migration Control Center cannot be contacted.

32941

Table 15. Logging known limitations

Known limitation

Issue ID

Migration summary of contacts does not count group documents.

34362

Table 16. Mail Migration known limitations

Known limitation

Issue ID

The subjects of migrated messages are not appended with "[BinaryTree Evaluation Copy]" when using an evaluation copy and the user is migrated more than one time.

16611

Font size properties within a migrated message are not maintained if the font size in Lotus Notes is not the default size.

16612

The color of text bullets is black regardless of the color of the text and bullets in the source document.

16624

Although the type of message to migrate is set to 'Mail Only' in the Migration Settings, Phone Messages still migrate and do not contain the correct formatting.

16628

The recipient of a message sent to one's self appears in the CC: field instead of the To: field of migrated messages.

16631

The text "Follow Up" is not present in the gray follow-up banner of the migrated messages when viewed in OWA. If there is no date associated with a follow up flag in Notes, the date and time the message was sent will appear in the gray follow-up banner of the message.

16634

The Follow Flag reminder time is 12 hours ahead after migration when viewed from Outlook. It is displayed properly in OWA.

16646

An embedded graphic in a migrated mail item is displayed incorrectly when opening the browser window minimized in OWA.

16657

When migrating phone messages, the 'spiral notebook' graphic that appears at the top of the phone message in Lotus Notes is migrated as an attachment.

16704

Legacy Archive migration currently only supports 5 archives per user.

16709

Follow Up dates associated with Follow Up flags do not migrate if the time field is not set in Lotus Notes. Furthermore, Follow Up dates and times only migrate if the Alarm is set in Lotus Notes.

16724

The "Sent" field in a previewed Draft in Outlook displays the Migration Date instead of "None".

16726

Migrated draft messages are not editable. Unable to resume editing or send a migrated draft message.

16743

Some bullet types do not maintain the same format in migrated message bodies. This can impact all document types such as email, calendar, task and to-do.

16754

The following error during migration causes mail messages to not appear in destination mailbox: ! Error: Failed to save changes in MimeToMapi 0x80040305

16765

The bodies of messages containing winmail.dat files are not migrated, because they cannot be processed with MIME.

16777

Multiple attachments of the same type in a single message, stored in the message as V4 attachment types, are not migrated across. An EML attachment is added to the email (file contains no content).

16786

Reservation Doclinks sent from the Rooms and Resources database migrate as database links.

16793

When an Office 365 validation check is performed and the folder destinations do not exist, an OLE: Automation object error occurs.

16815

Tasks migrated to Exchange 2016 mailboxes do not have the PR_CONVERSATION_INDEX_TRACKING property; however, this does not appear to impact the functionality of the task.

16824

A migrated message with a follow up flag does not include the Priority Status (FollowUpStatus) if the FollowUpText field is populated.

18388

There is an issue migrating Notes email that is stored in a MIME CSS format where the message body is missing post migration.

25942

Draft messages are not migrated if both the source and target are non-English.

28157

SMTP addresses do not support double byte character sets.

33652

The source file or progress bar does not display correctly if the migration is run from a staged replica of the Domino mail file and used the additional database tab to supply the source information.

33993

Submitting a migration job using the Schedule Migration option results in the worker not updating the controller to complete the job.

44627

Responses to conversation threads that occur after the first pass migration are not added to the conversation during subsequent migrations.

45601

The Remove Migrated data functionality incorrectly selects IPM.Schedule message class items for removal when the profile is intended to only select/remove Mail items.

55414

Journal entries are migrated with the date that they are created in Notes, this does not use the Diary Date or Time Created for the journal fields.

67532

Lotus Notes stored forms and the content within the stored form may not be rendered properly after migration.

16794

Table 17. Mail Migration\Attachments known limitations

Known limitation

Issue ID

There is a 240-character limitation imposed by Lotus Notes on the full file/path name of an attachment. If this is exceeded, an error will occur and the mail message will not be migrated.

16690

There is a limit of 100MB for attachments if the Large Attachment processing is not enabled. If this is enabled there is a limit of 125MB for a single attachment and 150MB for all attachments on a message

16696

Attachments in contacts are not displayed in OWA 2013, therefore migrated attachments in contacts are not displayed in OWA. They do function as expected when using an Outlook client.

16761

Table 18. Mail Migration\Delivery Options known limitations

Known limitation

Issue ID

Mail "Return Receipt:" loses all information after migrating to Exchange.

16684

If an unread message with a read receipt request is migrated to Outlook before being read, the read receipt is not sent to the sender when read in Outlook.

18275

Table 19. Mail Migration\Rich Text known limitations

Known limitation

Issue ID

Bulleted lists with checkmarks, circles and squares are not migrated correctly and appear as filled in circles in Outlook.

16694

Migrations that contain double byte character sets may experience Rich Text formatting issues in the message body. The message content is migrated, but may not retain the font colors, bold, or indentations.

34322

Table 20. Mail Migration\Views/Folders known limitations

Known limitation

Issue ID

Any folder name containing the word "Rules" (case sensitive) is not migrated to Exchange, however, the documents will be migrated to the Unfiled folder.

16644

The Migration profile choice to "skip folder" will not work if the folder has a leading or trailing space.

16779

When migrating to a PST running an Outlook client in a language other than English, Calendar, Contacts and the drafts folder migrate in English instead of the language being used.

16787

Accented characters in an unfiled folder name is not migrated properly.

42996

The Outlook system folder’s RSS Feeds and Search Folders (or language-specific folder’s names for these) are not migrated or updated during the migration processing.

66926

Table 21. Mail-In db Migration known limitations

Known limitation

Issue ID

The Verify Database process does not report on mail-in databases.

16710

Migration of Mail-in databases with a ":" in the name is not supported, and the Mail-in database should be renamed prior to migration to remove the ":".

16730

Domino Database names containing special characters, such as "&", cause a migration status of "Migration terminated abnormally" even though the migration was successful.

16759

Table 22. Match Users known limitations

Known limitation

Issue ID

The 'Matches the selected users on the Exchange CAS server' setting does not function properly. You must use LDAP to match users prior to migrations.

16602

The Password field does not allow a space in the password when logging into the CAS Server administration ID in the Settings and Additional tab.

16604

Users that have SMTP addresses starting with 'con.', for example 'con.test@mydomain.com' cause PowerShell matching to fail.

16796

If re-matching user accounts after an account has been deleted in Office 365, the original matching information is incorrectly used.

28502

In Archive Migrator for Notes, if the archive documents generated need to be matched/re-matched, the Last Name field value will be updated for the first archive file. Documents for the second and forward will not be changed.

38119

Table 23. Migration Workstation known limitations

Known limitation

Issue ID

The migration of a user with an ampersand (&) within the first name or last name will not send logs to the Migration Control Center.

17621

Migrations workstations with a double byte character set language pack installed crashes when starting migrations.

26681

Table 24. MTCW known limitations

Known limitation

Issue ID

When updating either a single occurrence meeting or any part of a repeating meeting, if the chair changes the time zone of the update, it may not be applied to the existing meeting, but may instead create a new entry on the calendar.

34256

Table 25. Name Translation known limitations

Known limitation

Issue ID

Contact group (Distribution List) will translate to LegacyExchangeDN if matching SMTP address exists in source 'Full Name' field. Outlook Distribution Lists cannot contain LegacyExchangeDN. This will cause email delivery failures.

16784

Table 26. Notes Migrator.nsf known limitations

Known limitation

Issue ID

When clicking the 'Migrate Users' action, in an empty Migrate view, the 'Select Migration Priority' dialog is launched instead of receiving the following error: "To run this agent you must have at least 1 document selected".

16616

The "Run Replica Comparison" agent does not function when a custom replication formula is used.

16819

Chinese character archives cannot be opened from the open link in the CMT Person Document.

33433

If an invalid password is entered in the Autodiscover Password setting, the Autodiscover process will prompt for a password when the migration begins. You must enter a valid password, check the box to remember these credentials and click OK for the migration to proceed. If you do not check the box to remember these credentials, the migration will end and not complete.

38838

Table 27. Notes Migrator.nsf\Configuration Settings known limitations

Known limitation

Issue ID

When configuring migration of user for future time, you see "migration status is set to error for user XX: migratecmtuser failed in the status bar at the button of the Lotus Notes client; however, the user will migrate.

16600

Changing a migration to a “Migrate Now (high priority)” does not queue the user on the next available migration workstation; only use the default selection: "Add to migration queue (normal priority)”.

16691

The "Past and Present Domino Domains" setting is limited to 255 characters.

18385

Separators, other than commas, in the list of Past and Present Domino Domains entered in the Email Repliability settings are not converted to commas.

39586

LDAP validation and processing will not complete if an AD Domain Controller GPO is set with “Domain controller: LDAP server signing requirements” set to “Require Signing”.

40768

Calendar items created from migrated data will not be removed by the Remove Migrated Data function.

48487

Table 28. Notes Migrator.nsf\Message Templates known limitations

Known limitation

Issue ID

The error message, "You do not have the permission to send the message on behalf of the specified user" appears when attempting to send a migrated draft message.

16636

When "receiving unencrypted mail, encrypt before storing in your mailfile:" is selected in the Person document (in the Domino Directory), the decrypt button will not decrypt these encrypted messages.

16740

Migration Message Templates that contain Notes buttons are not available if an end user views the email in iNotes (web mail). This limitation applies to all button email templates in Notes Migrator. The email buttons can only be processed in the full Notes client.

54536

Table 29. Notes Migrator.nsf\Migration Profiles known limitations

Known limitation

Issue ID

Attempting to Set Migration Profile when there are no documents selected, does not produce an error.

16642

Advanced settings in a Migration Profile disappear after Profile Refresh, if the profile is deleted from the UI, and not the back-end. The Advance Settings are still stored in the back-end but are not displayed in the UI. To work around this issue, enter the missing values and resave the document.

16785

When modifying a Migration Profile’s Migration Options, from the initially selected "Message of type" option with the 'Mail', 'Task', 'Calendar' or 'Contacts' checkboxes selected, to the "All message types" option, without unchecking the selected checkboxes, the migration will migrate the items which were initially selected, not all message types. The checkboxes must be unchecked prior to changing to the 'All message types' option.

45859

Table 30. Notes Migrator.nsf\Post-Migration Actions known limitations

Known limitation

Issue ID

The "Set Reader Access for Users mailfile" does not properly report the success and failed to process correctly.

16599

The "Set Reader Access" post migration action incorrectly reports no success when agent completes.

16811

Migrated data does not get removed when using a date range. 

29156

The Set Full Access button agent reports a PowerShell error when the Full Access delegation permissions are run on accounts that have been mail box enabled in Office 365 if there are two or more accounts that have the same Display Name attribute.

Error: The operation couldn't be performed because 'Account Name' matches multiple entries.

40699

Table 31. Notes Migrator.nsf\Pre-Migration Actions known limitations

Known limitation

Issue ID

A Mail Rules message doesn't show the Message Log under the Notes Migrator user document which prevents the migration administrator from verifying the rules message was sent to the selected user(s).

16640

When using the combined notification template for end users in the Notes Migrator database, there is no way to prevent execution alerts from being displayed to the end users.

16666

Unable to provision a user if any of the shortnames in the Notes Migrator person document are in firstname.lastname format, regardless of whether the value is single or multiple.

16746

CAS Server matching returns an erroneous message when it can't find a match for a user due to non-matching SMTP addresses between the source and destination objects.

16763

Verify Mail DB (Audit Mail file) does not support clustered mail servers.

16772

The Name Translation Table CSVDE matching option does not support the matching of the German o ( ö ) character and Greek Alphabet characters (Έλληνες χρήστη1). To work around this issue, use one of the other match options.

16788

Mail-in DB's or Rooms & Resources cannot be provisioned to Office 365. This must be manually performed.

16802

Set Full Admin access fails when the users name contains a "$" character.

16805

Private folders are not included in the Pre-Migration Mail File Audit.

22747

Table 32. Notes Migrator.nsf\Progress Summary known limitations

Known limitation

Issue ID

Scheduled migrations produced error in Notes status bar.

16667

Table 33. Rooms and Resources known limitations

Known limitation

Issue ID

The database template specified in the Rooms & Resource settings must be present on the Target server specified in the same settings document, or an error will display that the database template cannot be found.

16508

Room and Resources don't display on a migrated calendar entry on the scheduling tab.

16606

Leading and trailing spaces are trimmed in values of Room Label, Resource Label, Online Label, Location Detail Indicator, and Room Resource Separator Settings Fields.

16661

Recurring meetings in the Domino rooms and resources application are stored as individual documents for each instance and are migrated as such. These require direct management in Outlook for changes post migration. Additionally, modifications to recurring meetings in rooms and resources will not migrate instance changes correctly. 

16715

Room and Resources Migration will not load the worker on the controller if no other workers are registered.  You will encounter the error: "C:\program files\binarytree\cmt for exchange\cmt_migrationworker.exe could not be started.  Please confirm that CMT is Installed correctly and the settings doc reflects the correct install path."

28448

Room import fails when the room has quotes in the name.

38359

 

 

Table 34. To-Do Migration known limitations

Known limitation

Issue ID

Completing a migrated Task will send a notification to the SendTo user when the Task is created using the "Copy into new..." button in Lotus Notes. No notification should be sent.

16598

Text bullets appear as asterisks ("*") post migration when viewed from Outlook Web Access (only).

16613

Embedded graphics in Lotus Notes Tasks are migrated as attachments.

16619

Lotus Notes Tasks created by a delegate appear in Outlook with the delegate as the Owner, instead of 'Delegate (Sent on behalf of mail file owner)'.

16621

Migrated Tasks containing Notes links have an extraneous .gif attachment for each link.

16622

Read/Unread status is not maintained on migrated Tasks when using Outlook Web Access.

16623

Unaccepted To Do notices in Lotus Notes do not migrate to Exchange.

16632

Repeating tasks (to-do's) do not migrate to the correct dates.

16693

Assigned Tasks (To-Do's) are migrated as Task calendar events, not as Task Requests. The migrated Task will only be displayed in the To-Do's not in the Inbox.

16697

Yearly and Custom recurring Tasks become Weekly Tasks after migration.

16702

When migrated assigned tasks are completed the person who created the task and assigned it to someone else does not get the notification that it was completed. 

16706

The Task Owner name displays the ExchangeLegacyDN rather than the Display Name. This is a cosmetic issue only and there is no loss in functionality.

46929

Task assignees (Required, Optional, FYI) are not migrated to Outlook.

46986

System requirements

Refer to the Binary Tree Migrator for Notes 20.12 Requirements (http://support.quest.com/technical-documents/binary-tree-migrator-for-notes/20.12/requirements) for system requirements.

Product licensing

A valid license is required for Binary Tree Migrator for Notes.

To obtain licenses, see information on this page https://www.quest.com/company/contact-us.aspx or contact the sales team at sales@quest.com

Upgrade and installation instructions

Refer to the Binary Tree Migrator for Notes 20.12 Installation and Configuration Guide (http://support.quest.com/technical-documents/binary-tree-migrator-for-notes/20.12/installation-and-configuration-guide) for installation instructions.

More resources

Additional information is available from the following:

Globalization

This section contains information about installing and operating this product in non-English configurations, such as those needed by customers outside of North America. This section does not replace the materials about supported platforms and configurations found elsewhere in the product documentation.

 

This release is Unicode-enabled and supports any character set. In this release, all product components should be configured to use the same or compatible character encodings and should be installed to use the same locale and regional options. This release is targeted to support operations in the following regions: North America, Western Europe and Latin America, Central and Eastern Europe, Far-East Asia, Japan. It supports bidirectional writing (Arabic and Hebrew). The release supports Complex Script (Central Asia – India, Thailand).

About us

Quest creates software solutions that make the benefits of new technology real in an increasingly complex IT landscape. From database and systems management, to Active Directory and Office 365 management, and cyber security resilience, Quest helps customers solve their next IT challenge now. Around the globe, more than 130,000 companies and 95% of the Fortune 500 count on Quest to deliver proactive management and monitoring for the next enterprise initiative, find the next solution for complex Microsoft challenges and stay ahead of the next threat. Quest Software. Where next meets now. For more information, visit www.quest.com.

Technical support resources

Technical support is available to Quest customers with a valid maintenance contract and customers who have trial versions. You can access the Quest Support Portal at https://support.quest.com.

The Support Portal provides self-help tools you can use to solve problems quickly and independently, 24 hours a day, 365 days a year. The Support Portal enables you to:

  • Submit and manage a Service Request

  • View Knowledge Base articles

  • Sign up for product notifications

  • Download software and technical documentation

  • View how-to-videos

  • Engage in community discussions

  • Chat with support engineers online

  • View services to assist you with your product.

© 2021 Quest Software Inc.
ALL RIGHTS RESERVED.

This guide contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchaser’s personal use without the written permission of Quest Software Inc.

The information in this document is provided in connection with Quest Software products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest Software products. EXCEPT AS SET FORTH IN THE TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST SOFTWARE ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST SOFTWARE BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST SOFTWARE HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest Software makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. Quest Software does not make any commitment to update the information contained in this document.

If you have any questions regarding your potential use of this material, contact:

Quest Software Inc.

Attn: LEGAL Dept

4 Polaris Way

Aliso Viejo, CA 92656

Refer to our Web site (https://www.quest.com) for regional and international office information.

Patents

Quest Software is proud of our advanced technology.  Patents and pending patents may apply to this product. For the most current information about applicable patents for this product, please visit our website at https://www.quest.com/legal.

Trademarks

Quest, the Quest logo, and Join the Innovation are trademarks and registered trademarks of Quest Software Inc. For a complete list of Quest marks, visit https://www.quest.com/legal/trademark-information.aspx.  All other trademarks and registered trademarks are property of their respective owners.

Legend

CAUTION: A CAUTION icon indicates potential damage to hardware or loss of data if instructions are not followed.

 

IMPORTANT, NOTE, TIP, MOBILE, or VIDEO: An information icon indicates supporting information.

Self Service Tools
Knowledge Base
Notifications & Alerts
Product Support
Software Downloads
Technical Documentation
User Forums
Video Tutorials
RSS Feed
Contact Us
Licensing Assistance
Technical Support
View All
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating