Creating Sessions with PowerShell

Hello Marvin,

are you sure that the snapin is loaded in your external powershell? I created a powershell profile that I am sure it is loaded automatically and I only use the x86 version of powershell for RDM:

In C:\Windows\SysWOW64\WindowsPowerShell\v1.0 create a file named profile.ps1 with this content:

Then be sure to use the x86 version of powershell from here:
C:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exe

Best regards,
Andy

Ohh and only use the commandlets like Set-RDMSession - without the second dash. The commandlets with 2 dashes are old - the new ones are much more performant.

@andybandy - thank you for replying, this thread had fallen between the cracks (we missed it)

@marvin - if you need more assistance please let us know

Best regards,

That was my message... :D
..just forgot to login.

I am pretty sure, there is anything wron with my New-RDM-Session, cause I tryed to set it and it was still NULL. So the Session can't be set....

Commands:
set-variable -name session -value (New-RDM-Session -Name Testgroup -Kind Group)

get-variable session
Output:
Name Value
---- ----
session

Is there anything wrong?

If I finally try to set set the Session, it says the argument ($session) is NULL.
Command: set-rdmsession -Session $session

Hello,

Is it possible that the variable is cleared between invokes??

could you try with one invoke which runs all these commands

just in case you need a full script to test

$computerName = "wind10";
$theusername = "david";
$thedomain = "windjammer";
$thepassword = "123456";
$session = New-RDM-Session -Host $computerName -Kind "RDPConfigured" -Name $computerName;
Set-RDM-Session -Session $session -NoRefresh;
Set-RDM-Username -ID $session.ID $theusername;
Set-RDM-Domain -ID $session.ID $thedomain;
$pass = ConvertTo-SecureString $thepassword -asplaintext -force;
Set-RDM-Password -ID $session.ID -Password $pass -NoRefresh;

I may have identified an issue, it may depend on the data source type. We will have to perform more tests, but it looks like the Set-RDMSession call is asynchronous and returns before the new session is available for further commands.

By adding a Update-RDMUI call I never get the error

I discovered this when porting the sample script to use the newer cmdlets...

Here is the script that doesnt experience the issue

$computerName = "wind10";
$theusername = "david";
$thedomain = "windjammer";
$thepassword = "123456";
$session = New-RDMSession -Host $computerName -Kind "RDPConfigured" -Name $computerName;
Set-RDMSession -Session $session -Refresh;
Update-RDMUI;
Set-RDMSessionUsername -ID $session.ID $theusername;
Set-RDMSessionDomain -ID $session.ID $thedomain;
$pass = ConvertTo-SecureString $thepassword -asplaintext -force;
Set-RDMSessionPassword -ID $session.ID -Password $pass;

Ok, I didn't forgot to log in, it just logged me out automatically...

Does anyone know how to fix this issue, or have just an idea..?

Do you have the C++ runtime 64-bit installed?
Does RDM 64-bit work?
Are the files "blocked"? In windows explorer, open to the ""C:\Program Files (x86)\Devolutions\Remote Desktop Manager\x64\" path, right-click -> properties

Hello,

We will look into the null ID, but most likely it will be fixed only after the holiday break.


Best regards,

Hello,

nice to hear! Can't wait for it :D

The C++ Runtime is installed. It doesn't work in any bit version. And I don't even have the opportunity to block/unblock the files.

SQLite.Interop.dll