Forum

Posts by jdthird (jdthird)

jdthird
jdthird
Posts: 6

Thanks Maurice. End results is what matters, and this at least gives me a workaround to get where I wanted to get.


Thanks!

2 yrs Open external option for running session
jdthird
jdthird
Posts: 6

Done, thanks.

2 yrs stop RDM external windows stealing focus when main window is selected
jdthird
jdthird
Posts: 6

The ability to undock a running session is very handy when running multiple servers and needing to compare data between them. But sometimes I may have another program open, such as a word document, or a text document, that I need to copy data to / from for one of the open windows, but clicking on any of the remote sessions, docked or undocked, puts ALL of them to the front, giving them focus, and covering up any other document I was working on.


I understand we can do open/external and then this isn't an issue, but I often don't know I will need to pull something out like this until I'm in the middle of a task and the server is already connected. In that instance, I can't open external. The feature does nothing.

It would be nice if in those instances the open external option STILL WORKED, and simply allowed the external MSTSC to launch and log in with the credentials fed to it, since then it would simply take over the docked session within RDM. The effect is the same, but we don't have to disconnect first and then reconnect.

And, conversely, if we could then simply right click and choose an option, or double click in the main RDM window's left pane, to reconnect again via RDM which then would simply take over the session running in MSTSC.

Kind of being able to hand off each direction, knowing we'd kill the one session to take over in the other method...

2 yrs Open external option for running session
jdthird
jdthird
Posts: 6

Thanks. I assume that option is only available if it's not open yet, since the option if it's already running does nothing?

Any chance in a future version the right click from the server name in the left tree, if it's open, could launch it externally as normally and simply let the MSTSC instance take over the session that was opened in the docked position?


Since I never know when I'll need to pull one out like that, I can't do it at first launch, but if it could at least still launch MSTSC and we simply knew it would kill the docked session when it takes it over with the external program, I'd still have the same functionality.

Thanks regardless

John

2 yrs stop RDM external windows stealing focus when main window is selected
jdthird
jdthird
Posts: 6

And guessing the second part of my comment isn't possible since I just found in another thread the following:

"This is a technological limitation from Microsoft RDP. In External Mode, we open MSTSC.exe which is the native Remote Desktop Client of Windows."

2 yrs stop RDM external windows stealing focus when main window is selected
jdthird
jdthird
Posts: 6

I searched to find a solution to this, and found this thread. It's been two months, any word? For me, I always run everything embedded, but sometimes as I'm doing maintenance on servers, I'll yank one out to a second monitor (I use three) so I can see things on it while I work on another (such as trying to compare things with a domain controller and such) and this loss of focus if I have another program open over the undocked window can be frustrating. I don't want them to always open undocked, so I don't use external mode since for me this is just maybe 10% of the time, so less work for me to pull out once in a while than to always have to put it back for normal work.


Would be nice if there were an option to pull out to external mode just for one instance say, even if that meant in the background it disconnected and reconnected the remote session as it was pulled out if it couldn't just switch modes dynamically.

2 yrs stop RDM external windows stealing focus when main window is selected