Skip to content

Migrations.md

Latest commit

 

History

History
167 lines (120 loc) · 8.79 KB

Migrations.md

File metadata and controls

167 lines (120 loc) · 8.79 KB

Migrations

This is a help page for the different types of migrations that can be done.

Table of Contents

  1. Genreral info and help
    1. Setting MsExchangeMailboxGuid to NULL / AD synced users have no mailbox in the cloud, but have in on-prem exchange server
  2. Bittitan
    1. General info
    2. Disable throttling in EXO
    3. Timeout issues causing migration to fail - This migration has failed because the source or destination endpoint
    4. Add logging to failed items
    5. Turn off Calendar assistant
    6. Links to guides
  3. Movebot
  4. PST import to EXO
    1. AND FOR THE LOVE OF GOD AND ALL THAT IS HOLY, PLEASE DONT FORGET THE '/' IN THE TargetRootFolder PROPERTY IN THE CSV FILE
  5. ProfWiz
    1. Steps for migration to Entra ID
      1. Pre-migration steps
      2. Migration steps

Genreral info and help

Setting MsExchangeMailboxGuid to NULL / AD synced users have no mailbox in the cloud, but have in on-prem exchange server

Guide for this is found here

Bittitan

Everything useful I've found for Bittitan migrations.

General info

Mailbox data is migrated from newest to oldest items. So the user gets their newest emails first.

Disable throttling in EXO

Disabled via support request in the admin center.

  1. Log into the admin center as a GA for the customer.
  2. Write "Increase EWS Throttling Policy" in the support search field.
  3. Run tests and set the days to 90 and press "Update settings".

Timeout issues causing migration to fail - This migration has failed because the source or destination endpoint

Add the following to the advanced options of the project.
Both mailbox and document migrations.

ExtendedEwsTimeout=1
InitializationTimeout=8

Read more about the support options here

Add logging to failed items

Check the following checkmark in the advanced options of the project, under Maintenance -> Log subjects of failed items.

Turn off Calendar assistant

Note: This will disable the calendar assistant for all users in the tenant. This will need to be turned back on after the migration is complete. This is done to ensure that the calendar assistant doesn't interfere with the migration and break meetings and recurring meetings.

Get-EXOMailbox -ResultSize unlimited | Set-Mailbox -CalendarRepairDisabled $true

Note: Turn back on Calendar assistant for all users.

Get-EXOMailbox -ResultSize unlimited | Set-Mailbox -CalendarRepairDisabled $false

Links to guides

IP lockdown of migrations
Mailboxes over 100 GB/Large mailboxes
M365 to M365
On-Prem and Hosted Exchange to M365
Scoped inpersonation
OneDrive to OneDrive
All Bititan support options
MigrationWiz - Advanced Options & General Options

Movebot

Everything useful I've found for Movebot migrations.

PST import to EXO

Everything useful I've found for PST import to EXO migrations.
PST Import Guide from MS

  1. Add the Mailbox Import Export role to Organization Management role group, at least 24 hours before the import process.
  2. Follow the above guide to create a PST import job.
  3. Create the PST import CSV file.

AND FOR THE LOVE OF GOD AND ALL THAT IS HOLY, PLEASE DONT FORGET THE '/' IN THE TargetRootFolder PROPERTY IN THE CSV FILE 

Workload,FilePath,Name,Mailbox,IsArchive,TargetRootFolder,ContentCodePage,SPFileContainer,SPManifestContainer,SPSiteUrl
Exchange,,NameOfPST.pst,projekter@domain.dk,FALSE,/,,,,

If needed to import into a subfolder in the mailbox, add the subfolder name to the TargetRootFolder property.

Workload,FilePath,Name,Mailbox,IsArchive,TargetRootFolder,ContentCodePage,SPFileContainer,SPManifestContainer,SPSiteUrl
Exchange,,NameOfPST.pst,projekter@domain.dk,FALSE,FolderToImportTo,,,,
  1. Upload the PST files to Azure blob storage.
# For only folder contents add \* on the end of the path
# For uploading a full folder leave only the foldername on the end of the path, like E:\UploadFolder. Edit the FilePath in the CSV to your needs.
#  --recursive can be added if the PST files are in subfolders
azcopy copy 'E:\Batch1\*' 'https://b59aa7f2cf2e46b1bc82282.blob.core.windows.net/ingestiondata?skoid=IDSomeThingHere'
  1. Finish the import job in the Purview portal, by validating the CSV file and creating the job.
  2. Wait for the job to finish.
  3. Press the "Import to M365" button and do the thing.

ProfWiz

Everything useful I've found for ProfWiz migrations.

Steps for migration to Entra ID

Pre-migration steps

  1. Create the config files for the migration.
    1. Use the onmicrosoft.com domain for the config file.
    2. Create a ForensiTAzureID.xml file via the script that is found here. Save-AzureADUser.ps1 can be downloaded from: https://github.com/ForensiT/PowerShell.
    3. Create the provisioning file for the migration. Guide is found in the ProfWiz Corporate user guide too. This is the file that will be used to Entra join the machine.

Migration steps

  1. Check if the computer is a Home edition. If it is, upgrade to Pro edition.
  2. Make a local administrator account on the computer.
  3. Suspend BitLocker on the computer.
  4. If the browser is not synced, either sync it or create an export of the bookmarks and import them after the migration.
  5. Copy all the ProfWiz config and XML files to the computer. C:\Temp is a good place.
  6. Log into the local administrator account.
  7. If the device is already Azure AD/Entra registered, delete the device from Intune/Entra.
  8. If windows Hello is setup for the user, remove this. certutil.exe -DeleteHelloContainer. If that does not work: https://www.it-admins.com/reset-or-remove-the-windows-hello-pin/
  9. If using a provisioning package, skip to step 11.
  10. Remove the computer from the domain.
  11. Reboot the computer.
  12. Join the computer to the Azure AD/Entra domain via the settings app -> Accounts -> Access work or school -> Connect -> Join this device to Azure Active Directory.
  13. Run the ProfWiz migration tool. The Computer will reboot.
  14. Log into the migrated account. If the option is not shown, use the local administrator account to log in. Afterwards, press "Switch account" and log into the migrated account.
  15. Import the bookmarks into the browser, if needed.
  16. Make sure the computer is enrolled correctly in Intune via the Company portal.
  17. Run the command "sfc /scannow" in an elevated command prompt. VERY IMPORTANT, as the ACL in the registry is messed up otherwise and is far too permissive.
  18. Reboot the computer.
  19. Enable BitLocker on the computer.
  20. Uninstall Trend Micro, if needed.
  21. Reboot the computer.
  22. Delete the local administrator account.