Some Notes on the Machines

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/

These older versions of Outlook, now require special procedures to connect.

https://oit.colorado.edu/tutorial/office-365-outlook-windows-manual-exchange-configuration

When you encounter a user account that spins forever trying to sign in on a computer that already has a local copy of their profile, here is a few steps to resolve the issues quickly without either data loss or the need to create a new Windows profile:

1. Sign in on an account with Local Administrator rights
2. Navigate to “C:\Users”
3. Locate the profile folder of the user unable to sign in.
4. Rename the folder (Usually I add “.old”)
5. Sign out
6. Sign in as the user who’s profile has not been working
7. While signed in on this temporary profile, navigate back to “C:\Users”
8. Rename their profile folder back to what it was originally
9. Sign out
10. You should now be able to sign in normally to that user with their profile intact.

Contributed by the excellent Joe Busby.

Microsoft is no longer doing Service Packs for SQL Server, they’re doing Cumulative Updates. This page reports to be listing the most current for SQL 2017:

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

Prefix this, add a space to the end, and then type your Powershell:

%SystemRoot%\System32\WindowsPowerShell\v1.0\powershell.exe -NoProfile -InputFormat None -ExecutionPolicy Bypass -Command