In this post, you will learn how Configuration Manager uses binary differential replication (BDR) to update content. BDR minimizes the network bandwidth used to send updates for distributing content that you previously distributed to other sites or remote distribution points.
To support BDR’s reduction of bandwidth usage, install the Remote Differential Compression feature on distribution points.
According to Microsoft, BDR is used when files in the source content change, It resends only the new or changed content instead of sending the entire set of content source files each time you change those files.
If a file already exists on the distribution point and there’s a change, the site uses BDR to replicate the block-level change instead of the entire file. A file is considered changed if you renamed or moved it or changed the file’s contents.
Configuration Manager supports up to five incremental versions of a content set before it resends the entire content set. After the fifth update, the next change to the content set causes the site to create a new version of the content set.
Configuration Manager then distributes the new version of the content set to replace the previous set and any of its incremental versions. After the new content set is distributed, later incremental changes to the source files are again replicated by BDR.
Applications always use binary differential replication. BDR is optional for packages and isn’t enabled by default.
In Configuration Manager, BDR Optional on legacy packages. To use BDR for packages, enable this functionality for each package. You can check the option Enable binary differential replication when creating or editing the following
- Applications (Always enabled)
- OS images
- OS upgrade packages
- Boot images
- Software Update Patch Package
Enable Binary Differential Replication for SCCM Packages
Let’s follow the steps below to configure for packages –
In the Configuration Manager console, go to the Software Library workspace, expand Application Management, and select the Packages node.
Select an existing package. Right-click on the package and select Properties, options appear on the Data Source tab. For Example – Here’s how you can enable Binary Differential replication for existing packages.
Under Package properties In the Data Source tab, select Enable binary differential replication when you create or edit a package. Click Apply and OK.
I hope the above configuration helps SCCM Admin to reduce unwanted waiting time to replicate the changes specifically for packages to DPs. Enable Binary Differential Replication in SCCM | ConfigMgr | Endpoint Manager.
If you have any queries, Please use the HTMD Community Forum one-stop-shop for all your device management queries related to ConfigMgr (a.k.a SCCM), Intune, and more! This is the community built by Device Management Admins for Device Management Admins❤️
Fundamental concepts for content management in Configuration Manager – https://docs.microsoft.com/en-us/mem/configmgr/core/plan-design/hierarchy/fundamental-concepts-for-content-management
About Author – Jitesh, Microsoft MVP, has over five years of working experience in the IT Industry. He writes and shares his experiences related to Microsoft device management technologies and IT Infrastructure management. His primary focus area is Windows 10 Deployment solution with Configuration Manager, Microsoft Deployment Toolkit (MDT), and Microsoft Intune.