New Powershell Cmdlets

avatar

I saw your new list of cmdlets and I had a couple of questions in regards to these.

First - will there be updated documentation provided for these new cmdlets? I am assuming so but just checking.

Second - getting some odd behavior with some of the new cmdlets.... Here's an example.

PS C:\WINDOWS\system32> Set-RDM-DataSource "{#####################}" <- removed since this is public

PS C:\WINDOWS\system32> $newSession = New-RDM-Session -Name "Bob" -Kind "Credential" -Group "Test"Write-Host $newSession
Test\Bob

PS C:\WINDOWS\system32> write-host $newSession.ID
41ecd409-b73b-47a9-9be7-37b7be68981d

PS C:\WINDOWS\system32> Set-RDMSession $newSession

PS C:\WINDOWS\system32> set-rdmsessionusername -ID $newSession.ID -UserName "testing"
WARNING: Connection not found.


As you can see in the above I set the datasource using the old method since the new method doesn't seem to work like the old one at all. I create a session into a variable then show both the name of the variable and the ID of the variable used for the session. I've used the Set-RDMSession with success and it appears to function similar to previous with exception of the removal of the "-NoRefresh" parameter.

Then using the new set-rdmsessionusername cmdlet I get an error back about connection not found. This seems to happen with set-rdmsessionusername, set-rdmsessiondomain, and set-rdmsessionpassword.



New CmdLet
Add-RDMUserRole
Close-RDMSession
Export-RDMSession
Get-RDMCurrentDataSource
Get-RDMDataSource
Get-RDMDataSourceProperty
Get-RDMRole
Get-RDMSecurityGroup
Get-RDMSession
Get-RDMSessionDomain
Get-RDMSessionPassword
Get-RDMSessionProperty
Get-RDMSessionUserName
Get-RDMTemplate
Get-RDMUser
New-RDMDataSource
New-RDMRole
New-RDMSession
New-RDMUser
Open-RDMSession
Remove-RDMCurrentDataSource
Remove-RDMRole
Remove-RDMSecurityGroup
Remove-RDMSession
Remove-RDMUser
Remove-RDMUserRole
Set-RDMCurrentDataSource
Set-RDMDataSource
Set-RDMDataSourceProperty
Set-RDMRole
Set-RDMRoleProperty
Set-RDMSecurityGroupProperty
Set-RDMSession
Set-RDMSessionDomain
Set-RDMSessionPassword
Set-RDMSessionProperty
Set-RDMSessionUserName
Set-RDMUser
Set-RDMUserGroupRights
Set-RDMUserProperty
Set-RDMUserSecurity
Update-RDMUI

Old CmdLet
Close-RDM-Session
Get-RDM-DataSource
Get-RDM-Domain
Get-RDM-Password
Get-RDM-Property
Get-RDM-SecurityGroup
Get-RDM-Session
Get-RDM-Template
Get-RDM-UserName
New-RDM-SecurityGroup
New-RDM-Session
Open-RDM-Session
Remove-RDM-Session
Set-RDM-DataSource
Set-RDM-Domain
Set-RDM-Password
Set-RDM-Property
Set-RDM-SecurityGroup
Set-RDM-Session
Set-RDM-UserName

All Comments (2)

avatar

Hi dwilderman,

First, you can find the updated help at http://help.remotedesktopmanager.com/index.html?powershell_cmdlets.htm

Second, Set-RDM-DataSource is now Set-RDMCurrentDataSource because it’s now possible to create a new dataSource with the cmdLet New-DataSource, so Set-RDMDataSource saves the dataSource in RDM.

When you create a new session, you can use New-RDMSession

For the WARNING: Connection not found. You need to call the new cmdLet to refresh Update-RDMUI after the Set-RDMSession then you can use Set-RDMUsername

Best regards,
edited by Olivier Désalliers on 10/8/2014

Olivier Désalliers

avatar

Thank you for the info - I really appreciate it. I was not fully aware of how the update-rdmui worked so that was very good info.

Just an FYI but I want to thank all of you for the new powershell cmdlets - they work great and they don't run the system out of memory like the old ones occasionally did. It certainly helps when you are plowing thru 1500-2000 session objects... :)