Page 4 of 6

Re: Share your External Apps!

PostPosted: Mon Apr 08, 2013 10:01 pm
by maimon33
external putty
Application: putty
Filename: c:\putty.exe
Arguments: %Username%@%Hostname% -pw %Password%

Re: Share your External Apps!

PostPosted: Tue May 07, 2013 5:22 am
by RcGrnc
TightVNC Viewer

Filename = path:\to\tvnviewer.exe
Arguments = %Hostname%::%Port% -scale=auto -password=%Password% -viewonly=%UserField%
Try to integrate = Yes

User Field:
no = for full access
yes = for view only

Re: Share your External Apps!

PostPosted: Wed May 22, 2013 2:29 pm
by g0yjs0
I've been having trouble trying to set this up. I was wondering if it is somehow possible to tweak mRemote in the following way:

Where I work, we have regular user accounts for everyday tasks and also admin accounts for support tasks. If my regular account is "myacct", then my admin account is "admmyacct". Everyone's accounts are setup similarly.

mRemoteNG works great for remote login. What I'm trying to do is setup an external app to use the "Offer Remote Assistance" feature of WinXP/Win7. What I need to be able to do is use runas with the /user switch in such a way that it echoes the Windows %username% variable. The problem is that mRemoteNG uses %username% for its own info for that single entry.

Is there any way to echo out the Windows %username% environment variable? Or, possibly, to disable the mRemoteNG %username% variable for this instance?

Here's an example:

Filename: runas.exe
Arguments: /user:mydomain\adm%username% "cmd.exe /K msra.exe /offerRA %Hostname%"

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?

That way, I could have a central connections file on the network drive, that would stay in sync for everyone's use. And, I wouldn't have to enter different user names in the mRemoteNG username field for each of the 200+ workstations we support.

Re: Share your External Apps!

PostPosted: Fri May 24, 2013 10:39 pm
by rmcardle
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.

Re: Share your External Apps!

PostPosted: Tue May 28, 2013 3:26 am
by g0yjs0
Thanks! This will be great to have. Looking forward to the official implementation. :)

Re: Share your External Apps!

PostPosted: Mon Jun 17, 2013 9:55 pm
by IvanMP
Hi i have some problem with UltraVNC ... i have check the "Try to integrate" check box but when i try to connect, it start the VNC as separate program not integrated ... any idea ?
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%

Re: Share your External Apps!

PostPosted: Wed Jul 24, 2013 4:31 am
by luma
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?

Re: Share your External Apps!

PostPosted: Wed Jul 24, 2013 4:55 pm
by rmcardle
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?

It will be implemented by providing some way to escape the % signs. I don't think I'll make it an option to choose the variable designator.

Re: Share your External Apps!

PostPosted: Fri Aug 02, 2013 3:40 am
by stephenjirvine
Powershell Remoting:

It's almost like native SSH for windows!

Filename: C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe

-noexit enter-pssession -computername %Hostname% -credential %Username%@%Domain% -Authentication CredSSP

Information on PSRemoting

http://technet.microsoft.com/en-us/libr ... 49694.aspx

CredSSP is required to allow your credentials to "pass through" to other operating systems, for example if you wanted to access a network share on a third computer from your remote powershell session.

http://blogs.technet.com/b/heyscripting ... edssp.aspx

This is a security hole so do some reading before enabling.

Re: Share your External Apps!

PostPosted: Mon Aug 19, 2013 4:23 am
by Metzsch
Cisco ASA ASDM

Filename: C:\Program Files\Java\jre7\bin\javaws.exe
Arguments: https://HOSTNAME/IP/admin/public/asdm.jnlp