We are currently running RDM from a network drive for all users, so that configuring and updating only must be done once. Now we encountered the fact that this gives a small problem in our mixed environment with Windows 7 32bit and Windows 7 64bit.
Due to the fact that everybody uses the same remotedesktopmanager.cfg, the path to several addons differs and must be adjusted everytime to the 32bit (c:\program files) or 64bit (c.\program files (x86)) system. Is there a possibility to set an option per session, that it should have the 64bit path to look for?
Currently we have this phenomenon with the SQL Management Studio plugin anf the FileZilla Plugin.
Or is there any other possibility to get around this problem except from installing RDM locally, which would make updating a bit more complicated.
Thanks for your suggestions!
edited by klages on 10/27/2010
Hi,
I understand your problem, can you try the latest beta, I added a new registry key to set the path for the option:
Windows Registry Editor Version 5.00
[HKEY_CURRENT_USER\Software\RemoteDesktopManager]
"OptionPath"="%AppData%\RemoteDesktopManager"
David Hervieux
I don't think this is the right solution. If I add the registry key to my system, the real path for the .cfg is not recognized, everythime I start RDM.
I'll try to specify the scenario a bit more:
RDM is installed on a network drive, eg. drive G:\RDM. In this path lies the whole application, .cfg file and the database. The addons for SQL Management Studio and Filezilla are integrated. Every user starts RDM fom G:\RDM and has no local installation of RDM.
The Filezilla and SQL Management Studio applications are installed local in C:\Program Files on our 32bit systems or in C:\Program files (x86) on our 64bit systems.
The Problem now is, that the RDM plugins ask for the path, where the needed applications are installed. FOr example, the Filezilla Plugin asks me, and I set the path on my 32bit system to "C:\Program files\filezilla\filezilla.exe" for the plugin. So far everything is ok.
But when RDM is startet on a 64bit system, this path to the FileZilla application is not found, because it is installed in C:\program files (x86). So it must be corrected everytime a plugin is used on 32bit or 64bit.
I looked in the .cfg file, and there is only one path written for the FileZilla plugin, where the path to the application ist set.
I think of the following possible solutions:
- duplicate addons (one for 32bit path, one for 64bit path), but this is not really good due to the large number of different plugins
- providing an option per session, if the target application path is for 32bit or 64bit
- RDM automatically recognizes, if it is started on a 32bit or 64bit system and uses the correct path for the applications, without asking for the 64bit path and writing it into the .cfg
I hope this helps a bit.:)
edited by klages on 10/29/2010
Hi,
I don't understand why it's not working? The goal was to allow each user to have his cfg file saved locally on their machine, even if the application is installed on a shared drive. This mean that for each user will be prompted once with the installation path and after that the setting will be saved correctly on each machine.
You said that it was not working, what folder have you entered in the registry ? have you set it to %AppData%\RemoteDesktopManager ?
Can you verify that the cfg was correctly created at this location ?
David Hervieux
Aah, now I see where the .cfg is created: C:\Users\USERNAME\AppData\Roaming\RemoteDesktopManager
I'll do some tests and give feedback!
Update:
Ok, a short test showed that your solution works.
We now can create the reg key on each machine and copy the .cfg from the network drive onto the local machine. This truely has several advantages.
And again, thanks a lot for your work!
edited by klages on 10/29/2010
Hi,
I'm glad to hear that it works. Yes there is many advantages, like the local favorites, personal data sources, and more
David Hervieux