Powershellscript not executed from original script file?
Hi Devolutions Team,
was there a change which made it so that RDM copies a powershell script on execution into the users temp folder?
We (Admin Team) have some scripts which are only used by our servicedesk.
When there is an Issue and we have to troubleshoot one of the scripts we execute them via their respective RDM Powershell entries, which now no longer appears to work!
The difference is that the SD is executing it directly from a networkshare... (We enforce tha path of the scripts!)
I just tested this and noticed that all scripts get copied into the users temp folder at execution...
How can i disable this behaviour for all users of RDM?
All Comments (8)
Hello,
We'll open a ticket to investigate this behavior. We recently made some changes to powershell scripts to fix some issues (for example, resolving variables wasn't working on a previous version). It's possible we changed the behavior at the same time.
Regards,
Hubert Mireault
Hello Hubert,
do you have any update to this Issue?
Hello,
This is currently being worked on by one of our developers. I can't give you an estimate at the moment but I'm hopeful it should be fixed this week internally, to then be pushed into one of our releases.
Regards,
Hubert Mireault
Hello,
We did make a change to the behavior of PowerShell scripts of the filename type while addressing a related issue. The behavior has now been reverted to its previous state, so the issue should be resolved — you should no longer see copies of your scripts in the temp folder.
Regards,
Léon Le Brun
Hi Léon, Hi Hubert,
i just tried this with the current version of RDM (2025.2.13.1) and unfortunately this has not changed...
If i run a simple script which returns the $PSCOmmandPath from my desktop i would expect the output to be:
C:\Users\myuser\Desktop\tests\Untitled1.ps1
but if run with RDM i get this:
D:\Temp\myuser\51\RDM\5d2781e2-1eaf-46dd-8eba-f1c0de93c861.ps1 (yes my Temp is redirectod to another disk, this is on purpose)
I tested this with an existing Session and a new one from Type PowerShell terminal (local). (PS5 or PS7 did not make any difference)
Is there maybe a checkbox / setting that needs to be set for it to work as in earlier versions?
Hello,
The change Léon mentionned will be available starting with 2025.2.14.0, which we are hoping to release this week. The version is currently built and is going through QA testing. We should have specified the version number to avoid this confusion, sorry about that.
If you still encounter the issue after updating to this version, please let us know and we'll investigate to see what we might have missed.
Regards,
Hubert Mireault
Just here to confirm that 2025.2.14 fixed the issue, thanks for the help
That's great, thank you for the feedback! If you encounter any additional issue, please let us know so we can address it.
Regards,
Hubert Mireault