Patch Audit for MSPs & IT Admins Measure Caching ROI Across Clients Using patch caching tools like WSUS or Delivery Optimization can reduce bandwidth consumption and accelerate update deployments. But to prove it's working, you need to run regular patch audits. In this video, we'll show you how to measure caching performance with the tools you already have and turn that data into clear, actionable insights. Before we begin, be sure to subscribe to NinjaOne's IT Video Hub and our YouTube channel for more tech content like this. Step 1 Collect Delivery Optimization Metrics To make sure patch caching is actually reducing bandwidth, audit Delivery Optimization (DO) using these methods. Use Cloud-based Reports for a Broad View Open Windows Update for Business reports in the Microsoft Intune admin center. Check the built-in dashboards to compare peer vs. CDN download data over the last 28 days. Use a Log Analytics workspace and assign users the proper access such as Log Analytics Reader or Contributor. Run a KQL query in Azure Monitor Log Analytics against UCDOAggregatedStatus to calculate cache hit rates. Check Individual Clients With PowerShell Open PowerShell as Administrator. Run Get-DeliveryOptimization PerfSnapThisMonth to see total bytes downloaded from peers vs. the internet. For live update data, run Get-DeliveryOptimizationStatus and check PercentPeerCaching and BytesFromPeers. This quick audit gives you clear proof of bandwidth savings and cache efficiency. Step 2 Measuring Delivery Optimization Performance In distributed networks auditing Delivery Optimization helps confirm updates are being delivered locally instead of using your WAN. Open Performance Monitor on a client device using perfmon.exe. Click + expand Delivery Optimization and add these counters: BytesFromPeers: bytes downloaded from peers. BytesFromHttp: bytes downloaded from Microsoft CDN. BytesToPeers: bytes shared with peers. Collect data during a patch cycle, then export the log to CSV for reporting and trend analysis. To quickly estimate peer usage, calculate: Step 3 Review WSUS or Intune Compliance Reports Your central management consoles give you the most reliable data for a patch audit. For WSUS/Configuration Manager Run built-in reports like Update Compliance or Computer Status to track installation success across your environment. These reports help you prove compliance and quickly spot failed updates. For Intune Windows/Update for Business Use the Windows Update for Business reports in the Intune admin center. These dashboards show deployment status compliance percentages and Delivery Optimization savings. Note that reports appear only after Windows Update for Business reporting is enabled and connected to an Azure Log Analytics workspace. Step 4 Compare Results Against Compliance Targets Compare your audit results to clear SLAs to demonstrate effectiveness. Compare your actual patch compliance rates and timelines to targets like 95% patched within 7 days. Identify devices with failed or unknown status that are missing those deadlines. Also, calculate your cache hit ratio using the data you've collected and compare it against your bandwidth-reduction targets. A thorough patch audit transforms patch caching from an assumed benefit into a proven asset. You can measure bandwidth savings and compliance without added cost. Tracking these results against your SLAs helps you refine your strategy and clearly demonstrate ROI to clients. For more information, check out our official blog post on measuring a caching ROI while doing patch audit linked in the description below.