such as PowerShell, Windows Admin Center, and all the existing MMC tools work as well (Failover Cluster Manager, Hyper-V Manager, etc.). That's why it uses the same tools and management experience. One of our very intentional goals with AzS HCI was for it to be familiar and love current Hyper-V admin's.

but I want to understand what's most important to you. which value is important to you? We have lots of room to further optimize the composition of AzS HCI. NET Core with PowerShell7?Ĭan you elaborate on your footprint feedback? Disk drives for the boot device are plenty big these days. NET'less? Would love to better understand the scenario / goals. I'm curious why you want to remove PowerShell, as that obviously has some major management trade-off's? I'm assuming your goal is more about.

So it wouldn't have been a differentiator per se. The new sconfig is in AzS HCI, Windows Server 2022 core, and if we had shipped a Hyper-V Server 2022 it would have been in there as well. We innovated sconfig, and it is true that it now has dependencies on PowerShell.

Server 2022 essentials