In some migration scenarios it may be necessary to migrate users after their SMTP/DNS/UPN domain name has been moved from the source to the target Office 365 tenant.
Some accounts receive the following error: "Invalid domain name in the request url"
Once the domain has been removed from the source Office 365 environment, then the user's source email address will likely change to email@example.com. You will need to run a new Discover task for On Demand Migration (ODM) to be made aware of these changes. Additionally, if the target users' UPN is also changing, perhaps to the domain being moved, then those users will need to be re-mapped or re-matched to their new target UPN.
NOTE: If the the UPN of the source admin account that was used to "Grant Consent" to ODM changes, then you will likely need to regrant consent after the change. We would suggest not making any changes to the target account used to grant consent to ODM.
NOTE: Before moving the DNS domain from the source Office 365 tenant to
the target Office 365 tenant, ensure that you have another way to login
to the ODM Portal if you are logging in using an account that exists in
the source Office 365 tenant. This KB article, How to use Access Control to add Users and set their Roles within ODM, explains how to add additional admin users to your ODM organization.
Here are the steps:
1.) Remove the DNS domain from the source Office 365 tenant
2.) Add and verify the DNS domain to the target Office 365 tenant
2.) Change Addresses in the target Office 365 tenant to update the user's UPN and primary SMTP address to the newly moved domain, as necessary
3.) In the ODM Portal, run the Discover task
4.) On the Accounts tab, select all accounts that you need to re-migrate, select Match, select Clear existing matches
5.) Now create a new Match, or map from file task as necessary. If using a mapping file, the source and target UPNs will need to be updated in the file.
6.) After running the map from file or Match task, go to the Tasks tab, single-click on the task and verify there are no errors or warnings in the right-hand details pane.
7.) Navigate to the Dashboard in the main pane
8.) Click Configure Connections
9.) Click Source, verify that the source migration admin UPN is in the format of: firstname.lastname@example.org
10.) Click Advanced Options (Target)
11.) Enter the following in the Custom EWS URL box:
12.) Click Save
13.) Click Finish
14.) Re-migrate the users by selecting users, or collections as necessary.
The steps above should allow for a successful migration of Mail, OneDrive, SharePoint and Teams data.
© 2021 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Termini di utilizzo Privacy