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' configuration.

1. Follow the installation procedure for all users. This ensures that the Microsoft Installer Database contains all of the needed information 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 configuration options to find the set of options that you wish to distribute. The data sources deserve special interest since it is much better when they are configured by an administrator. You may even take the opportunity to lock the data sources to protect against any modification by the users. Please refer to Lock Data Source for more information.

   When using advanced data sources, for effective logging methods, proper session security and user-based features, it is critical that each user has their own account to authenticate against the data source.

   Redistributing a data source registration should follow one of the patterns below:

   • The data source 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 data source that contains saved credentials while also enabling Include data source credentials.

3. When running Remote Desktop Manager under a Remote Desktop Services environment, we may have to tweak the parameters of the RDP entries to use less resources as possible and improve the startup performance of the application.

   1. To improve the Remote Desktop Manager startup performance, please see Solution #3 of the Startup performance article.

   2. To limit the memory consumption of RDP entries, please see RDP sessions memory tuning.

4. When Remote Desktop Manager is configured to your liking, use File – Settings – Export Options. This will allow you to choose exactly the data sources to include, as well as the various categories of settings. Please refer to Export options 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).

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.

A group policy exists to force the new configurations to be accepted automatically. Please see Apply policies to know how to deploy the Force the loading of the default.cfg file parameter.

If the user chooses to ignore the new configuration file when presented with the dialog below, he will not be presented with the choice until the date/time of the default.cfg file has changed.

If the main concern is deploying a new license key and you are using an advanced data source, you should rather use the feature to store it in Administration – Licenses.

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

By selecting Use New Configuration (Lose Mine), the user's configuration is simply overwritten. If you only wish to update the Remote Desktop Manager license key after a renewal, choose Retrieve New Registration Only.