> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/server/getting-started/installation/web-server-prerequisites.md).

# Web server prerequisites

Devolutions Server requires IIS Manager, URL Rewrite, Application Request Routing, and the Microsoft .NET 10.0 hosting bundle as prerequisites.

The installation of Devolutions Server is supported by Windows Server 2016, 2019, 2022, and 2025.

As a web application, Devolutions Server requires the following:

* IIS Manager
* The following Microsoft IIS modules:
  * [URL Rewrite](https://www.iis.net/downloads/microsoft/url-rewrite)
  * [Application Request Routing](https://www.iis.net/downloads/microsoft/application-request-routing)
* [Microsoft .NET 10.0](https://dotnet.microsoft.com/en-us/download/dotnet/10.0) hosting bundle
* Specific web server roles on the host machine

These prerequisites can be installed from the Devolutions Server Console or through an existing PowerShell script provided with the Devolutions Server Console.

Installing prerequisites from [Devolutions Server Console](/server/devolutions-server-console.md) or from the PowerShell script requires internet access to download the following:

* [Microsoft .NET 10.0](https://dotnet.microsoft.com/en-us/download/dotnet/10.0) hosting bundle
* [.NET Desktop Runtime 10.0](https://dotnet.microsoft.com/en-us/download/dotnet/10.0) (Devolutions Server Console)
* The following Microsoft IIS modules:
  * [URL Rewrite](https://www.iis.net/downloads/microsoft/url-rewrite)
  * [Application Request Routing](https://www.iis.net/downloads/microsoft/application-request-routing)
* [Microsoft Edge WebView2](https://developer.microsoft.com/en-us/microsoft-edge/webview2/consumer/) (Devolutions Server Console)

### Devolutions Server Console method

1. Open the [Devolutions Server Console](/server/devolutions-server-console.md).
2. Go in the ***Support*** tab and click on ***IIS Diagnostic***.
3. Click on ***Install Prerequisites*** to run the PowerShell script. The window below only appears if a prerequisite is missing during a new installation or an update.

### PowerShell method

1. Run Windows PowerShell with elevated privileges.
2. Change the current path to the sub-folder Scripts that is located in the current installation folder of Devolutions Server Console (**C:\Program Files (x86)\Devolutions\Devolutions Server Console\Scripts**).
3. Run the **DVLS-Prerequisites.ps1** script.
4. The script will install the missing web roles and the following IIS components:
   * IIS [URL Rewrite](https://www.iis.net/downloads/microsoft/url-rewrite) module.
   * IIS [Application Request Routing](https://www.iis.net/downloads/microsoft/application-request-routing) module.
   * [Microsoft .NET 10.0 Core Module hosting bundle](https://dotnet.microsoft.com/en-us/download/dotnet/10.0).

### Required HTTP verbs

Devolutions Server uses the following HTTP verbs. They must be allowed in the IIS ***Request Filtering*** feature (***HTTP Verbs*** tab) of the Devolutions Server website:

* GET
* POST
* PUT
* DELETE
* PATCH

{% hint style="info" %}
The ***web.config*** file of Devolutions Server removes the IIS WebDAV module for the website, since it can intercept PUT and DELETE requests. If a Request Filtering rule at the server level denies one of these verbs, IIS rejects the requests that use it before they reach Devolutions Server.
{% endhint %}


---

# 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://docs.devolutions.net/server/getting-started/installation/web-server-prerequisites.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.