What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
In Configuration Manager current branch, applications use binary differential replication (BDR) automatically. Packages do not: BDR is optional and disabled by default. To use it, open each package in the Configuration Manager console, select Enable binary differential replication while creating or editing the package, and ensure the Windows Remote Differential Compression feature is installed on the distribution points that will transfer the content. Microsoft documents the behavior in Fundamental concepts for content management in Configuration Manager (current-branch documentation last updated October 4, 2022).
What binary differential replication does
BDR reduces the amount of software content that Configuration Manager transfers after content has already been distributed. Instead of sending the complete source set again whenever content changes, Configuration Manager uses Windows Remote Differential Compression to identify differences and replicate the changed content to supported sites and distribution points.
As an Amazon Associate I earn from qualifying purchases.
The reduction applies to content distribution, not to the Configuration Manager site database and not to every kind of replication in a hierarchy. It is a content-transfer method for software such as packages, applications, and other distributed source files. Bandwidth throttling and distribution schedules remain separate controls: they determine when or how quickly content moves, whereas BDR determines how much of previously distributed content needs to move.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Microsoft does not publish a fixed percentage of bandwidth saved. The amount transferred depends on what changed in the source. A small edit can produce a small transfer, while adding files or replacing large files can require substantially more data.
#1 Best Overall
Which Configuration Manager objects use BDR?
| Object or transfer path | BDR behavior | What the administrator must do |
|---|---|---|
| Applications | Applications always use BDR in the current branch. | No per-application BDR switch is required. |
| Packages | BDR is optional and is not enabled by default. | Enable Enable binary differential replication for each package that should use it. |
| Parent site to child site | Supported for content replication. | Use a package or application configured as above, and verify the receiving infrastructure is a supported distribution point. |
| Site server to a regular distribution point | Supported. | Install Remote Differential Compression on the distribution point and enable BDR on each applicable package. |
| Pull-distribution point | Does not support BDR content transfer. | Do not expect block-level BDR transfers to this destination. |
| Content-enabled cloud management gateway | Does not support BDR content transfer. | Plan for the transfer behavior supported by that role instead of relying on BDR. |
The setting is per package. Enabling it for one package does not turn it on for other packages, and it does not change the behavior of applications, which already use BDR.
Prerequisites and scope before you enable it
Install Remote Differential Compression on distribution points
Microsoft calls out the Windows Remote Differential Compression feature as the distribution-point prerequisite for BDR. Install the feature on the distribution points that will participate in BDR-based content transfer. The cited Microsoft guidance identifies this requirement but does not prescribe a particular Windows Server installation procedure or PowerShell command, so use the feature-management method appropriate to your server operating system and change-control process.
Confirm the destination supports BDR
BDR works between a parent site and its child site and between a site server and its regular distribution points. It is not supported for content transfer to pull-distribution points or content-enabled cloud management gateways. A package can be correctly configured and still transfer without BDR when its destination is one of those unsupported roles.
Rank #2
Decide whether the package’s change pattern benefits
BDR is most relevant when an existing package is updated repeatedly and much of its previously distributed content remains unchanged. It does not guarantee a small transfer for every update. New files are copied, and a change that causes a full content-set version can require the complete set to be distributed again.
How to enable BDR for a Configuration Manager package
Use the package’s own creation or editing dialog. The documented control is the same in both cases.
- Open the Configuration Manager console and start creating a package, or open an existing package for editing.
- In the package configuration interface, locate the option labeled Enable binary differential replication.
- Select that option for the package. Leave it cleared when the package should not use BDR.
- Complete the package creation or save the package edits according to your normal Configuration Manager workflow.
- Confirm that the distribution points involved in the transfer have the Remote Differential Compression Windows feature installed.
- Distribute or update the package content through your normal content-distribution process, keeping in mind that BDR applies only where the source and destination relationship supports it.
There is no equivalent package-wide or hierarchy-wide switch described by Microsoft. Repeat the selection for every package that needs BDR. Applications do not require this package setting because they always use BDR.
What happens when package content changes
Changed content is represented by an incremental version
When source content that was already distributed changes, Configuration Manager creates an incremental content version. BDR uses the previously distributed content to identify and transfer the differences rather than automatically resending the entire source set. Replacing a driver file in a driver package is Microsoft’s example: the changed driver file is replicated instead of the unchanged files in the package.
A rename, move, or other content modification counts as a changed file. BDR does not infer that two files are equivalent merely because their names or locations changed; those operations are treated as content changes for versioning and transfer.
New files are copied
For packages, BDR handles changed existing files at the block level, but a file that did not exist in the previously distributed version has to be copied. Therefore, adding several large files can result in a sizeable transfer even when BDR is enabled.
Rank #4
Five incremental versions are retained before a full set
Configuration Manager supports up to five incremental versions of a content set. After five incremental versions, the next source change creates and distributes a new version of the full content set, replacing the previous full set and its increments. Later changes begin a new sequence of BDR increments. This limit is an expected versioning behavior, not an indication that the package option stopped working.
BDR versus delta replication
| Characteristic | Binary differential replication | Delta replication |
|---|---|---|
| Difference granularity | Block-level differences identified with Windows Remote Differential Compression. | File-level differences. |
| Configuration | Automatic for applications; optional per package and disabled by default for packages. | Enabled by default and not configurable. |
| When an existing file changes | Changed blocks in the existing file can be transferred for a supported BDR relationship. | The file-level delta model does not provide the same block-level transfer. |
| When a new file appears | The new file is copied. | New files can be transferred as file-level changes. |
| Supported BDR destinations | Parent-child sites and site server to regular distribution points; not pull-distribution points or content-enabled cloud management gateways. | Pull-distribution points support file-level deltas, but changed blocks inside an existing file are not transferred through BDR. |
These mechanisms are separate. Calling a transfer a “delta” does not necessarily mean that only changed blocks are moving. In particular, delta replication being enabled by default does not mean that an optional package BDR setting has been enabled.
Recommended Free Tools
Troubleshooting unexpected transfer sizes or behavior
The package sends much more data than expected
- Check whether the destination is a pull-distribution point or a content-enabled cloud management gateway. Those roles do not support BDR content transfer.
- Check whether the update added new files. New files are copied rather than reconstructed from blocks in an older file.
- Check the package’s setting. BDR must be selected separately for each package; enabling it on another package does not affect this one.
- Check the content-version history. If the change follows five incremental versions, Configuration Manager is expected to create and distribute a new full content-set version.
- Verify that Remote Differential Compression is installed on the participating distribution point.
The BDR option is not visible or seems unnecessary
- If you are working with an application, there is no need to enable a package option: applications always use BDR.
- If you are editing a package, use the exact label Enable binary differential replication in the package creation or editing interface.
- Do not look for a hierarchy-wide database-replication setting. The documented control is a package-level content-distribution setting.
A pull-distribution point receives new files but not changed blocks
This is consistent with the supported behavior. Pull-distribution points can use file-level deltas, so new files can transfer, but changed blocks inside an existing file are not transferred through BDR to that role. If block-level BDR is a requirement, evaluate a supported regular distribution-point path instead.
Transfers are delayed even though BDR is enabled
BDR changes the content difference that must be transferred; it does not override distribution schedules, bandwidth controls, or other content-distribution policies. Review those independent controls when the timing, rather than the amount of data, is the problem.
Operational checklist
- Classify the content as an application or a package.
- For applications, rely on the built-in BDR behavior.
- For packages, select Enable binary differential replication individually during creation or editing.
- Install Remote Differential Compression on participating regular distribution points.
- Map the transfer path: parent-to-child site and site-server-to-regular-DP paths support BDR; pull-DP and content-enabled cloud-management-gateway paths do not.
- Expect changed existing files to benefit from block-level differences, while new files are copied.
- Track the five-incremental-version limit so a subsequent full content-set distribution is not mistaken for a configuration failure.
- Keep BDR conceptually separate from delta replication, throttling, and scheduling.
For the product definitions and current-branch qualification, consult Microsoft’s Fundamental concepts for content management in Configuration Manager, last updated October 4, 2022.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
