copycon

I sent a PM over David.

Thanks for all of the hard work.

The "Group/Folder" listing does not wrap correctly in the dashboard view.

Okay. Thank you for the quick response.

Sort priority seems to have been reversed with the latest RDM release.

Hi All, I'd like to know if anyone has managed to run Remote Desktop Manager using application virtualization using either Citrix XenApp Server or Microsoft App-V / RemoteApp?

If so, please share how difficult it was and any compatibility or usability issues that you've run into?

Thanks!

I will help with testing SecureCRT support as well if it is needed.

This works perfectly in 5.6.2.0. :)

I was using 5.6.1.0 for testing. I will test again with 5.6.2.0. Thanks for responding!

I have SQL permissions specified as follows:

Database 1:

Group 1:

sysadmin (role)

Group 2:

db_owner

public

Group 3:

db_datareader

public

Group 2 does not have the ability to modify the RDM database. Group 1 does. If Group 2 is added to the sysadmin role the users can make changes to the RDM database.

Are there any other system databases and/or permissions that the users should have to allow changes to the RDM database(s)?

Thanks!

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

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!

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.

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.