Microsoft Connected Cache in Azure (Microsoft’s answer to bandwidth issues with DO?) is the topic which I’m going to cover in this post. All the screenshots are taken from the Ignite session demo by Andy Rivas & Narkis Engler. More details about the session and recording below section of this post.
Ignite 2019 Coverage
- Microsoft Endpoint Management SCCM Intune Windows Updates
- Microsoft Endpoint Manager is the future of SCCM Intune MEMMI MEMCM
- iOS Android macOS Mobile Enrollment Options with Intune
- Basics of Windows Dynamic Update Explained Update Management
- WVD End User Experience Availability Updates
- MSIX Updates from Ignite Reliability Network Disk-space
- Microsoft Learning Certification Exams Updates
- On-Prem WVD Options Azure Quantum Qualys Scan Integration
- Intune Reporting Strategies Advanced Reporting
- Intune Endpoint Security Policies Enhancements
- Intune Policy Sets Collection of Workflows
- Windows Autopilot Updates Timelines
- Microsoft Connected Cache Container Instances in Azure via Intune
- SCCM and Microsoft Connected Cache Integration
- Windows 10 Bandwidth Management DO Delivery Optimization with LEDBAT in LAN
TL;DR
Introduction
Microsoft Connected Cache Private preview now. More details about private preview and roadmap are available in the below section of the post. The connected cache node instances will be on a server which is located in your on-prem data center.
Connected Cache Container is a Linux container and you can run it on:
- Connected Cache Container Host
- Windows Server 2019
- Connected Cache Container
- Linux Server Ubuntu Server 16.04
- Connected Cache Container
- Windows Server 2019
NOTE 1 – You might need to Azure tools (like Azure IOT Edge runtime) to securely deploy provision and manage these Microsoft connected cache instances.
NOTE 2 – Microsoft E3 & EMS A3 licenses (more details coming soon) are enlightened to use Microsoft Connected cache managed in Azure.
How Microsoft Connected Cache in Azure Works?
- Connected Cache Container Host
- Connected Cache Container Instances (Linux container) deployed on to your Windows 2019 or Ubuntu 16.04
- Clients configured to download the content from Connected Cache
- Configure the policies through Intune/Airwatch/Mobileiron (MDM solutions)
- Group Policy
- DHCP options (coming in 2020 H1 timeline)
- Windows Clients request the content from Connected Cache Container
- Connected Cache Container get the content from CDN and deliver it to client
- Once the content is available on the client devices, the DO peer to peer can be used to transfer the content between clients
IT Admin Testing Experience with Connected Cache in Azure
- You can download an app from Microsoft store
- You can see the files getting stored in Connected Cache container
- You can use following PowerShell commands to get more details
- Get-DeliveryOptimizationStatus | FT
PS C:\Users\Anoop C Nair> Get-DeliveryOptimizationStatus | FT
hitBytes missBytes egressBytes Summary
NOTE! – Microsoft Connected Cache Summary Report (shown below) refreshes every 15 secs.
- hitBytes – what are Bytes the coming from cache server
- missBytes – what are the Bytes not there in Cache Servers that Cache server had to go out and retrieve it from Internet?
- egressBytes – What are the Bytes coming OUT from the cache server?
Reporting Options – Microsoft Connected Cache
You can get all the reports in Azure portal directly from your on-prem Microsoft connected cache instance via container host connectivity.
- Efficiency: Connected Cache Hit/Miss Ratio
- Bytes from connected cache
- Connected Cache Hit/Miss Counts
- Connected Cache Hit/Miss Bytes
Connected Cache in Azure Roadmap
- Private preview – Reach out to msconnectedcache at microsoft com
- Blog post details – https://aka.ms/PreviewConnectedCache
Microsoft Solutions to Endpoint Bandwidth Network Issues
Session
Stay current while minimizing network traffic: The power of Delivery Optimization. Session Recording by Andy Rivas & Narkis Engler. https://myignite.techcommunity.microsoft.com/sessions/81680?