![]() Client A verifies complete file via hash.Client A verifies hashes of chunks and builds file from chunks.Client A requests chunks from MS content server and peers B, C, ….Client A gets download sources (MS content server and additional clients (peers) B, C, ….Currently Microsoft supports the following content: ![]() How does Delivery Optimization work in detail?įirst of all the published content must be chunked and hashed. Delivery Optimization can accomplish this because it is a self-organizing distributed cache that allows clients to download those packages from alternate sources (such as other peers on the network) in addition to the traditional Internet-based Windows Update servers. You can use Delivery Optimization to reduce bandwidth consumption by sharing the work of downloading these packages among multiple devices in your deployment. In case of Windows Update for Business we need to focus on Delivery Optimization (DO). To prevent internet traffic congestion we can utilize Peer 2 Peer technologies like BranchCache and Delivery Optimization to optimize Windows 10 update delivery. To monitor the Delivery Optimization Performance we have the Delivery Optimization Status in the Windows Analytics solution – Update Compliance.įor successful servicing we need to make sure an internet break out with proper bandwidth capacity is available to support our devices. This article will not show the details of the WUfB settings. The WUfB settings can be configured in Intune via Software Udpates. That means our content is provided by Microsoft Update servers and we define the installation behavior like deferrals or even pause of feature or quality updates. This is called Windows Update for Business (WUfB). To support the Windows as a Service strategy with cloud services we rely on the well known Windows Update service, but with the controls for business usage.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |