Topic "URL Protocol Handler REG entry issue" a message from twistfox

ok, ran into this problem trying to get RDM working with the URL's it will generate. I don't know precisely when this bug got introduced, but on upgrading to the latest version of 9.2.10 I still had some bad entries in the registry. Now, we originally installed way back in version 8 I think and have been upgrading since (might even have been 7), and i'm assuming the upgrade logic doesn't check the actual windows registry entries to see if they are all there. I haven't used this feature prior to today.

The basic problem is there are a few things missing in the windows registry in order to get it working as a URL protocol Handler.

1. HKey classes root\rdm key needs to have the reg string value of &quotURL Protocol&quot added
2. The hkey_classes_root\rdm\shell\open has a extra slash right before the remotedekstopmanager.exe entry that needs to be removed.

For example, here is the registry output in question for something that does NOT work.

HKEY_CLASSES_ROOT\rdm]
@=&quotURL:rdm Protocol&quot

[HKEY_CLASSES_ROOT\rdm\DefaultIcon]
@=&quotC:\\Program Files (x86)\\Devolutions\\Remote Desktop Manager\\\\RemoteDesktopManager.exe&quot

[HKEY_CLASSES_ROOT\rdm\shell]

[HKEY_CLASSES_ROOT\rdm\shell\open]

[HKEY_CLASSES_ROOT\rdm\shell\open\command]
@=&quotC:\\Program Files (x86)\\Devolutions\\Remote Desktop Manager\\\\RemoteDesktopManager.exe \&quot%1\&quot&quot

Here is the registry output of something that I cleaned up and got working.


[HKEY_CLASSES_ROOT\rdm]
@=&quotURL:rdm Protocol&quot
&quotURL Protocol&quot=&quot&quot

[HKEY_CLASSES_ROOT\rdm\DefaultIcon]
@=&quotC:\\Program Files (x86)\\Devolutions\\Remote Desktop Manager\\\\RemoteDesktopManager.exe&quot

[HKEY_CLASSES_ROOT\rdm\shell]

[HKEY_CLASSES_ROOT\rdm\shell\open]

[HKEY_CLASSES_ROOT\rdm\shell\open\command]
@=&quotC:\\Program Files (x86)\\Devolutions\\Remote Desktop Manager\\RemoteDesktopManager.exe \&quot%1\&quot&quot



Once those two things are resolved we can now pass URL strings in IE, and get it working (Chrome is still locking us out, but that's a chrome specific issue from what I can tell).

While I can adjust this on our current installs, if the upgrade switches it back to not working, or just having to remember to do it on all new installs is a bit of work. Can we get the installer to make sure these entries are correct in the future?