Avoid creating the default datasource when opening RDM the first time

Hello,

To my knowledge what could be done is you can remove the credentials from your data source configuration, under File > Data Sources, once that's done export the data source configuration, and when your users open up RDM they can then import the data source configuration file into their local installation. Since the credentials would be empty the last step would be to login to the data source.

To my knowledge, there's no other way to make the process easy without the need of a custom installer package.

If you truly wish to make it so that RDM is preconfigured before the first launch, the custom installer is your only solution.

Best Regards,

HI,

On launch, if no data source exists, RDM will automatically create a SQLite data source.
I don't think there's a way around that.
However, you could run a PowerShell script (using our PowerShell module) that could create the appropriate data source and delete the SQLite one.

Would that be an acceptable workaround?
Regards

Note I'm not the OP but would like to react on this.
As a matter of fact we already have something like this, we have a PowerShell script for this, that runs (once) on initial login of any user on a workstation. It configures the default RDM datasource. That script has been working fine until about a year ago, until the powershell module was changed from being included in the install, to a separate download from the PSGallery.
As of that time, it broke. I used the new PS module, when creating an RDM datasource in PowerShell it IS visible on PowerShell, but it is NOT visible in the GUI, nor is it active when the application starts.
I've already mentioned that in https://forum.devolutions.net/topics/37654/newrdmdatasource--does-not-create-new-datasource-anymore

Regards, Ben van Zanten

Hello,

to be honest I don´t like the way this works. Instead of automatically creating a SQLite datasource on first launch, you could ask if this should be done. Because the way you do it now leaves some garbage on workstations, where MS SQL is used. And if the user does not follow the rules he has two datasources configured which could also be confusing.

I like and use PowerShell for various automation tasks, but fixing something that should be done different is not my favorite usage of PowerShell. And as Ben wrote - the module is no longer shipped with RDM. And I don´t want to deploy it to all workstations where RDM is used. The PowerShell module should be included...

What about a GPO that when not configured creates a default SQLite database, but when enabled and set to MS SQL, this database connection is created, and ideally with the parameters passed via GPO. This is what an enterprise expects.

Would be nice if you could pass this to your developers for review.

Brgds Andreas

Hello,
We plan to add an onboarding wizard in RDM 2023.1 to ask if you want to add a SQlite, Hub Personal or another data source type. I will add your idea to use GPO or something that can be deployed easily as an alternative to the custom installer.

Regards

Hello,

that would be great!!! And PLEASE use GPO as this would be the easiest way for an enterprise to do it. No need to create a custom installer and easy to deploy.

Basically it would be gread to have ALL (important) configuration options available as an GPO. This will be a lot of work to do for you, but would make admin life much easier and controllable!

Brgds Andreas