Custom Installer and updates
Hi,
We uses SCCM to deploy RDM and use a custom installer on an older version. It works fine and I can see the cfg-file in the folder, but as it is an older version, then do our PatchMyPC updates RDM.
This does sadly remove the cfg-file and it takes to much time to created a new custom installer and package in SCCM very time RDM gets updated. We deploy workstations before users are going to use RDM, so that is why we are sad the configuration is gone when they a starting RDM for the first time.
So my questions - is there a way to prevent the CFG-file (default.cfg?) from being deleted when installing an update on a custom made installed RDM? Of cause might it be a PatchMyPC issue
Kind regards
Martin Jensen
All Comments (3)
Hello,
Thank you for contacting the Devolutions Support Desk !
The only solution would be to have your PatchMyPC application ignore RDM, as otherwise the custom installer will always update over the .cfg file.
Best Regards,
Sorry for the late reply, but have been away.
Not quite sure if you answer is the same way or the other way around as I believe PatchMyPC uses the default installer. It is our first installation with a custom installer that generates the .cfg-file.
But if the default installer also always delete the cfg-file, then is it the same thing for us - Just to be 100% sure :)
Hello,
If I understand correctly
Then the default installer is applying the default .cfg to your custom one, which is why you always need to restart.
Which is why PatchMyPC should ignore RDM
Best Regards,