zachary

Installed the new version and verified it now prompts for a password. Thanks for the amazingly quick turnaround on this!

Thanks for the quick reply! Please update me when it's available.

I've recently switched from using Putty sessions to the SSH Shell session type there's one thing that I haven't been able to figure out. When you have an incorrect password specified in a Putty session, you get the failure prompt and can then just type in the correct password for that user. Is there anything similar for SSH Shell? The default behavior of just closing the window is not very intuitive and leaving the window open just show's access denied.

I tried this with the new 11.9.1.0 and the coloring now works as expected. This can be closed.

Thanks,

Any update on beta availability? Looking forward to test this out!

Hubert,

As soon as a beta for 12 is out, I'll update all my outstanding issues ;)

Thanks!

Hubert,

That's great news. Can we expect to see a beta of RDM 12 soon?

Thanks,

Zach Anderson

I've downloaded version 11.7.1.0 and verified this is working. Thanks for the quick turnaround!

Hubert,

I looked for this in 11.7.1.0 but didn't see it, did it make it in? If not, do you have a projected release for this?

Thanks,

Downloaded the new version and verified this is fixed. Thanks!

David,

I'm using 11.6.2.0. I've only been able to reproduce this with my SQL Server datasource. Local data sources seem to work like my first post.

Thanks,

David,

Going back to the folder coloring, I experienced a strange issue this morning. I expired a parent entry and the groups/folders beneath it randomly seemed to pick up the red color or not.

Default Status:

Expired Status:

Any idea why there would be inconsistency? It's very repeatable with the selection I have here. I'll try to come up with a generic repeatable example like I have in my first post.

David,

That works for me!

Thanks,

Hubert,

Thanks for the reply and looking forward to the fix!

Hey David,

Thanks for the reply. What about the Child entries, is there any way to bulk set status for those without expanding all entries and selecting them all? Ideally we want to use locked & expired here for a couple use cases but I'm looking for how best to do it quickly.

Thanks,

I'm looking into using expired status to hide old connections and seeing some unexpected results.

If I select the top level -> right-click -> Edit -> Status -> Expired, I would expect that all folders and sessions underneath that level will be marked as Expired and show in Red color.

Instead I'm seeing the following:

-> Top Level and parent entries are formatted as red and show Expired if you try to access them

-> Intermediate folders are not formatted red but show expired if you open them

-> Child sessions are not formatted red and do not show expired

Is this the expected behavior? I would think that all folders would show red and child sessions would also be marked as expired.

Hubert,

I have one issue with the proposed solution. When using the SSH Tunnel along with alternate hosts it pre-populates the alternate host list with the incorrect entry ($HOST$:$DYNAMICPORT$); that is how we figured out why the SSH Tunnel wasn't working for us in the first place.

Example:

Configure the following entry in Alternate Hosts:

Then, connecting through the SSH will give you:

Would it be possible to just change the SSH tunnel to always go to localhost instead of $HOST$? Is there a reason that you would ever want $HOST$:$DYNAMICPORT$ other than the documented case of using localhost as $HOST$?

NOTE: I just used 192.168.222.1900 as an invalid IP that I do not have access to so that I can force it to go through the SSH tunnel.

Jean-Phillipe,

Thanks for the quick response. It's not a major issue but was just something annoying as I have to use export/import instead of the quicker copy/paste.

Have you had a chance to look yet Hubert?

I am attempting to copy/paste sessions from one datasource to another and noticed that once pasted, the sessions do not reside in the correct folder structure.

This is the starting datasource:

Right-click on testCust and select clipboard -> copy -> Uncheck Resolve Variables -> OK

Open 2nd datasource and select clipboard -> paste:

Note: This behavior also occurs when copying inside the same datasource.

RDM Version 11.6.2.0 - Enterprise Edition

Sorry to resurrect an old thread, but the suggestion of list-rdmproperties was a very good one and something that seems to have been left out of the recent powershell overhaul. The online help "tip" to reverse engineer the properties just seems like work for the sake of work.

Is there any chance that this can be added to lower the complexity of finding applicable properties for each session type?

Olivier,

I was using the standalone powershell ISE. I further narrowed it down to when I run ISE in administrator mode. So for now, it looks like I'm able to get it to work.

Thanks,

Hmm... when I run this snippet in ISE I get the above warning, but when I run directly in powershell it works as expected? Is this something you can duplicate?

The configuration is in the default location:

AppData\Local\Devolutions\RemoteDesktopManager\RemoteDesktopManager.cfg

Do I need to do anything special to load the configuration file? I tried running the cmdlet from both the product installation and appdata and got the same warning.

Hello,

I'm trying to run the following code snippet:

[color=00FFFF]# Register RDM Snap-in

Write-Host 'Registering RDM PowerShell Module...'

set-alias installutil "$([System.Runtime.InteropServices.RuntimeEnvironment]::GetRuntimeDirectory())installutil.exe"

installutil "$env:PROGRAMFILES\Devolutions\Remote Desktop Manager\RemoteDesktopManager.PowerShell.dll"

Get-PSSnapin -Name *Remote.Desktop* -Registered | % {

Write-Host "$_..." -NoNewline;

if ((Get-PSSnapin -Name $_ -ErrorAction SilentlyContinue) -eq $null){

Write-Host "installing" -ForegroundColor Yellow; Add-PsSnapin $_

}

else {

Write-Host "already installed" -ForegroundColor Green

}

}

$dataSourceList = Get-RDMDataSource[/color]

But I get the following warning:

WARNING: The PowerShell CmdLet feature is only available in the Enterprise Edition!

But I have an enterprise site license that is valid until April 1st, 2017:

License information ... Free upgrade until: Saturday, April 1, 2017

I'm running on Windows 10 with RDM version 11.6.1.0