Share your External Apps!

[maimon33]

external putty
Application: putty
Filename: c:\putty.exe
Arguments: %Username%@%Hostname% -pw %Password%

[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

[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.

[rmcardle]

[g0yjs0]

Thanks! This will be great to have. Looking forward to the official implementation.

[IvanMP]

[luma]

[rmcardle]

[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.

[Metzsch]

Cisco ASA ASDM

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