Hyper-V

You know, I remember ESX, I think the first version of ESX I ever used was version 3.

And I was certified on 4, certified on 5, and then after that I went whole hog Hyper-V.

But, I mean, when I did use that platform, it was incredible.

I mean, they really brought virtualization to the vast majority of enterprises during that time frame.

And like, okay, somebody gets on my home network.

Well, I don't really, I don't keep like financial data anywhere in the house.

So if you broke my home network, what you're going to find is a great big, like my Hyper-V deployment that I use for writing stuff.

So domain controllers and Hyper-V hosts and all kinds of stuff.

Office received twenty-two critical fixes, including vulnerabilities that could potentially execute code when a malicious file is merely previewed.

Hyper-V flaws could enable attacks from a compromised guest virtual machine against its host.

The broader September patch cycle is similarly busy.

Adobe fixed more than one hundred and seventy vulnerabilities, including an actively exploited unauthenticated Commerce and Magento RCE zero-day.

So as you talked about, you can deploy it on almost anything.

If you got VMware infrastructure, Hyper-V, Xen, Scale, Nutanix, you name it, bare metal hardware, Windows 11 desktops, you name it, you can run AVD on it and use that as your remote session manager, which is great.

And I think it really does provide a really good, probably more cost-effective option than things like VMware Horizon, Citrix and RDS.

I hate running RDS, its Remote Desktop Service is so insecure and it's a lot of maintenance and this is a much better option.

You also, if you're, when you Arc-enable that virtual machine, it gets...

You can assign it permissions and all sorts of stuff, but the main challenge is Arc-enabling that virtual machine.

The way that I've been doing it on our Hyper-V cluster is with Azure DevOps.

So I deployed a DevOps agent on the Hyper-V cluster and created a managed service account and gave it permissions to the Hyper-V hosts, and it runs, the agent on that DevOps virtual machine runs with, in the context of that GMCA account, right? The group managed service account.

And then in your backup and running, there's very, very little that you have to do from that point.

So with this one, what I actually ended up doing is I installed Proxmox, which is like a virtual machine host, like Hyper-V or VMware, that kind of a thing, but open source and free.

Yeah.

Well, it has a free version.

How to read the structure of an Ethernet frame.

So that's come up in Hyper-V a few times when it's like it doesn't look like we're getting VLAN items correctly while Hyper-V's networking stack is visible to Wireshark.

Maybe if you're doing SRI, IOV, it may not catch all of it.

But for a standard switch, it does.

The screenshot tool was one of them, but I also included client virtualization in this list.

So that would be a hypervisor running on my daily driver.

For Windows, that was always client Hyper-V for me.

On Linux boxes, this was always KVM, the kernel virtual machine.

So there's a total addressable market for virtualized infrastructure.

You got VMware, you got Citrix, you got Hyper-V, you got a few other things.

Basically, VMware was about as large as it was ever going to be.

No matter how much advertising Broadcom did, no matter how many salespeople Broadcom put out into the world, VMware probably just wasn't gonna grow any bigger than it was, right? This is just how it is.

returned to the host when containers are idle instead of being held indefinitely.

Windows developers are getting a notable change here, moving to a VM built and maintained directly by Docker, aiming for Hyper-V level isolation combined with WSL2-like

speed.

The same engine also powers Docker Sandboxes, so improvements in future enterprise admin controls for governance.