Example of our cross tenant user data migration approach

-

 

Example of our user data migration approach:

Important is the completion of your data pre-load for OneDrive and Exchange.

Remember, that the pre-load should include as much data as possible. Syncing on the cut-over day data > 10 GB or more than 500 files in OneDrive, might end up with an INCOMPLETE set of data in the target. Therefore, you should urge using the OneDrive Cross-tenant OneDrive Migration tool from Microsoft.
The user will than see data being migrated (missing data) upon he starts working in the target environment. This will not be happening with the cross-tenant migration tool. The switch to the target tenant will take approx. 15min.

Migration of Teams personal Chat messages, we mostly limit to 15 days. The performance is acceptable migrating approx. 400 – 800 users/day.

Note:
You should have special procedures in place for legal-hold users, white glove and user object facing issues.

  1. Prepare source and target tenant and ensure the readiness for Microsoft tools
  2. Prepare computer migration (if it goes along with the user migration) and start the computer migration (3rd party tool)
  3. Teams EV Phone Number assignment
  4. Place user in any AD Group required (e.g. for computer object migration/ Desktop update Agents)
  5. Set SMTP Redirect
  6. Initiate OneDrive cross-tenant move
  7. Migrate D15 Teams personal Chat Messages (15 days of chat)
  8. Finalize Mailbox Content migration (cross-tenant move)
  9. Start Teams Meeting Link Migration (3rd party tool)
  10. Run User Profile migration
  11. Execute computer management (e.g. Intune, AutoPilot or SCCM)

Upon all users are migrated, you can start the Teams Personal Chat Migration, e.g. into a HTML File, or other archive solution.

Comments

Post a Comment

Popular posts from this blog

How to hide users from GAL if they are AD Connect synchronized

-
Image
How to hide and un-hide users from Global Address List (GAL) in Exchange Online if they are AD Connect synchronized Hiding User from GAL isn't possible if those are synchronized form On-Premises Active Directory. The local AD is the leading system for all important attributes, like SMTP, UPN and hiding from GAL. Especially during a cross-tenant migration, you do not want to see not migrated user in the GAL. Those User aren't actively working until their cut-over day. Since the Exchange Online attribute  msExchHideFromAddressList s is an AD on-premises parameter, we have two possible ways hiding user in BME from GAL.   Modify the AD Connect for your teant with a custom rule, by using a extensionAttribute to set the HidefromGAL. In this rule, for users which have an entry in the extensionAttribute, hiding / un-hiding will be controlled by AD Connect This is the best option for Cross-Tenant Migration, if you run 2 or more AD Connect system We direct modify the AD hide at
Read more

Cannot join external Lync Meeting: Lync Edge Server Single IP Address (Lync Edge Server Single IP Web Conferenceing Problem)

-
Image
Lync Edge Server FQDN and IP PORTS (Version 1.2, Update 26.11.2014) As we all know, we can configure Lync Edge Server in several way. 1) Single Edge Server with a SINGLE IP ADDRESS 2) Single Edge Server with MULTIPLE IP ADDRESSES (3x IPs) 3) Multiple Edge Server in a Pool, with MULTIPLE IP ADDRESSES (Zx 3 IPs) Regardless what we are going to configure, there are common / well-known TCP Port necessary making Lync work, which are: Access: Port: 443 and 5061 Conferencing: Port: 443 and (444) AV: Port: 443 (I have not listed other ports, e.g. STUN or the dynamic port range. This is not required for the topic discussed here) External FQDN with single IP address: What can we see here? If we are going to choose a single IP address, we would have TCP Port overlapping. Therefore the only way avoiding this is assigning other ports. Additionally we will also see and are reminded that Lync highly depends on DNS. If we have single IP, we must have use single, unique FQDN fo
Read more

MFA with Guest Access and different tenants settings

-
Image
There is an update regarding MFA Multi Factor Authentication. If you are guest with a different Tenant, the MFA Settings are now reflecting the settings of all tenants in a different way. Each MFA setting is reflected and you can setup your MFA device as per tenant and the admin settings allow. Login to your Profile in Office 365/ Azure AD: https://account.activedirectory.windowsazure.com/r/#/profile or https://myapps.microsoft.com Go to your PROFILE: Sign in to https://myapps.microsoft.com Select your account name in the top right, then select profile. Select Additional security verification. If might be happen, your admin hast configured MFA, so you wouldn't see this menu. Simply switch the tenant to the guest tenant where you need to configure MFA. Once you go back to your profile and you will find the MFA device and other settings a usual:
Read more