Some Notes on the Machines

A couple of links:

https://itpro-tips.com/2019/this-users-on-premises-mailbox-hasnt-been-migrated-to-exchange-online/

https://answers.microsoft.com/en-us/msoffice/forum/all/this-users-on-premise-mailbox-hasnt-been-migrated/5735f499-7079-42a4-a5e9-8da275404d09

One can use this to import really big ones, dozens of gigabytes in size, imports which will crash, hang, and otherwise cough on Outlook very easily. Runs directly to folders inside of mailboxes. The amazing Yvonne Wynkoop found the first really good set of instructions we have seen:

blog.natfan.io/importing-psts

Mysteries do abound about the Microsoft-provided command line tool AzCopy, not the least being the fact that there is a version 10 and a version 8.1. Items as of this writing:

• Version 8.1 is downloadable from Office 365, and works. Have no clue what 10 is for.
• Usage and download of it, is now through Office 365 Security & Compliance, Information Governance, Import.
• When you run it for an upload, add “/NC:2” to the end of the command line. This increases its speed and stability quite a lot, and prevents timeouts. Default is reportedly 24. Perhaps the developers are sitting on Google Fiber?
• If it times out, just restart it carefully, it will usually continue where it left off.

If the above works for you, use the same number when downloading PSTs from eDiscovery, via registry edit:

https://docs.microsoft.com/en-us/microsoft-365/compliance/increase-download-speeds-when-exporting-ediscovery-results?view=o365-worldwide

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\Client\eDiscovery\ExportTool]
"DownloadConcurrency"="2"

If you let the eDiscovery Export Tool time out, it will eventually give you a link:

https://docs.microsoft.com/en-us/office365/securitycompliance/increase-download-speeds-when-exporting-ediscovery-results

which has the registry edit below. No explanation is given, but it does say that adjustment of the number (in some direction?) can help.

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Exchange\Client\eDiscovery\ExportTool]
"DownloadConcurrency"="2"

New methods, reportedly considerably better, have not tested yet myself:

https://docs.microsoft.com/en-us/powershell/exchange/exchange-online/exchange-online-powershell-v2/exchange-online-powershell-v2?view=exchange-ps

1. Install the Azure Active Directory Module for Powershell.

2. Connect to Azure AD, and disable sync:

Set-MsolDirSyncEnabled –EnableDirSync $false

3. Check status, repeatedly, until it returns False. It can take 72 hours for sync to be fully deactivated.

(Get-MSOLCompanyInformation).DirectorySynchronizationEnabled 

It can happen fairly easily, that one or more user’s Office 365 login is wrong, and AD Sync fails to correct it. Here is a manual override, courtesy of the excellent Joe Busby.

1. On a domain controller, verify the AD username and proxy addresses is set correctly.
2. Connect to O365 Powershell on any machine with Powershell 5.1, and run this command:

Set-MsolUserPrincipalName -UserPrincipalName "user@old.address" -NewUserPrincipalName "user@new.address"

3. On the user’s PC:
   1. Navigate to Settings > Accounts > Access work or school
   2. Disconnect from any accounts linked to the new or old username
   3. Hit the [ + ] Connect button and provide the credentials to sign in to Office 365
   4. If their password has been changed since their account was synced up with the wrong username, the password may need to be reset.
   5. Remove any credentials from windows credential manager that match the old username.
   6. Check Outlook, you may have to create a new profile.

Excellent tool.

https://support.office.com/en-us/article/microsoft-support-and-recovery-assistant-sara-e90bb691-c2a7-4697-a94f-88836856c72f

There are many different products / licenses for Office 365, in several categories. The first item has links to the rest:

Business, general

Small business

Education

Government

Nonprofits

Home

Firstline Workers

The above suggested by the excellent Tharin Brown.

There is an alternative activation logon screen.

https://answers.microsoft.com/en-us/msoffice/forum/msoffice_account-mso_win10/unable-to-sign-in-to-office-2016-desktop-apps-sign/b32738c8-1b17-43d1-839b-cb97c8ae3c29

From the indefatigable Mike Crayton:

https://www.thecloudjournal.net/2016/08/reset-microsoft-office-product-activation-status/

https://gallery.technet.microsoft.com/office/How-To-Reset-Office-01cf9c07

This can help a lot when Office will not activate.