> 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/windows-server-bare-metal-from-cloud.md).

# Windows Server bare metal from cloud

The **Windows Server bare metal from cloud** template deploys Windows Server 2025 without importing an operating system image first. Like the [Windows bare metal from cloud](/deployr/task-sequences/task-sequence-templates/windows-bare-metal-from-cloud.md) template, it downloads the operating system from Microsoft (here, the Windows Server 2025 evaluation media) and the driver pack from the device manufacturer.

The template contains these steps:

* **Windows PE**
  * **Set Windows settings**
  * **Format disk**
  * [**Apply Windows Server operating system from cloud**](/deployr/reference/step-definitions/apply-windows-server-operating-system-from-cloud.md): Datacenter evaluation, en-us, x64.
  * **Inject cloud drivers**
  * **Prepare OS**
  * **Reboot**
* **Full OS**
  * **Configure new OS**
  * **Enable BranchCache**
  * **Install updates**

After creating a task sequence from this template, review the edition and language on the **Apply Windows Server operating system from cloud** step. Evaluation editions expire after 180 days unless they are activated, so this template is best suited to labs and testing. Also consider adding an **Offline domain join** or **Enable Administrator account** step so that you can sign in to the new server.


---

# 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/windows-server-bare-metal-from-cloud.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.