Customizing a Task Sequence to Support BranchCache
Last updated
Last updated
Once you have a BranchCache enabled WinPE image it’s time to edit a task sequence to enable BranchCache and configure the Cache Location.
There are three phases within a task sequence which need to be modified in order to support BranchCache. Rather than documenting each task individually, 2Pint has conveniently created three task sequence modules which can be downloaded and imported into Configuration Manager directly.
Visit our Github respository to download a ZIP file which includes the three modules. On the top-right of the page, click the ellipse icon and in the menu, select the Download option.
Once downloaded, extract the ZIP to a shared folder on your Configuration Manager site server. This should result in three ZIP files referenced as Phase 1, Phase 2, and Phase 3.
In the Configuration Manager console, right-click the Task Sequences node and in the content menu, select Import Task Sequence. Follow the "Import Task Sequence Wizard" to import each Task Sequence module individually.
The result should be three new task sequences which can be later added to your deployment task sequences.
Please see this page on 2Pint OSD Module Details for more information on which steps are included in each module.
Review the OSD Toolkit Task Sequence Modules Details page for more information.
If you are currently using a StifleR Server, the StifleR Client should be installed during the task sequence in order to support peer-to-peer downloads of Software Updates or Applications later in the task sequence. In the Phase 3 Module, there is a disabled step which can be enabled to install the StifleR Client package.
Important Note: Even if you are not using the OSD Modules referenced on this page, it is highly recommended that you install the StifleR Client as soon as possible after the "Setup Windows and Configuration Manager" step in your task sequence.
Note: In order for the 2Pint Alternate Content Provider (BITSAcp.exe) to download the StifleR Client using p2p, the StifleR Client must be created as a package and not an Application.
If you want to include support for installing the StifleR Client, edit the task sequence: Module- 2Pint Software OSD Toolkit Phase 3.
Enable the "Installing StifleR..." task in the Options tab, and select the Package and Program for the StifleR Client.
You can add the above Task Sequences Modules to your deployment task sequence in specific sections of your current task sequence.
This can be done in the Task Sequence editor by selecting Add - General - Run Task Sequence.
The task sequences are then added as steps under your task sequence within the sections below.
