From 5df53ceb023d8e4c9f3bab62fe84928c8ce5edd5 Mon Sep 17 00:00:00 2001 From: Carmen Forsmann Date: Sun, 5 Sep 2021 16:23:50 -0600 Subject: [PATCH 01/58] Add new Delivery Optimization workflow documentation --- windows/deployment/TOC.yml | 2 + .../update/delivery-optimization-workflow.md | 39 +++++++++++++++++++ 2 files changed, 41 insertions(+) create mode 100644 windows/deployment/update/delivery-optimization-workflow.md diff --git a/windows/deployment/TOC.yml b/windows/deployment/TOC.yml index fdc36528a1..216bdb78e9 100644 --- a/windows/deployment/TOC.yml +++ b/windows/deployment/TOC.yml @@ -48,6 +48,8 @@ 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 new file mode 100644 index 0000000000..d560a58ca2 --- /dev/null +++ b/windows/deployment/update/delivery-optimization-workflow.md @@ -0,0 +1,39 @@ +--- +title: Understand the Delivery Optimization Client-Service Communication Explained +manager: laurawi +description: Settings to use with various proxy configurations to allow Delivery Optimization to work +keywords: updates, downloads, network, bandwidth +ms.prod: w10 +ms.mktglfcycl: deploy +audience: itpro +author: carmenf +ms.localizationpriority: medium +ms.author: carmenf +ms.collection: M365-modern-desktop +ms.topic: article +--- + +# Delivery Optimization Client-Service Communication Explained + +**Applies to**: Windows 10 + +## Download Request Workflow + +The DO workflow described below allows Delivery Optimization to securely and efficiently deliver requested content to the calling device. + +* 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. + +## 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. | | +|