Hello,
After several tests, we noticed a difference in behavior between local recording through RDM and remote recording through Devolutions Gateway.
We understand that:
Local recording via RDM is managed directly from the user workstation, which provides more flexibility regarding certain output parameters, specially the generated file name.
Remote recording through the Gateway is designed more for centralized management, session traceability, and auditing purposes, with a more controlled and consistent handling of recordings.
However, in our environment, we would need the ability to customize file names for recordings generated through Devolutions Gateway as well, in order to better integrate them into our workflow and archiving processes.
Would it be possible to consider adding this functionality in a future version of Devolutions Gateway?
Thanks for your feedback.