I’m not sure that “AuthenticAMD” is any better. There’s probably an entire table of words like this that we should be wary of.
That said, this took me down a small rabbit hole of CPUIDs. I want one with “AMDisbetter!” Or “CyrixInstead”
The standalone Hyper-V Server was last released for server 2019. Not only was this leaner than Server 2019 w/ the Hyper V role, it was available for free.
Hyper-V is discontinued, at least as a standalone hypervisor. It’s only available as an additional role on a full OS.
IOW, it’s a replacement for VMware Workstation, not ESXi, and certainly not vcenter.
You’re giving up your sleep, and by extension your health, to make someone else richer.
You should be pushing that you get the entire day off. And when your manager denies it, and they will because this doesn’t sound like a one-off emergency, insist that you need to call them and wake them up each and every time. If it truly is an emergency, they will be glad that you are keeping them in the loop. When it’s not (and it almost never is), they need to champion your need to make it stop.
Everyone involved needs to feel the pain for the harm they are causing.
Proxmox is missing a lot of enterprise features. If you run a virtualized data center, it’s really not going to cut it. OTOH, if you are a small operation with just a handful of virtual servers, it might be “good enough”.
The obvious alternative was Hyper-V, but it looks like MS is already killing it to force people into Azure.
When you look at enterprise-level hypervisors, there really aren’t a lot of options.
What’s your endpoint management/MDM? It sounds like your org has about 500 PCs, which means you definitely need something to manage them after deployment. That’s where I would start.
If you don’t have an MDM, you need to push upper management that you do. Intune or PDQ are probably right for your size. Each comes with strings and complications, but they will save you a significant amount of time and money in the long run
Everyone suggesting WDS or MDT is overlooking something very important- both are being phased out, and have limited or no support for Win 11.
If you are building a new workflow, you should not build on these tools. You should build on something supported going forward.
Thick/captured WIMs are generally not recommended anyway due to their higher maintenance needs. What are you trying to do in the first place? There are probably better approaches to solve that instead of capturing an image.
It will become a more specialized, niche knowledge. It’s similar to cars. In the 1950s, it was extremely common for regular people to know how to fix their own car. But as cars became more reliable and complex, fewer and fewer now know how. There’s still a definite market for mechanics and mechanical engineers, but it’s a specialty line. You go to college, or generally go through a manufacturer’s training program.
What’s going to change are the expectations and expertise going in. When Microslop wants new developers, or support staff, or whatever else, the candidates aren’t going to be (as) familiar with it going in. They won’t be able to meaningfully apply their knowledge of similar systems and products.
They’ll have to bring back extensive company-led training programs.
This will apply to every large tech company, regardless of field. In your networking example, it would probably be run by Cisco, which isn’t too different from how it is today.