CMT for Exchange 3.5.1. Known Limitations

CMT for Exchange 3.5.1 Known Limitations August 2015

Table of Contents Known Limitations 3.5... 3 AWD\Configuration... 3 AWD\Migration Workstation... 3 Calendar Migration... 3 Calendar Migration\All Day Events... 4 Calendar Migration\Anniversary... 4 Calendar Migration\Delegation... 5 Calendar Migration\Meetings... 5 Calendar Migration\Reminders... 7 CMTforExchange.nsf... 7 CMTforExchange.nsf\Configuration Settings... 7 CMTforExchange.nsf\Message Templates... 7 CMTforExchange.nsf\Migration Profiles... 7 CMTforExchange.nsf\Post-Migration Actions... 8 CMTforExchange.nsf\Pre-Migration Actions... 8 CMTforExchange.nsf\Progress Summary... 9 Contact Migration... 9 Data Validation... 10 Discussion or Document DB Migration... 10 Documentation... 10 Encrypted Items... 10 HeartBeat and Monitor... 10 Help Button...11 Installation...11 Logging...11 Logging\Viewer...11 Mail Migration...11 Mail Migration\Attachments... 13 Mail Migration\Delivery Options... 13 Mail Migration\Header Fields... 13 Mail Migration\Rich Text... 13 Mail Migration\Views/Folders... 13 Mail-In db Migration... 14 Match Users... 14 Name Translation... 14 Rooms and Resources... 14 SQL... 15 To-Do Migration... 15 About Binary Tree... 17 CMT FOR EXCHANGE 3.5.1 KNOWN LIMITATIONS 2

Known Limitations 3.5.1 AWD\Configuration The Store Password feature does not validate the password, and will allow you store an incorrect password without prompting for a valid password when "Get Server List" is clicked. (556) When a comma is used as a decimal separator in Windows, it can causes problems during the migration. (576) Saving default settings in Windows GUI causes Root element is missing error and forces reinstall. (738) AWD\Migration Workstation If more than one instance of Lotus Notes or CMTE is installed on a migration workstation, you will be prompted for the Notes password for each migration. (704) When installing migration workstation with SQL, you must connect using SQL authentication, or you will receive a login failed error message when connecting to the SQL server. (747) The Lotus Notes Designer client must be installed in the migration workstation for doc links to migrate properly. (750) Calendar Migration "Description:" appears in the body of migrated calendar documents when viewed in Outlook Web Access. (598) Attachments in migrated calendar entries may not appear in the same position as in Notes when viewed from Outlook. (611) 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. (644) Calendar entries with a repeat pattern of Every Other Year are not natively supported in Exchange, and are migrated as Yearly entries. (649) 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. (650) Subjects of Repeat Calendar entries that have carriage returns will not be displayed properly in Outlook and OWA 2007. (654) 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. (661 & 662) Invitees added 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. (663) CMT FOR EXCHANGE 3.5.1 KNOWN LIMITATIONS 3

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). (669) Migrated Notices pending approval appear as simple mail when opened in OWA and cannot be acted on. (675) 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. (701) If a migrated calendar item and a regular mail item are both selected and moved to a folder, a new message window is opened instead of moving the messages to the folder. (726) 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. (740) A migration crash can occur with an excessive amount of data (over 50 entries) in the Location and Rooms fields. (744) Enterprise Vault links in Domino calendar items are missing after migration. (1301) Meetings with the following nonstandard time zone "Z=-8$DO=0$ZX=190$ZN=Asia/Shanghai", will not migrate to the correct time. (1568) The "Calendar Age Limit" filter causes all calendar items be added to message history whether they are migrated or not. (3723) Calendar Migration\All Day Events The 'Mark Private' option in a recurring all day event is not maintained on each occurrence of the event when viewing from OWA. The Mark Private option is properly maintained when open the series in OWA or when using the Outlook client. (588) Attachments in recurring calendar events will not appear in OWA if all instances of the meeting were rescheduled prior to migration. (616) Calendar Migration\Anniversary Repeating anniversaries do not display on the correct date when viewed from Outlook Web Access. (573) The gray information banner, at the top on a migrated recurring anniversary, displays the recurrence pattern as daily instead of annually, however is appears correctly on the calendar and series documents. (575) The Play Sound reminder option in Lotus Notes Calendar items does not migrate to Outlook. (586) Lotus Notes Anniversaries with the 'Pencil In' option selected are migrated to Outlook with a Show As: Free, instead of Tentative. (594) The Mark Private setting on nonrecurring Anniversaries (only) is not maintained after migration. (647) Reminder sound notification is not maintained on a non-repeating Anniversary after migration. (648) Nonrecurring Anniversaries are not visible via OWA. (651) CMT FOR EXCHANGE 3.5.1 KNOWN LIMITATIONS 4

Nonrecurring anniversaries are not removed by the removal job. (676) 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. (703) Location and Category fields are not migrated in Anniversaries. (739) Calendar Migration\Delegation 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. (3613) If an invitee delegates one or more instances of a repeating meeting to someone else and that person does not accept the delegated invitation prior to migration, it will appear on their calendar as if it had been accepted post migration. (3614) Calendar Migration\Meetings A migrated recurring meeting cannot be cancelled by an Outlook 2007 client. This functions properly if cancelling from Outlook 2010. (69) Updating the category field of a Lotus Notes meeting is not supported. Outlook does not support category exceptions. (574) Embedded images in calendar entries appear as attachments in migrated calendar documents. (581) The chairperson of an unaccepted meeting appears in the Required field after migration. (596) Address translation does not occur for calendar documents migrated to a PST file. (599) When removing the One and Only Attendee from All occurrences of a Meeting, the attendee remains after migration. (643) In the Domino 6.5 and Exchange 2003 environment, when the Chair of a meeting migrates and then reschedules a meeting that was already accepted by Notes users, the reschedules to Notes users come across as new invitations. (665) Responses from attendees added after the original invite is issued do not update the chair's calendar tracking status. (682) 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. (683) Meetings with No End Date, originating outside of Notes, do not migrate properly when option "Process no end date meetings with ICAL information" is set to NO. No End Dates in Notes are created as a 530 occurrence custom list meeting. There is no repeat pattern information in the Notes document. The Original ICAL field does contain repeat information, but when the option is set to NOT use ICAL we have no repeat pattern. (684) The recurrence summary line displayed in Outlook/OWA will display incorrect series start/end/repeat information for meetings created in Notes as a Custom List Meeting. The actual calendar entries/occurrences display correctly. (685) The description that has been updated on a recurring meeting with pattern that moves or deletes on the weekends will not be updated post migration. (686) CMT FOR EXCHANGE 3.5.1 KNOWN LIMITATIONS 5

A Notes user who accepted a meeting request for a repeat meeting (reoccurring Daily or every <number> of days with no end date) that was created in Outlook, and then migrated to Exchange, will not be able to view the accepted meeting in OWA. (699) Changes to migrated meetings with Rooms and/or Resources are not updated in the Domino Resource Reservations database. (715) 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. (716) When migrating Custom List meetings or No End Date meetings, the calendar child document was being opened in preparation for looking for ICAL repeat information even when the option to Use ICAL for Repeat Info was disabled. The unneeded opening and closing of the child docs causes a slowdown, especially when using a remove Domino server. (746) All occurrence of a recurring meeting aren't visible in OWA when rescheduling future & previous instances. (756) Comments added during a reschedule to a single occurrence meeting will not appear in Outlook if the original meeting was not accepted prior to migration. (770) 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. (894) Meetings and Appointments in Notes that have the choice "Mark Available" checked are listed as "Tentative, instead of "Free, when migrated to Exchange. (1272) 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. (1387) A table located in the body of a meeting is not migrated properly. (1425) Unknown time zones display the incorrect time even though the meeting is on the calendar at the proper date and time. (2039) 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.(3014) Monthly meetings scheduled for more than one day or date a month are not supported by Exchange and are not migrated. An error log entry is generated for these calendar items and migration continues with the next item. (3081) The word "Tentatively" is missing from the banner on a migrated tentatively accepted meeting. (3657) CMTE does not recognize the "America/Chicago" time zone label set by the Lotus Notes client on a Mac resulting in wrong times for repeating meetings. (4172) If the entire series of a repeat meeting was rescheduled prior to migration, changes post migration will generate an NDR. (4743) CMT FOR EXCHANGE 3.5.1 KNOWN LIMITATIONS 6

Calendar Migration\Reminders Updates to the description of a repeating Reminder are not present after migration. (595) 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. (724) Because there is no equivalent in Outlook, Reminders migrate as appointments with the free time blocked out. (1705) CMTforExchange.nsf 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". (584) The Migration Users Set Profile view shows hidden documents. (4545) CMTforExchange.nsf\Configuration Settings 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. (59) Changing a migration to a High Priority job does not queue the user on the next available workstation. (707) There are two Migration Status Codes sections in the CMT for Exchange database. The Migration Status Codes section on the Required/Additional tab is the functional section. (1989) CMTforExchange.nsf\Message Templates 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. (614) When "receiving unencrypted mail, encrypt before storing in your mailfile:" is selected in the Person document (in the Domino Directory), the decrypt button button will not dedcrypt these encrypted messages. Please refer to this Knowledge base article at http://www.binarytree.com/special-pages/iframes/cmtn-kb.aspx for a workaround. (879) The contact count shown in the pop up message when the user clicks the sync contact button, counts the same entries multiple times if the contact is in multiple categories, giving the user the impression that they have more contacts in your mail file then they actually do. (2679) After running the Fix Folders option, an ECL Alert may be displayed when navigating into any folder. (4259) CMTforExchange.nsf\Migration Profiles Attempting to Set Migration Profile when there are no documents selected, does not produce an error. (636) Selecting "Use Outlook 97-2002 format" when migrating to PST files uses the Outlook 2003-2007 format. (698) CMT FOR EXCHANGE 3.5.1 KNOWN LIMITATIONS 7

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. (2821) CMTforExchange.nsf\Post-Migration Actions The "Set Reader Access for Users mailfile" does not properly report the success and failed to process correctly. (55) The "Set Reader Access for User Mailfile" agent does not consistently uncheck the 'Write Public Documents' box. This will allow users to create documents in the Domino mail file after migration. (1353) The "Set Reader Access" post migration action incorrectly reports no success when agent completes. (4542) CMTforExchange.nsf\Pre-Migration Actions When auditing a mail database, and the mail file no longer exists, or the file is renamed, CMTe 3.3.0.1 displays "Object Variable Not Set" as the reason for audit failure. (434) A Mail Rules message doesn't show the Message Log under the CMTe user document which prevents the migration administrator from verifying the rules message was sent to the selected user(s). (619) When using the combined notification template for end users in the CMT for Exchange database, there is no way to prevent execution alerts from being displayed to the end users. (666) Unable to provision a user if any of the shortnames in the CMT for Exchange person document are in firstname.lastname format, regardless of whether the value is single or multiple. (949) 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. (1375) Verify Mail DB (Audit Mail file) does not support clustered mail servers. (1816) 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. (2920) Matching users by CSVDE is not supported for Office 365. (2927) The Migration Transitional Calendar Workflow does not reach out to the chairperson to return chair data when it is run against an invitee as expected. (3199) The contact fix status and folder fix status columns are empty after running the agents. (3692) Mail-in DB's or Rooms & Resources cannot be provisioned to Office 365. This must be manually performed. (3712) Set Full Admin access fails when the users name contains a "$" character. (3842) Users do not appear in the Office365 - Provisioning - Enable Mailboxes view after the workflow moves them from the notification phase to the matching phase because the ExHomeMDB field in empty. (4101) CMT FOR EXCHANGE 3.5.1 KNOWN LIMITATIONS 8

CMTforExchange.nsf\Progress Summary Scheduled migrations produced error in Notes status bar. (667) Contact Migration Migration of personal NAB nested groups causes delivery failure for Nested Groups. (514) Migrating Personal Groups with internal Notes users creates delivery failures due to lack of "EX" value in 'Type' field. (559) The Location field values in Lotus Notes contacts are not migrated to Outlook. (570) 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. (603) Embedded graphics in Migrated Contacts are not visible in OWA. (615) The Home Address is migrated into both the Home and Business Address of Contacts. (641) Comments and embedded graphics are not migrated to Contacts in Exchange 2007, only. (642) 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. (645) The entire Business Address is migrated to the City field in a Contact. (653) If the member of a Personal Mail Group was copied from the Domino Directory (into the Personal Address Book), the members have invalid smtp SMTP addresses with a Domain of "@unk domain" after migration. (658) The Country Codes of Personal Addresses are not migrated in Contacts. (660) Double Space between the first name and last name in migrated contacts. (668) Embedded files in contacts do not migrate. (712) The IM Address in contacts does not migrate to Exchange. (948) The Fix Contacts and Group Members agent in the CMT for Exchange database is not removing unresolved contacts. The unresolved member produces delivery failures when emails are sent to this group in Exchange. (1012) 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. (1046) 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. (1265) When migrated to Exchange, the friendly email address format is incorrect and results in an email delivery failure when used. (1376) Personal Contact non-primary email fields with a canonical format do not get translated to an SMTP address.(2545) The Blog Site field in a Notes contact does not migrate because there is no corresponding field in Outlook. (2626) CMT FOR EXCHANGE 3.5.1 KNOWN LIMITATIONS 9

The Children field in a Notes contact does not migrate to the Children field in an Exchange contact. (3002) The Contact Migration button will prompt to replicate when the user's mail file contains contact documents, and no contact documents in the user NAB. This message can be ignored. (4153) Data Validation When an Office 365 validation check is performed and the folder destinations do not exists, an OLE: Automation object error occurs. (4799) Discussion or Document DB Migration Lotus Notes stored forms and the content within the stored form may not be rendered properly after migration. (3329) Documentation Comprehensive User Guide - Staging Replicas Section 13 does not match the application functionality. (550) The information in the Getting Started tab is out of date. (775) Encrypted Items CMTe does not decrypt all calendar entities and notices. (474) 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. (1373) HeartBeat and Monitor The Heartbeat Monitor Alerts do not send emails to the Administrator. (991) Clicking on browser headers on the Heartbeat Monitor page cause the browser to freeze. When this occurs, the browser task needs to be ended via the task manager.(992) The list of saved alerts in the CMT Heartbeat Monitor application does not include a column for the value selected from the Define new alert for drop-down list when an alert is defined. (1254) If you deselect the Heartbeat Monitor during the installation on the Migration Control Center (MCC) and subsequently run a migration from the MCC, you will see the following erroneous error: Error initializing HEARTBEAT: Code = 80070002 Code meaning = The system cannot find the file specified. Source = BinaryTree.ApplicationMetrics Description = Could not load file or assembly 'System.Core, Version=3.5.0.0, Culture=neutral, CMT FOR EXCHANGE 3.5.1 KNOWN LIMITATIONS 10

(1693) Help Button Some of the links in the Help document do not open to the intended location. (635) When enabling the Resource Forest setting in the UI, the Help information displayed for the Linked Master DC and Linked Master Domain are incorrect. Please refer to the Comprehensive User Guide for the correct information. (1982) The Help Icon for the MAPI Custom Settings on the Settings document Other Settings tab contains the help for the heartbeat interval field. (1990) Installation When installing CMT for Exchange, the Computer Browser service must be started in order for the IIS Application Pool Identity user name browser to work. (61) Although.NET 2.0 is a requirement for CMT for Exchange, it is optional during the installation process. Selecting No when prompted to install.net 2.0 results in a failure to initialize error when launching CMT for Exchange. (582) CMT for Exchange cannot be installed when the operating system is installed on any drive letter other than "C:\" and a migration will not start if the product is not installed to "C:\". (748) The Back button does not work on the 'Choose Destination Location' page of the Installer. (753) The installation page to create the BTCodex Custodian does not correctly display the space required or available on the selected drive. (776) The installation wizard for CMT for Exchange Monitor does not display the correct point release. (789) Logging When installing CMTe on a 32 bit machine, there is a popup stating MSSoapv3SDKx64 needs to be installed. It appears to install it and then continue with the install. (1106) If there is a failure reading the Modified Notes Table, CMTe will now return a critical failure and cancel the migration. Previously it would return a successful migration with 0 documents processed. (3358) CMTE does not return the total migrated successfully count in the CMT.exe (backend). The UI should be used to view all statistics. (3884) Logging\Viewer Migrating with the log viewer open it can significantly decrease migration performance. (677) Mail Migration 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. (578) CMT FOR EXCHANGE 3.5.1 KNOWN LIMITATIONS 11

Font size properties within a migrated message are not maintained if the font size in Lotus Notes is not the default size. (579) The color of text bullets is black regardless of the color of the text and bullets in the source document. (592) 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. (597) The recipient of a message send to one's self appears in the CC: field instead of the To: field of migrated messages. (601) 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. (610) The Follow Flag reminder time is 12 hours ahead after migration when viewed from Outlook. It is displayed properly in OWA. (640) An embedded graphic in a migrated mail item is displayed incorrectly when opening minisize window in OWA. (652) If the Outlook client language is not English, end-user migrations to a PST will not work (please contact support for a workaround). (680) To migrate from a Notes.nsf archive to Exchange 2010 Archive server, must first migrate to a.pst and then import into the Exchange 2010 Archive. (689) 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. (723) Archive migration currently only supports 5 archives per user. (728) 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. (751) The "Sent" field in a previewed Draft in Outlook displays the Migration Date instead of "None". (755) Lotus Notes Journal Entries migrate as a Memo in Outlook, instead of a sticky note. (898) Migrated draft messages are not editable. Unable to resume editing or send a migrated draft message. (922) Unable to move a migrated calendar item to a folder in Outlook. Moving this item creates a mail message addressed to the meeting Chair. (923) The following error during migration causes mail messages to not appear in destination mailbox:! Error: Failed to save changes in MimeToMapi 0x80040305 (1377) The bodies of messages containing winmail.dat files are not migrated, because they cannot be processed with MIME. (2036) Multiple PDF attachments in a single mail 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). (2858) Reservation Doclinks sent from the Rooms and Resources database migrate as database links. (3228) "Distribution Group Migration" views are displayed in the Navigator when configured for Office 365, but this functionality is not supported for migrations to Office 365. (3493) CMT FOR EXCHANGE 3.5.1 KNOWN LIMITATIONS 12

Mail Migration\Attachments In OWA there is a redundant attachment in the preview mail when mail contains an icon. (702) 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. (706) Migrations of attachments larger than 100 Mb have not been validated. (713) Attachments without extensions in Mail and Tasks are migrated to Exchange as.dat files. (722) When a user in Lotus Notes receives an S/MIME signed message from a user in Exchange and is then migrated, the message is migrated without attachments except the smime.p7s file named "ATTxxxx". (1220) 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. (1371) Mail Migration\Delivery Options Mail "Return Receipt:" loses all information after migrating to Exchange. (700) The advanced delivery option in Lotus Notes 'Replies to this memo should be addressed to' does not migrate to Exchange. (741) Mail Migration\Header Fields Migrated draft emails do not display the send to, cc and bcc fields in Outlook. (705) Unresolved recipients in a Lotus Notes draft memo do not migrate to Exchange. (749) Mail Migration\Rich Text Bulleted lists with checkmarks, circles and squares are not migrated correctly and appear as filled in circles in Outlook. (711) Form objects, such as buttons and hotspots with code, will not migrate. (719) Hotlinks in tasks are not migrated. (720) Certain messages that contain Rich Text can cause a crash due to the Lotus Notes CD to RTF conversion that CMT Universal utilizes. (760) Mail Migration\Views/Folders Any folder name containing the word "Rules" (case sensitive) is not migrated to Exchange, however, the documents will be migrated to the Unfiled folder. (638) Error creating folder "Drafts" when migrating to Outlook when the folders are in German. (708) Moving migrated items that contain a migrated meeting "acceptance" response to a folder in Outlook, Outlook creates a new message with the items now part of the e-mail body. (745) The Migration profile choice to "skip folder" will not work if the folder has a leading or trailing space. (2256) CMT FOR EXCHANGE 3.5.1 KNOWN LIMITATIONS 13

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. (2871) Mail-In db Migration Discussion and Mail-in databases can only be migrated to PST files, not an Exchange server. (618) The Verify Database process does not report on mail-in databases. This will be fixed in a future release. (731) 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 ":". (773) Domino Database names containing special characters, such as "&", cause a migration status of "Migration terminated abnormally" even though the migration was successful. (1307) Match Users The 'Matches the selected users on the Exchange CAS server' setting does not function properly. You must use the GAL or LDAP to match users prior to migrations. (62) 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. (73) When migrating to a PST the default file name of the PST is shortname-servername-mailfilenameandlocation instead of just the shortname (for resolved users). (585) Users without a shortname get stuck in "pending" state. (743) Unable to match users to Office 365 Wave 15 tenant via the GAL. (1535) Users that have SMTP addresses starting with 'con.', for example 'con.test@mydomain.com' cause PowerShell matching to fail. (3480) Name Translation The Upload Name Translation.CSV file option must be run from the Migration Control Center and is applicable only when using Classic name translation and MS Access as the backend. (687) 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. (2788) Mail in Database Common name translation entry disappears or is missing from the Translation Table view when an SMTP address is added as the second entry to the fullname field in the translation record. (4067) Rooms and Resources 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. (306) Room & Resource FORM doesn't show the "Shortname" unless "Enable BPOS Features" is set. (509) CMT FOR EXCHANGE 3.5.1 KNOWN LIMITATIONS 14

Room and Resources don't display on a migrated calendar entry on the scheduling tab. (571) If the Notes field "OrgRepeat" on the Rooms documents has a value, it will cause the Room to be migrated as a repeating event, instead of a mailbox. (639) Leading and trailing spaces are trimmed in values of Room Label, Resource Label, Online Label, Location Detail Indicator, and Room Resource Separator Settings Fields. (659) Modified reoccurring meetings in rooms and resources not migrating correctly. (742) The "Setting document does not contain path to CMT Users.xml" error message is received when choosing additional actions/delete selected db(s) in the advanced rooms and resource view. (1065) The meeting organizer is incorrect after the migration of a room calendar. The resource owner is listed as the meeting organizer instead of the actual meeting chair. (1140) The "Clear Selected Db(s) and repopulate" agent on the Rooms & Resources Advanced View only runs on one document out of the selected collection. (2360) SQL The BT_JobStates table is not updated with the new job status when SQL components and the BTCodex Custodian is installed. (2025) To-Do Migration 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. (560) Text bullets appear as asterisks ("*") post migration when viewed from Outlook Web Access (only). (580) Embedded graphics in Lotus Notes Tasks are migrated as attachments. (587) 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)'. (589) Migrated Tasks containing Notes links have an extraneous.gif attachment for each link. (590) Read/Unread status is not maintained on migrated Tasks when using Outlook Web Access. (591) Unaccepted To Do notices in Lotus Notes do not migrate to Exchange. (602) Repeating tasks (to-do's) do not migrate to the correct dates. (709) 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. (714) Yearly and Custom recurring Tasks become Weekly Tasks after migration. (721) 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. (725) A migrated task that had been created by "copying into new todo" from a received mail item incorrectly tries to send an email to the original addressee of the email that the task was created from when the task is completed. (727) CMT FOR EXCHANGE 3.5.1 KNOWN LIMITATIONS 15

Some bullet types do not maintain the same format in migrated tasks. (1244) CMT FOR EXCHANGE 3.5.1 KNOWN LIMITATIONS 16

About Binary Tree Binary Tree is a singularly focused global provider of migration software and solutions for Lotus Notes, Microsoft Exchange, Active Directory, and Windows Server environments. Since 1993, Binary Tree has enabled more than 6,000 customers to migrate more than 30 million email users, and facilitated some of the most complex migrations on the planet. Its software solutions are available for migrating from Exchange 2003/2007/2010/2013 and Lotus Notes to onpremises and online versions of Microsoft Exchange, as well as migrations of Active Directory and Windows Server environments. Binary Tree is a Microsoft Gold Partner, an IBM Advanced Business Partner, and is one of Microsoft s preferred vendors for migrating to Microsoft Office 365. The Company is headquartered outside of New York City with offices in London, Paris, Stockholm and Sydney. For more information, visit us at www.binarytree.com. Binary Tree Social Media Resources Copyright 2015, Binary Tree, Inc. All rights reserved. Binary Tree, the Binary Tree logo, the SMART Migration graphics, and any references to SMART Migration and Binary Tree s soft ware products, are trademarks of Binary Tree, Inc. All other trademarks are the trademarks or registered trademarks of their respective rights holders. CMT FOR EXCHANGE 3.5.1 KNOWN LIMITATIONS 17