Ask most endpoint teams how current their view of the estate is, and the honest answer is: it depends when the last cycle ran.
That isn't a criticism of the people running Configuration Manager. It's how SCCM was designed.
By default, ConfigMgr refreshes hardware inventory every seven days. Clients check in for new policy every 60 minutes.[1] (opens in a new tab) For most of SCCM's life, that was fine. Change moved at the pace of a maintenance window.
It doesn't anymore.
Frontier AI models have now turned newly disclosed vulnerabilities into working exploits in hours.[2] (opens in a new tab) An exploit that moves in hours, against an inventory that moves weekly, isn't an inconvenience. It’s a design problem.
Turning the dial doesn't close the gap
The obvious answer is to shorten the intervals. You can. But:
Real time isn’t a dial you can turn up. It’s an architecture that removes the wait altogether.
This is what real-time looks like
Tanium asks your estate a question and gets the answer back in seconds, across hundreds of thousands of endpoints. Not the result of last week's scan. What's true now.
And you don't have to rip anything out to get there. Run Tanium alongside ConfigMgr, move workloads across in phases, and retire SCCM when you're ready.
The question isn't whether SCCM still works. It’s whether you can respond to real-time threats in this AI era with a view of your estate that isn’t real time.
Get the SCCM Replacement Guide →
This is the first post in our Built for Now series. Next: real time, at real scale - Coming soon
Sources
[1] Microsoft Learn: Configure client status – Configuration Manager (opens in a new tab) (default hardware inventory and client policy intervals)
[2] Anthropic Frontier Red Team: Measuring LLMs' impact on N-day exploits (opens in a new tab) (June 2026)

