Even though I'd prefer it clickable (and winlogon too) since user32 is still present, even on the most stripped down installation. The new sconfig certainly is better than the 2016 one. With that said, I'm curious how you were licensing the guest OS's on Hyper-V Server? Windows Server Standard is also an option for SMB customers (with VM limits). Where Datacenter is a purchased license and the guest OS's are free. Hyper-V Server and Windows Server Datacenter are the licensing inverses of each other, where Hyper-V Server provided a free host OS and required the guest OS's be independently licensed. AzS HCI also charges based on core usage to scale down for SMB customers. The free trial gives the first 60-days as free for all subscriptions, so that's a value you can take advantage of for production deployments as well. Eval is a special product that is time-bombed and can only be used for a period of time before you must move to a licensed product. The 60-day free trail with AzS HCI is a little different than an Evaluation with a perpetual license. But it's your choice if you want hybrid capabilities or not. and with a goal that it's just incremental on top of a Hyper-V admin's existing skillset. For those looking to augment on-prem with hybrid capabilities, we provide the Azure integration to enhance AzS HCI. The only difference is that it's a subscription model. For a customer that doesn't desire Azure, they can use AzS HCI as they are using Hyper-V today (in WS or Hyper-V Server).
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.
0 kommentar(er)
