Variables in RDCman

Tom Fox 16 Reputation points

I am using RDCMan 2.83

We are currently implementing Cyberark as our PAM solution, which allows us to connect to RDP sessions using Admin credentials stored in a Vault.

To do this, we can use the AlternateShell feature of RDP, known as "Start Program" in RDCman. I can create these connections in RDCman, but would like to be able to use variables to make it easier to manage.

I need to use the follow connection settings to build a jump connection:

ServerName - (fixed RDS server)
DisplayName - actual server name
Logon crendentials - my standard user credentials, inherited from parent.
Start Program - psm /u /a /c PSM-RDP (inherited from parent to make config easier)

Is it possible to somehow define the displayname here as a variable, linked to the DisplayName of the Connection? That way we just need to clone the existing settings and nothing else needs to change. It would also be super handy if you could right click on a connection and Clone it, copying all existing settings to a New Connection window.

Tom Fox

Remote Desktop
Remote Desktop
A Microsoft app that connects remotely to computers and to virtual apps and desktops.
3,417 questions
{count} votes

3 answers

Sort by: Most helpful
  1. Brauner Sabino 6 Reputation points

    I have the same question. I am trying to do the same thing. Use variables to use as parameter to a "Start Program".

    mRemoteNG support variable like %NAME%

    So... I have to change my favorite tool ?

    1 person found this answer helpful.
    0 comments No comments

  2. David C. Miller 1 Reputation point

    Did you find an answer to this question? I was looking for the same information myself.

    0 comments No comments

  3. Robinson, Wesley 6 Reputation points

    I am trying to do the same thing. I was able to write a Powershell script that would ingest a current rdg file and update each server properties for ServerName, DisplayName, and Start Program and pass in the correct vaules. It spits out a new file that has all the same connections but they are configured for the Cyberark instance. This is working great for existing files, but when adding new servers I am still having to manually configure these settings.

    0 comments No comments