external putty
Application: putty
Filename: c:\putty.exe
Arguments: %Username%@%Hostname% -pw %Password%
g0yjs0 wrote:Could mRemote offer a way to choose the format of variables; i.e., %username% vs. #username# or ^username^, so that both mRemoteNG and Windows environment variables would be available for External Apps' use?
For those of you like me to find the Built in vnc view lacking sometimes, I was able to setup UltraVNC like this:
UltraVNC
C:\Program Files\UltraVNC\vncviewer.exe
%HostName%:%port% -password %Password%
rmcardle wrote:g0yjs0 wrote:Could mRemote offer a way to choose the format of variables; i.e., %username% vs. #username# or ^username^, so that both mRemoteNG and Windows environment variables would be available for External Apps' use?
This is a good idea for an improvement. I have added it to JIRA:
https://mremoteng.atlassian.net/browse/MR-486
As a workaround for now, you should be able to set the Description, MAC Address, or User Field setting for your connections to %USERNAME% and then use the associated variable (e.g. %DESCRIPTION%) in the external app instead of %USERNAME%. mRemoteNG will then replace %DESCRIPTION% with %USERNAME% and send it on, unaltered, to the shell.
You can use inheritance and/or a search and replace in the connections XML file with a text editor to set the setting for all of your connections.
luma wrote:rmcardle wrote:g0yjs0 wrote:Could mRemote offer a way to choose the format of variables; i.e., %username% vs. #username# or ^username^, so that both mRemoteNG and Windows environment variables would be available for External Apps' use?
This is a good idea for an improvement. I have added it to JIRA:
https://mremoteng.atlassian.net/browse/MR-486
As a workaround for now, you should be able to set the Description, MAC Address, or User Field setting for your connections to %USERNAME% and then use the associated variable (e.g. %DESCRIPTION%) in the external app instead of %USERNAME%. mRemoteNG will then replace %DESCRIPTION% with %USERNAME% and send it on, unaltered, to the shell.
You can use inheritance and/or a search and replace in the connections XML file with a text editor to set the setting for all of your connections.
The trouble I see with this is that you are now creating incompatibilities with existing configurations. If I have a config that is using %variable% and send the xml to somebody that is using #variable# or whatever, what would the impact be?
Users browsing this forum: Google [Bot] and 4 guests