Logging with Duplicated Sessions

Hello Stefan,

Thank you for contacting us on that matter.

Could you please provide us with the RDM version and the workspace you are currently using?
https://docs.devolutions.net/rdm/workspaces/workspace-types

Thank you for your collaboration.

Best regards,

Hello Alexis,

thank you for the fast reply.

I use currently the version: Free 2026.1.18.0 with a local workspace.

Best Regards,
Stefan

Hello Stefan,

Thank you for the information.

Since you are currently using Remote Desktop Manager Free 2026.1.18.0 with a local workspace, could you please update to the latest 2026.1 version, 2026.1.23.0, and verify if the issue still occurs?

You can find previous versions here:
https://devolutions.net/remote-desktop-manager/previous-versions/

Alternatively, if possible, you may also update to the latest 2026.2 version, 2026.2.8, and let us know if the logging issue persists after the update:

https://devolutions.net/remote-desktop-manager/download/

Best regards,

Hello Alexis,

I've tried both version 2026.1.23.0 and version 2026.2.9, and the issue persists in both. As soon as I duplicate a session, no new log file is being created.

Br,
Stefan

Hi,
Thanks for the report. We were able to pin down what's happening.

By default, an SSH/Telnet session logs to a single fixed file path. When you duplicate an entry, the copy keeps that same log path; so if the original and the duplicate are open at the same time, they both point at the same file. The first session to open holds it, and the second one ends up writing nothing. (Editing the path while a session is already open won't take effect either, until you reconnect.)
The reliable workaround is to give each entry its own log file by adding a variable to the path. On the duplicated entry, open its properties → Logs and set:

1. Enable logging on.
2. Log mode → All printable output (the Event mode doesn't write the full session to a file, which is another reason nothing shows up).
3. Log path type → Custom, with a variable in the filename, for example:
4. C:\RDM-Logs\$NAME$_$SESSION_ID$.log
5. $SESSION_ID$ is unique per entry, so the original and the duplicate get separate files. If you also want a new file each time you open the session, use C:\RDM-Logs\$NAME$_$DATE_TEXT_ISO$_$TIME_TEXT_ISO$.log.
6. Click OK and reconnect the session.

After that, each session writes to its own file and logging works for both. We're also looking at improving the default behavior so this works without the manual step.

Let me know if that does the trick.

Hello David,

Unfortunately, it is not working.

I followed your steps, but no new log file is being created. What happens is that as soon as I modify the duplicated session, the logging settings are also changed in the original SSH entry. When I click Reconnect on the tab, the session reconnects, but no new log file is created.

The only way I can get it to work is by closing both sessions completely and opening them again from the navigation pane. In that case, logging works as expected. However, logging two instances of the same SSH session simultaneously does not seem to work.

Anyway, I will use another program when I need to log different activities from the same session.
Thank you for your fast reply and for your help.

Br,
Stefan

Hello,
Just to continue my investigation, could you let me know exactly what is configured for the path of the logs? You could export you session without the credentials if you want or post a print screen of the log configuration.

Regards

Hello David,

this is configured for my standard logging:

and this for my duplicated session:

Br,
Stefan