Adhoc cli connection

I’m trying to create a connection via CLI. Ultimately i’m trying to integrate GNS3 with Royal TS.

I’m working off of the old cli command structure that GNS3 still has built in:
“C:\Program Files (x86)\Royal TS V5\RoyalTS.exe” /protocol:terminal /using:adhoc /uri:“{host}” /property:Port=“{port}” /property:IsTelnetConnection=“true” /property:Name=“{name}”

Looking at the documentation it looks like i should be able to do something like this:
.\rtscli.exe action connect-adhoc --uri=“{host}” --scheme=terminal --property=“Port”:“{port}” --property=“IsTelnetConnection”:“true” --property=“Name”:“{name}”

unsure if the one property should actually be this: –property=“ConnectionType”:"telnet”

Regardless i’m having an issues with the uri/scheme structure. If i try to run this:
.\rtscli.exe action connect-adhoc --uri=telnet://10.50.150.10:5001
Error: Please enter an allowed value: .

I’ve tried various variations and just haven’t found the right one yet. I don’t think GNS3 will pass the URI telnet:// i’m assuming the {host} variable will just be the ip address of the host.

Also worth mentioning the output for help of the connect-adhoc command “scheme” attribute is cut off and doesn’t show the “valid” schemes:

.\rtscli.exe action connect-adhoc -h
usage: rtscli [args] [options]
Type ‘rtscli [scope] [command] -h|–help’ for help on a specific scope and/or command.

The argument --uri and --scheme are required.

-h, --help Shows the help for this command.
-v, --verbose Shows additional output for troubleshooting.
-s, --silent Shows no output at all.
-b, --background Prevents the main window from being focused.
–create-link Creates a link instead of executing the command.
–uri=VALUE The uri (computer name or URL) of the connection
you want to establish. Can also contain the
scheme, like: rdp://192.168.72.1 or https://

–scheme=VALUE The scheme (connection type) of the connection you
want to establish. Allowed values:
–credential-id=VALUE Optional: The unique identifier of an existing
credential which should be overridden to connect.
–credential-name=VALUE
Optional: The name of an existing credential which
should be overridden to connect. Note: When the
argument --credential-id is not used and
multiple credentials with the specified name are
found, a prompt to select the correct credential
will appear.
-u, --username=VALUE Optional: The user name which should be overridden
to connect.
-p, --password=VALUE Optional: The password which should be overridden
to connect.
–property=VALUE Optional: Property to override. Can be used
multiple times to set multiple properties. For
example: --property=“AutoRefresh”:“True” –
property=“AutoRefreshIntervalInSeconds”:“5”
Note: the property name is case sensitive. A
list of available properties can be found here:

objectproperties

Hi!

we recently released a new version and was wondering if you still see the same issue. If so, can you open a new support ticket?

Thanks!