Custom Powershell Synchronizer $RDM Object

Hello CryRig,

Thank you for reaching out to the Devolutions support team.

If you already have a synchronizer configured in RDM, I suggest using the command Open-RDMSyncSession.
https://docs.devolutions.net/powershell/powershell-commands/open-rdmsyncsession/

To automate the process, you can use the application identity to authenticate in RDM.
This requires the use of the Devolution Server or the Hub Business.
And the permission set on this account.
https://docs.devolutions.net/server/web-interface/administration/security-management/applications/

You can add this application identity to the RDM data source information under the PowerShell tab.

Best regards,

Hi Patrick,

sorry about the radio silence. I had no time till today to work on this.

i got it to work with hard-coded credentials, but I can't seem to get it to work with linked credentials.
The credential is used to connect to the IMC API.

What i tried was setting the linked credential inside the synchroniser config, then add the $USERNAME$ and $PASSWORD$ variables as parameters called Username / Password.

But when I run a get-variable inside the sync, the variables are not available.

What's the correct way to transfer a credential inside the sync job for use with the script?

PS:
Would Devolutions be interested in the api docs from HPE IMC? Maybe one day we could get native Sync support :)

Hello cryorig,

Sorry as well for the radio silence.

I am still working on my script to reproduce this on my side.

I will let you know as soon as I have results.

Best regards,

Hello cryorig,

I appreciate your patience on this case.

After multiple tests, it looks like this entry cannot sync or create entries.
I tested it with an internal and external value, and got some errors.

I will open an internal ticket to go through all of them and let you know when it is fixed.

Could you tell me if this entry was working on an older version of RDM?

Best regards,

I think my first test was with version 2025.3.22.0 and later 2025.3.29.0., both did/do not work.
Havn't yet tested it with 2025.3.30.0, but reading the release notes i don't think it would make a difference.

Hello cryorig,

Thank you for this feedback.

An internal ticket is open regarding the issue that occurs with the custom PowerShell synchronizer.
We will let you know when the fixed version of RDM and the module will be available.

Best regards

hi @Patrick Ouimet
Any news on this?

BR,
CryoRig

Hello,

Regrettably, the Support Department cannot provide an exact release date as the full process (Build – Quality Assurance – Release) is out of our control.
The development team needs to implement a fix. After that a series of events must take place:

- A pull request must be approved, by a peer primarily, but sometimes also by a security specialist;
- A build must be generated;
- The whole build contains typically many fixes, which each must be validated by our QA department
- if need be, the build is rejected for a specific issue, or a combination thereof, which would trigger another build cycle

Best regards,

if you add me to your GIT / CICD infra i can do the merge :)
jokes aside, thanks for the update!

Hello cryorig,

This issue should be fixed in version 2026.1.9.0.
This version is not available yet, but it will be released soon.

Let us know if this version fixes your issue.

Best regards,