Configure Microsoft Peer-to-Peer Components
Last updated
Last updated
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.
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.
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:
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:
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.
In the Configuration Manager console, BITS settings can be configured in "Client Settings" as shown below:
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.
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.
