SysAdmin Weekly - 054 - Windows Admin Center in 2026: Good Tool, Broken On-Ramp?

[asyrewicze]

Hey everyone!

This week Eric Siron and I get into Windows Admin Center, the tool Microsoft keeps pointing us to as the future of Windows management. Short version: the tool is useful once it is running, but getting there on an all-Core Server 2025 lab took me four hours and a from-scratch certificate authority. So we walk the whole thing, gripes and all.

What we cover:

• The 60-day self-signed cert trap, and why letting it expire can leave you with no UI to swap it.
• The four-hour gauntlet: ERROR_DS_RANGE_CONSTRAINT, a web server template that blocks computer requests, a blank SAN that silently kills the HTTPS binding, and the red herrings in the logs along the way.
• What WAC actually gets right once it is up, and where it still falls down in daily use.
• Azure Arc, the "let's pull you into the Azure portal" energy, and who WAC is really built for.
• Does it move the needle for managing Windows long term? Our honest verdict.
• Plus a News React on open-source AI, China's Kimi K3, and talk of a US federal clampdown on open-weight models, and a Nerd Hour on the KVM-to-Hyper-V lab rebuild.

Relevant Links Below!

Podcast Episode - YouTube
Podcast Episode - Spotify

Here is the one I want to hear from you on: have you actually installed Windows Admin Center in a Core or workgroup environment, and did the on-ramp bite you the way it bit me, or did you get it running clean? What finally made you stick with it or walk away?

[yllekz]

I just finished removing it for our team recently. None of us found WAC incredibly useful overall and we grew tired of having to care and feed for it with its frequent updates and certificate management. Like you touched upon, the idea of the suite is a noble one, but unfortunately it was built strangely and doesn't offer the speed and efficiency of the consoles it wishes to replace. What really killed it for me personally was the notion that it had no tabbed management nor ability to very quickly flip between multiple servers. As a sysadmin I may quite often have Powershell, MMC and RDP windows open in mass quantities. WAC can offer quite a few of these but if you are needing to bounce around between servers simultaneously, WAC had no answer to that challenge. Like you said in the episode, I was like "why am I bothering with this?" and went back to RDPing into servers so I didn't have to pay the time penalty.

I never had the "pleasure" of installing it, but I also remember it had a bizarre quirk (maybe bugs, unsure) where if you logged in by typing your username as username@domain.com and not domain\user, you would not be able to connect to systems with PowerShell because I guess it was pulling your username (exactly as typed at the login box) as the username for random things. I don't know if they ever fixed that, but that was wild.