ConfigMgr remote site bandwith size with no DP

Question

Hey,

I've been asked to recommend a minimum link size for 1000 configmgr clients at a new site we are commissioning, this new site is not to have a DP because of a new approach our organization is taking (currently we have DPs for most sites).

Just wondering if anyone has any tools or guides to base some of these calculations on as I need to provide some evidence to back this up, we perform MS and Third party updates as well as have over 1000 packages which range from a few kb to many GB. I understand there is no perfect answer as such I'm hoping to base it on the assumption of all devices downloading Windows updates around the same time. Branch cache isn't something we are currently using but I plan to include recommendations with it both on and off.

Any logic people have used in the past for similar kinds of projects would be apperciated.

Answer 1

Hi,

Thanks for posting in Microsoft MECM Q&A forum.

As it's not supported to use DP and Branch cache in your remote site, it's recommended to use Peer Cache to help manage deployment of content to clients in remote locations. Peer Cache is a built-in Configuration Manager solution that enables clients to share content with other clients directly from their local cache.

Please choose only clients best suited as peer cache sources. Evaluate client suitability based on attributes such as chassis type, disk space, and network connectivity. For more information, please refer to:
Peer cache for Configuration Manager clients
Configuration Manager Peer Cache: Custom Reporting Examples
Configuring Peer Cache for Configuration Manager Clients

Thanks for your time.

Best regards,
Simon

---

If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.