remcovergoossen

I would like to check the endpoint log for information about issues but i could not find a get-psuendpoint -log parameter or anything.

I am assuming it does not exist.

Do i have a way of checking the log that an endpoint produces programatically?

Product: PowerShell Universal
Version: 4.2.11

Hi,

Is there another possibility to achieve this? maybe editing a (config) file for the user that has the data source?

Hi,

Thanks for your reply, using the empty data source i am able to get to the others without a credential popup.

I would like to automate the process, is it possible to set the default data source using powershell?

i can find creating the source as xml using the following command, but was unable to find where i can edit the 'rdm startup' or default property of a datasource.

New-RDMDataSource -XML -Filename DefaultXML -Name DefaultXML -SetDatasource

if will notify you of the behaviour after the update, of course.

Hi,

right now we are on DVLS 5.0.2.0 with RDM client 13.5.6.0.

This weekend after an update we will have DPS 6.1.1.0 and RDM client 14.1.1.0

are there noticable differences? and will it incluse an updated powershell module?

The problem i have with the get-rdmdatasource command is that upon 'getting' the source, i get a credential popup. the get command does not allow a username and password, so that does not work.

This is why i have a Set-RDMCurrentDataSource set to the guid/id of the admin source, which works.

Problem is this only works once (i run get-rdmsession and get all sessions returned), if i run another Set-RDMCurrentDataSource in the same ISE window for example, the get-rdmsession returns nothing.

I have temporarily solved this by running the Set command only once in the testscript and then using a $rdm = $true to define wether the set needs to be run another time:

if (-not $rdm) { Set-RDMCurrentDataSource -id 37cc52aa-c300-4351-865e-cef5fdfc56b0 -Username adm_rvergoossen -Password (Get-Content .\rdmpass.txt | ConvertTo-SecureString); Import-Module "${env:ProgramFiles(x86)}\Devolutions\Remote Desktop Manager\RemoteDesktopManager.PowerShellModule.dll" $rdm = $true }

This allows me to run the script multiple times and get data from get-rdmsession

The behaviour seems weird to me, am i missing something? As i mentioned above, your example does not work because of the credential popup for getting the datasource.

Hi,

I'm trying to automate a few things, namely removing sessions based on a variable that is received from another powershell script.

Searched the forum but was unable to find a solution to this problem.

Currently i have a datasource set up in RDM called 'ADMIN' which has all the required permissions to mutate sessions.

I use the following code in powershell to switch the script to the datasource:

Set-RDMCurrentDataSource 37cc52aa-c300-4351-865e-cef5fdfc56b0

i have found i can pass credentials to the datastore using the username and password option

unfortunately when i do this and use get-rdmsession 9 times out of 10, the result is that nothing gets returned, while there are definitely entries in the datasource.

example login:

to store pass in txt file :

(get-credential).password | ConvertFrom-SecureString | set-content ".\rdmpass.txt"

Set-RDMCurrentDataSource 37cc52aa-c300-4351-865e-cef5fdfc56b0 -Username adm_rvergoossen -Password (Get-Content .\rdmpass.txt | ConvertTo-SecureString)

is there a better way to achieve a seamless login? thanks in advance

Hi,

I've been fiddling some time now with the PowerShell module and basically what I am trying to do is create a new RDMSession of type credential by providing simply a username and a password and perhaps a description.

Unfortunately, I cannot find anything about this in the documentation on the PowerShell scripts, so I've come to the forums for help.

Currently, I am simply stuck because the module feels very unintuitive:

After using:

New-RDMSession -name testing -type Credential -Group test

I receive a whole list of properties that I'm unsure about which need setting and exactly how these can be set, the credential does not show up in RDM after adding it using the above statement, probably because the information provided in the creation is insufficient, however I would expect some type of parameters for each required property to show up in the ISE or PowerShell window.

I understand for existing credential entries that I've manually created the requirement might be a System.Security.SecureString, but I'm not even getting to this point.

The reason I'm attempting the above is that at some point I might want to use PowerShell to generate random passwords and put them in appropriate folders.

Can someone point me in the right direction, also confirming this can or can't be done?

Any help would be greatly appreciated.