# Configure Microsoft Peer-to-Peer Components

## Enabling BranchCache <a href="#toc30142823" id="toc30142823"></a>

BranchCache is the key Microsoft peer-to-peer technology in which StifleR manages the best. In order to prepare for a successful POC, it is important to enable BranchCache on all systems relevant to the POC.&#x20;

### Step: If using Configuration Manager, enable BranchCache on all Servers / CM Distribution Points

If you have a simple lab environment, you should perform this step (if required) on all your Distribution Points. If you are planning on testing in a production environment, make sure that you perform this step ONLY on the relevant DP where your test clients will obtain their deployment content. The below page describes the process of enabling BranchCache on Windows Server, including DPs.&#x20;

* [ ] [Configuring BranchCache on Windows Server](https://documentation.2pintsoftware.com/stifler/2.10/configuration/configuring-branchcache-on-windows-server)

## Enabling Delivery Optimization <a href="#toc30142831" id="toc30142831"></a>

As well as BranchCache, StifleR can utilize download jobs which use Microsoft's Delivery Optimization (DO) peering technology. See the below page for more information on DO and some caveats:

* [ ] [Configuring Delivery Optimization](https://documentation.2pintsoftware.com/stifler/2.10/configuration/configuring-delivery-optimization)

## Enabling LEDBAT on CM DPs (Optional)

Microsoft integrated LEDBAT technology into Configuration Manager distribution points several years ago. LEDBAT is a bandwidth congestion control technology which is designed to use unused bandwidth and to reduce network congestion when load is high. See the below page for more information on LEDBAT and how to enable it:

* [ ] [Enabling LEDBAT on CM DPs](#enabling-ledbat-on-cm-dps-optional)

## Remove BITS Policies <a href="#toc30142842" id="toc30142842"></a>

In this step you will check for and remove any BITS policy that has been set within Configuration Manager and/or Active Directory. Such settings can interfere with the efficient operation of the automated Bandwidth mechanisms in StifleR.&#x20;

### Step: Remove Configuration Manager Client BITS Policy (if configured) <a href="#toc30142843" id="toc30142843"></a>

In the Configuration Manager console, BITS settings can be configured in "Client Settings" as shown below:

<figure><img src="https://109907496-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYUaU4nvWOjjzrdVpKtdy%2Fuploads%2F4t719EWVdhTzqvbWViWl%2FStifleR-2.10-DisableBITSinCM.png?alt=media&#x26;token=37a22010-af03-4b49-a5b1-883776bc8441" alt=""><figcaption></figcaption></figure>

Make sure that this is set to **No** (default setting), as this configures a local BITS policy on the clients which we do not want.

### Step: Remove any BITS AD Group Policy (if configured) <a href="#toc30142844" id="toc30142844"></a>

Within the Active Directory Group Policy Editor, go to:\
**Computer Configuration** - **Policies** - **Administrative templates** - **Network** - **Background Intelligent Transfer Service (BITS)**

Ensure that there are no BITS policies configured. If present, remove them from effecting any test clients.