RDM: Pre-configuring DVLS Data Source / SSO Settings for All Users
Hi Team,
We are currently deploying Remote Desktop Manager (RDM) in a shared/server-based environment where vendors log into a Windows host, launch RDM, and connect to our Devolutions Server (DVLS).
Today, users are required to manually configure the DVLS data source (host + “Use domain single sign-on (SSO)” option) the first time they open RDM. We are looking for a way to streamline and standardize this experience.
Objective:
We want users to log into the server, open RDM, and be immediately ready to go — without needing to configure the DVLS connection themselves.
Questions:
(lots of questions, feel free to combine)
Environment Context:
We’re trying to eliminate user-side configuration drift and reduce onboarding friction while maintaining a secure, standardized connection method.
Appreciate any guidance or documentation you can point us to.
Best,
Jimmy
Hello Jimmy,
Is there a supported method to pre-configure or “bake in” the DVLS data source settings (host, SSO enabled, etc.) for all users?
Indeed, I would suggest the Custom installer service, where you can deploy the MSI file including a pre configured data souce.
Is there a recommended approach for multi-user or RDS/VDI environments to ensure a consistent, zero-touch initial setup?
For TS advices I can recommend the following KB topic: Remote Desktop Services (Terminal Services).
Regards,
Min
Hello Jimmy,
Is there a supported method to pre-configure or “bake in” the DVLS data source settings (host, SSO enabled, etc.) for all users?
Indeed, I would suggest the Custom installer service, where you can deploy the MSI file including a pre configured data souce.
Is there a recommended approach for multi-user or RDS/VDI environments to ensure a consistent, zero-touch initial setup?
For TS advices I can recommend the following KB topic: Remote Desktop Services (Terminal Services).
Regards,
Min
@Min Destens
Thanks for pointing me to the Terminal Services documentation — I’ve reviewed that approach around using a shared/default configuration.
I understand how default.cfg can be used to standardize settings, but I’m unclear on how to ensure our DVLS data source is fully preconfigured and used by default.
Our goal is for users to launch RDM and automatically connect to our DVLS using SSO, without needing to manually add or select a data source.
From the documentation, it’s not clear:
Is there a recommended or supported way to achieve this using the Terminal Services / shared configuration method, or is the Custom Installer still the only way to fully preconfigure the DVLS connection?
Also, for users who have already launched RDM, is there a way to centrally enforce or update this configuration?
Appreciate the clarification.
Jimmy