> 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/reference/step-definitions/apply-windows-server-operating-system-from-cloud.md).

# Apply Windows Server operating system from cloud

The **Apply Windows Server operating system from cloud** step works like [Apply operating system from cloud](/deployr/reference/step-definitions/apply-operating-system-from-cloud.md), but for Windows Server. It downloads the Windows Server 2025 evaluation media from Microsoft and applies it to the `S:` volume created by the **Format disk** step.

The step always applies the **Desktop Experience** installation of the selected edition, not Server Core.

### Options

| Option                        | Description                                                                                                                                                                                                        |
| ----------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Operating system              | **Windows Server 2025**.                                                                                                                                                                                           |
| Language code                 | Operating system language, for example `en-us`.                                                                                                                                                                    |
| Operating system edition      | **ServerStandardEval** (Standard evaluation) or **ServerDatacenterEval** (Datacenter evaluation).                                                                                                                  |
| Operating system architecture | **x64**.                                                                                                                                                                                                           |
| Unattend.xml answer file      | Optional content item containing an `unattend.xml` file, used with the **Use provided unattend.xml** continuation method.                                                                                          |
| Continuation method           | How the task sequence resumes in the new OS. The choices are the same as for the [Apply operating system](/deployr/reference/step-definitions/apply-operating-system.md) step. Default: **Use SetupComplete.cmd**. |

{% hint style="info" %}
Select the edition when you add this step. The evaluation editions are the only ones available from the cloud.
{% endhint %}

Evaluation editions expire after 180 days unless they are activated with a product key. To use a licensed Windows Server image, import it as an operating system content item and use the **Apply operating system** step instead.

The [Windows Server bare metal from cloud](/deployr/task-sequences/task-sequence-templates/windows-server-bare-metal-from-cloud.md) template uses this step.


---

# 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/reference/step-definitions/apply-windows-server-operating-system-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.