PowerShell Script (remote) not available

Hello,

Thank you for contacting us regarding this matter.

Could you please let us know your RDM version, as well as the workspace/data source you are using?

In the meantime, could you please try selecting the All tab instead of Macro/Script/Tool and let us know if that resolves the issue?

Best regards,

I am using Remote Desktop Manager version 2026.2.12.0 64-bit (PreJIT).
As our data source, we are using Devolutions Cloud at: https://cisgruppe.devolutions.app
On the All tab, when I search for "remot", I do see "PowerShell Terminal (remote)". However, it is available as a Session type, not as a Macro/Script/Tool type, as shown in the tutorial.

Hello,

Thank you for your response.

I see it under Session as well, so it may be an issue with the tutorial. Could you please send me the link to the tutorial you're following so I can take a look?

Best regards,

Hello,

The (Remote) entry was deprecated. I believe that you can instead use the generic PowerShell script and in the "Run" section there is a "Mode" that can be set to either local or remote.

In most cases the "Automatic" mode should work fine but you might have hit a limitation in your use case where you have to configure the mode by hand.

Please do let us know if this works for you.

Best Regards,

Changing the Mode property to either Remote or Local always produces the same result: a PowerShell window opens and reports that there is no service named “Zabbix Agent”. The window remains open. When I then enter the command $env:COMPUTERNAME, it always displays the name of my local computer instead of the server on which I am trying to stop the service. Interestingly, the open PowerShell tab is labeled with the name of the remote server.



The tutorial I am following is called “Remote Desktop Manager - Advanced -> Automating tasks with scripts and macros”, time 0:36.

Hello,

Sorry for the delay we had to test quite a bit to reproduce the issue. From what I can see we enter a case where opening the session with RDP stops the script from working properly.

I have put the script "hostname" in the remote script and execute it against the machine.

1. RDP is opened towards the same machine -> The hostname returns the local machine
2. RDP is not opened to the same machine -> The hostname returns the remote machine

To do this you can right click the session -> Macro/Script/Tools -> Select your remote script. Do it when the RDP session is running and then when it's not running

Can you confirm if you have the same behavior and we can investigate further from there?

Best Regards,

Hello,

To add to what Michael said, if you were only getting this issue when the RDP session was running, a fix will be included in version 2026.2.14.0.

Regards

Hello,

When the RDP session is not running, I get the following output:


When the RDP session is running, I get the following output:

You absolutely don’t need to apologize for the late reply. On the contrary, I really appreciate your analysis of the issue and your effort to help. Thank you very much.

Hello,

Now this makes more sense. The PSSession is what we use to connect to the remote machine in the script and it is most likely failing due to missing configurations on your computers.

Usually it's about activating WinRM on both the local and remote computers, then adding the remote computer to your trusted hosts on your local computer. You can also try with and without the "Use SSL" setting in your Powershell Script entry's properties.

You can try playing with these 2 settings depending on your configuration.

I would say that, from here on, your best bet would be to provide the PowerShell error messages you get to whichever AI agent you use and let it help you configure your local environment to support the PSSession

I would also suggest talking with your IT or Security departments about these actions to make sure they do not go against any of your company's policies.

Best Regards,

Hello,

Thank you for being so patient!

I'm pleased to inform you that a new version of RDM (2026.2.14.0) has been released, featuring the fix for your issue.

Latest Version: Download RDM

Please let us know if this works or if you encounter any issues.

Best regards,