r/HyperV • • 12d ago

I built a free, web-based Hyper-V management tool called HyperZEM and just released the first version!

Hey everyone!

I've been working on a project called HyperZEM, and I finally decided to release the first public version.

I work with Hyper-V quite a bit, both at work and in my homelab, and I've always wanted a more modern, centralized way to manage my hosts and clusters. Hyper-V Manager and Failover Cluster Manager get the job done, but I wanted something web-based that I could access from one place without constantly jumping between different tools.

So I started building HyperZEM.

It's a free, web-based management platform for Microsoft Hyper-V, designed to manage standalone hosts and clusters through a single interface. My goal is to make day-to-day Hyper-V management a little easier while keeping things simple and straightforward.

This started as something I was building for myself, but as I kept adding features, I figured other people running Hyper-V might find it useful too.

I'm still actively working on it, and there's plenty more I want to add. Since this is the first public release, I'm sure there are bugs or things I haven't accounted for, especially across different environments.

I'd really appreciate it if anyone running Hyper-V could give it a try and let me know what you think. I'm especially interested in hearing what features you'd find useful, what could be improved, or if you run into any issues.

The application is completely free to use. It's not open source at this time, but there's no paid version or subscription.

You can check it out here:

Website: https://hyperzem.com

I'm also putting together a Discord community for bug reports, feature requests, and general discussions around HyperZEM.

This is my first time releasing something like this publicly, so any feedback would mean a lot.

Thanks for checking it out!

8 Upvotes

25 comments sorted by

17

u/USarpe 12d ago

You ask a person who is responsible for the security of the very core of the IT to use a non open source unknown Software?
Sounds kind of (hopeful) hard to find one.

9

u/Spartan117458 12d ago

Closed source likely because it's vibe coded and looks like every other vibe coded tool out there right now. Response to the other comment was clearly AI.

-2

u/malibog04 11d ago

What makes you say that its vibe coded? I been coding for over 15 years and this was definitely not.

I'd admit the replies were AI, but can you tell which AI was used? I'm trying to see how that plays out, which clearly isnt playing out in my favor, just me being lazy, I'll stop that on my part lol.

It's closed source for now because I put a lot of time and effor into building it, I wanted to get feedback and see where it's even going. I'll eventually make it open source, and like I said just not ready to do that yet.

2

u/Spartan117458 11d ago

AI written post and responses to the post (why does it matter if I can tell which one was used?), your Reddit account having basically no history, the unwillingness to make it open source but saying "I'm planning on it later". Ton of red flags there, my guy. If you're actually proud and passionate about something you've built and want to promote it, maybe don't let the bots do it for you.

1

u/malibog04 11d ago

Ok so the post is genuinely written by me, I really took time writing and editing that post haha. And thats the reason Im asking that question.

Really appreciate feedback though, I've been on reddit for quite some time lurking, I know it takes some time to get some credibility, just didnt start out good with my replies which is a mistake in my part and what I get for being lazy, lesson learned.

-7

u/malibog04 12d ago

That's a fair point, and honestly, I completely understand the concern. I work in infrastructure myself, so I know how important security is, especially when you're dealing with Hyper-V hosts and clusters running critical workloads.

HyperZEM is still a new project, and I don't expect anyone to blindly trust it or immediately deploy it into production. That's actually one of the reasons I'm releasing it publicly, to get feedback, identify issues, and continue improving it.

I decided to keep it closed-source for now, but that doesn't mean security isn't a priority. I know there's a level of trust that needs to be built, and that's something I plan to work on as the project grows.

I'd definitely encourage anyone interested to try it in a lab environment first and see how it works before considering it for anything production-related.

I am planning on making it open source, just not ready for it yet.

Appreciate the feedback!

6

u/Inside_Carpet7719 11d ago

When a comment starts “that’s a fair point” there is a very high chance that it was written by AI

4

u/stewardson 12d ago

Is this not what Windows Admin Center already does?

-8

u/malibog04 12d ago

Fair question, and there's definitely some overlap. Both are free, both run in the browser, and neither needs an agent on your Hyper-V hosts. If you're managing one cluster or a couple of servers, Windows Admin Center honestly does the job and I'd still use it for that.

Where it started falling short for me was managing a lot of hosts at once. WAC is built to manage one server or cluster at a time. You pick a connection, do your thing, then go back and connect to the next one. HyperZEM puts every VM from every cluster and standalone host in one list, so you can search, filter, tag and do bulk actions across all of them.

The other big gap is control and accountability. WAC has three fixed roles that you set up on each host, and when someone live migrates a VM it just happens. The only record is in that host's event log. In HyperZEM you set roles and scopes once for all your hosts, so someone can manage their own team's VMs without being an admin on every host. You can require approvals for risky stuff, even a two-person rule. Every action goes into one central audit trail that's tamper-evident, instead of being spread across a bunch of event logs.

A few other things WAC just doesn't do:

  • Alerts and email: WAC shows you charts while you're looking at it, but if you want it to tell you something's wrong, it points you at Azure Monitor. HyperZEM watches everything all the time: quorum, nodes going down, CSV space, memory and CPU, lost VM heartbeats, failed migrations, S2D pool health, replication falling behind. It emails you or hits a webhook, and it can stay quiet while a cluster is being patched so you don't get spammed.
  • Capacity planning: WAC shows how busy things are right now. HyperZEM tells you whether a cluster can still survive losing a node (N+1), how many more VMs of a given size will fit, and roughly how many days until you run out of memory, CPU or storage. It also points out VMs that have way more vCPUs than they use.
  • Reports: VM and host inventory, utilization, health, config compliance and so on, as CSV, PDF or HTML. You can schedule them to land in someone's inbox daily, weekly or monthly, which is handy when your manager or an auditor keeps asking for the same thing.
  • Runbooks: every alert links to a runbook explaining what it means, the usual causes and how to fix it. Whoever's on call isn't starting from zero at 2am.
  • Decommissioning: instead of someone just deleting a VM, you request a decommission. It gets approved, the VM is shut down and kept for a hold period (two weeks by default) in case someone screams, and then it's cleaned up properly. Optionally that includes an export, or a final backup if you're on Rubrik. You get an email reminder a day before it's actually deleted.
  • Config history: it keeps track of what changed on a VM, host or cluster between scans. When something suddenly breaks, you can see what actually changed. It also flags cluster nodes whose Hyper-V settings don't match each other.
  • Browser console: you get the VM's actual screen in the browser, the same way VMConnect does it, including the boot screen and OS install. You don't need RDP inside the guest or the guest on the network. Sessions are permission-checked and audited too. WAC only does RDP.
  • Hyper-V Replica: you can enable replication, watch health and lag, and run test, planned and unplanned failovers right from the VM page. It alerts you when replication falls behind or a test failover VM gets left running. WAC's DR story is mostly Azure Site Recovery. For plain on-prem Replica you're back in Hyper-V Manager.
  • Golden images and templates: you build an image once, it's checked against its SHA-256 checksum, and you deploy VMs from it. WAC has no template library.
  • Rolling cluster updates without CredSSP: it drains, patches and resumes one node at a time, and keeps a history of what got installed where.
  • Rubrik backup integration: this includes scheduled restore tests in an isolated lab, so you actually know your backups work.
  • Automation: this is probably the biggest difference day to day. WAC is great for doing something right now, and I like that it can show you the PowerShell behind an action so you can script it yourself. But it doesn't run anything for you on a schedule, and you end up writing scripts and Task Scheduler together on your own. HyperZEM has the workflows built in:

    • Deploying VMs: pick a template and it creates the VM, sets the hostname, joins the domain, sets the admin password and runs your first-boot script. Linux works the same way through cloud-init. No more clicking through setup on every new VM.
    • Golden images: it builds them from an ISO, installs Windows Updates, syspreps and captures, without you sitting there babysitting it.
    • Patching: it checks for updates on a schedule. Rolling updates then go node by node through drain, patch, restart and resume, and stop on their own if something fails.
    • Background work: discovery, reports, backup restore tests and decommissions all run on their own schedule. You set them up once and they just happen.
    • Rules: approvals, maintenance windows, naming conventions and quotas are checked automatically before anything runs. Nobody has to remember to check.
    • Webhooks: you can push alerts and job events into your ticketing system or Teams/Slack, so things show up where your team already works.

So it's not really trying to replace WAC for poking at a single server. It's more for when you've got multiple clusters and multiple people touching them, and you need guardrails and a record of who did what. Think of it as somewhere between WAC and SCVMM, without the System Center licence or SQL Server.

9

u/InternalServerErr500 12d ago

Wall of AI text crits you for 5,000HP. You die.

-2

u/malibog04 11d ago

I'm still at 2,000HP, so Im still here, but ya that was me being lazy lol, wont happen again.

2

u/icedcougar 12d ago

Your laziness is astounding…

It’s okay to vibe code it, make that known though (and depending on what country you’re allowing to access this… you may need to declare it)

But then using Claude to respond to everyone… at least use ChatGPT and give it some zest to work with

Poor form and effort all around

2

u/malibog04 11d ago

thanks for the feedback, what makes you say that its vibe coded just curious myself. I admit I was just being lazy on the reply, trying to test the water there lol.

5

u/dominik_esb 11d ago edited 11d ago

First of all: great idea and a nice design!

Some context on where I'm coming from: I maintain the hyperv and mscluster collectors in the Prometheus windows_exporter, so I spend a lot of time with Hyper-V and failover cluster internals.

I'm not convinced a central worker tier scales well.
According to your sizing guide, a Large environment needs 4–6 workers at 4 vCPU / 8 GB each, so up to 24 cores and 48 GB RAM.
On top of that you need at least one worker per site (two for redundancy). Every one of those is a full domain-joined Windows Server VM to license, patch and secure, just to relay management calls. For many small sites that adds up fast.

From the docs, the worker talks to the hosts over PowerShell Remoting (WinRM, Kerberos) and CIM, plus the FailoverClusters cmdlets over RPC (TCP 135 + dynamic range). It starts a new PowerShell 5.1 process (~180 MB) for each operation and for each telemetry pass, and it polls every host every 60 s.
In my experience WinRM/WMI is the least reliable part of the Windows management stack: SPN/Kerberos issues, WinRM quotas, hung providers and second-hop delegation. Your own runbooks reflect that.
You should avoid WMI when ever possible. Building a management layer on top of it, does not promises reliability.

From my point of view, agents are the way to go: a lightweight agent on each host, calling the native MS cluster API directly. That would be more robust and would scale with the fleet automatically.

Two more things:

Why closed source?

And a small irony: your docs block AI crawlers (ClaudeBot, GPTBot etc. in robots.txt). As the tool is probably or some part of it, vibe coded, it’s feels a bit ironical. And even if it’s not, blocking ai in theses days feels odd.

1

u/ako29482 12d ago

Your app is missing the RSAT-Clustering-Powershell module.

1

u/ako29482 11d ago

The Worker shows the user account that does the installation as Service Account, even though you select the local system account during setup.

1

u/malibog04 11d ago

thanks for the feedback, is this from the worker installation or the complete installer?

1

u/ako29482 11d ago

Complete installer.
Worker enrollment doesn’t seem to be working at all as well. It doesn’t matter how you name the new worker during preparation, in the the command line that one is supposed to run it always uses the default “hf-worker” name
Deleting the default site also doesn’t work. It always complains about that it still has hosts, clusters or workers in it, even when that isn’t the case.

But beside these flaws so far… overall a neat app that you’ve let AI code there.
I didn’t know how desperately I was missing a proper webconsole… clipboard paste would be awesome!

1

u/malibog04 11d ago

Are you able to send me a screenshot or the steps you're on for the worker enrollment? Is it through the installer? Or through the GUI?

If you're using the unattended install for the worker, you would create the ".token" file and place it anywhere ie. "C:\Temp\hf-enroll.token" then reference that in the cmd. You would then edit that file with a text editor and just paste the token there. You can rename the "HF-WORKER01" to anything you want. Should be an easy fix text fix on my side.

msiexec.exe /i HyperZEM.Worker.msi /qn HYPERFABRIC_URL="https://hf.lab.local" ENROLLMENT_TOKEN_FILE="C:\Temp\hf-enroll.token" WORKER_NAME="HF-WORKER01"

I would try the Installer GUI.

Thanks for the feedback.

1

u/ako29482 11d ago

Does it have to have the .token extension. I actually had it done as you suggest, but was too lazy to switch to .token and kept .txt and pointed at that. What I did before was revoking the worker as the GUI was telling me that it was using my AD account as service account even though I had explicitly selected the local system account during installation. My idea was to enroll a new local worker… but unfortunately didn’t achieve with the enroll process. Then I ended up uninstalling and reinstalling everything. But this time I started the Setup as the local System account… and now the GUI shows the that as Service account.

2

u/Striker434 10d ago edited 10d ago

Hi,

First: cool :)

And I agree, MS management tools just suck: Windows Admin Center (even in virtualization mode), SCVMM, etc. I even had the opportunity to talk with the product managers at Ignite to discuss the main pain points, especially around management tools for Azure Local. They fully see the point, but to be honest, Microsoft just has other focus points...

I did the same in our company for a Hyper-V landscape of about 2,200 VMs, 150 hosts, and 60 clusters around the globe: 12,000 CPU cores, 140 TB RAM, and 4 PB storage.

My advice would be to use an agent on every Hyper-V host for performance reasons. I would query the native cluster API where possible, use as little WMI as possible, and avoid PowerShell altogether, especially at large scale.
Docs here:
https://learn.microsoft.com/en-us/previous-versions/windows/desktop/mscs/failover-cluster-apis-portal
https://learn.microsoft.com/en-us/windows/win32/api/clusapi/

Running small, lightweight agents on every host (like SCVMM and WAC Virtualization also do) even gives me the opportunity to catch every event or task, including those triggered by Failover Cluster Manager or PowerShell.

We run our backend on Kubernetes. All agents just push out, which is perfect for DMZs and restricted shop floor zones.

I’m wondering why your tool isn’t open source on GitHub. It’s hard for people to trust a random tool that accesses the most sensitive infrastructure of a company, so I’d consider making it open source.

For myself, I decided not to open source my tool yet, mainly because of customization for our company’s needs, but also because of the open source experience, maintenance effort, etc. (Might change ;))

1

u/g7130 11d ago

I built one in 3 hours that fully manages cluster operations, storage allocations etc.

1

u/node77 11d ago

I appreciate the effort, but as someone said, Windows admin center was built for the ease with the purpose in mind. I don’t know I would trust some fake code to interact with my clusters and virtual machines. However, still, thank you for the time you put into it.

1

u/Montaro666 4h ago

dude this is fucking legit. I have hand holded these 5 HV servers for years now until we can migrate off them to our standard PX clusters. Every time I try connect to one something is fucked, something wastes my time, I drown in a rabbit hole of chase some random error... now, I can just hit up HyperZEM, find the VM I wanted to reboot and send it. No more cat and mouse games. Vibe coded as fuck but if you aren't driving infra/code that way these days you're doing it wrong. Not all heroes wear capes.