> 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.md).

# Getting started

Getting started with Devolutions Server covers domain requirements, Active Directory groups, and the installation steps for setting up a new instance.

A Devolutions Server instance is in itself a web server application which acts as a backend for our client applications. You can think of it as a specialized database for your data. All instances can be installed on the same physical server or spread across many. Devolutions Server can be installed through different [topologies](/server/overview-of-devolutions-server/topologies.md).

### Domain requirements

These requirements apply especially if you intend to use Automatic User Account Creation (see [Authentication](/server/web-interface/administration/configuration/server-settings/general/authentication.md)) and/or User Groups to manage your instance.

1. Create Active Directory groups to manage your instance. Typical examples are: Remote Desktop Manager Admins, Remote Desktop Manager Operators, Remote Desktop Manager Users.
2. Add domain users to the Active Directory groups.
3. Create a VaultDBOwner account that will be the owner of the database. Performing upgrades with this account will ensure the proper rights are held.
4. Create a VaultDBRunner account that will be used as the identity of the website. This will allow you to harden the permissions to what is minimally required.

### Installation steps

1. Create a new instance of Devolutions Server (see [Create Devolutions Server instance](/server/getting-started/installation/devolutions-server-instance-creation.md)).
2. Create a Devolutions Server administrator account in the [User management](/server/web-interface/administration/user-and-security-management/users.md).
3. Create [User groups](/server/web-interface/administration/user-and-security-management/user-groups.md).
4. Add domain users or built-in users (see [User management](/server/web-interface/administration/user-and-security-management/users.md)).

#### See also

* [Devolutions Academy – Devolutions Server path](https://academy.devolutions.net/student/path/2942210-devolutions-server?sid_i=0)


---

# 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 dynamically 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.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 `build a script that syncs our docs to a CMS` 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.