Remote PowerShell Script entry needs Arguments property to utilize configurable parameter properties

Hello,

Thank you for the request. I'm not sure why it's missing, as the macro-type remote powershell entry also has an arguments field. Either the entry is unclear, or it's not currently possible to pass them. We will investigate and get back to you when possible.

Regards,

Hello,

Could you please tell us which version of RDM you are using?

I have downloaded our latest version of RDM and looked at the "PowerShell Script (remote)" entry type and it has the exact same properties as the local version of the script.

Please let us know if this issue is already fixed for you in the latest version of RDM.

Best Regards,

Using 2024.2.17. The remote variant has a 'Configuration' property but that doesnt seem to accept variables. The local variant doesnt have a 'configuration' field, but does have one for arguments.

Hello,

Sorry about this, I thought you were talking about the Powershell "Macro/Script/Tools" entry type and not the Powershell "session" entry type.

The Powershell (Remote) entry indeed does not have the arguments field and instead has the "Other Parameters" field in the advanced tab which seems to intend to do something similar but from looking at the code it does not build the script exactly the same way as the arguments field.

We will create a ticket to normalize this and keep you updated on the progress.

In the meantime, please let us know if the "Other Parameters" works for you as an alternative solution (it should simply append whatever you type in the field after your command).

Best Regards,

Hi Michael,

Thanks for the info. I tried using the 'Other Parameters' field to pass an argument and it does seem to pass it, but not in a usable way. It results in error 'positional parameter cannot be found that accepts argument'.

Joe

Hello,

Thank you for testing this. We have created the ticket to add the "Arguments" field. We will let you know when the change is done.

Best Regards,