If we get the DO implementation right we can enjoy great working peer to peer content delivery supported by an additional cache server. Looks like a complete list, right? Actually for an Intune managed device this should represent the complete list of content you have to deal with regularly. Okay clear, the MCC acts as a transparent proxy to cache content. Devices A,B, and C still use DO to get missing pieces of content from their other peers.If the MCC is unavailable or fails to respond, the device downloads the content from the CDN.If the cache does not have the content, the MCC gets the content from the CDN.
#Slide ignite microsoft edge windows#
Device A checks for Windows Updates and gets the address for the content delivery network (CDN).Microsoft Intune configures Delivery Optimization (DO) settings on the devices, including the Microsoft Connected Cache (MCC) server name (DOCacheHost).This way clients requesting content can get peer lists belonging to their group. The cloud tracks peers based on a defined grouping strategy. It utilizes the cloud (Microsoft Delivery Optimization Services) for peer discovery. As already mentioned it is designed for the cloud era which means it does not rely on peer discovery based on broadcast like BranchCache does. Let’s start with a short introduction into Delivery Optimization. The latest addition to that concept is the so called Microsoft Connected Cache (MCC) formerly known as DOINC (Delivery Optimization In-Network Cache). It is a very well designed solution especially for the cloud era. It is a distributed cache solution using peer to peer transfers for content downloads. Intune managed devices must be configured to leverage Delivery Optimization (DO) to reduce the overall internet bandwidth usage.
0 kommentar(er)
