Default RDP client?
I use an application/database to manage servers that I work on (homegrown by some developers that I work with). It's a fantastic app, and it works great. It has a button to click on to launch the RDP client with the server I am currently looking at in the database. Is there any way to get RDM to be the default client to load up with that server as a quick connect session? I would much rather have the servers load up in RDM instead of the default RDP client because I have multiple windows (sometimes over a dozen or so) at the same time, and it drives me crazy! I would be so happy if I could get the connect button to launch a quick connect session in RDM, so I could have all of my sessions inside of one application window.
If you tell me that the developers would have to re-tool their app to look for RDM, that is not going to be a solution for me, because I am one of about a dozen members on my team that use RDM (the others just won't embrace anything 3rd party), and it's my own choice to use it (although I think the entire support team should be using it!). I can continue to copy and paste the server name from the database into RDM, but I would REALLY like to have it tie together seamlessly.
Is this even a possibility to do?
edited by grberk on 12/13/2012
All Comments (6)
Yo! Anyone! Hello? No response? Where is support? Is this even possible?
What is the command that this app executes? I would suspect that it is calling mstsc.exe directly. If that is the case not sure we could "redirect it" to RDM.
We do however have the option of calling RDM via command line which might help you (first create a local template for you rdp sessions) then type something like:
remotedesktopmanger.exe /Datasource:8d9b43ce-7bbb-4f20-8ab6-76199fff2a1f /Template:84313c97-3efb-423d-b48e-92107d6a7294 /Host:PC002
(to get the IDs for the command line, see the Advanced tab Data Source ID & Session ID fields)
More info on the RDM command line arguments can be found here:
http://help.remotedesktopmanager.com/index.html?installation_commandlinearguments.htm
Hope that helps,
edited by stefane on 1/22/2013
Stéfane Lavergne
I am pretty sure that when I click on the "Launch RDP" button in our app that it directly calls MSTSC.exe with the paramaters of the currently selected host. I would have to check with the developer and see for sure.
It would be nice to be able to choose the default handler for RDP connections like we do with http, ftp, telnet, etc... and have them go to the program of our choice.
In my case, there probably isn't much I can do. Your application is not an authorized application where I work (but it should be - I will have to work on getting others to see the power of RDM), so getting anyone to make changes to our app to accommodate RDM are pretty much non-existant. I am the only one where I work that uses it.
I'll do my best to spread the word about it. :-)
edited by grberk on 1/22/2013
You could ask your development team to add an app settings for the "Launch RDP" command (.config file or even in the UI). They could default it to the RDP client command line "mstsc.exe /v:{hostname}". That would give you the option to override it with the RDM command line instead.
Just a thought.
Stéfane Lavergne
I'd love for this feature to be added. Why launch an external mstsc app from quick connect when you have a much more full featured rdp client available.
We have so many servers in our environment, maintaining an up to date list in the app is not viable. It's much more practical to set default login/screen/resource settings and then just type in the name of the server you want to connect to. Please please add this feature
Hi,
you can configure a template and use it in the quick connect. As soon as you create a new template, it become available in the list (click on the image to get the dropdown). The next version will allow you to define the default settings.
David Hervieux