> 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/knowledge-base/how-to-articles/configure-devolutions-server-to-always-be-available.md).

# Configure Devolutions Server to always be available

Configure IIS application pool settings in Devolutions Server, such as start mode and idle timeout, to keep the web application always running.

To prevent that the Devolutions Server web application will recycle periodically and to be on idle mode, please follow these instructions.

1. Open IIS Manager and expand the ***Tree View*** and select ***Application Pools***. In the ***Application Pools*** list, select your web application and click on ***Advanced Settings*** in the Actions panel on the right. Then, change the ***Start Mode*** option to the value ***AlwaysRunning***.
2. Still in the ***Advanced Settings***, set the ***Idle Time-Out (minutes)*** option to the value 0. When this value is set to a value different to zero, on the first connection to the web site after an idle period, the application pool needs to create a new process, loads all needed frameworks. These operations can be very slow.
3. Finally, set the ***Regular Time Interval (minutes)*** option to the value 0. This will prevent the application pool to recycle periodically.


---

# 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/knowledge-base/how-to-articles/configure-devolutions-server-to-always-be-available.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.