Hello,
I found you use hardcoded paths at the RDM configuration.
This is bad if you need to recover a RDM configuration on another PC without an existing export.
I need to create a user with the same name like on the old PC to get the configuration running and to do an export.
It would better if you use a variable for this like "%LOCALAPPDATA%\Devolutions\RemoteDesktopManager" .
Kind regards
Stefan Klatt
Hello,
We don't use hardcoded path by default. The path is exactly the one you've posted if RDM is installed in %program files% but if it's installed in another folder, it will use this folder. This is used for the portable version of RDM.
https://docs.devolutions.net/rdm/installation/client/configuration-file-location/
Let me know if I missed something
Regards
David Hervieux
I used RDM on a VM with the User "stefan", the user profile path was
c:\Users\stefan
This VM crashed and I used a new VM with user "stefan.CAC":
c:\Users\stefan.CAC
Then I copied from the old VM the complete configuration from
c:\Users\stefan\AppData\Local\Devolutions\
to the new VM with the path
c:\Users\stefan.CAC\AppData\Local\Devolutions\
On the new VM RDM couldn't start because it tried to create a file at the profile path
c:\Users\stefan
I got it working with creating a user "stefan" at the new VM with the profile path "c:\Users\stefan", exporting the configuration and importing it at the correct user "stefan.CAC".
Hello,
We don't use hardcoded path by default. The path is exactly the one you've posted if RDM is installed in %program files% but if it's installed in another folder, it will use this folder. This is used for the portable version of RDM.
https://docs.devolutions.net/rdm/installation/client/configuration-file-location/
Let me know if I missed something
Regards
@David Hervieux
No comment?
Hello,
Is it only the data source configuration that is hard coded? You can take a look in File->Data Sources?
Regards
David Hervieux