Changes done by PowerShell are not available for RDM on MacOS

Resolved

Changes done by PowerShell are not available for RDM on MacOS

avatar

Hello,

My setup:
MacOS Sequoia 15.4.1
Remote Desktop Manager 2025.1.13.3
PowerShell 7.5.0
Devolution.Powershell module 2025.1.3.0
Trial license, valid, not expired.

Issue:
I've created new XML data source like this:

PS /Users/user> $s = New-RDMDataSource -XML -Filename 'XML_DS_powerShell' -Name 'XML_DS_powerShell'
PS /Users/user> Set-RDMDatasource $s
PS /Users/user> Update-RDMUI


After that I've checked is it created:

PS /Users/user> Get-RDMDataSource                                              

< Previously created data sources >

ID          : 358a2b5c-f4cc-4a66-a52d-0e3c039a9cf9
IsConnected : False
IsOffline   : False
Name        : XML_DS_powerShell
Type        : Xml


Issue is, that RDM app doesn't see this new data source. Also file XML_DS_powerShell is not created, directory with data source ID is also not created, I've checked RDM directory '~/Library/Application Support/com.devolutions.remotedesktopmanager/' where all other data sources are located.
Only after I've created new RDP entry in this new data source, using PowerShell, file and directory appeared in RDM directory.
But RDM app still can't see this new data source.
Is it expected? Do I missed some command?

Regards,
Denys

All Comments (7)

avatar

Hello,

Thank you for your feedback.

What folder configuration file location do you get with the Get-RDMInstance cmdlet?

Is it the same as the one where your RDM configuration files are located?

Could you please try with the full path for the -Filename 'XML_DS_powerShell' option with the New-RDMDataSource cmdlet?

Best regards,

Érica Poirier

avatar

Hi,

Config file location is same as for data sources:

Both files, config and data source, are located in same dir:

I also have tried with full path in -Filename option - result is the same: file is not created.

DevolutionDirContent.png

DevolutionConfigPath.png

avatar

Hello den_zorg,

I just tested the latest version on MacOS, and it works on my end.

Can you run this script to make sure you are connected?

PS /Users/user> $s = Get-RDMDataSource | Where-Object {$_.Name -eq 'XML_DS_powerShell'}
PS /Users/user> Set-RDMCurrentDatasource $s
PS /Users/user> Update-RDMUI

Let us know if the connection is true after this.

Best regards,

Patrick Ouimet

avatar

Hi,
Yes, according to Power Shell - data source is connected:


But I think, I've found "happy path" to create DS with cmdlets. Some pre-requisites are needed:

  1. New-RDMDataSource creates file in directory where this cmdlet is called, so if you want to have DS file with all other files (eg where config is stored) you need go there with cd command and then call New-RDMDataSource. Seems, option -Filename is really about only filename.
  2. RDM app should be closed. In other case it can't see newly created DS.


Steps:
PS /Users/user/Library/Application Support/com.devolutions.remotedesktopmanager> $s = New-RDMDataSource -XML -Filename 'XML_DS_powerShell' -Name 'XML_DS_powerShell'
PS /Users/user/Library/Application Support/com.devolutions.remotedesktopmanager> Set-RDMDatasource $s
PS /Users/user/Library/Application Support/com.devolutions.remotedesktopmanager> Update-RDMUI
PS /Users/user/Library/Application Support/com.devolutions.remotedesktopmanager> $s1 = Get-RDMDataSource | Where-Object {$_.Name -eq 'XML_DS_powerShell'}
PS /Users/user/Library/Application Support/com.devolutions.remotedesktopmanager> Set-RDMCurrentDatasource $s1
PS /Users/user/Library/Application Support/com.devolutions.remotedesktopmanager> Update-RDMUI

Not sure, that first Update-RDMUI call is needed. Seems, that most important part - call Set-RDMCurrentDatasource with result of Get-RDMDataSource. Immediately after this call file XML_DS_powerShell is created. For some reason is needed result of Get-RDMDataSource (eg $s1) and not result of New-RDMDataSource ($s).
If after that start RDM, in list of DS should be present new DS.

DS_isConnected.png

avatar

Hello Den,

Every time you execute New-RDMDataSource, it will create a data source configuration under File -> Data Source in RDM.
When you want to connect to an existing data source in RDM, you have to use the Get-RDMDataSource -Name.

Since you have run it multiple times, could you check how many data sources are under File -> Data Sources?

Best regards,

Patrick Ouimet

avatar

Hi,
Checked DS, all of them are also present in Get-RDMDataStore list: some of them are created using RDM app, other - using previously described workaround. Some of them are XML DS, some - SQLite.

Now, what is really interesting:

  1. Created DS using initial approach (New-RDMDataSource -> Set-RDMDatasource -> Update-RDMUI) and then check "File->Data sources" in RDM. Result - DS is present, despite fact, that file is not created;
  2. Try to edit this DS. Do not change anything, just Cencel for edit screen and click Ok on Data Sources screen - as result, file is created (see screenshot)




BTW, seems, that New-RDMDataSource for SQLite DS works a bit different: -Database option requires full path for file, otherwise it creates database file in user directory.

P.S.
Out of topic, but still: what are requirements to create Cyberark SIA entry (using powershell or RDM app)? Does it depend on DS type? Does it depend on license type? Asking, because previously, without trial license, I was not able to create any Cyberark entry. Now, with trial license I can create some of them, but not Cyberark SIA. When I say "I can't create" - I mean that entry is not present in list.

Thank you,
Denys

CreateDS .png

avatar

Hello Denys,

Thank you for this feedback.

I tried a trial license on a local data source, and the SIA entry is available in RDM.

Could you try to search for CyberArk on 2025.1 version of RDM?
Note that this entry is new from the latest version.



Best regards,

Patrick Ouimet

2025-05-13_13-26-32.png