Quest® On Demand Migration
February 02, 2023
Quest® On Demand Migration is a Microsoft 365 tenant-to-tenant migration service that allows you to simply and securely migrate Microsoft 365 information from Exchange, OneDrive, SharePoint and Teams. It is a part of the Quest® On Demand cloud-based platform solution.
These release notes provide information about the latest Quest® On Demand Migration release.
The following is a list of enhancements implemented in On Demand Migration.
|Enable Automapping for shared mailboxes is a new option in the Migration Settings step of the New Mail Migration Task wizard. Auto-mapping is an Exchange & Exchange Online feature. When this option is enabled, the delegate's Outlook client automatically opens mailboxes in a persistent state with Full Access permissions.
The following is a list of issues, including those attributed to third-party products, known to exist at the time of release.
General known issues
|If the Skip if the target file is the same version or newer option is selected, files that were previously migrated and for which additional sharing permissions have been added may not appear in the Shared With Me panel of users who have been granted this additional sharing permission. Workaround: Remove and re-grant permissions directly to previously migrated files in the target.
|Statistics related to permissions can be incorrect in some specific cases.
|Deletion of target object after the migration may not be reported.
|In case the created Mailbox Switch task is edited and the mail forwarding direction is changed, all selected notification messages will be readdressed, but the wizard may not display notification settings correctly. Workaround: Select Run later and finish the task to re-open it. After the task is re-opened you can see the actual notification settings. Now you can schedule the task as necessary.
|If you remove a tenant that is currently used in migration projects from On Demand, the affected projects can still be opened without any alerts or notifications. However, all project tasks will fail.
|Mail Migration Task Wizard cannot be finished if you add and then clear the value in Exclude mail before and Exclude mail after fields. Workaround: Close the wizard and create a task anew.
|Double-clicking Finish button in wizards may result in creating several duplicate tasks.
|All accounts must be matched or migrated before migrating the groups they belong to, or with the same task that migrate groups. Otherwise, the newly migrated accounts will not be added to the target groups. Workaround: Re-migrate the affected groups after all their members are migrated.
|If you migrate a mail-enabled group with non mail-enabled members, some of those users might not be added to the target group. The following error is displayed for each affected user: "Group membership migration completed with errors. Couldn't find object [User GUID]. Please make sure that it was spelled correctly or specify a different object." Workaround: Re-migrate the affected groups.
|Deleting or moving a file in the OneDrive storage that is currently being migrated may result in aborting the storage transfer with Content transfer failed error. Other storages from the migration task are not affected. Workaround: Re-migrate the failed storage.
|A search query entered by user to filter content may be lost in case the user switches tab.
|Migration of Microsoft Office 365 groups and security groups with dynamic membership is not supported.
|Migration fails if internal account is matched with external account and the following message is reported: Property usageLocation is invalid / Insufficient privileges to complete the operation
|Migration of security group to distribution list or to mail-enabled security group fails (this migration cannot be supported) and the following message is reported: Unable to update the specified properties for objects that have originated within an external service
|Migration of Office 365 group to distribution list or to mail-enabled security group fails (this migration cannot be supported) and the following message is reported: REST API is not yet supported for this mailbox.
After the migration, the calendar invites with Teams links may need to be updated.
|ODM -788 |
|In case of re-migration, On Demand Migration re-migrates mail and calendar items that have changed in the source mailbox to the target mailbox. Also, calendar items that have been removed from the source mailbox will be removed from the target mailbox. Re-migration of other types of items that have been modified or deleted in the source mailbox is not supported.
Due to Microsoft's Exchange Online limits on messages sent from the tenant that are calculated according to purchased Exchange Online licenses, some of the sent messages exceeding this limit will not be delivered within 24 hours and will wait in the queue to be send next day. If waiting time will be longer than 24 hours, the sender will receive an NDR.
Workaround: To increase bandwidth you need to purchase more Exchange Online licenses
Account migration known issues
|Resource Processing is not available when GCC High tenants are used. Resource Processing is only available with commercial tenants.
|Source UPN and Primary SMTP will be used after migration for existing target hybrid accounts.
|In case of re-migration of hybrid account the Migration task state may appear to be completed before the actual completion.
|Source user mailbox is required to be kept to ensure receiving of mail messages addressed to this mailbox after migration. To remove these mailboxes you can manually configure forwarding in on-premises environment for all affected accounts after target mailboxes are provisioned.
|Hybrid accounts has New status even in case these accounts are in progress.
|Matching task may hang with In progress state in case on-premises connection credentials are not configured. No events are reported.
|Matching task may hang with In progress state in case of any issues related to connection problem of integration service, e.g., secret is not installed properly or unavailable.
|In case matched target hybrid account is removed intentionally, but source account is selected for the migration task, the target object will be provisioned and no event is reported.
|In case of any target conflicts related to existing objects in on-premises part processed by Quest Migration Manager, events generated by Quest Migration Manager will not appear in Events.
|Migration Task progress may be reported incorrectly. Refer to task details for actual information.
|Mail flow is not currently displayed for migrated objects.
|Mapping from file is not currently supported
Mail addressed to target Room/Equipment/shared mailbox will not be redirected to source. Reason: forwarding from target to source after account migration for Room / Equipment / shared mailbox is not set.
|In case object is removed in source, during re-migration this object cannot be included in migration scope, but object status remains unchanged. In task details this object status is New.
|Migration tasks may hang with In progress state in case of any issues related to integration with Quest Migration Manager. No events are reported.
Resource processing To allow target users access source SharePoint, linked guest users were created in the source and On Demand Migration immediately attempts to grant these user accounts necessary direct permissions. It can take time for guest accounts to replicate to SharePoint, which can result in a "User not found" error message for a guest account that has not yet been replicated during granting permissions.
Workaround: Retry the SharePoint processing later.
Mailbox migration known issues
|A Meeting link migration task does not preserve the "time zone" settings for the calendar items. The meeting start time and the end time properties will be converted to UTC.
OneDrive migration known issues
|If Migrate Sharing Link Permissions option is selected, some link sharing permissions will not migrate properly if the user has shared this file or folder with more than 30 users. Only 30 users will have permissions from the Sharing Links, while others will not be processed due to a Microsoft limitation.
Public folder migration known issues
|There is currently no way to stop running tasks.
|After migration to the target, the folder name remains unchanged, even the original source folder has been renamed. On Demand Migration does not support renaming folders.
SharePoint migration known issues
|When using collections with On Demand Migration for SharePoint, if a site is added to a collection after running a Discover SharePoint Contents task for the site, the child objects will not be added to the collection. Re-run the Discover SharePoint Contents task for the site to add the child objects to the collection.
|When using collections with On Demand Migration for SharePoint, if a SharePoint object is added to a collection without its parent or child elements, the SHOW PARENT and SHOW CONTENTS buttons may be active but will link to a blank a filtered list because the child or parent is not included in the collection.
|When using collections with On Demand Migration for SharePoint, note that the Remove from Collection and Remove Collection functions are not yet available.
|Files and List Items cannot be migrated if same entities exist in target recycle bin.
|The following events may be reported while migrating some folders from Document Libraries connected to Microsoft Teams: A file or folder with the name ... already exists... and Failed to lookup file info of object... The migration proceeds as expected.
|After migration the system account is specified as an author of migrated folder instead of the source folder author.
|Web address of this view in List View settings cannot be updated due to SharePoint limitations.
|Migrated discussion board replies are not tagged as "Best reply" on target.
|Custom content type assigned to documents is not migrated. All documents will have the default content type on target.
|Discussion List created by the site Community feature is renamed to Community Discussion in Team site (STS#3 template.)
|Files and list items are not migrated to subsites with the following characters in the URL: <, >, &, ", '
|Site collection status is not updated if the migration task includes more than one site collection.
The search field shows a limited number of characters. Only the first 22 characters are visible for the long search queries.
|Hub settings for sites located in non-central regions of a multi-geo tenant cannot be migrated. The hub and spoke relationship for sites in non-central regions must be built manually after the site migrations are complete.
Teams migration known issues
If the external sharing settings of the target tenant is more restrictive than the settings in the source tenant, then Office 365 groups and SharePoint items cannot be migrated tot he target tenant.
Workaround: Ensure that sharing settings in the target tenant is the same or less restrictive than the source tenant. You must create a fresh task to migrate the items.
|When two or more users are participants in a chat, the chat migration task event is not linked to any particular user.
|On Demand cannot migrate the file if the SharePoint admin center (under Settings | Site Creation) has been used to change the default URL.
|Meeting links in Teams calendar items of migrated teams don't work because the links still point to source tenant.
|Resource processingIf EDU team group has been migrated in the Account Migration project first and then this EDU team is provisioned in the Teams Migration project, the error "Request failed with BadRequest status code (Bad Request)" is reported.
Workaround: Delete the EDU team group created by Account Migration, then perform discovery and provision with Teams Migration project.
Links to attachments in chats that are migrated and archived cannot be opened from the Conversation History in the Teams client if you left-click the link.
Workaround: Right-click the attachment and select Open Link in New Tab or Open Link in New Window from the context menu.
|When teams are provisioned with the option to merge with an existing team in the target tenant and a new channel is created with the original name plus suffix, the SharePoint folder for the new channel retains the original name.
|Replies to private chats are migrated as regular chats but the reference to the original chat is not retained.
|Unexpected error occurs in a chat discovery task when matched users are deleted in the source tenant
|When the same chat is migrated simultaneously by two tasks, a failure in one task leads to a failure in the other with the following error message: The initiator <service-id> is not a member of the roster <chat-id>