Let’s look at the SCCM and Microsoft-connected cache integration (of course with Delivery Optimization – DO) options.
All the screenshots are taken from the Ignite session demo by Andy Rivas & Narkis Engler. More details about the session and recording are 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
Microsoft’s answer to network bandwidth issues in the modern workplace is Microsoft Connected Cache + Delivery Optimization + Microsoft Endpoint Manager. The solution we are going to see in this post is the pure hybrid solution (very tightly integrated with SCCM investments) on the EDGE!
Microsoft Connected Cache can seamlessly integrate with Microsoft Endpoint Manager solutions like SCCM/MEMCM.
Microsoft connected cache with DO solution is based on IIS and Application Request Routing (ARR). This solution is based on the Windows Server native toolset. This Windows solution helps deliver Microsoft connected cache solution with DO & SCCM (MEMCM).
- Cloud Managed
- Microsoft Connected Cache is designed for the cloud era
- Localized Cache
- Use one or many alongside Delivery Optimization
- Cache only content that is needed by your devices at the byte range level
- Reliable & Flexible
- Cache aware distribution ensures seamless fallback to the cloud
- Configure once and forget
- Enjoy new content that does support
Architecture Flow Diagram
Microsoft Connected Cache service can use Configuration Manager/SCCM or MEMCM DP as its connected Cache content location. Also, SCCM clients can get the content from the Connected Cache Container.
- SCCM DP configured to enable Connected Cache service so that it can download the content from Microsoft CDN on client request
- Clients configured with Connected Cache enablement policies
- Client requests for Connected Cache supported content
- Connected Cache container gets content from CDN and delivers it to the client
- The client uses Delivery Optimization (DO) to share this content with other client devices
SCCM and Connected Cache Integration
You can fully unitize the existing investment with SCCM and Microsoft Connected Cache. The integration experience will be seamless for SCCM admins.
NOTE! – More details on the setup and configuration of Microsoft Connected Cache Containers and nodes are explained in the blog post.
SCCM Server Side Configuration for Microsoft Connected Cache
- You can configure Microsoft Connection Cache from the SCCM console -> Distribution Point Properties.
- Select the option – Enable Distribution Points to be used as Microsoft Connected Server.
SCCM Client-Side Policies for Microsoft Connected Server
You can configure the SCCM client policies from Client Agent policies.
- Client Agent Policies – Delivery Optimization
- Select YES for the configuration called “Enable Devices Managed by Configuration Manager to use Microsoft Connected Cache servers for content download.“
Real-World Story – SCCM and Microsoft Connected Cache Integration
This SCCM + Connected Cache is the example provided in the Microsoft Ignite session. Highly efficient caching – the pilot customer.
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?
- Introducing Microsoft Connected Cache: Microsoft’s cloud-managed cache solution
- How to Handle SCCM Bandwidth Issues with Branch Cache Vs. Peer Cache
8 thoughts on “SCCM and Microsoft Connected Cache Integration to Help with Bandwidth Issues”
Will SCCM 1806 or 1906 capable to track daily patching deployments ?
Will I get to know where is the patching delays while in deployments ??
How delays can be track or monitor ?
How about checking this https://www.anoopcnair.com/powershell-script-patch-installation-status/
No Does not much helps
How do we monitor which DP or SE doing slow Deployments or CLients.
Any solutions ??
??? Use SCOM https://www.anoopcnair.com/sccm-scom-alerts-fine-tune-alerts/
Can connected cache be installed on a server core distribution point?
You mean Windows server core OS … I have not seen that support statement yet.
The server core installation of the following server OS versions are supported for use as a distribution point:
More detail https://docs.microsoft.com/en-us/mem/configmgr/core/plan-design/configs/supported-operating-systems-for-site-system-servers#bkmk_core
“Connected Cache doesn’t support content that Configuration Manager manages, like software updates with an integrated software update point.”
Does this mean I cannot used connected cache for updates deploying using a traditional ADR even if there is no content package?