Neolisk

This is now exported in the version 8.4.4 that I've just uploaded.

Confirmed - now it's working.

Good news - thank you. Hope I can convince our management to upgrade.

It's right beside the Don't warm me combo. Could you try to export the entry into an .rdp file to see the content?

I exported the entry into an *.RDP with different settings.

authentication level:i:0 is exported fine.

enablecredsspsupport:i:0 is not present in the file, regardless of the option value (Default, True or False).

If it helps, I am using version 8.2.0.0 of Remote Desktop Manager.

Do you use RDM in embedded or external mode?

External all the time. Where do I find this option "Activate Network Level Authentication"?

It's in connection in the combobox "Don't Warn me"

Could you try to change the NLA as well?

That one is already set to "Connect and don't warn me", are you saying it's an equivalent to authentication level:i:0?

Problem is that I have checked most of the servers to "don't ask" one by one, so I cannot really tell that it's working, until we add a new server.

What about enablecredsspsupport:i:0? The relevant option in Remote Desktop Manager does not seem to work.

Hi,

You need to edit the configuration directly in RDM. You can change the enablecredsspsupport:i in the Advanced tab of the RDP settings

I tried that, seems to have no effect.

Default, True or False - does not matter, it keeps prompting me for credentials before logging in.

Also, how do I set authentication level:i:0?

I applied two changes to my Default.RDP under my user's folder, as described here, namely these:

enablecredsspsupport:i:0

authentication level:i:0

Remote desktop connection is picking those up just fine, but not if I go through Remote Desktop Manager.

Am I doing anything wrong, or is it using a different *.RDP file for configuration?

Absolutely. But I don't believe we are the only company with this requirement.

Unless nobody runs a data centre as big as ours. And we're just at 100+ machines.

For example, server information, such as OS, MAC, Software, Hardware ... server Description etc. Everything that's editable and currently grayed out (read-only).

Well, good thing you know about it. Until you upgrade, it could probably be edited out manually.

Would be nice if you could edit connection details inline through corresponding tab, so no need to CTRL+E, edit and then close/save (RDM version 7.9.5.0). Group updates could then be easier.

Perhaps, not the best place to put this request, but did not find any better. See this topic for example: http://forum.devolutions.net/topic2152-another-one-of-those-feature-requests.aspx

What's the "#next_pages_container { width: 5px; hight: 5px; position: absolute; top: -100px; left: -100px; z-index: 2147483647 !important; }" being added to every Nth line in everyone's replies?

Anything that can improve current maintenance will be better. If you have some thoughts, we can discuss here, and possibly incorporate into one solution.

Because I have no means to check if it worked as I wanted, I went the more stable way. Here is a Powershell script to change 'KeyboardHook = InFullScreenMode' for all connections.

param($Path,$Key,$Value)

$doc = [xml](gc $Path)

$doc.ArrayOfConnection.ChildNodes | foreach {

$keyHook = $_.SelectSingleNode($Key);

if($keyHook -eq $null) { #KeyboardHook does not exist

$keyHook = $doc.CreateElement($Key);

$keyHook.InnerText = $Value;

$_.AppendChild($keyHook);

} else { #KeyboardHook exists, will be changing it

$keyHook.InnerText = $Value;

}

}

$doc.Save($Path + ".new")

edited by Neolisk on 9/24/2012

Thanks for your reply.

Honestly I did not know "Apply Windows key combinations" option is responsible for the Windows key itself, since it is hardly a combination.

Set it to "Full screen mode only" as this is how it's configured in my RDP client - and it's working.

Now I have a related problem - I have over 50 connections in Remote Desktop Manager that have the same issue (BTW - is there any way to tell how many connections I have? could use current scope vs total).

Any quick way to change them all in one shot, but edit only this setting and do touch others? I recently had bad experience with using batch edit with some other tool, so better not assume it will work for this purpose without your confirmation.

In the long run, it would be nice if you could implement templates for RDP parameters, so you can define 2-3 different sets and make all sessions use either of them, without hard-code per connection. Easier to maintain and troubleshoot this way.

If I try to connect via RDP from Remote Desktop Manager, pressing a Windows button on the keyboard opens the client start menu.

If I connect using regular remote desktop application, it successfully redirects windows button, so it opens start menu on the server.

This was never a big problem until Windows 2012, where Start button is missing. Now you have to use keyboard shortcuts.

edited by Neolisk on 9/21/2012