Configuration Manager 2609: A ConfigMgr Admin's Wish List

Microsoft has officially set the stage: version 2609, scheduled for September 2026, is the first annual release of Configuration Manager under the new yearly cadence. With Microsoft pivoting innovation toward Intune, ConfigMgr 2609 is being positioned as a stability- and security-focused release rather than a feature showcase. After 20+ years in the trenches with SMS, SCCM, and MECM, here's my wish list — built from the daily gripes I and so many other admins live with.

The Daily Pain Points That Need Fixing

1. The Console Still Feels Like 2012

Let's be honest: the ConfigMgr console is functional, but it hasn't aged gracefully. Right-clicks deep in nested nodes, modal dialogs stacked five-deep, refreshes that hang on large environments — it's a productivity tax we pay every day.

Wish for 2609: Modernized console performance, async loading on large collections, and consistent right-click behaviour between the Devices node and Collection > Show Members. While we're at it, give us a proper dark mode.

2. Dashboards and Reports Disagree With Each Other

Open the console, you get one compliance number. Open the SSRS report for the same deployment, you get a different one. Open CMPivot, you get a third. Which one do I trust when leadership asks?

Wish for 2609: A single source of truth for deployment state, with timestamped reconciliation between the console summary, SSRS reports, and the underlying SQL views. If they can't match, at least tell us why.

3. Boundary Groups Are Still a Nightmare at Scale

Anyone managing 3,000+ subnets across a federated environment knows the pain. Every network change ripples into ConfigMgr. Clients fall outside boundaries silently. Content goes to the wrong DP. PXE breaks because someone added a VLAN without telling us.

Wish for 2609: Smarter boundary diagnostics — proactive alerts when clients land outside defined boundaries, a visual boundary overlap map, and bulk import/export that doesn't fight you. IP range-based recommendations would be welcome over the legacy subnet model.

4. Distribution Point Health Is Still a Babysitting Job

Disk full. WSUS sync broken. IIS app pool crashed. Content library corruption. DP-related tickets are the bread and butter of any sizable ConfigMgr team, and they still require manual investigation across log files that haven't changed in a decade.

Wish for 2609: Built-in DP self-healing for common issues (disk pressure cleanup, IIS recycle on known errors, automatic content library rehydration), and a unified DP health dashboard that shows me everything in one pane instead of clicking into each one.

5. Software Update Point and WSUS — The Pain That Never Ends

WSUS database bloat, deprecated drivers sync, classification mismatches, declined updates re-appearing after a sync — every SCCM admin has WSUS scar tissue. And with Microsoft signalling reduced WSUS investment, we're stuck supporting a dependency that's clearly on borrowed time.

Wish for 2609: Either fix WSUS for good or give us a fully supported native replacement that doesn't require us to migrate to Intune for patching. A managed, ConfigMgr-internal update catalog with cloud-backed content delivery would change my life.

6. SQL Replication Troubleshooting Requires a PhD

DRS backlog. SSB queues stuck. spdiagdrs. The day a CAS-to-primary replication breaks, you cancel your weekend. The tooling for diagnosing replication issues is buried, log-driven, and assumes you already know what's wrong.

Wish for 2609: A first-class replication diagnostics view in the console — current backlog, broken messages, last successful sync, and one-click reset for stuck queues. Stop making us drop into SQL Management Studio for routine triage.

7. "Are You Sure?" Should Be a Standard Prompt

Deploying to All Systems by mistake remains one of the easiest, most catastrophic clicks in ConfigMgr. The deployment wizard summarizes the action, but there's no firm confirmation step before that policy hits 50,000 endpoints.

Wish for 2609: A mandatory confirmation modal showing target collection name, member count, software being deployed, and required vs available status — with a typed confirmation for collections over a configurable threshold.

8. Client Health Was Weak Last Week

Most environments hover at 60-70% healthy clients. The Client Health Dashboard introduced years back was a start, but it doesn't give actionable remediation. We're left writing PowerShell to reinstall the client, fix WMI, repair certificates — work that should be one click.

Wish for 2609: Native, opinionated client remediation. Detect WMI corruption, ccmexec stopped, certificate expiry, or registration failures — and offer a guided fix from the console. Bonus points for trend graphs showing client health drift over time.

What 2609 Probably Will Be (And What We Should Push For)

Microsoft has been transparent: 2609 is the first annual baseline under a stability-first cadence. Expect security hardening aligned with the Secure Future Initiative, lifecycle improvements, ARM64 polish following 2509, and incremental fixes rather than headline features. That's fine — for many of us, on-prem ConfigMgr is mission-critical infrastructure that doesn't need shiny, it needs solid.

But "stability and security" shouldn't be code for "we're not fixing the friction." The gripes above aren't feature requests — they're paper cuts that erode admin productivity every single day. The annual release model gives Microsoft a longer runway to actually polish these areas. Let's hold them to it.

Final Thought

Configuration Manager isn't going away. Even with Intune as the strategic direction, hundreds of thousands of enterprises — including the public sector environments many of us work in — will run ConfigMgr for years to come. A maintenance-focused cadence is the right call, but only if maintenance includes fixing the things that have annoyed admins for a decade.

What's your biggest ConfigMgr gripe? I'd love to hear what you're hoping makes it into 2609. Drop me a line — let's compare notes.

— Christopher N. Hazlitt, IT Technical Advisor