Start Web Browser After Successful RDP Connection
I have several devices on a remote network that are only accessible via the local network (192.168.1.x). To get to these devices, I must fist RDP to one of the servers on that network and then open a web browser to get to the admin interface. Is there a way to set up a session to automatically do this?
Step 1 = Connect to remote computer
Step 2 = Open Web browser at specific address after remote connection is established. (i.e. Open a tab at https://192.168.1.50 in Firefox).
If I can do this via scripting, it would be great if I could get some tips (I'm new to scripting).
Thanks in Advance
All Comments (4)
Hi,
It's not possible for now to have this directly but we have good solution. You can install RDM on the jump point and use it to open the other connections. To simplify everything you can create a desktop shortcut.
However you will need to double click manually on the shortcut. There is not way to automate everything.
David Hervieux
That's what I'm doing now. I just figured that I could configure an "After Connect" event that would do that. Thanks anyway.
Hi,
Unfortunately we can't send a remote command to execute it. I think you could try to add the shortcut in the Program tab page of the RDP settings.
David Hervieux
Why not just use the "Start the following program on connection" feature with-in RDP. So under your RDP session, go to the Programs tab. Check the box, put in the path to internet explorer and include the URL at the end so it opens that automatically. If you need more features, install RDM on the system you're RDPing too and use the session shortcut feature to create a shortcut, then have the RDP session launch that shortcut.
Dave, was thinking of a way today to do this automatically, for local systems you may be able to do a file copy to the system (obviously dependent on network connectivity and firewalling) then launch that trigger file on the remote system using RDP "start the following program on connection". For a trigger file you could make your own proprietary launcher, something like how AutoIt is able to package itself up into a single executable.
Just some food for thought.