Add run summary, Delivery Optimization diagnostics, and Settings Catalog policy state

[YeehomZhu]

Summary

Three improvements to make ODC ZIPs faster to triage and to fill diagnostic gaps for common Intune support cases.

Changes

1. Run summary (_SUMMARY.txt) at root of collected data

New Write-RunSummary function in IntuneODCStandAlone.ps1 writes a one-page summary at the root of the ZIP so engineers see device state at a glance:

• ODC version, run duration, OS, file count, total size
• Health indicators: AAD/Domain/Workplace join, IME service status, MDM cert expiry, free disk space, ODC log error count
• Items flagged with [!] for quick triage (e.g., IME stopped, cert expiring within 30 days, free space < 5 GB)

2. Delivery Optimization diagnostics (Intune.xml)

For diagnosing Win32 app / update download issues:

• Get-DeliveryOptimizationStatus, Get-DeliveryOptimizationPerfSnap, ...ThisMonth
• Get-DOConfig -Verbose, Get-DOPercentageMaxBackgroundBandwidth, Get-DOPercentageMaxForegroundBandwidth
• Microsoft-Windows-DeliveryOptimization* event log capture

3. Settings Catalog / Policy CSP state (Intune.xml)

Full export of effective policy state:

• HKLM\SOFTWARE\Microsoft\PolicyManager\current (effective policy values)
• HKLM\SOFTWARE\Microsoft\PolicyManager\providers (per-provider ownership)
• HKLM\SOFTWARE\Microsoft\PolicyManager\AdmxInstalled (Settings Catalog ADMX-backed policies)
• HKLM\SOFTWARE\Microsoft\PolicyManager\AdmxDefault (defaults for comparison)

Why

• Run summary dramatically reduces triage time — engineers no longer need to dig through dozens of files just to confirm basic device state
• Delivery Optimization data is critical for Win32 app deployment failures (peering, bandwidth caps, DO group ID issues)
• Settings Catalog policy state lets engineers see exactly what policies were applied and from which source — currently only the legacy PolicyManager\current\device subset is captured