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"

Recently received these. Not all work in all versions of Windows. Run these commands in administrative CMD. Some will take effect at next reboot.

netsh int tcp set global chimney=disabled
netsh int tcp set global rss=disabled
netsh int ip set global taskoffload=disabled
netsh int tcp set global autotuninglevel=disabled
netsh int tcp set supplemental custom congestionprovider=none
netsh int tcp set global ecncapability=disabled
netsh int tcp set global timestamps=disabled
netsh int tcp set supplemental custom congestionprovider = ctcp
netsh int tcp set global ecncapability=enabled
reg add HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters /v EnableTCPA /t REG_DWORD /d 1

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"

Just got this from HP support. They’re taking a while to answer, but they do have some help to give.

For HP business machines: support.hp.com/in-en/document/c05115630

For HP consumer machines: support.hp.com/in-en/document/c06162205

Apparently, not only is there SMB1, SMB2, and SMB3, but there is also NTLMv1 and NTLMv2. If we need to access older NASes and the like reliably, we may need to create or set this DWORD:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\LmCompatibilityLevel

to 1.

By far, ‘guvcview’, “GTK+ UVC Viewer”:

http://guvcview.sourceforge.net/

Chooses from any of the audio devices on the machine, of any sort, including JACK audio sources; chooses from any video capture device; and combines the result. Simple to use and extremely effective. Only one I found to do all of this reliably, out of many.

For a very long time, it was thought gospel that Outlook had hard caps on size of PST and OST files, which equals a hard cap on the size of a mailbox that Outlook can see. This has, apparently, changed. 100-gigabyte OSTs are possible, and larger. It is thought that very fast hard drives primarily, and certainly also good CPU and lots of RAM, are needed to reliably handle huge mailboxes and PSTs without corruption. Here is a method by registry entries. It’s also possible by Group Policy.

https://support.microsoft.com/en-us/help/832925/how-to-configure-the-size-limit-for-both—pst-and—ost-files-in-outloo

https://www.msoutlook.info/question/increase-pst-file-size-limit

Today it was found that an Office 2019 installation via 365, did not have any of the registry keys involved. After creating them manually in Regedit, the desired results did occur. These very registry entries are also created by the Group Policy method.

Once you install the Office 2016 templates:

https://www.microsoft.com/en-us/download/details.aspx?id=49030

you can set the maximum sizes:

This creates the same registry entries as the manual method.

An in-script fix:

[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12

A permanent fix:

Set-ItemProperty -Path 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\.NetFramework\v4.0.30319' -Name 'SchUseStrongCrypto' -Value '1' -Type DWord
Set-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft\.NetFramework\v4.0.30319' -Name 'SchUseStrongCrypto' -Value '1' -Type DWord