tukan

Hello Maurice,

addendum 1) Perfect. I will play around with VPN sessions to see how it could fit my scenario.

addendum 2) I see. You are right that SSMS command line does not have this feature via switch. The only "hackish" way would be to have all the necessary connection defined in a project and open a project with the connections and you could open them. Otherwise it would be better to use registre server functionality.

addendum 3) Well I thought about RDP. You have to have means to enter a id/password to the login window. What would be the difference in pressing any key, {enter} in this example, before entering the credentials (even without detecting the actual window)?

Thank you for your reply.

Hi David,

Thank you for the tip, but disabling did not help in any way. The application still refocuses even when not selected. What I noticed about this behavior is that if I minimize it and then select any application via mouse and then use alt + tab to switch the application does not refocus. However, when I try to switch directly after minimize it it the refocus behavior is there with the check button enabled or disabled.

Hello,

After some usage time I have made a list of features that could greatly improve RDM usability (for every one I tried to find answer in documentation but I did not find it):

1) Sub-connection functionality

It would be really useful if I could call root node from sub-connection. For example, I need to login via IE when I want to launch customized version of citrix application that is launched also from IE. It would be great if the sub-connection would call the root node for login and after certain amount of time launch itself (e.g. 10 seconds).

2) SQL Server Addon - multiple connections

It would be great if you could add a feature that if you have sql server management studio opened the new connection from RDM would join already opened studio. Currently only new instance of SSMS is opened for every connection, which means huge amount of SSMS if I would open it from RDM.

3) After connect - macro functionality for RDP

It would be really nice if one could enter a trigger like certain window opened perform following action. We have after the RDP session a pre-login window with warning message shown where one must press enter before entering login information. Currently, I'm doing it via macro that waits 5s and then presses {ENTER} - the problem is that the quality of connection is always different. If the connection speed is lousy then the macro misses the enter and I have to do it manually and I don't want to increase the value as I would have to wait additional time when the connection is good. The great solution then would be to recognize that the warning window is displayed and that would trigger a macro with the {ENTER} key.

That is it for now,

Thank you

edited by tukan on 1/21/2015

I have made a video of that behavior. Please notice that I have done it twice to show it.

http://vimeo.com/117368620

I've found a weird RDM behavior. The setup is win7 x64 and RDM 32-bit. When using alt+tab to switch between applications right after minimizing RDP session then the RDP session takes forcefully focus.

Steps to reproduce it.

1) I connect to embedded RDP session (full-screen) and then minimize it.

2) Then hold alt+tab longer than three seconds

3) full-screen embedded RDP session takes focus ignoring alt+tab.

You might have the "Always prompt for password" setting checked in the server's Terminal Services Configuration settings. Under "Connections", right click the "RDP-Tcp" (by default) connection and select "Properties". The setting is on the "Logon Settings" tab. Here's a picture on one of my servers:

edited by robbinsd on 12/11/2014

I have performed additional tests and found out that indeed, if you have that checkbox checked it won't work. If it is unchecked that it works as it should. Thank youDennis Robbins.

I'm really puzzle. Could you test the port scan (3389) to see if it connect. You could also try to download RDCMan and test the connection as well. We use the same ActiveX to control RDP.

It started to work!!! Ufff, that was really something.

I have finally managed to locate the problem. I have performed the tasks you have suggested. The connection was ok. The issue was that the default RDP port 3389 was blocked. When I tried it outside the RDM it worked fine. I have found out that there is a application which is configured to block the 3389 outside the mstsc.exe. When I have removed the blocking everything started to work as charm.

After fixing (removing the RDM from blacklist) the issue the portscan:

Everything started to work. Thank you David for helping. I hope this will help also some other folk. In External mode it still does not work only the embedded works for win2003 and for making sure everything is fine also with the newest version I tried also the RDM 10.1.1.0 and everything works fine there too.

Take care,

It works from inside RDM or from the command line?

I have tested it from within RDM. The command line would be pointless to try as it would not test anything.

Could you try to ping the host from RDM?

Yes, ping works correctly.

Hi,

There is no difference between the two versions. The only thing is that some components are not available in 32 bit. This means that we have to launch the 32 bit version. However for RDP it will use the 64 bit RDP and you will be able to open more connections.

Hi,

Thank you for clearing it out. For now I'm using 32bit RDM as I thought there could be less issues.

I have tried to disable all I could think of but to no avail. Do you have any more tips or something more I could disable or check?

Here is the screenshot of what I have disabled:

Hi,

I might know what could be the problem. It could be your Firewall or anti-Virus. Could you try to exclude RDM from the watched application? This could explain why it does not work in embedded. In external mode it's mstsc and it must already be excluded.

Hi,

I'll do that today. I have one more question. The OS I'm launching the remotedesktopmanager from is a x64 win7 is there any difference in functionality when I launch RemoteDesktopManager.exe or RemoteDesktopManager64.exe? Of course, I undestand one is 32bit and second is 64bit. My question is more geared towards the RDP and keepass plugin.

I have now upgraded to 10.1.0.0 and the problem remains. If I try to copy the password from the repository it copies itself correctly.

Hi,

Could you try to turn on the network authentication level and retry the embedded mode?

http://help.remotedesktopmanager.com/troubleshooting_automaticlogon.htm?zoom_highlightsub=nla

Hi,

It does not work either for the embedded mode. I found this page before and it did not work so I sticked with the external mode.

Just for a test could you try to open it in External mode?

I'm using only External mode. The other modes do not work.

They produce this error message:

You might have the "Always prompt for password" setting checked in the server's Terminal Services Configuration settings. Under "Connections", right click the "RDP-Tcp" (by default) connection and select "Properties". The setting is on the "Logon Settings" tab. Here's a picture on one of my servers:

edited by robbinsd on 12/11/2014

I did have it checked. However, un-checking it did not help. It still does not fill the password. The server is windows 2003 R2 SP2 and I think the major problem is that the RDP 5.2 has the login inside the RDP session, but I don't know how to get the password filled.

Hello dhervieux,

I have checked what you have suggested. Storing domain\passwd & local password does not work either, suggests that keepass plugin is working. To me it looks like after the logon banner you enter only user id but not passwd.

I have checked also the Windows policy and security. Did not find anything suspicious.

See here the interactive logons:

http://tukanos.rajce.idnes.cz/b/#Interactive_logon_rules_in_domain.jpg

and user rights assignment settings:

http://tukanos.rajce.idnes.cz/b/#security_settings_on_server.jpg

I have also tried to find more information on the MSDN etc.

The only thing I could find is related - http://support.microsoft.com/kb/324737

(we do have a login banner, but I use macro on remotedesktopmanager to press enter and continue - maybe that is an issue)

At the bottom there is this message, maybe it does apply in this case too?:

This registry change does not work if the Logon Banner value is defined on the server either by a Group Policy object (GPO) or by a local policy. When the policy is changed so that it does not affect the server, the autologon feature works as expected.

Hello,

I'm currently testing RDM if it would be usable for us. I tried the Keepass integration. It works fine with win2008R2. Howerver, with windows 2003 server it does not work.

It copies successfully the username but fails to enter the password and thus login into the server. I tried most of the suggestions on this forum but to no avail.

Could you try to reproduce it and fix it?

Thank you,