sccm branch distribution point setup

[logan_walker]

deploying sccm to a remote office with terrible bandwidth. is setting up a branch distribution point still the best way to handle this?

 

[isla]

yeah, branch dp is kinda the traditional answer for this. but honestly, in our experience, if the clients are mostly win10/11, distributed optimization (DO) can actually work really well and you avoid managing another server. it really helps with that awful bandwidth, esp if you have enough devices to peer.

 

[DianeSawyer_49]

yeah, branch dp is kinda the traditional answer for this. but honestly, in our experience, if the clients are mostly win10/11, distributed optimization (DO) can actually work really well and you avoid managing another server. it really helps with that awful bandwidth, esp if you have enough devices to peer.

oh nice thanks for the tip about do that makes a lot of sense

 

[Frenchie]

Setting up a Branch Distribution Point (DP) in SCCM is pretty straightforward. You basically install the DP role on a remote site server to cache and distribute content locally, which helps save bandwidth. In the SCCM console, go to Administration → Site Configuration → Servers and Site System Roles, add a new site system server (your branch machine), then assign the Distribution Point role and configure settings like drive space, rate limits, and content validation. After that, distribute your packages to this DP so clients in that branch can pull content locally instead of hitting the main server. I’ve used this in smaller remote offices, and it really helps with slow WAN links.