If you are having performance issues with your brand new File Server running on Windows Server 2019, particularly when working with small files over a network share, these PowerShell commands might save hours of troubleshooting.

Get-NetAdapter | Set-NetAdapterAdvancedProperty -DisplayName “Large Send Offload Version 2 (IPv4)” -DisplayValue “Disabled” -NoRestart

Get-NetAdapter | Set-NetAdapterAdvancedProperty -DisplayName “Large Send Offload Version 2 (IPv6)” -DisplayValue “Disabled” -NoRestart

Get-NetAdapter | Set-NetAdapterAdvancedProperty -DisplayName “Recv Segment Coalescing (IPv4)” -DisplayValue “Disabled” -NoRestart

Get-NetAdapter | Set-NetAdapterAdvancedProperty -DisplayName “Recv Segment Coalescing (IPv6)” -DisplayValue “Disabled” -NoRestart

Get-NetAdapter | Set-NetAdapterAdvancedProperty -DisplayName “Receive Side Scaling” -DisplayValue “Disabled” -NoRestart

Get-NetAdapter | Restart-NetAdapter

Note: The VM’s network adapter will be restarted, there will be a downtime of about 10 seconds.

References:

https://community.spiceworks.com/topic/2225989-server-2019-network-performance?page=8#entry-8745935

If you are syncing local AD users to Azure AD and using Seamless Sign-On (see https://www.ajni.it/2021/05/configuring-azure-ad-connect-for-user-synchronization/ and https://www.ajni.it/2021/05/configure-seamless-sign-on-for-microsoft-365-login-with-azure-ad-connect/), there is an awesome registry key that automatically creates the Outlook profiles without user interaction.

HKEY_CURRENT_USER\Software\Policies\Microsoft\Office\16.0\Outlook\AutoDiscover

DWORD ZeroConfigExchange 1

Alternatively, you can add the DWORD ZeroConfigExchangeOnce 1 key to automate the creation of the first profile. Successful profiles have to be created manually.

References:

https://docs.microsoft.com/en-us/outlook/troubleshoot/profiles-and-accounts/let-zeroconfigexchange-automatically-create-first-profile

If you have an AD synced distribution group and want to only allow senders from your organization, the msExchRequireAuthToSendTo attribute must be set to TRUE in the Attribute Editor. If you try changing that in the Exchange Online console, an error will appear.