User Profile
JanRingos
Iron Contributor
Joined Jun 15, 2017
User Widgets
Recent Discussions
Re: Hyper-V Server 2022
From the perspective of the topic of this thread: Every single one of our business partners, who was running Hyper-V Server 2019, is either still running that, moved the machine to Server 202X Core (where the license terms allowed), or is moving to other hypervisors. AFAIK only single one was seriously considering "upgrading" from Hyper-V Server 2019 to Azure Stack HCI, and, from what I'm told, the Microsoft reseller representative was laughed out of the building after presenting the quote. But we are very small ISV so don't consider our experiences to be a representative sample.676Views0likes0CommentsRe: Hyper-V Server 2022
I don't know precise details, but one of our customers (small margin-operating factory floor) has one single expensive beefy server, running Hyper-V Server 2019, onto which they migrate workload VMs for whose they need immediate compute capacity (or network throughput), and then later migrate them off to more efficient HW. Those VMs are running various versions of Windows Server, older, newer, some even Client OSs. I'm told that having Hyper-V Server on that machine saves them tons of money on licenses, and headache figuring out how to have that legally. The alternative is having properly licensed Datacenter Server, and upgrading all the workload VMs to be EULA compliant.2KViews0likes0CommentsRe: Hyper-V Server 2022
You obviously haven't read many scenarios presented on the last 10 pages here. But I will repeat one: One of our customers run Hyper-V Server 2019 and regularly swaps various licensed VMs on it. While licensing allows them run the 3rd virtual host only instance of the licensed Servers, installed as you described, it certainly wouldn't pass audit if caught mismatched, i.e. the guests version and key not matching the host(s). Hyper-V Server 2019 alleviated that concern significantly for them.4.6KViews0likes0CommentsRe: Anyone else having a problem clean installing 25083?
Yes, the ISO won't boot for me too. But upgrade, or booting from older ISO and then starting the installation from the new ISO, or deploying through dism, works. Defrag doesn't work for me in this build, but that's whole different story.1.1KViews0likes0CommentsRe: Hyper-V Server 2022
> What if there was a mode that had significantly reduced functionality but allowed basic VM hosting? Such as maybe removing enterprise grade / production critical features... like clustering / HA? VM mobility? DR capabilities? Yes. That's what significant portion of people here would love to see. Separate product "Azure Stack Lite" or installation option, without the features you mention (although keeping VM migration would be sweet), and provide that product on the same licensing terms as Hyper-V Server 2019. As I wrote before, we have currently handful of Hyper-V Servers both in lab and production, that VMs (licensed in various ways) get moved onto and out as needed. And there's currently not a good and proper way forward with this scenario without incurring additional licensing costs.14KViews0likes0CommentsRe: Hyper-V Server 2022
We innovated sconfig, and it is true that it now has dependencies on PowerShell. 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. So it wouldn't have been a differentiator per se. Yeah, I understand that. The new sconfig certainly is better than the 2016 one. Even though I'd prefer it clickable (and winlogon too) since user32 is still present, even on the most stripped down installation. But I guess you don't want to close the door to bringing back something like Nano Server on bare metal ...which would be awesome IMHO. 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 .NET'less? Would love to better understand the scenario / goals. Are your feelings different about .NET Core with PowerShell7? Can you elaborate on your footprint feedback? Disk drives for the boot device are plenty big these days... which value is important to you? We have lots of room to further optimize the composition of AzS HCI... but I want to understand what's most important to you. This is actually somewhat tangential to Hyper-V Server, but: A significant portion of our (as a company) projects are in telco domain. One of our largest partnership involved mixed proprietary communications routed and processed on a proprietary hardware. The specs of the hardware were well under the officially supported Windows Server minimum, e.g. 4 GB of disk space, so we properly stripped down the OS. Something like Intel's DE3815TYKHE. The small on-board storage allows one to deploy Hyper-V Server onto it, but freely swap the SATA disk with VMs to run. Not the actual scenario in this story though. If you are asking why Server SKU and not IoT Enterprise LTSC, then basically the latter wouldn't fit, and the partner had procured Telco SKU licenses. We've even deployed some as the aforementioned Nano Server 2016, but that wasn't usually possible due to various driver incompatibilities, and even then we reverted most due to partner being uncertain if the licensing applied properly. On several of the larger devices, used in backbone, we needed to isolate a problematic legacy voice software from our services, and for several reasons, we deployed them into different VMs, with Hyper-V Server 2016 as host. Now, yes, the licensing would allow us to use the 3rd instance to manage the VMs, but using stripped-down Hyper-V Server, we saved about 0.5 GBs of disk space. Insignificant amount in many scenarios, but this time it helped a lot. Side note: Uninstalling WoW64 leaves behind about 300 MB of unused DLLs in SysWow64. I've reported it both here and on FeedbackHub, but probably it's not a priority. Just FYI. I would not normally remove PowerShell nor .NET, if the space constrains allowed, because doing so often breaks Windows Update, but luckily these installations weren't updated (on isolated network), classic tools were enough to manage what I needed to, and the partner's administrators had their own ways. And yes, PowerShell7 is great, especially since it's self-contaned. I can bring it on a flash drive, plug it onto any stripped down installations of mine, and it works. It even runs on the Nano Server (although I've so far tested it only in container, not in 2016 VM or bare-metal installation). The last part of my footprint concerns is lab testing. When simulating higher amount of nodes, through swarm of local VMs, the used disk space quickly adds up. It's good being able to remove everything not needed and minimize the images. And this applies to Hyper-V Server too, since I've discovered the support for nested virtualization. I am using that SKU for some middle layer VMs. Now with AMD-V support I might be using it even more ...well in Server SKU if Hyper-V Server 2022 is not coming. That's why it uses the same tools and management experience... such as PowerShell, Windows Admin Center, and all the existing MMC tools work as well (Failover Cluster Manager, Hyper-V Manager, etc...). If some of the basic MMC tools, the GUI part, were available locally, I wouldn't be even mad. Not all things from ServerCoreAppCompatibility packs, just a couple of locally useful tools, e.g. diskmgmt.msc. The 60-day free trail with AzS HCI is a little different than an Evaluation with a perpetual license. 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 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. So some trade-off's. AzS HCI also charges based on core usage to scale down for SMB customers. So, do I read it right that we CAN continue to use Azure Stack HCI, after the 60-day free trial, the way we use Hyper-V Server now? Given we don't connect any Azure subscription and the guests are properly licensed?189KViews1like0CommentsRe: Remote Desktop users have access to shutdown/restart, how disable these ?
hasanemresatilmis Note that this affects only the GUI options. The user still can shutdown the system from command line or third-party application. To prevent more resourceful users from shutting down the system, remove their right to do so. Still in gpedit.msc, go to Computer Configuration / Windows Settings / Security Settings / Local Policies / User Rights Assignment, edit the "Shut down the system" privilege and remove "Users" from the list.158KViews4likes5CommentsRe: Any chance to see preview builds of Hyper-V Server?
Elden_Christensen Quick follow up and questions, if I may: I've found some old VM and ISO backups and there actually were previews for Hyper-V Server. The ISOs were named Windows_InsiderPreview_ServerHypercore_17692.iso (till 17744). The Azure Stack HCI is very interesting, but the preview available is based on build 17784, which isn't exactly recent. Would you know when/whether newer ones will be available? Also Hyper-V Server licensing has important restriction, where it forbids from running production software (other than management tools) directly on the host. I haven't been able to find anything detailing this regarding Azure Stack HCI. Would you know where I can find this info?1.4KViews1like1CommentRe: Any chance to see preview builds of Hyper-V Server?
I think I saw a few preview builds of Hyper-V Server some time around builds ~17700, but I might be remembering it wrong. NVM, it's just my personal affinity for this type of things. The Azure Stack HCI SKU is new to me. Thank you for pointing it out. It seems super interesting, especially as both I, and we as a company, were somewhat vary of cloud deployment, at least until recently. I'll try it out today.1.5KViews1like0CommentsAny chance to see preview builds of Hyper-V Server?
Great to see LTSC builds flighting again. We've already started some small-scale preliminary testing, and all is going great so far. But as I have also plain Hyper-V Server deployed here and there, it would be nice to try that one too. It doesn't need to follow weekly cadence. Not at all. Just when there are some substantial changes to networking merged. That'll be more than enough.1.6KViews1like4CommentsRe: Minimizing Server footprint
Removing Windows Defender was basically a part of an experiment. Generally we keep it. I do use devices without the Defender, but only in controlled environment, behind NAT and firewalls, or totally without physical connection outside. Although on a single core 5W Atom, removing Windows Defender can make a world of difference in apparent performance.4KViews1like1CommentRe: Minimizing Server footprint
If you are deploying on regular-sized SSD and without using the tricks I've mentioned above, then the difference between Core and GUI is certainly unremarkable. But when you find yourself trying to put to use a few devices with 3.7GB embedded MMCs, it's nice being able to do without allocating more hardware.4.1KViews1like3Comments
Recent Blog Articles
No content to show