> For the complete documentation index, see [llms.txt](https://documentation.2pintsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.2pintsoftware.com/osd-toolkit/appendix/2pint-osd-toolkit-task-sequence-module-details/module-2pint-software-osd-toolkit-phase-2.md).
# Module- 2Pint Software OSD Toolkit Phase 2
## Overview
This module should be added before the **Setup Windows and Configuration Manager** step in which the target OS is already laid down on the disk.
## Individual Steps
### Setting BranchCache Repub Quorum Size Windows
This step will set the RepubQuorumSize registry value to 100 in Windows. There a detailed article which explains why we recommend changing this value [here](https://2pintsoftware.com/news/details/optimizing-branchcache-with-repubquorumsize-an-undocumented-yet-crucial-tweak).
### Moving BranchCache
The step executes the BCEnabler.exe utility to move the BranchCache cache to the target OS drive. For more information on BCEnabler.exe, check out this [page](/osd-toolkit/appendix/enabling-branchcache-in-the-deployment.md).
#### Options
This group /step will run if the following conditions are met:
File: **x:\Windows\System32\BCEnabler.exe**
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://documentation.2pintsoftware.com/osd-toolkit/appendix/2pint-osd-toolkit-task-sequence-module-details/module-2pint-software-osd-toolkit-phase-2.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
