Moving the Database

Hello,

We recommend consulting the top section of this help article to move your database properly.
https://help.remotedesktopmanager.com/tipsandtricks_data_migration.htm

Best regards,

We use a SQL server and our DBAs can move the databases just fine. However, how do you recommend we update all our users so that their local install of RDM can connect to the new Datasource location? Or is there some way to push that out through the program itself by leaving one up that points to the other?

Hello,

New server mean new server name, mean that the data source configuration need to be updated. The data source configuration (File -> Data Sources section) is saved in a file called RemoteDesktopManager.cfg. This file is located in %localappdata%\Devolutions\RemoteDesktopManager. This section of the file is encrypted, so we cannot edit it.

Firstly, I suggest to create your own .exe or .msi using our custom installer. This executable will contain the new data source pointing on the new server.
https://helpcloud.devolutions.net/custominstaller_introduction.htm

Secondly, I would manage the RDM version in your organization via the data source settings. In the Administration -> Data Source Settings -> Version Management section. In that section, it would be possible for you to configure the URL or network path to download your custom executable and manage the minimum and maximum version of RDM for your staff.

In conclusion, it's also possible to export the data source configuration into a .rdd and ask your staff to import it manually. However, there's a few manipulation to do, it depends if this something that is possible in your organization.

Best regards,

So it sounds like we'd either have to have everyone reinstall RDM with our custom file that contains the new database information?

So maybe I could set the Minimal version to v14 (since that doesn't exist yet) on our "old" database location. I could then insert a path to our new custom installer that's pointed to the new database? Then once they install the "new" version it would point them to the new location which would NOT have the minimal version set?

Hello,

Indeed, your users would need to reinstall RDM or you can wait to deploy your new database with a new version of RDM at the same time.

Regarding your second point, indeed, this should work.

Best regards,