Ok so I have been playing around with a custom RDM installer to aid in rolling out a base install for about 40 users.
Following the documents here (https://docs.devolutions.net/rdm/windows/installation/client/custom-installer-service/) which seem straight forward.
My base install just consists of some template changes, and some pre-defined folders, no hosts or credentials or anything stored. However when installing the custom installer, none of the defined settings are there, templates are not updated, and the pre-defined folder entries are not there.
When I created the installer file, I selected, Proxy Settings, Saved templates, Force always retrieve new registration, and I made sure to select the data source type of "local data source"
Yet after creating the msi file using this installer file, the install has none of the set settings, templates are all defaulted.. the base folders created are not there.
When building the custom installer I am using version 2023.2.32.0
One thing I just tested today was I made another installer, set the installer file with the correct settings I want, and as a test I set the default theme to dark.
After loading my custom installer msi, it ran but the only setting that stuck was the theme, the templates are not set, the folders I created in the installer are not there, nothing took except for the theme. Am I missing some step in this process? The creating seems straight forward yet, nothing I am looking to set it actually being set in the custom installer.
Are sub folders inside the data source not something can be defined in a custom installer?
Basically I want to define a few template settings, and have two domains folders with one sub folder of Credentials in them in the data source, no entries, no hosts, just the folder structure and templates defined yet they are not carrying over.
I have even tried a data source export and import with the folders and templates, yet even that doesn't work.. seems crazy that there is no way to replicate a local data source with any of the built in tools in RDM.
Hello,
You can simply copy the SQLite data source in %localappdata%\Devolutions\RemoteDesktopManager. RDM is not designed to shared a copy of data source to multiple users. Usually when you have a team, you create an advanced data source like SQL Server, Devolutions Hub and Devolutions Server.
Regards
David Hervieux
Why when making the custom installer, there is an option for the local data source, and templates, if it doesn't actually work?
Hello,
A ticket has been opened today in our ticketing system regarding questions about the custom installer.
We will use this case to contact you directly and schedule a remote session. My team will do this tomorrow morning.
Best regards,
Jeff Dagenais
Awesome, thank you. Look forward to your team's call.
Hello,
A ticket has been opened today in our ticketing system regarding questions about the custom installer.
We will use this case to contact you directly and schedule a remote session. My team will do this tomorrow morning.
Best regards,
Any ETA on this? Have not been contacted as of yet.
Hello,
We send you a email yesterday.
it is possible that our email may have landed in your junk folder. Could you kindly take a moment to check?
Thank you for your attention to this matter.
Best regards,
Carl Marien
I did check that before sending, nothing in my junk, but other communications from you guys all come through fine. I also did a message trace on my email server for all mail sent to me for the last two days, and I have nothing blocked there either. Also the only messages that came from @devolutions.net email are the forum posts and I received them all.
Hello,
It's quite peculiar. I'll forward you a link through a direct message. During our session, we can also investigate the potential issues with the email.
Best regards,
Carl Marien
Hello,
We were able to conduct a session together during which I explained that the custom installer can only save the configuration of RDM, not the data source entries. To address this, I have created an internal ticket to update the documentation accordingly.
Best regards,
Carl Marien