I am using RDM 10.1.13.0 (BETA). A few versions back (maybe 10.1.10.0 or 10.1.11.0), the command-line stopped working and I dismissed it at the time (hoping that it would be resolved in the next release). However, I just recently updated again and it still isn’t working. I have tried using both RDM 32-bit and RDM 64-bit but I experience the same results. I have a MS SQL 2008 R2 data source on a server. I am using a normal RDM command-line (by copying it from the Advanced page of the session) to try and open a RDP session (please note that the DataSource and Session data shown below were changed for security reasons):
"C:\Program Files (x86)\Devolutions\Remote Desktop Manager\RemoteDesktopManager.exe" /DataSource:ABC /Session:XYZ
If RDM is not running, the command-line will launch RDM but won’t open the RDP session. If RDM is already running, it will switch the Windows focus to RDM and bring it to the forefront but RDM still won’t launch the RDP session. I have tried using different RDP sessions and have the same results.
If I use other types of sessions (VMware, SCP, PuTTy, etc.), they all work with RDM – it is just RDP sessions no longer seem to be working. Interesting how these other session types don’t actually start RDM but only open up the requested session.
And the RDP sessions that won’t start when using the RDM command-line, they work fine when using the Web URL (although the data source is different with the Web URL??). But I use the following command-line from a Windows command prompt and it works correctly for RDP sessions (it doesn’t matter whether RDM is already running or not):
"C:\Program Files (x86)\Internet Explorer\iExplore.Exe" “rdm://open?DataSource=ABC&Session=XYZ”
Also, I still have not figured out why RDM doesn’t return to the command prompt after launching from the command-line (this isn’t anything new for RDM). When I launch RDM in a command prompt window, I have to press ENTER once to get back to a command prompt.
Thanks
edited by STGdb on 3/11/2015
This is fixed internally. I will release a new beta later today. The protocol handler works.
Sorry about that.
David Hervieux
No worries - thanks for the follow up / update!!
Got the update and installed/tested - issue resolved.
Thanks