Different behavior with latest version when using e.g. export report data.
For longer time we are using Power Automate to expiring entry data and other reports and now noticed that in version 2025.1.30 the RDM background process is not closed (which means that Power Automate action will not take the next action/step)
When Remote Desktop Manager is normally running on the local machine for the user it can be reproduced by starting an export of a report via the cmd or RUN, after which every start/run a Remote desktop manager process will remain active in the background. Previously this process was terminated after completion.
Repro: For example start an export of RDM report via cmd line/RUN:
remotedesktopmanager.exe /DataSource:*******-****-****-8a20-29d43db262f3 /report:b30f6c4a-****-****-bc4b-3f3253b3ccbd /reportoutput:"C:\Temp\test.csv" /reportsettings:"C:\Temp\test.rdr"
File is generated in Temp directory, but background process Remote Desktop Manager stays active and same process will be added when starting the export again.
Previously these background processes were terminated/closed properly after generating a file.
If you have any questions or need further information, please let me know.
Regards, Marcel
ce2936a4-d353-45bf-96a9-08794a5939d3.png
Hello Marcel,
Thank you for contacting the Devolutions support team.
Since this is from PowerAutomate, could you also tell me if this is the same result with a Powershell script?
Best regards,
Patrick Ouimet
Hi Patrick,
I was talking about Power Automate because it handles the whole process of processing some audit and alerting stuff from RDM using some generated files, basically the file is generated on an internal audit server which uses the default functionality Exporting through cmd line (As indicated in your docs: Report export - Devolutions Documentation).
When you execute this on your local machine (with an open RDM session) you will see that the report is generated, but the windows background process 'Remote Desktop Manager" started with this exe does not end/close when using client version 2025.1.30. If the local version is RDM 2024.3.29 you will see that after executing by cmd this linked Windows process closes/terminates properly.
Regards, Marcel
Hi Patrick,
When I test the version released yesterday (2025.1.34.0) I see that it works on my side as before.
No new background processes remain present :-)