> 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/deployr/task-sequences/task-sequence-templates/cache-all.md).

# Cache All

{% hint style="info" %}
BranchCache peering requires DeployR Enterprise.
{% endhint %}

The **Cache All** template pre-loads DeployR content into the BranchCache cache of an existing Windows device. Other devices on the same network can then download the content from that device instead of from the DeployR server. Use it to pre-stage content at a site before a deployment.

The template contains two steps:

* [**Enable BranchCache**](/deployr/reference/step-definitions/enable-branchcache.md): makes sure BranchCache is installed and configured.
* [**Cache content**](/deployr/reference/step-definitions/cache-content.md): downloads all active content item versions into the cache, including boot images. Versions still in development are skipped.

Run this task sequence in the full OS of a device that stays on the network, for example from Intune or by starting the DeployR client. See [Starting a task sequence in an existing OS](/deployr/deployment-methods/starting-a-task-sequence-in-an-existing-os.md).

To cache only some content, specify a tag on the **Cache content** step. Only content items with that tag are cached.


---

# 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/deployr/task-sequences/task-sequence-templates/cache-all.md?ask=<question>&goal=<user_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.