Online Help > Installation > Client

Terminal Services / Remote Desktop Services

Description

 

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

 

Please ensure that you have followed Microsoft's recommendation on how to setup a RDS environment. It will severally impact the performance if default Windows installations are performed.

 

https://docs.microsoft.com/en-us/windows-server/administration/performance-tuning/role/remote-desktop/session-hosts

Each user must have a unique application data folder (Roaming profiles or similar technologies). Remote Desktop Manager writes some user preferences to the local configuration file. The folder can be wiped out whenever the user logs out of the Windows Session, but it must be writeable for the duration of Remote Desktop Manager execution.

The Devolutions Web Login (DWL) was created for a normal desktop environment. It uses inter process communication (IPC) with the client application. Using it on a terminal server introduces a level of risk that may be unacceptable for corporate users.

 

If you insist on using it, it is critical that each user is assigned a distinct port and that port be kept secret. An application key must be set as well. The first client application that starts will be able to use the port exclusively. ALL Devolutions Web Login calling on that port will get the responses, unless an application key is set.

 

In summary, safe usage of DWL requires a manual configuration of both RDM and DWL, and this on each of the user profiles.

 

Procedure

 

1.Install by following the procedure For All Users. This ensures that the Microsoft Installer Database does contain all of the needed information for all user profiles of the host.

 

2.After installing Remote Desktop Manager, configure it as you prefer. We really recommend going through all the configuration options and finding the set of options that you wish to distribute. The data sources are of special interest because it is much better if they are configured by an administrator. You can even take the opportunity of locking the data sources to protect against any modification by the users. Please refer to Lock Data Source for more information.

 

When using an Advanced Data Sources, in order to have effective logging, 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 following patterns:
 

oThe data source is configured to always ask the user name and password;

oYou are using integrated security against SQL Server;

oYou use environment variables for the user name, and require the password.
(we recommend %USERDOMAIN%\%USERNAME% or %USERDNSDOMAIN%\%USERNAME%)

 

3.When Remote Desktop Manager is configured to your liking, use File - Options, 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

 

Do not check the options to include Devolutions Cloud Credentials as well as any data source that contains saved credentials while also enabling Include data source credentials.

 

4.Move that file in the installation folder of Remote Desktop Manager, if you have used the default installation settings, it is under %ProgramFiles(x86)%\Devolutions\RemoteDesktopManager.

 

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

 

A group policy exists to force the new configurations to be accepted automatically. Please consult the knowledge base article.

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 of of the Advanced Data Sources, you should rather use the Data source settings - Serial feature.

 

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

 

New default.cfg detected 

New default.cfg detected

 

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.