Endpoint360 replaces the aging WinForms console with a fast, browser-native cockpit over your entire Configuration Manager estate: devices, CMPivot, run scripts, software, patching, health, and compliance, in one place. Installs beside your existing site. No new infrastructure.
Runs on your Windows Server · no cloud dependency · air-gap ready · Kerberos SSO
Exploits are weaponized in hours; change boards meet on Thursdays. Endpoint360 closes that gap. Vulnerability feeds become governed remediation campaigns that score, deploy, verify, and document themselves. Your team keeps exactly one job: the decision.
CISA KEV & BOD 22-01 clocks · NIST 800-53 evidence · dual-auth, distinct humans
Estate-wide client health, infrastructure monitoring, and deployment SLAs, with anomaly agents that turn a spike into a governed incident and Knowledge Chat answering questions grounded in your own environment. AI is optional, off by default, and provider-pluggable, including IL4/IL5 paths.
Client health · infrastructure monitor · Knowledge Chat · anomaly agents · SLA tracking
Most consoles show you the problem. Endpoint360 runs the whole loop, and writes the evidence trail your assessor asks for, while it happens.
The feed ingests (connected fetch or offline bundle, your posture decides), reconciles IAVA → CVE → KB, and measures exactly who is exposed. Live, against your site database.
By the time your team sits down, Vanguard has already done everything except decide.
AdminService, direct SQL, CMPivot and the fast channel: one console over all of ConfigMgr. Vulnerability reconciliation maps IAVA → CVE → KB → deployment gap in seconds, a chain DoD admins have walked by hand for twenty years.
The GO / SLOW / NO-GO confidence score is computed from your own live telemetry: catalog readiness, update hygiene, deployment conflicts, client-estate health, and pilot results, with an honest denominator that discloses what it couldn't measure.
Every gate stamps the NIST 800-53 controls it satisfies into an assessor-readable trail: who approved, what the exposure was, when each ring promoted, and the measured compliance that closed it. Audit questions become database queries.
Patch governance built from the regulations backward (BOD 22-01, NIST 800-53, the DISA IAVM process) and run at the speed the AI threat era demands. Do less. Ship faster. Carry less risk. That is the whole design.
A NO-GO blocks execution until a named human accepts the risk in writing. Approval is always human. That line is never crossed.
One console over your whole Configuration Manager estate. Step through the modules: what each one is, and why an AI-era operations team needs it.
The morning briefing for your estate: what changed in the last 24 hours, error trends, infrastructure status, and what needs attention. The whole picture before your coffee is cold.
Reconcile threat feeds against what ConfigMgr has actually deployed. See every exposed device for a CVE or IAVA in seconds, with KEV due dates and CVSS front and center.
A campaign board that scores, deploys, promotes on evidence, and closes on measured compliance, with dual-authorization and a NIST 800-53 evidence trail written as it happens.
Compliance by software update group and collection, deployment rings at a glance, and a blast-radius preview that shows exactly what a deployment will touch, recorded as evidence before you commit.
Drop a package in a folder; it validates, creates the app, distributes, deploys to a pilot ring, and auto-promotes on success, with an approval gate for the rings that need a human.
Find superseded and expired updates cluttering your groups and remediate in one click. Then cluster deployment failures by model, subnet, boundary, or DP to find the one signature behind a wave of tickets.
Watch task sequences move through their state messages in real time (which step, which device, which failure) instead of parsing SMSTS logs after the fact.
Estate-wide client-health scores, a healthy-percentage trend, and the worst clients first with their actual issues (WMI, ccmexec, inactive) so you fix causes, not symptoms.
Overlapping and orphaned boundaries, clients outside any boundary group, distribution-point content status, and site-server health. The plumbing that quietly generates tickets, made visible.
Plus Devices & Device 360, CMPivot and Run Scripts web consoles, Software Catalog, Collection Watchdog, Deployment SLA tracking, Knowledge Chat, the NLP report builder, and the Site Health Map. Every view ships dark and light, responsive to 375px, with real loading, empty, and error states.
Endpoint360 ships five AI capabilities that work where AI usually can't. Every answer is grounded in your own site data, never a generic guess. And the whole layer is built for shops where "we ran it through a chatbot" fails the audit.
Plain-language questions about your environment, answered from your site database, your configuration, and the product docs, with the sources cited inline.
Background agents watch estate signals around the clock and turn a spike into a governed incident with an owner and an SLA clock, not a chart nobody opens.
Deployment failures cluster by model, driver, subnet, and DP. Then the AI names the signature in one sentence a human can act on.
Describe the report you need and get validated SQL against your site database. The safety layer fails closed: read-only, schema-checked, and audited, so the worst case is "no report," never "wrong data."
Campaign evidence compressed into the one page an approver actually reads: severity, exposure, confidence score, the weakest check, and the deadline math. The human decision, fully briefed.
Troy has worked with this product line for 28 years, starting with SMS 1.0 in 1998. He went on to support Configuration Manager at Microsoft itself, across every sector of government and a range of industry verticals, on some of the largest deployments in the world.
"I've seen a lot of what works and what breaks. Like so many admins still running this product, I spent years wishing the product group would ship a web console. Eventually I stopped wishing and built it."
That is why Endpoint360 feels different: every feature started as a real ticket, a real Patch Tuesday, or a real audit question. Lean by design, no layers, no bloat, and support that talks to the engineer who built it, not a tier-1 script.
We're onboarding early-access customers now: enterprise and government, connected or air-gapped. Whether your team says ConfigMgr, SCCM, or MECM, this is the console built for it.
