Some Notes on the Machines

Great info:

https://www.laptopmag.com/articles/move-onedrive-folder

There are several attempts, this one I have found to be by far the most reliable:

https://fastcopy.jp/en/

In an administrative Powershell, all of the following. Some OSes will not have all of them, just ignore any errors. Yesterday (10/23), on an older machine running Windows 10 with 8G RAM and a 1/2T platter drive, SATA bandwidth was showing a tad less than 1 megabit in Resource Monitor; afterwards, 10 megabit. Most gains have not been so high.

Enable-MMAgent -ApplicationLaunchPrefetching
Enable-MMAgent -ApplicationPreLaunch
Set-MMAgent -MaxOperationAPIFiles 8192
Enable-MMAgent -MemoryCompression
Enable-MMAgent -OperationAPI
Enable-MMAgent -PageCombining
Set-Service sysmain -StartupType Automatic
Start-Service sysmain

The last two enable and start the service, if necessary. The service is called Superfetch in services.msc, but very clearly, it does a whole lot more than drive fetching. It is not clear how the observed drive bandwidth increase is achieved. One theory has it that, with appropriate configuration, the service reorders OS disk reads and writes for maximum sequentiality, minimum seeks.

Here’s a great place to start:

Get-CimInstance -Class Win32_OperatingSystem | ForEach-Object -MemberName Caption

This gets profoundly useful strings like “Microsoft Windows 10 Enterprise”. If you need the numeric version, the best so far has been:

(Get-ItemProperty -Path c:\windows\system32\hal.dll).VersionInfo.FileVersion

which, right now on this machine, gets us “10.0.18362.387 (WinBuild.160101.0800)”. And for the Windows 10 build:

(Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion' -Name ReleaseID -ErrorAction Stop).ReleaseID

which gets “1903”. All of these are fast, do not depend on systeminfo, and appear to be nice and reliable.

Here:

https://appget.net/

Its silent install actually works well for Adobe Reader:

appget update adobe-reader --silent

These reportedly work for the EXE, MSI, and server-based push install settings:

https://help.eset.com/era/53/en-US/idh_ra_remoteinst_commandline.html

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 

These packages bundle configurations, even domain joins, and other items. Native to Windows 10:

https://docs.microsoft.com/en-us/windows/configuration/provisioning-packages/provisioning-create-package

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.

Right here:

https://www.serversupply.com/NETWORKING/NETWORK%20INTERFACE%20CARD/4%20PORT/