Microsoft Connected Cache — reference notes

Look up the Connected Cache service model, included/excluded Delivery Optimisation content and recorded maintenance responsibilities.

What is Microsoft Connected Cache?

  • MCC is a free service from Microsoft to provide local proxying and caching of Delivery Optimisation content
  • Runs on either a Linux server, or on Windows under WSL2 (CCM will only use Linux)
  • Each server is a node connected to a management and monitoring instance in Azure
  • Configuration is very limited – you can choose the location for cached content and how much space to consume on that drive, but all Delivery Optimisation traffic on configured clients will use the server when possible

Delivery Optimisation Content

What is Delivery Optimisation content?

  • Windows Updates
  • Feature updates, quality updates, language packs, drivers
  • Store applications and updates
  • Office Click-to-Run updates
  • Edge updates
  • Intune content
  • Win32 apps packaged as .intunewin

What is not Delivery Optimisation content?

  • Intune content
  • Configuration profiles, scripts and policies
  • Line-of-business apps uploaded as .msi or .appx
  • Third-party content
  • For example, the Store version of Adobe Creative Cloud will be via DO, but then installing Photoshop via the creative cloud app will not.

Maintenance

  • The CCM Central Office will be responsible for checking your cache node is ‘healthy’ in the Azure portal
  • Microsoft will automatically maintain the version of the Connected Cache software.
  • Occassionally MS will release an update to connected cache that requires a manual in-place upgrade. In this instance an updated <school_prefix>_mccscripts.zip file and provisioning command will be supplied by CCM IT.
  • Local College IT is responsible for OS updates as per usual.
  • Sudo apt update –y
  • Sudo apt upgrade –y
  • You can automate this if desired
  • sudo dpkg-reconfigure -plow unattended-upgrades