diff --git a/windows/deployment/TOC.yml b/windows/deployment/TOC.yml index 67733d50fd..8daccb955a 100644 --- a/windows/deployment/TOC.yml +++ b/windows/deployment/TOC.yml @@ -52,8 +52,6 @@ items: - name: Using a proxy with Delivery Optimization href: update/delivery-optimization-proxy.md - - name: Delivery Optimization Client-Service Communication Explained - href: update/delivery-optimization-workflow.md - name: Best practices for feature updates on mission-critical devices href: update/feature-update-mission-critical.md - name: Windows 10 deployment considerations diff --git a/windows/deployment/update/delivery-optimization-workflow.md b/windows/deployment/update/delivery-optimization-workflow.md index d560a58ca2..03df1c3743 100644 --- a/windows/deployment/update/delivery-optimization-workflow.md +++ b/windows/deployment/update/delivery-optimization-workflow.md @@ -19,21 +19,22 @@ ms.topic: article ## Download Request Workflow -The DO workflow described below allows Delivery Optimization to securely and efficiently deliver requested content to the calling device. +The Delivery Optimization workflow described below allows Delivery Optimization to securely and efficiently deliver requested content to the calling device. Delivery Optimization leverages content metadata to determine all available locations to pull content from, as well as content verification. -* When a download starts, the DO client will attempt to get its content metadata, from the DO service, which is a hash file containing the SHA-256 hash of each piece in the file, typically piece = 1 MB. Separate metadata that is obtained, through an SSL channel, provides DO a way to verify the authenticity of the hash file itself once it is downloaded. -* When DO pulls a certain piece of the hash from another peer, it is verified against the known hash in the hash file. -* If a peer provides an invalid piece, that piece is discarded. A peer that sends multiple bad pieces is banned and will no longer be used as a source by the client performing the download. -* If DO is unable to obtain the hash file, or the verification of the hash file itself fails, the download will fall back to “Simple Mode” (pulling content only from an HTTP source) and peer to peer will not be allowed. -* Once DO is done downloading and puts together the file from all the pieces it got, the caller using DO (ConfigMgr for example) performs yet another check for the entire file as well as verify the signature of it prior to proceeding with installation. +* When a download starts, the Delivery Optimization client will attempt to get its content metadata, from the Delivery Optimization service, via an SSL channel. This content metadata is a hash file containing the SHA-256 block level hashes of each piece in the file (typically one piece = 1 MB). The authenticity of the content metadata file itself is verified prior to any content being downloaded. +* Once the content metadata file is verified, Delivery Optimization proceeds with accessing the requested pieces of the content file. +* When Delivery Optimization pulls a certain piece of the hash from another peer, it is verified against the known hash in the content metadata file. +* If a peer provides an invalid piece, that piece is discarded. When a peer sends multiple bad pieces it is banned and will no longer be used as a source by the Delivery Optimization client performing the download. +* If Delivery Optimization is unable to obtain the content metadata file, or if the verification of the hash file itself fails, the download will fallback to “Simple Mode” (pulling content only from an HTTP source) and peer to peer will not be allowed. +* Once Delivery Optimization downloading is complete, all retrieved pieces of the content are used to put the file together. At that point, the Delivery Optimization caller (e.g. ConfigMgr) performs another check of the entire file to verify the signature, prior to proceeding with installation. ## Delivery Optimization Service Endpoint And Data Information |Endpoint hostname|Name|Description|Data sent from the computer to the Endpoint (Field/Description) -|----|-----|---------------|-----------------------| -| | Geo | Service used to identify the geo location of the device in order to direct it to the nearest data center. | | -|