When a file is moved to a different folder on the same NTFS volume, its permissions don’t automatically update to match the destination folder’s settings. Instead, the file keeps its original permissions, which can lead to unexpected access issues if the destination has different security settings

To ensure files inherit the permissions of their new location when moved within the same NTFS volume, you can adjust the Windows Registry to change this behavior. Set the following registry key on the file server:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer
MoveSecurityAttributes
REG_DWORD 0

EDIT:

This key does not work on newer Windows Server Operating Systems. It worked on Windows XP/Server 2003.

Microsoft Teams NEW can now be installed on Server 2019. Server 2016 is unfortunately not supported.

Firstly, enable these GPOs:

Computer Configuration > Administrative Settings > Windows Components > App Package Deployment:

• Allows development of Windows Store apps
• Allo all trusted apps to install

Download the MSIX Package: https://go.microsoft.com/fwlink/?linkid=2196106

Install Package:

Dism /Online /Add-ProvisionedAppxPackage /PackagePath:”C:\temp\MSTeams-x64.msix“ /SkipLicense

Tip: If you are having issues adding the MSIX Package, try removing the package first:

Get-AppxPackage -AllUsers -Name MSTeams | Remove-AppxPackage -AllUsers

Install MS Edge Webview2, which is also needed:

Evergreen Standalone x64: https://developer.microsoft.com/de-de/microsoft-edge/webview2/?form=MA13LH#download

To install Meeting Addin for Outlook check out https://www.ajni.it/2024/03/microsoft-teams-lightweight-teams-meeting-addin-in-outlook-missing/

References:

https://learn.microsoft.com/en-us/microsoftteams/new-teams-vdi-requirements-deploy

Download button inside WIndows Updates greyed out? This could be because of a GPO which sets the following registry key:

HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate

SetDisableUXWUAccess 0 (1 greyed out)

If you want to apply the settings without restarting your server/computer, restart Windows Updates service.

Have you ever gotten this annoying error when trying to open old control panel settings from the new settings app? This usually occurs in a domain environment.

You can fix this by creating a Domain policy or locally through secpol.msc > Local Policies > Security Options > User Account Control: Admin Approval Mode for the Built-in Administrator account:

References:

https://martinsblog.dk/windows-server-2016-systemsettingsadminflows-exe-error/

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