Exchange 2016 Hybrid Wizard Fails to validate Domains.

 You are running the Exchange Hybrid Configuration Wizard (HCW) and it gets stuck at validating domains.  You try-

Set-FederatedOrganizationIdentifier -DelegationFederationTrust "Microsoft Federation Gateway" -AccountNamespace "MYDOMAIN" -Enabled $true"

You get- An error occured while attempting to provision exchange with the partner sts.

Add the following registry keys and reboot.

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft.NETFramework\v2.0.50727]
"SystemDefaultTlsVersions"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft.NETFramework\v2.0.50727]
"SystemDefaultTlsVersions"=dword:00000001

Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft.NETFramework\v4.0.30319]
"SystemDefaultTlsVersions"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft.NETFramework\v4.0.30319]
"SystemDefaultTlsVersions"=dword:00000001

Go into EAC, organization, remove the federation.  Re-add it, add your domains, set your TXT records.  Verify they are there with NSLookup, click Update.  Re-run the hybrid wizard.

VMware vReplication replication changes are HUGE even though changes are minimal on server.

This issue is caused by a GuestOS sent unmap command.

To disable Unmap in the Guest OS-
fsutil behavior set DisableDeleteNotify 1

To re-enable the feature, use the following command:
fsutil behavior set DisableDeleteNotify 0

To verify the current setting, use the following command:
fsutil behavior query DisableDeleteNotify

DisableDeleteNotify=0 - indicates the Trim and Unmap feature is on (enabled)
DisableDeleteNotify=1 - indicates the Trim and Unmap feature is off (disabled)

What is unmap/deletenotify-
Delete notifications (also known as trim or unmap) is a feature that notifies the underlying storage device of clusters that have been freed due to a file delete operation. In addition:

For systems using ReFS v2, trim is disabled by default.
For systems using ReFS v1, trim is enabled by default.
For systems using NTFS, trim is enabled by default unless an administrator disables it.

If your hard disk drive or SAN reports that it doesn't support trim, then your hard disk drive and SANs don't get trim notifications.

Enabling or disabling doesn't require a restart.

 - Trim is effective when the next unmap command is issued.
 - Existing inflight IO are not impacted by the registry change.
 - Doesn't require any service restart when you enable or disable trim.