Quickly deploy Devolutions Server

This guide shows you how to quickly deploy and configure Devolutions Server.

Before you begin

  1. Download Devolutions Server.

    • Database access: Make sure you have access to the SQL database if the DB was created beforehand.

    • Certificate: Make sure you have a valid certificate. You can use a temporary self-signed certificate, but it should be replaced with a valid one afterward.

  2. Installation account.

    • Use the Domain Account DVLS_Owner for the installation.

    • The account must be a local administrator.

  3. It must have the following SQL permissions:

    • db_creator If the DB was not created beforehand.

    • Alter any login securable.

    • IIS prerequisites: Verify that all IIS prerequisites are installed using the Devolutions Server Console.

Installation of Devolutions Server

  1. Log in to the Server: Log in to the Windows Server that will host the Devolutions Server using the DVLS_Owner account.

  2. Install Devolutions Server: Follow the installation guide available here.

  3. Admin account and encryption keys : During the installation, you will be prompted to create a local administrator account. This account will serve as the primary Devolutions Server Administrator.

  4. Keep this account enabled at all times.

  5. Store the credentials securely outside the Devolutions Server (e.g., in a password manager).

  6. If your main authentication method ever fails, this account will allow you to regain access to the Devolutions Server web interface and restore authentication.

  7. You will also be asked to create a password for the encryption keys, which will be used to generate the Recovery kit. The Recovery kit is critical for recovery purposes. It contains a copy of the encryption keys file, encrypted with the password you define. If an issue occurs and only a database backup remains, these encryption keys will be required to decrypt the data. Without them, it will be impossible to recover the information stored in the Devolutions Server.

Post-installation configuration

  1. Change the IIS Web Application Identity

    • Go to IIS – Application pools – dvls – Advanced settings – Identity.

    • Change it to: DVLS_Runner.

  2. Set File permissions

    • Give modify rights on the App_Data folder of the website (default: C:\inetpub\wwwroot\dvls\App_Data) .This is required for the DPS_Main.log files.

  3. Update the Scheduler Service Account

    • Go to: Services – Devolutions Scheduler Service – Properties – Log On – This account

    • Change it to DVLS_Scheduler.

  4. Grant Read Permission on Encryption Config

    • Give read rights to the encryption.config file under the website folder (default: C:\inetpub\wwwroot\dvls\App_Data) for both accounts (DVLS_BRunner and DVLS_Scheduler).

  5. Apply the Least permission script

    • From the Devolutions Server Console, go to EditDatabaseAdvanced Credentials. Apply the least permission script to both accounts (DVLS_BRunner and DVLS_Scheduler).

Onboarding guide

Refer to the Devolutions Server onboarding guide for setup instructions.

Security score

Read this article to improve your Devolutions Server security score.

If you are using Remote Desktop Manager, you can create your Devolutions Server data source under FileData source.
Devolutions Forum logo Share your feedback