I've been reading the manual http://help.remotedesktopmanager.com/macroscripttools_commandline.htm regarding tools that can be launched for a session entry.
So I've been thinking it would come in handy to have an option to launch PuTTY for any kind of session entry and figured an entry in the Macro/Script/Tool section would be the way to go.
I've created a command line M/S/T entry which launches PuTTY and defined the necessary parameters and values ($HOST$, $USERNAME$, $PASSWORD$) and referenced them in the command line call.
However, when I select a session dashboard and execute the PuTTY Tool, PuTTY gets launched but the variables are not resolved.
So maybe I'm getting the whole concept wrong, but how do I use the session specific variables to launch a tool?
-------------------
Remote Desktop Manager Enterprise Edition 12.6.6.0 64 Bit - Data Source: SQL Server
Running on Windows Server 2012R2 VMs with Remote Desktop Services feature, serving as common work environment for 30 Windows Server administrators
Hello,
Is it all the variables that they are not resolved or only the $PASSWORD$?
For the $PASSWORD$ variable, you need to check the Allow password in variable option in the Security section of your session. If your are using an advanced data source like SQL Server or DVLS as example, in the Data Source Settings under Password Policy, please check allow password in macro.
Best regards,
Jeff Dagenais
Hi,
I am aware of the fact that $PASSWORD$ resolution needs to be enabled - and it is.
However, none of the variables are resolved at all. Maybe I'm getting the concept all wrong. Please see the attached screenshots.
When actually calling the tool for a session entry (Right click>Macros/Scripts/Tools>PuTTY) I receive a command line parameters dialog with the variable names as shown on the second screenshot.
-------------------
Remote Desktop Manager Enterprise Edition 12.6.6.0 64 Bit - Data Source: SQL Server
Running on Windows Server 2012R2 VMs with Remote Desktop Services feature, serving as common work environment for 30 Windows Server administrators