Prevent team users to create solo databases

Resolved

Prevent team users to create solo databases

avatar

Hi, i am doing a poc with RDM using a central SQL database. Got everything working so far, but users are able to add a datasource to RDM. Is there a way to prevent this? I do not want users to create other datasources, and be able to leak credentials etc. Is this possible using RDM?

avatar

Recommended Answer

Hi!

Thanks for posting.

You can disable the ability to add a new workspace (formerly data source) with the help of GPOs - https://docs.devolutions.net/rdm/knowledge-base/how-to-articles/apply-policies-gpos

Disable the menu File – Workspaces
%Root%\SOFTWARE\Policies\Devolutions\RemoteDesktopManager\DisableFileDataSources

Hope this helps!

Regards,

Marc Beauséjour

All Comments (5)

avatar

Hi!

Thanks for posting.

You can disable the ability to add a new workspace (formerly data source) with the help of GPOs - https://docs.devolutions.net/rdm/knowledge-base/how-to-articles/apply-policies-gpos

Disable the menu File – Workspaces
%Root%\SOFTWARE\Policies\Devolutions\RemoteDesktopManager\DisableFileDataSources

Hope this helps!

Regards,

Marc Beauséjour

avatar

Thanks Marc! I will look into that. Looks like this is what i am looking for.

avatar

I found a setting to block the access to datasources. But i cannot seem to find a setting to set the default datasource? The user must be able to select the SQL database at first logon. Or am I missing something?

avatar

Hello,

Thanks for your question — here's how to set this up.

There isn't a standalone "default data source" toggle in RDM. Instead, this is handled through the Custom Installer Service, which replicates your reference RDM configuration into a deployable installer package:

  1. On your reference RDM instance, configure the SQL data source as you want it to appear for all users — using integrated security or an environment variable for the username (never a hardcoded password).
  2. Go to Tools – All tools – Custom installer service – Export custom installer configuration.
  3. This generates an .rdi installer file that replicates your current configuration, including the data source(s) you've set up.
  4. Deploy the resulting installer, then either copy the generated default.cfg into the installation folder (%ProgramFiles(x86)%\Devolutions\RemoteDesktopManager by default), or use the "Use new configuration" option so the installer automatically overrides the default configuration file.


As a result, on first launch, users will see the SQL data source already pre-configured instead of a blank "New data source" screen. Since you won't be including workspace credentials (leave the "Include workspace credentials" option unchecked), they'll still be prompted to enter their own SQL login credentials — which is exactly the behavior you're looking for.

Full documentation here: RDI file generation options

Best regards,

Tommy Sanders

avatar

Thank you for your reply! This is just what I am looking for.

Regards

Jack