Sunday, 19 July 2026

Configuration Manager software update scans separate cache reuse from WSUS connectivity

The period contains a substantive clarification to Configuration Manager Software Updates guidance. It separates the forced/non-forced decision, which controls cache reuse, from the online/offline decision, which controls whether a scan obtains metadata from WSUS or local storage. This is documentation clarification, not evidence of a new feature, preview, general availability change, retirement, or changed product behavior.

• Configuration Manager · Compliance

  Forced scans ignore the cached compliance results

  A non-forced scan reuses the last scan results while they remain current and within the TTL, running a new scan only when the cache is stale. A forced scan always runs a new scan and ignores the cache.

• Configuration Manager · General

  Online and offline scans use different metadata sources

  For a scan that actually runs, online mode connects to WSUS on the software update point to refresh metadata. Offline mode evaluates the client with metadata already stored locally and does not connect to WSUS. An online scan therefore does not necessarily contact WSUS when a non-forced scan can use current cached results.

• Configuration Manager · Compliance

  One scan evaluates the entire synchronized update catalog

  A scan evaluates all update metadata synchronized on the software update point, including updates in new deployments, existing deployments, and no deployments. Targeting a client with 1 deployment or 10 deployments does not change the number of scans.

This period briefing was generated by AI from the tracked Microsoft Learn and Message Center changes.