Minimum requirements
Devolutions Server requires Microsoft .NET 8.0 to operate. Please adapt your environment depending on which version you are running.
Devolutions Server now verifies that the domain and forest functional levels are at least Windows Server 2016. This is essential when using Active Directory authentication.
The following table lists the minimum recommended hardware specifications for Devolutions Server. These specifications may vary depending on the usage of the application, as indicated later in the topic.
| Basic implementation | Mid-Range implementation | Large implementation |
|---|---|---|
| (1-20 concurrent users) With a standalone SQL Server 4 core processors 8 GB RAM Network adapter (1 GB) |
(21-75 concurrent users) With a standalone SQL Server 4 core processors 8 GB RAM Network adapter (1 GB) |
(75+ concurrent users) We recommend deploying multiple Devolutions Servers in a load-balancing topology with a high-availability SQL Server. |
| With a SQL Server installed on the same machine. 4 core processors 16 GB RAM Network adapter (1 GB) |
With a SQL Server installed on the same machine. 4 core processors 16 GB RAM Network adapter (1 GB) |
See High-availability topology. |
Software dependencies
- Microsoft SQL Server 2016/2017/2019/2022 (including Express editions).
- Azure SQL database is supported with SQL login accounts only. Azure Active Directory accounts are not supported.
- Windows Server 2016, 2019, and 2022.
- Windows Server 2016 domain and forest functional level or higher.
- Microsoft .NET Framework 4.8 (required for the Devolutions Server Console).
- Microsoft .NET 8.0.
- Internet Information Services (IIS) 7.0 or later.
- Devolutions Server Console must be installed on the server to manage the Devolutions Server instance(s).
Server sizing
Many of our customers often ask how to properly customize their servers for various topologies. In fact, it is impossible for us to answer this question adequately. The way the system works has a significant impact on the resource usage of each node in your topology. Most of these configurations are virtual environments, making it easy to allocate additional resources.
For a proper estimate, the following aspects must be considered:
-
Number of entries stored in your instance (server details, credentials, etc.).
-
Churn of these entries; do you create entries daily or are they quite static?
-
Number of concurrent users that connect to the Devolutions Server instance during peak times.
-
User behavior:
- Are they launching 10 sessions at a time, doing a batch operation that takes a few minutes and then repeating the cycle; or
- Are they opening only a few sessions but working within them all day long?
This results in write operations to our logs; therefore, the former case is more intensive then the latter.
64-bit support
Devolutions Server is compatible with all 64-bit versions of Windows.