I have a number of 2016 servers. It seems like 99% of them fail when doing automatic updates. I am able to install them manually by going through sconfig and selecting option 6 but it takes FOREVER. During installation, the CPU or Memory isn't maxed out at 100% so I have no idea what is causing it to take forever. All other previous versions of Windows run and install updates just fine in the same VMware environment.

Continue support and updates for Advanced Group Policy Management. Our company uses AGPM extensively and would like to see future enhancements and support continued. If there is a replacement Microsoft product, it doesn't seem to be found.

Enough said.

Post a list of what the error codes mean in the error log for transferring files with storage migration service. I have no idea what code 2, 32 or 40973 mean! Would be nice to know so I can know why files failed to copy.

#Windows Firewall Log BUG

Situation:
New Installed Server With 2016 Standard. Patched and up2date with June-2019 CU.
Created a new Domain with itself beeing the first domaincontroler. Created a GPO to activate Windows Firewall and enable Logging of DROP and ALLOW to pfirewall-domain.log in the default-path.

What happens?
The Log can´t be written, no access denied. Sysinternals Procmon shows no "Access Denied". Shows a few creates but does not write.
[...]
Detailed Explanation:
https://social.technet.microsoft.com/Forums/en-US/b8ba16b4-8b7e-4c3a-a610-a67fed2e87ae/is-this-a-permissionbug-in-windows-firewall-logging?forum=win10itprosecurity

There's a pretty big problem on some servers (at least two Dell PET Servers I've tried so far) that stops Server 2019 from booting/goes into a boot loop once the Hyper-V role is installed.

When Creator Owner is removed from NTFS permissions, change permissions is still given when a person with Modify rights creates a new folder/file. If the Modify permission is the only permission granted, a person who creates a new folder/file should not be granted the Change Permissions when Creator Owner has been removed from the NTFS permissions.

ADFS 2019 allows for 300 IPs to be added to the "Banned IP list"

https://docs.microsoft.com/en-us/windows-server/identity/ad-fs/operations/configure-ad-fs-banned-ip#adding-banned-ips

As there are nearly four billion public IPs on the internet, 300 is woefully inadequate.

Small customers that are only trying to block a few users aren't likely using ADFS anyway. Large organizations that rely on ADFS will hit the 300 limit almost immediately.

I'd like to see this number raised to 65538 (/16) or something similar.

Error message that i spend 3 month search for a solution no one knows what's the problem

Getting this error in server 2019 and 2016 after closing GPMC.msc

Error ID 1000

The massage is:

Faulting application name: mmc.exe, version: 10.0.17763.1, time stamp: 0x176b88f0
Faulting module name: GPOAdmin.dll, version: 10.0.17763.1, time stamp: 0x84e18916
Exception code: 0xc0000005
Fault offset: 0x00000000000bb4cb
Faulting process id: 0x980
Faulting application start time: 0x01d50e351f75ca91
Faulting application path: C:\Windows\system32\mmc.exe
Faulting module path: C:\Windows\System32\GPOAdmin.dll
Report Id: 918fa381-d469-4623-9544-9a949e90666d
Faulting package full name:
Faulting package-relative application ID:

While never fully supported, the support WinPE had for WPF was enough to allow folks to build flexible, customized tools. Most of us who have done it are SCCM admins building custom front-ends for the OSD process.

The excellent community has found a workaround to keep WPF going, but it would be nice to have support officially back to at least the level it was.

Thanks!

It would be great if it could be displayed directly in the console to which users and computers a new or changed policy could already be applied.

Dear Microsoft Windows Server team. We would like _complete control_ over when we would like our our WS2016 to install windows updates! No more slow / timeconsuming server restarts because of "Getting Windows ready. Do not turn off your computer" messages when we just would like a quick restart of a production server.. No more TiWorker.exe using 100% of a CPU core during "*********" and so on.. And please fix the issues with '2017-08 Update for Windows Server 2016 for x64-based Systems (KB4035631)' asap. Thank you.

Add Support for Remote Desktop using a Biometric for Key Trust environments

We still need a Windows Version for small customers getting easy connection to Azure and Office 365. So do NOT remove the Essential Role out of Version 2019.