Chat now with support
Chat with Support

Welcome, erwin customers to Quest Support Portal click here for for frequently asked questions regarding servicing your supported assets.

On Demand Migration Current - Release Notes

Known Issues

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

 

Table 4: General known issues

Known Issue Issue ID
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. ODM-1112
Statistics related to permissions can be incorrect in some specific cases. ODM-872
Deletion of target object after the migration may not be reported. ODM -855
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. N/A
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. N/A
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. ODM-176
Double-clicking Finish button in wizards may result in creating several duplicate tasks. DO-728
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. N/A
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. ODM-309
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. ODM-335
A search query entered by user to filter content may be lost in case the user switches tab. ODM-293
Migration of Microsoft Office 365 groups and security groups with dynamic membership is not supported. ODM-37
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 ODM-1576
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 ODM-1566
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. ODM -1567

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. 4781288-1

Address Rewriting
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

4783213-1

Table 5: Account migration known issues

Known Issue Issue ID
Resource Processing is not available when GCC High tenants are used. Resource Processing is only available with commercial tenants. 251283
Resource Processing is not available when credentials are not provided. 248836
Source UPN and Primary SMTP will be used after migration for existing target hybrid accounts. ODM-1251
In case of re-migration of hybrid account the Migration task state may appear to be completed before the actual completion. ODM-1174
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. ODM-1345
Hybrid accounts has New status even in case these accounts are in progress. ODM-1053
Matching task may hang with In progress state in case on-premises connection credentials are not configured. No events are reported.
ODM-1383
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. ODM-1469
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. ODM-1292
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. ODM-1255
Migration Task progress may be reported incorrectly. Refer to task details for actual information. ODM-1175
Mail flow is not currently displayed for migrated objects. ODM-1376
Mapping from file is not currently supported ODM-1365

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.

ODM-1344
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. ODM-1331
Migration tasks may hang with In progress state in case of any issues related to integration with Quest Migration Manager. No events are reported.
ODM-1332

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.

ODM-1878

Table 6: OneDrive migration known issues

Known Issue ID
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 ti Microsoft limitation. ODM-1640

Table 7: Public folder migration known issues

Known Issue ID
There is currently no way to stop running tasks. PFM-76
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. PFM-77

Table 8: SharePoint migration known issues

Known Issue ID
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. 163227,179261
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. 173081
After migration the system account is specified as an author of migrated folder instead of the source folder author. 171641
Web address of this view in List View settings cannot be updated due to SharePoint limitations. 169946
Migrated discussion board replies are not tagged as "Best reply" on target. 157005
Custom content type assigned to documents is not migrated. All documents will have the default content type on target. 161588
Discussion List created by the site Community feature is renamed to Community Discussion in Team site (STS#3 template.) 168288
Files and list items are not migrated to subsites with the following characters in the URL: <, >, &, ", ' 169663
Site collection status is not updated if the migration task includes more than one site collection. 161760

The search field shows a limited number of characters. Only the first 22 characters are visible for the long search queries.

164683

Table 9: Teams migration known issues

Known Issue ID

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.

259757
When two or more users are participants in a chat, the chat migration task event is not linked to any particular user. 256913
Planner migration: If there are more than 400 tasks in a bucket then On Demand migrates the first 400 tasks only.  
On Demand cannot migrate the file if the SharePoint admin center (under Settings | Site Creation) has been used to change the default URL. 240044
Links to files in migrated messages are not supported in case these links point to files located outside the default SharePoint URL. These links are missing in the target. 223575
If you rename a tab in the source team and then re-migrate, the renamed tab will be migrated. The target will then have two tabs, one with the old name and one with the new name. 197275
Meeting links in Teams calendar items of migrated teams don't work because the links still point to source tenant. 196069
Provisioning of public teams is not supported for migration scenarios from one education tenant to another. Only private teams can be provisioned for these scenarios. 218826
Multi-Geo tenant is not currently supported. 213280

OneNote tabs migration fails if the team contains a large number of items (folders or files, some of which could be OneNote entities such as notebooks, sections or section groups) and the following error message is reported: Request failed with Forbidden status code (Forbidden). { "error": { "code": "10026", "message": "One or more of the document libraries on the user or group’s OneDrive contains more than 20,000 OneNote items (notebooks, sections, section groups). Please try again later."....

Workarounds:

Before proceeding with migration consider the following Microsoft recommendations to avoid the problem: https://docs.microsoft.com/en-us/archive/blogs/onenotedev/onenote-api-calls-fail-with-a-large-number-of-items-in-a-sharepoint-document-library

-OR-

Before proceeding with Teams migration use SharePoint migration to migrate the site collections for affected teams. Then retry Teams migration with Use previously migrated files option selected

216192

When the team name in source tenant is different from the one in target tenant, a blank default team’s notebook (with the target team name) will be created in target tenant. The original default team’s notebook (with the source team name) will be migrated correctly by Team’s migration. This results in two default team’s notebook in target.

N/A
Archived teams are not supported. In case you need to migrate these teams, you need to unarchive them in the source to migrate and then archive them again in the source and in the target. 181522

Target team settings are not updated if you re-run the provisioning task.

Workaround: Update the target team settings manually or remove the team and re-run the provisioning task.

N/A
Incremental migration migrates new messages that was created since the last migration. On Demand Migration for Teams cannot modify or delete messages on the target if they have been modified or deleted on the source. 167428

The target tenant's Global Administrator is displayed as the owner of all migrated messages on the target: The original owner and creation time of a message are displayed in the first line of the message starting with "Originally posted by...".

157045

Channel isFavoriteByDefault property migration is not supported . Workaround: Enable Automatically show this channel in everyone’s channel listoption for the channel manually in your Teams client. 154722

The memberships is not updated in Teams client immediately after provision. It takes a while before Microsoft synchronizes memberships between group and Teams.

Workaround: Wait for membership synchronization

N/A
The following warning is reported: Cannot migrate attachment ***: file not found
Workaround: Verify whether the file is not blocked or deleted in the source. File Migration task cannot migrate file in case it is not available.
N/A
Target administrative account are added to source teams automatically. This is mandatory requirement for migration. The following warning is reported: Adding *** as a member of the group '***' on the source...

No action required.

N/A

The following warning is reported: Cannot add *** as group ***: User Mapping does not exists. The team member or owner was not matched or migrated by Account migration project.

Workaround:In Account Migration project match or migrate the account and then re-run provision task.

N/A
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.

N/A
Private one-to-one chats with a Skype user are not migrated. The Microsoft Graph API List chat messages do not support querying messages of that type. N/A
If you have personalized the name of a group chat then that personalized name will not be migrated. Post migration, on the target, the group chat name will revert to that supplied by Microsoft: the list of team members in the chat. Post migration on the target you can re-enter the name you gave to the group chat if you wish. N/A
Private one-to-one chats are migrated as group chats. On the source the name of the chat is given by the other person in the chat; on the target the name of the chat is of the form " name and name - migrated". On the target the private chat becomes a group chat when the migration account granting consent to the tenant is added to the chat as a participant. This is by design to workaround Microsoft's API limitations. To preserve privacy this account is removed from the chat as soon as the chat migration is completed. N/A
On the source a member removed from a chat can still see the history of the chat in the source. On the target, members cannot see the history of chats they have been removed from. N/A
Individual messages larger than 4 MB will not migrate. Messages containing several inline messages can exceed 4MB. The chat will migrate without the large messages. An error will display in the On Demand Migration for Teams Events tab of the form: Request failed with RequestEntityTooLarge status code (Request Entity Too Large). N/A
Users deleted on the tenant are not migrated, so do not show as members of a chat on the target. Deleted users do remain visible as members of a chat on the source. 1:1 chats, where one of the users is deleted, are migrated for the user that is still a member of the tenant. N/A
Private one-to-one chats with an ‘External user’ (user from another tenant) are treated as follows. Private one-to-one chats initiated by an ‘External user’ are not migrated. Private one-to-one chats not initiated by an ‘External user’ are migrated, and in the title the external user’s real name is replaced with the text ‘External user’. N/A

Release History

May 27, 2021

Table 10: New Features

Module Feature Description
Mail Migration Support for X500 email addresses The On Demand Migration for Mail service will migrate X500 email addresses of user and group mailbox accounts if they are not already synchronized with the online Office 365 Active Directory in the target tenant. Migration of X500 addresses prevents NDR (Non-Delivery Report) problems with older email addresses as described below:

X500 email addresses are generated when user mailboxes from older versions of on-premise Microsoft Exchange environments or hybrid environments are synchronized with the online Office 365 Active Directory. After mail migration, if X500 addresses are not added to the user’s attributes in the target tenant, and the user interacts with old mail or calendar items, the sender receives an NDR reporting that the specific recipient doesn’t exist.

Table 11: Enhancements

Module ID Description
Teams Migration ODMTOG-53 When teams are migrated, each instance of @mentions generates a new activity email and users could receive a large number of unexpected emails. As a result @mentions are migrated as text and new activity emails are suppressed.

May 06, 2021

Table 12: New Features

Module Feature Description
SharePoint Migration Support for the Enterprise Wiki site template Includes fuller support for the SharePoint Server Publishing Infrastructure site collection feature and SharePoint Server Publishing site feature. Migration of the Pages library activated by the publishing features is supported.
SharePoint Migration Support for SharePoint 2013 Workflows Migration of site, list and reusable workflows is supported. Migration of workflow definitions and subscriptions (associations) is supported. However, the migration of workflow instances or completed and in progress workflows, is not supported.
SharePoint Migration Support for Image columns Migration of the Image column in SharePoint online lists and libraries is supported.

Table 13: Resolved Issues

Module ID Description
SharePoint Migration 4874100-1 Improved stability when gathering child objects for migration
SharePoint Migration 4870323-1, 4843650-1 Improved support for remapping links in web parts when migrating a site from the root site to a managed path site

April 30, 2021

Table 14: New Features

Module Feature Description
Mail Migration Skip License Assignment The Licensing Plan step of the New Mail Migration Task wizard offers a new check box that controls whether you want to select or skip the assignment of an Exchange Online license plan. If a license plan is selected, then you can choose how to assign the plan to matched user accounts in the target tenant. If a license plan is not selected, then the mailboxes of user accounts in the source tenant that are matched with unlicensed user accounts in the target tenant cannot be migrated.

Table 15: Resolved Issues

Module ID Description
SharePoint Migration 4870787-1 An error event occurs even when a SharePoint site is locked. It can occur only when the lock state of the site is either ReadOnly or NoAccess.
SharePoint Migration 253104 A SharePoint migration task occasionally throws the exception: Messages cannot be larger than 65536 bytes.

April 27, 2021

Table 16: New Features

Module Feature Description
OneDrive Migration Collect Statistics

The new OneDrive Collect Statistics Task conducts an assessment of selected accounts in the source tenant and provides the following information to help you plan your OneDrive migration:

  • The number of items in the OneDrive for each account and the total number of items across all selected accounts where the assessment was possible.
  • The total size of all the items in the OneDrive for each account and the total size of all items across all selected accounts where the assessment was possible.

April 23, 2021

Table 17: Resolved Issues

Module ID Description
On Demand Migration 4870787-1 Throttling problem with the Copy Permission task was resolved

April 16, 2021

Table 18: New Features

Module Feature Description
SharePoint Migration List Repair The On Demand Migration for SharePoint service can repair lists with the content state Migrated with Issues, in addition to the incremental migration already available. For both incremental and repair migrations, if the option Clear selected SharePoint objects is selected, a full migration will occur because the target list will be deleted and the existing migration state will be ignored.

Table 19: Enhancements

Module ID Description
Teams Migration 251182 Migration support for Group - general settings
Teams Migration 252534 Migration support for renamed channels
Teams Migration 244308 Migration support for Commercial tenant to GCC High tenant

Table 20: Resolved Issues

Module ID Description
SharePoint Migration 4871402-1, 4869752-1 Unable to download some files for migration
SharePoint Migration 4770182-2 Unable to remap links in hyperlink and picture columns when migrating a site from the root site to a managed path site

March 25, 2021

Table 21: Enhancements

Module ID Description
Account Migration 251283 Resource Processing is not available when GCC High tenants are used. Resource Processing is only available with commercial tenants.
Account Migration 248836 Resource Processing is not available when credentials are not provided.

March 24, 2021

Table 22: Enhancements

Module ID Description
Mail Migration 244192 On Demand Migration has added a new column “mailbox status’ to mailboxes migration user interface.
SharePoint Migration   On Demand Migration for SharePoint now supports SharePoint hub sites: hub site and settings and sites associated with the hub site.
SharePoint Migration   On Demand Migration for SharePoint has additional settings to control the number of versions migrated with documents: a limit on the number of versions of a document migrated each day and a limit on the maximum number of versions of a document migrated in a migration task.

March 18, 2021

Table 23: Resolved Issues

Module ID Description
Account Migration   Improved on the error messaging when the customer is trying to do "Resource Processing" for a Guest User.
Mail Migration   Corrected problem behind exception "Messages cannot be larger than 65536".

March 15, 2021

Table 24: Resolved Issues

Module ID Description
Mail Migration 4829441-1 On Demand Migration has corrected an issue where unread marks were not migrated correctly and deleted mails reappeared in the migrated mailbox.

Table 25: Enhancements

Module ID Description
Mail Migration 4829441-1 On Demand Migration now supports migration of Read/Unread status updates on subsequent migrations.

March 11, 2021

Table 26: Resolved Issues

Module ID Description
Resource Processing CSR 4846689-1

On Demand Migration now shows an appropriate error message when trying to process the SharePoint Website (Resource Processing) when SharingCapability is disabled for the Sharepoint website.

March 09, 2021

Table 27: Enhancements

Module ID Description
Mail Migration 223637 On Demand Migration now allows for flexible mapping for mailbox folders.
Mail Migration 243217 On Demand Migration now provides the functionality to upload a CSV file from the user interface for scope based discovery.
Account Migration ODM-28 Resource processing of Azure Active Directory Groups and Guest accounts in Sharepoint - There is now the ability to process the all types of group permission (Security Group, Mail enabled security group, Distribution List, Office 365 Group)
Account Migration 4846689-1 On Demand Migration now processes the Azure Active Directory group membership for Distribution Lists and Mail Enabled Security Group.
Teams and Groups Migration 242265 On Demand Migration supports Tab Link Migration.

Table 28: Resolved Issues

Module ID Description
Mail Migration 243902 On Demand Migration has fixed a mailbox migration status/task state discrepancy where the task failed and the migration status was left in a hung state.
Teams and Groups Migration 245089 On Demand Migration has corrected the ArgumentNullException issue for chat migration.

March 04, 2021

Table 29: Resolved Issues

Module ID Description
Teams and Groups Migration 245096 On Demand Migration has corrected the problem behind the error "Forbidden by policy" during provision of teams.
Teams and Groups Migration 245726 On Demand Migration has corrected a provision issue when a user email contained an apostrophe.
Teams and Groups Migration 246314 On Demand Migration has corrected an issue provisioning an incorrect target user to team members.

March 02, 2021

Table 30: Enhancements

Module ID Description
Teams and Groups Migration 196092 On Demand Migration now supports migration of announcements.

February 25, 2021

Table 31: Enhancements

Module ID Description
SharePoint Migration   On Demand Migration for SharePoint has added the “Members” object as child of the site object. The Members entity contains the user groups associated with the site. Users and groups can be re-migrated by selecting and migrating the Members object
SharePoint Migration   On Demand Migration for SharePoint now supports Collections. Child objects are not automatically added to a collection when a parent is added. Run Discover SharePoint Contents to add child objects.
SharePoint Migration   The On Demand Migration for SharePoint Match task now has an option to include the site structure in the matching operation. When the option is enabled, all discovered child objects will be matched on the target with the corresponding object if it exists.

Table 32: Resolved Issues

Module ID Description
Mail Migration 244258 On Demand Migration has fixed a problem "System.Exception: Error occurred while executing the request. BadRequest (Bad Request)" when migrate Teams Group Mailboxes.
Teams and Groups Migration 203906 Corrected an issue such that the migrator account is no longer added to the source team as owner.
Teams and Groups Migration 244727 On Demand Migration has fixed an issue where the Groups link was not working for the task of migrate/provision of Microsoft Office 365 groups.

February 18, 2021

Table 33: Enhancements

Module ID Description
Account Migration 224794 The Resource Processing Task has been enhanced to optionally grant target users access to source systems when an Active Directory group they are a part of is granted access.
Account Migration 243217 Set the preferred data location when migrating to a multi-geo tenant.

Table 34: Resolved Issues

Module ID Description
Account Migration 4793828 On Demand Migration has fixed a problem where the display of verified domain names was limited to 100 items or less. The display now shows all managed domain names.

February 16, 2021

Table 35: Enhancements

Module ID Description
Account Migration 221174 Customers now have the option to disable mail forwarding when migrating a mailbox.

Table 36: Resolved Issues

Module ID Description
Account Migration CSR 4840268-1 Corrected a problem where the Client Update Agent failed to work for a soft deleted mailbox.

Incident Response Management

Quest Operations and Quest Support have procedures in place to monitor the health of the system and ensure any degradation of the service is promptly identified and resolved. On Demand Migration relies on Microsoft Azure infrastructure and as such is subject to the possible disruption of the related services.

You can view the following status pages:

System requirements

The following web browsers are supported with On Demand:

  • Microsoft Internet Explorer 11
  • Microsoft Edge
  • Google Chrome (latest version)
  • Mozilla Firefox (latest version)
System requirements for Client Update Agent deployment

NOTE: Client Update Agent supports the MAPI over HTTP only. If the Outlook version is earlier than specified above and uses RPC over HTTP instead of MAPI over HTTP, it must to be upgraded to minimal supported version.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating