> 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/rdm/installation/client/remote-desktop-services-terminal-services.md).

# Remote Desktop Services (Terminal Services)

Remote Desktop Manager has an excellent support for running under a Remote Desktop Services environment. A master configuration file can be created to distribute settings for all new users of the system or even to update existing users' configurations.

{% hint style="success" %}
Make sure to follow [Microsoft's recommendations](https://learn.microsoft.com/en-us/windows-server/administration/performance-tuning/role/remote-desktop/session-hosts) regarding RDS environment setup as default Windows installations severely limit performance.Each user must have a unique application data folder (roaming profiles or similar technologies). Remote Desktop Manager saves some user preferences on the local configuration file. The folder can be wiped out whenever the user logs out of the Windows Session, but it must be accessible for the duration of Remote Desktop Manager execution.
{% endhint %}

### Procedure

1. Follow the installation procedure [for all users](https://docs.devolutions.net/rdm/installation/client/all-users/). This ensures that the Microsoft Installer Database contains all the information needed for all the user profiles of the host.
2. After installing Remote Desktop Manager, configure your preferences. It is recommended to go through all the options to find the set of options that you wish to distribute. The workspaces deserve special attention since it is much better when they are configured by an administrator. You may even take the opportunity to lock the workspaces to protect against any modification by the users. See [Lock a workspace](https://docs.devolutions.net/rdm/workspaces/lock/) for more information.

{% hint style="danger" %}
When using [Devolutions Server or Devolutions Cloud workspaces](https://docs.devolutions.net/rdm/workspaces/workspace-types/native-workspaces/), it is critical that each user has their own account to authenticate against the workspace. This enables effective logging methods, proper session security, and user-based features.Redistributing a workspace registration should follow one of the following patterns:- The workspace is configured to always ask the username and password.

* You are using integrated security against SQL Server.
* You use environment variables for the username and require the password (we recommend %USERDOMAIN%%USERNAME% or %USERDNSDOMAIN%%USERNAME%).

Do not enable the options to include Devolutions Account credentials as well as any workspace that contains saved credentials while also enabling ***Include workspace credentials***.
{% endhint %}

3. When running Remote Desktop Manager under a Remote Desktop Services environment, it is best to tweak the parameters of the RDP entries to use as few resources as possible, thus improving the startup performance of the application.
   * To further improve the Remote Desktop Manager startup performance, consult solution #3 of the [Startup performance](https://docs.devolutions.net/rdm/kb/troubleshooting-articles/startup-performance/) article.
   * To limit the memory consumption of RDP entries, refer to [RDP sessions memory tuning](https://docs.devolutions.net/rdm/kb/how-to-articles/rdp-session-entry/memory-tuning-rdp-sessions/).
4. Once Remote Desktop Manager is configured, click on ***File*** – ***Settings*** – ***Export options***. This will allow you to choose exactly the workspaces to include, as well as the various categories of settings. Please refer to [Export options](https://docs.devolutions.net/rdm/commands/file/options/export/) for further details. Save the file with the name default.cfg.
5. Move the default.cfg file in the default installation folder of Remote Desktop Manager (`C:\Program Files\Devolutions\Remote Desktop Manager`).

{% hint style="info" %}
Remote Desktop Manager will automatically choose the newest file between remotedesktopmanager.cfg**and default.cfg**in the Local AppData folder.
{% endhint %}

### Workflow

#### New users

Whenever a new user creates a profile on the system, Remote Desktop Manager detects the presence of the `default.cfg` file and uses it as a template to create the user's configuration file.

#### Existing users

There is a group policy to automatically force the new configurations. See [Apply policies](https://docs.devolutions.net/rdm/kb/how-to-articles/group-policies/) to find out how to deploy the **Force the loading of the default.cfg file** policy.

If the user chooses to ignore the new configuration file when presented with the dialog below, they will not be offered the choice until the `default.cfg` file is modified.

Whenever Remote Desktop Manager is started and it detects a new `default.cfg` file, the following dialog will appear:

![](https://cdnweb.devolutions.net/docs/RDMW6051_2025_3.png)

By selecting ***Use new configuration (lose mine)***, the user's configuration is simply overwritten. ***Keep my configuration*** retains the user's configuration and ignores the new default file.


---

# 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 current page URL with the `ask` query parameter:

```
GET https://docs.devolutions.net/rdm/installation/client/remote-desktop-services-terminal-services.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
