Delivery Optimization in Update Compliance
- Windows 10
- Windows 11
The Update Compliance solution provides you with information about your Delivery Optimization configuration, including the observed bandwidth savings across all devices that used peer-to-peer distribution over the past 28 days.
Delivery Optimization Status
The Delivery Optimization Status section includes three blades:
- The Device Configuration blade shows a breakdown of download configuration for each device
- The Content Distribution (%) blade shows the percentage of bandwidth savings for each category
- The Content Distribution (GB) blade shows the total amount of data seen from each content type broken down by the download source (peers vs non-peers).
Device Configuration blade
Devices can be set to use different download modes; these download modes determine in what situations Delivery Optimization will use peer-to-peer distribution to accomplish the downloads. The top section shows the number of devices configured to use peer-to-peer distribution in Peering On compared to Peering Off modes. The table shows a breakdown of the various download mode configurations seen in your environment. For more information about the different configuration options, see Configure Delivery Optimization for Windows client updates.
Content Distribution (%) blade
The first of two blades showing information on content breakdown, this blade shows a ring chart summarizing Bandwidth Savings %, which is the percentage of data received from peer sources out of the total data downloaded (for any device that used peer-to-peer distribution). The table breaks down the Bandwidth Savings % into specific content categories along with the number of devices seen downloading the given content type that used peer-to-peer distribution.
Content Distribution (GB) blade
The second of two blades showing information on content breakdown, this blade shows a ring chart summarizing the total bytes downloaded by using peer-to-peer distribution compared to HTTP distribution. The table breaks down the number of bytes from each download source into specific content categories, along with the number of devices seen downloading the given content type that used peer-to-peer distribution.
The download sources that could be included are:
- LAN Bytes: Bytes downloaded from LAN Peers which are other devices on the same local network
- Group Bytes: Bytes downloaded from Group Peers which are other devices that belong to the same Group (available when the "Group" download mode is used)
- HTTP Bytes: Non-peer bytes. The HTTP download source can be Microsoft Servers, Windows Update Servers, a WSUS server or an Configuration Manager Distribution Point for Express Updates.
Monitor Delivery Optimization
Windows PowerShell cmdlets
Starting in Windows 10, version 1703, you can use new PowerShell cmdlets to check the performance of Delivery Optimization.
Get-DeliveryOptimizationStatus returns a real-time snapshot of all current Delivery Optimization jobs.
|File ID||A GUID that identifies the file being processed|
|FileSize||Size of the file|
|FileSizeInCache||Size of the file in the cache|
|TotalBytesDownloaded||The number of bytes from any source downloaded so far|
|PercentPeerCaching||The percentage of bytes downloaded from peers versus over HTTP|
|BytesFromPeers||Total bytes downloaded from peer devices (sum of bytes downloaded from LAN, Group, and Internet Peers)|
|BytesfromHTTP||Total number of bytes received over HTTP|
|Status||Current state of the operation. Possible values are: Downloading (download in progress); Complete (download completed, but is not uploading yet); Caching (download completed successfully and is ready to upload or uploading); Paused (download/upload paused by caller)|
|Priority||Priority of the download; values are foreground or background|
|BytesFromCacheServer||Total number of bytes received from cache server|
|BytesFromLanPeers||Total number of bytes received from peers found on the LAN|
|BytesFromGroupPeers||Total number of bytes received from peers found in the group|
|BytesFromInternetPeers||Total number of bytes received from internet peers|
|BytesToLanPeers||Total number of bytes delivered from peers found on the LAN|
|BytesToGroupPeers||Total number of bytes delivered from peers found in the group|
|BytesToInternetPeers||Total number of bytes delivered from peers found on the LAN|
|DownloadDuration||Total download time in seconds|
|SourceURL||Http source for the file|
|CacheHost||IP address for the cache server|
|NumPeers||Indicates the total number of peers returned from the service.|
|PredefinedCallerApplication||Indicates the last caller that initiated a request for the file.|
|ExpireOn||The target expiration date and time for the file.|
|IsPinned||A yes/no value indicating whether an item has been "pinned" in the cache (see
Get-DeliveryOptimizationPerfSnap returns a list of key performance data:
|FilesDownloaded||Number of files downloaded|
|FilesUploaded||Number of files uploaded|
|TotalBytesDownloaded||Total bytes downloaded|
|TotalBytesUploaded||Total bytes uploaded|
|AverageDownloadSize||Average transfer size (download); that is, the number bytes downloaded divided by the number of files|
|AverageUploadSize||Average transfer size (upload); the number of bytes uploaded divided by the number of files|
|DownloadMode||Delivery Optimization Download mode used to deliver file|
-Verbose option returns additional information:
- Bytes from peers (per type)
- Bytes from CDN (the number of bytes received over HTTP)
- Average number of peer connections per download
Starting in Windows 10, version 2004,
Get-DeliveryOptimizationStatus has a new option
-PeerInfo which returns a real-time list of the connected peers.
Starting in Windows 10, version 1803,
Get-DeliveryOptimizationPerfSnapThisMonth returns data similar to that from
Get-DeliveryOptimizationPerfSnap but limited to the current calendar month.
Manage the Delivery Optimization cache
Starting in Windows 10, version 1903:
set-DeliveryOptimizationStatus -ExpireOn [date time] extends the expiration of all files in the cache. You can set the expiration immediately for all files that are in the "caching" state. For files in progress ("downloading"), the expiration is applied once the download is complete. You can set the expiration up to one year from the current date and time.
set-DeliveryOptimizationStatus -ExpireOn [date time] -FileID [FileID] extends expiration for a single specific file in the cache.
You can now "pin" files to keep them persistent in the cache. You can only do this with files that are downloaded in modes 1, 2, or 3.
set-DeliveryOptimizationStatus -Pin [True] -File ID [FileID] keeps a specific file in the cache such that it won't be deleted until the expiration date and time (which you set with
set-DeliveryOptimizationStatus -ExpireOn [date time] -FileID [FileID]). The file is also excluded from the cache quota calculation.
set-DeliveryOptimizationStatus -Pin [False] -File ID [FileID] "unpins" a file, so that it will be deleted when the expiration date and time are reached. The file is included in the cache quota calculation.
delete-DeliveryOptimizationCache lets you clear files from the cache and remove all persisted data related to them. You can use these options with this cmdlet:
-FileIDspecifies a particular file to delete.
-IncludePinnedFilesdeletes all files that are pinned.
-Forcedeletes the cache with no prompts.
Work with Delivery Optimization logs
Starting in Windows 10, version 2004:
Get-DeliveryOptimizationLogAnalysis [ETL Logfile path] [-ListConnections]
With no options, this cmdlet returns these data:
- total number of files
- number of foreground files
- minimum file size for it to be cached
- number of eligible (larger than the minimum size for peering) files
- number of files that found peers
- number of peering files (the number of files that got at least 1 byte from peers)
- overall efficiency
- efficiency in the peered files
-ListConnections option returns these details about peers:
- destination IP address
- peer type
- status code
- bytes sent
- bytes received
- file ID
Starting in Windows 10, version 1803:
Get-DeliveryOptimizationLog [-Path <etl file path, supports wildcards>] [-Flush]
Path is not specified, this cmdlet reads all logs from the DoSvc log directory, which requires administrator permissions. If
Flush is specified, the cmdlet stops DoSvc before reading logs.
Log entries are written to the PowerShell pipeline as objects. To dump logs to a text file, run
Get-DeliveryOptimizationLog | Set-Content <output file> or something similar.
For more information on Delivery Optimization, see Set up Delivery Optimization for Windows.
Submit and view feedback for