RDM default log on domain
Hello, first and foremost I would like to say thank you to the developer(s) that are working to bring this excellent tool to the market. Outstanding work!!
Secondly, during my evaluation I have run into a small problem regarding the log on domain setting that is stored on the properties of an RDP host connection object. I searched the forum before posting and I saw mention of a similar issue back on 7/31 referring to the RDP client that is included with Windows Server 2008 R2. I am currently using the RDP client that was released with the SP2 version of Windows Server 2008 with the same result.
The thread mentioned above is here: http://forum.devolutions.net/messages.aspx?TopicID=157
The issue causes all connection objects that are created to ignore the domain name that is entered into the "Domain" field on the connection properties. A simple workaround is to specify the DOMAINNAME\ into the username field which causes the RDP client to "gray out" the domain selection drop-down and to use the domain name specified, and although this workaround does provide a way to force the application to use a specfic log on domain, it would be nice if the application passed the information onto the client to reflect the correct domain name in the Domain drop-down of the login prompt. I've also tried the latest beta release of RDM and it seems to be affected by the same issue.
I have nothing but respect for the people who are working to bring this fantastic product to the industry, so please do not take offense to my suggestion.
Any help or advice would be greatly appreciated.
Thank you again.
All Comments (5)
Hi,
I will try to do my best to find a solution, but the application is now setting (since 5.6) the domain field to the client.
I don't know what I can do but I will keep an eyes on that problem. Let me know if you find anything.
David Hervieux
Devolutions inc.
David Hervieux
This is purely an observation, but I am a previous user of mRemote which shares similar functionality as RDM and does not seem to be affected by the default log on domain issue.
The source code for mRemote has also been posted on the download page if it helps:
http://www.mremote.org/wiki/Downloads.ashx
My own knowledge prevents me from being able to offer more than an observation unfortunately, but I will do what I can.
Is this something that you have intentions of looking into David?
The reason I ask is because I am currently evaluating the product for use by a large number users with a variety of technical levels and I would very much like to simplify the process of logging into 500+ servers in multiple domains with the ability to specify a login domain.
Thanks again!
Hi,
The version 5.6 handle this exactly like mRemote does. I don't know why it's not working. Have you tried the latest beta 5.6.0.15 ?
David Hervieux
Devolutions inc.
David Hervieux
I've just tried to reproduce the issue with the 5.6.0.15 build and it seems to work great for Windows Server 2008 and later hosts, but oddly enough Windows Server 2003 and earlier still defaults to the last logged on domain.
I have a feeling that the symptom is related to the DefaultDomainName registry key on the host rather than a client setting and maybe the reason for the different behavior is that the newer version of RDP uses a different method as you suggested.
edited by copycon on 10/5/2009