Please fix the command line Ping.
This is a very old function and feature that has be broken for a long time.
the -w or /w function does not work for Ping.

RDP Connections to Server 2019 are not stable - connection drops within seconds.

1 Dell R730 and 1 Dell R710 upgraded from Server 2016 to Server 2019. RDP worked perfectly under 2016. 2019 cannot maintain a stable connection. Performed Clean install on R710 but problem persists.

This must be a new bug in 2019 as the same hardware and NIC configuration worked under 2016.

I own a surface and when I move by accident and the keyboard is still attached there should be a small window not to rotate the screen, it could be used to determine sleep. through motion and inactivity.. this could leads to less battery drain. by keeping the screen off often.

Broken link to images on https://www.microsoft.com/upgradecenter

https://www.microsoft.com/upgradecenter/scenario/WS2008R2-on-prem-to-WS2012
https://www.microsoft.com/upgradecenter/scenario/WS2008R2-on-prem-to-WS2016
https://www.microsoft.com/upgradecenter/scenario/WS2008R2-on-prem-to-WS2019
https://www.microsoft.com/upgradecenter/scenario/WS2012-on-prem-to-WS2016
https://www.microsoft.com/upgradecenter/scenario/WS2012-on-prem-to-WS2019
https://www.microsoft.com/upgradecenter/scenario/WS2012R2-on-prem-to-WS2016
https://www.microsoft.com/upgradecenter/scenario/WS2012R2-on-prem-to-WS2019
https://www.microsoft.com/upgradecenter/scenario/WS2016-on-prem-to-WS2019

EVERTHING WILL SAFE FOR ....

I'm interested in using Powershell to bulk create Group Policy Objects for Registry Items using the command Set-GPPrefRegistryValue but I'm not able to modify any of the settings under the Common Tab. I would like to do Item-Level Targeting and Check the box for Remove this Item when it is no longer applied specifically. Is there some Commandlets that modify those values for a registry item? If not can you please make them? Thank you

You should add Windows Server 2019, Windows 10 Enterprise LTSB / LTSC to the list of "Latest updates" below. Not everyone can distinguish the corresponding update.

Summary of new Japanese era Windows updates - KB4469068
https://support.microsoft.com/en-us/help/4469068/

we need to use command prompt more often to maniupulate files and it keeps the network heallthy.

Cannot install other language or ssh server because every time i try i got error "Check your Windows Insider Program settings"

This is joke right? I use latest stable release of 2019 Standard not insider preview. I download iso from my MSDN/MAPS site.

Idea: a test = a WEB page detailed and understandable by all the worlds (with image).
BSA - the instructions of 2019 are even less clear than those of 2016, which were already less explicit than those of 2012.
Although there is one URL per test, the explanations are often not understandable. Sometimes the error (or suggestion) seems to indicate something that already exists. Maybe it's the mistake itself that is not clear. In this case, I suggest images that will be more talkative than words (often poorly translated).

3 different icons for the three types of VM please!
Keep the current icon for a main VM. Then, use an icon for the replica and another icon for the secondary replica.

Folder structure (example):

Company (Company is shared as Company)
Sales
Administration
Office
…

Folder Company:
Share permissions:
Everyone, Change

NTFS permissions:
Group “Alle_MAs”, Read, This folder only
Group “Admin”, “System”, Full control
right inheritance, disabled

Supfolders of Company (Sales, Administration, Office):
Folder „Sales“, Group „Sales“, Change
Folder „ Administration“, Group „ Administration“, Change
Folder „ Office“, Group „ Office“, Change

For example, if I delete the folder “Sales”, on the share “Company”, all NTFS permissions have disappeared except for “Administratos” and “System”

Thanks for your help
Michael

Migrations of highly-available VMs from one cluster to another while using S2D and SOFS as a storage solution (NOT hyper-converged) should be supported by VMM.

VMM has built-in functionality to allow migration of a VM from one cluster to another.

This does NOT work with HA VMs when your storage solution is SOFS on S2D. The VM will be placed in pause-critical, effectively a failed migration.

I believe this is a shortcoming on the part of Failover Clustering not properly handling storage communication, but not sure as this action isn't able to be automated outside VMM.

The 1809 version of RSAT does not include the tools required to manage Network Policy Servers (NPAS), and they need to be reinstated for managing these servers on networks.

currently the autounattend.xml is both limited and slow. Things like network setting updates cause reboots, and other things like the Administrator name can't be changed at all.

Windows needs to be more inline with tools like cloud-init in Linux: it should be extremely fast to make boot-strap changes to the OS. In the world of auto-scale, seconds count and autounattend.xml sometimes takes minutes.

it's the new hotness, but more importantly I think it would increase usability if answer files were written in yaml.

from autounattend.xml to powershell, user accounts are managed by base64encoded strings. This is ... frankly ... terrible, as it's not even technically encrypted. Want to see that admin password default in the autounattend.xml file? simply run:

$nextstep = [System.Convert]::FromBase64String("<put it here>")
$finalstep = [System.Text.Encoding]::UTF8.GetString($nextstep)

Please allow hashing/salting to be used for password conifguration, be it from an unattend.xml file or as an option when creating new accounts to allow at least modest protection when passing credentials.