Mac OS deployment
Currently generate a custom installer .msi that contains the datasource config and publish that to intune, looking into how to deploy Mac OS version is to package the normal installer with ~/Library/Application Support/RemoteDesktopManager.cfg from a configured machine.
This file doesn't seem to be the correct config file as when i try on a fresh install and replace the file after installing i still get the datasorce setup wizard when i launch the application, please help point me in the right direction :)
All Comments (6)
Hello,
If I understand correctly, you would like a way for users to install RDM and already have your datasources setup.
We do not currently have a feature like that for macOS. And the reason it doesn't work when you try to copy the .cfg file is because the datasources are not stored there, since they are encrypted.
If you really want to, we were able to copy datasources to an other RDM instance by copying the .cfg, .stv, .stb and .enc files. But be aware that this is not recommended since those files also contain other data related to licenses and other sensitive data.
The correct way to do this would be to export your datasources as .rdd files and ask the users to import them, but I understand this isn't as convenient.
Best regards,
Maxim Buisson
Hello,
If I understand correctly, you would like a way for users to install RDM and already have your datasources setup.
We do not currently have a feature like that for macOS. And the reason it doesn't work when you try to copy the .cfg file is because the datasources are not stored there, since they are encrypted.
If you really want to, we were able to copy datasources to an other RDM instance by copying the .cfg, .stv, .stb and .enc files. But be aware that this is not recommended since those files also contain other data related to licenses and other sensitive data.
The correct way to do this would be to export your datasources as .rdd files and ask the users to import them, but I understand this isn't as convenient.
Best regards,
@Maxim Buisson
Hi Maxim,
so if the datasource is exported as a .rdd is the only way to deploy this being a manual import, not able to be automated or bundled in a package?
Hi,
Correct, .rdd files must be manually imported. However, since we have had this situation with other clients before, I'm wondering if we could not add a feature to do this automatically...
If we add something so when RDM opens, if .rdd files are present in the 'Library/Application Support/com.devolutions.remotedesktopmanager' folder, they get automatically imported, would that give you the result you want ? I could create a feature request for this.
Please let me know if that sounds good to you or if you have an other idea.
Best regards,
Maxim Buisson
yes if that effectively has the same outcome as when we create a basic .MSI that would work, all we want is for the name and datasource url to be populated on a devolutions server instance, i dont think that folder would work though as would not exist if never installed and not everybody uses so wouldn't want to send to everyone.
But yes if we can do it this way that would really help as we are now deploying lots or Macs as our security policy has been updated.
I see,
I will create a ticket and talk to people to think of the best way to do this. We will let you know when we have updates.
Best regards,
Maxim Buisson
great many thanks.
Dean