> 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.md). # Task Sequence Templates Instead of creating a task sequence from scratch, you can start with one of the predefined templates included with DeployR and customize it to meet your needs. To use a template: * From the DeployR task sequence list in the StifleR Dashboard, click the "+ Add" button and choose "Add from template".\ ![](https://content.gitbook.com/content/8m0VARX9oyZ2zXWCdPgr/blobs/L6ojgNlMieM6j86AzZkc/image.png) * Choose one of the available templates. Select **Open after creation** to open the new task sequence, then click **Clone**. * Click "Edit mode" to edit the task sequence. Ensure that all task sequence steps (for example, **Apply OS**) reference the required content items, then click **Save all changes**. ### Operating system tags Starting with DeployR 1.4, the templates are tagged with the environments they are designed to start in. When a task sequence has any of the tags `Windows PE`, `Windows 10`, `Windows 11`, or `Windows Server 2025`, it only appears in the task sequence list when the device is running one of the tagged environments. For example, the **Windows refresh** template is tagged `Windows 10` and `Windows 11`, so it is not offered when booting from Windows PE, and the bare metal templates are tagged `Windows PE`, so they are not offered in an existing OS. Task sequences without any of these tags are always listed. You can add or remove these tags on your own task sequences to control where they are offered. Templates that require DeployR Enterprise are also tagged `Enterprise`. --- # 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.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.