Home Software About

RemoteLaunch Documentation

Getting Started

Command Tab

Machines Tab

Execute Tab



To get to the Options screen, click the Wrench icon in the top right corner, and select Options from the menu.

PSExec.exe Location

RemoteLaunch uses PSExec to do the remote launches, so if needs to have the path to the executable. If you don't already have it, you can use the Download button to get it. You can put it anywhere that you have access, including a network path. E.g. c:\temp\psexec.exe

Network Paths

Please read this page to understand why you would want to use this, and why it is a necessary complication. Essentially, RemoteLaunch will need to perform a fresh authentication to any network paths that you wish to access in your command or script. This is the place to list them, and to provide the required credentials. The same list is used for all commands, since it doesn't hurt to authenticate to a few resources even if they are only used in some of your scripts.

If the script or command you wish to launch resides on the network, you'll need to add that network path as well.

If accessing multiple paths under a single share, only the top level share needs to be added. Once authenticated, all paths under the share are open for access.

To Add a path to the list, enter a new network path in the Network Path field, and click the [Add] button.

To Remove a path from the list, select it from the list to hilight it, then click the [Remove] button to remove it.

Username and Password represent the credentials that will be used to re-authenticate to all of the listed network paths at the client side, before launching your command or script. Typically, you can just use your own admin account.

If you find the products or web site helpful, please donate to support continuing development.

Thank you!

@Copyright 2012 2thePoint Software Ltd. All rights reserved.