Hello Soni,
Thank you for posting question on Microsoft Windows Forum!
Based on your query of setting up a dedicated Microsoft Connected Cache (MCC) server on a local machine to act as a permanent local update repository to protect your metered internet line in an environment with 300 Windows laptops.
Well! It is important to highlight this point here is that if you are looking for a traditional "permanent repository" where you manually sync, approve, and indefinitely store update binaries on a local disk, this is the job of the Windows Server Update Services (WSUS). On the other hand, if your goal is simply to prevent WAN saturation while using modern update mechanisms like Windows Update for Business (WUfB), Microsoft Connected Cache (MCC) is the right tool for the job. Hence, MCC acts as a dynamic transparent cache, not a permanent, managed repository.
MCC integrates seamlessly with the Delivery Optimization (DO) framework you already have turned on. Instead of pushing updates from a central database, it sits passively on your network and builds its cache based on active client requests. The first Windows laptop asks Microsoft for a Patch Tuesday update. The laptop's DO policy points it to the local MCC node instead of the public internet. If the MCC server does not have the payload, it downloads the exact byte ranges from Microsoft's CDN, caches them on its local disk, and serves them to the laptop. When the remaining 299 laptops request the same update, the MCC server delivers it entirely over the LAN, virtually eliminating the WAN hit.
You can consult the following links for further reference.
- https://learn.microsoft.com/en-us/windows/deployment/do/mcc-ent-create-resource-and-cache
- https://learn.microsoft.com/en-us/intune/configmgr/core/plan-design/hierarchy/microsoft-connected-cache
- https://learn.microsoft.com/en-us/windows/deployment/do/mcc-ent-faq
Hope the above information is helpful! If it is. Free feel to hit "Accepted" for benefitting others in community having the same query too.