I am building a new SCCM 2012 R2 site for a client that will only be deploying software updates and (very) few apps/packages to machines across 41 locations (all in the US for now). Some of the WAN links are slow and sensitive to other apps that need bandwidth for their processes.  Of the total number, approximately 40% of the sites have slow links (less than 1.5 mb/s) and another 40% are up to 3 mb/s at most.  The remainder are above 3 mb/s and fairly good.

The number of clients at each remote location will vary from 5 to 30 at most and will be all Windows 7 SP1 devices with Office 365.  The machines are imaged with standard apps at a central location and shipped out, so they won't use SCCM OSD or PXE for imaging at remote locations.

This client has an Azure service with dedicated connection.  With the need to throttle/schedule traffic, I can't use pull DPs.  From what I can tell cloud-hosted DP's (in 2012 R2) can't be used to deploy updates or SCUP packages.  So that points to using 'standard' DPs.  Is this correct?

TIA!

• Edited by David M. Stein 11 hours 4 minutes ago

With the need to throttle/schedule traffic, I can't use pull DPs.

Why not? Pull DPs can be throttled.

 From what I can tell cloud-hosted DP's (in 2012 R2) can't be used to deploy updates or SCUP packages. 

This is correct however it doesn't make sense to put update binaries already available directly from Microsoft (via the Internet) on to their cloud DP? Thus, there is a simple check box on update deployments that enables clients to download update binaries directly form Microsoft if they are not available on a preferred DP.

There's no getting around the SCUP limitation though.

Have you thought of using BranchCache or one of the third-party (for-pay) alternate content providers?