Most of the SCCM ConfigMgr administrators must have tasted (at least once) bandwidth related priority 1 (p1) tickets in the organization. The office package replication is using all the bandwidth available. The point is, the throttling settings in SCCM console doesn’t work very well. There is no guaranteed bandwidth usage or control for these activities. So it’s better to have network team manage bandwidth usage of SCCM servers from their endpoints like switches or routers. Also, BITS throttling algorithms often don’t work very well on slower WAN links.
We never have enough WAN link to support OSD and office package deployments. You don’t need to worry much about slow WAN links when you’ve enterprise peer to peer technologies like Adaptiva OneSite. Adaptiva OneSite uses Third Generation Predictive Bandwidth Harvesting (PBH). PBH is a revolutionary technology breakthrough that redefines the possibilities for WAN optimization.
Advantages of PBH: there is no chance of congestion due to SCCM / ConfigMgr traffic. For example, OneSite can deliver 17 GB file from North America to rural China over multiple narrow WAN links without generating a single network ticket. This is during the peek business hours. Also, Predictive Bandwidth Harvesting is much faster than other solutions because it automatically harvests all unused bandwidth without creating network congestion.
To know more about Predictive Bandwidth Harvesting read very detailed post here.
- Packet-level driver – A OneSite NDIS kernel driver monitors the length of the data queues on WAN edge routers in real-time.
- Network independence – OneSite operates without SNMP passwords by using publicly available information, and requires no router configuration changes.
- UDP not TCP – Because PBH uses UDP, it reevaluates what to send on a packet-by-packet basis, optimizing traffic in sub-millisecond intervals.