Some Notes on the Machines

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

As of version 2019 (and possibly before), QuickBooks has a new feature: native support of Office 365 webmail and some other major email providers. When users send email via QuickBooks, go to Preferences, Send Forms, and instead of choosing Outlook, choose Webmail, and then set up integration with the user’s Exchange Online account. Works much smoother, faster, more reliably.

To count the total number of folders in use within a mailbox, first connect Powershell to Exchange Online, then:

$MailboxToCountFoldersWithin = Get-Mailbox username
$MailboxToCountFoldersWithin | Get-MailboxFolderStatistics | Measure-Object | Select-Object -ExpandProperty Count

The total number of folders, will be output as a number.

This error often occurs when a longstanding Windows Server network is given a much newer domain controller. The WINS records embedded in DNS, don’t work anymore; when you try to delete them or change them, you get the error message in the title of this article.

The best thing to do, is PowerShell:

Remove-DNSServerResourceRecord -ZoneName dns_zone.local -Force -RRtype "WINS" -Name "@"

Try that (substituting dns_zone.local for your LAN DNS zone!), then right-click on the zone name, choose “All Tasks” and then “Reload”, then press F5 for refresh. The error-causing situation will go away, you can then reconfigure easily. If there are other zones, you’ll want to repeat for all of them. If there is a WINS record in a reverse lookup zone, the RRtype is WINSR instead of WINS, the result being something akin to this:

Remove-DNSServerResourceRecord -ZoneName 1.168.192.in-addr.arpa -Force -RRtype "WINSR" -Name "@"

Sometimes the actions above only take effect, and show up in the servers, if you reload and refresh (often both) the zones.

Here is the standard procedure, as given just now by an HP tech, to get HP Thunderbolt docking stations to work, when they don’t. The report is that these things are emphatically not plug-and-play, each of these steps has to be done in order.

The order below is consistent for all HP Thunderbolt-equipped laptops and HP Thunderbolt docking stations. The very specifics are correct for just one particular model of each (ia HP Zbook 17 G4 on an HP Thunderbolt Dock G2), as of right now, 2020-02-04.

1. Update the BIOS.

2. Set Thunderbolt to no security, in the BIOS.

We need to change thunderbolt security level to no security: Boot into the BIOS via F10, go to Port options, and if it’s set to user authentication or secure connect, change the dropdown to no security. If the option of no security is not available, disable the setting that reads ‘require thunderbolt password to change thunderbolt security’. Once the change has been identified and made, save and exit.

3. Install Intel Thunderbolt 3 Secure connect. Reboot.

ftp.hp.com/pub/softpaq/sp98501-99000/sp98877.exe

4. Install or update HP Thunderbolt Dock G2 Firmware. Reboot.

ftp.hp.com/pub/softpaq/sp98501-99000/sp98906.exe

5. Install or update Intel Thunderbolt 3 FW for HP Zbook 17 G4. Reboot.

ftp.hp.com/pub/softpaq/sp98001-98500/sp98136.exe

It’s called Amazon Corretto.

This seems to be quite the tool. Haven’t tested it yet.

https://github.com/oneget/oneget

Can be installed or updated in 10 with: Install-Module -Name PackageManagement -Force

Currently, the only known way is this sort of effort:

Set-MpPreference -DisableIntrusionPreventionSystem $true `
-DisableBehaviorMonitoring $true `
-DisableRemovableDriveScanning $true `
-DisableScanningMappedNetworkDrivesForFullScan $true `
-DisableScanningNetworkFiles $true `
-DisableEmailScanning $true `
-DisableBlockAtFirstSeen $true `
-DisableIOAVProtection $true `
-DisableRealtimeMonitoring $true `
-DisableScriptScanning $true `
-EnableControlledFolderAccess Disabled `
-MAPSReporting Disabled `
-SubmitSamplesConsent NeverSend `
-PUAProtection Disabled

Try this, in administrative Powershell:

wevtutil el | ForEach-Object { "$_"; wevtutil cl "$_" }

This, in Powershell:

Set-LocalUser -Name "pcunlocker" -PasswordNeverExpires 1