Deploying software and updates using Configuration Manager
Microsoft Connected Cache (MCC) can be used with Configuration Manager version 2503; upgrading to 2509 is not required just to perform a POC.
The hotfix KB33247081 explicitly lists Configuration Manager versions 2409, 2503, and 2509 as supported:
"An update is available to resolve the following issues with Configuration Manager current branch, version 2409, 2503, and 2509."
and:
"To apply this hotfix, you must be using Microsoft Endpoint Configuration Manager, versions 2409, 2503, and 2509."
This hotfix also adds key enhancements for MCC, including support for HTTPS delivery of content and additional Office/Teams CDN endpoints, which are relevant for a modern MCC POC.
Therefore, with Configuration Manager 2503 you can:
- Apply the MCC hotfix (DoincInstall.exe 1.5.6.44280) as documented.
- Enable and test Microsoft Connected Cache on your distribution points.
The provided context does not state any blocking limitation related to Windows Server 2012 R2 Datacenter for running MCC in this scenario. The POC feasibility is determined by the supported ConfigMgr versions (2409, 2503, 2509) plus the MCC hotfix and prerequisites (such as proper TLS certificate configuration on the distribution point’s IIS for HTTPS content delivery).
So, the statement "we won't be able to do the POC of Microsoft Connected Cache" with Configuration Manager 2503 is not correct based on the referenced documentation.
References: