Remote Tab

This tab of the VisBuildPro Project action is used to execute Visual Build Pro on a remote computer.

VisBuildProRemote

Computer: The name of one or more remote computers (separated by commas) to run the command on. If blank, the project will be built on the local computer.

Timeout: Specifies a timeout (in seconds) for connecting to remote computers (optional).

Run in System account: If checked, the remote process will be run in the System account, the account that Windows services and Windows processes such as Winlogon and the Local Security Authority Subsystem Service (LSASS) run in.

Username: Used to specify a username and password that the process will be run under on the remote system (optional).

Note: If not provided and 'Run in System account' is unchecked, the remote system impersonates the account that Visual Build Pro is running under on the local computer, and the remote process will not have access to network resources that the user normally would have access to. If the account that VBP is running in doesn't have local administrator privileges on the remote system, the process needs access to network resources, or to run the process under a different account, provide a username and password of another user that the remote process should run under.

Password: Password for the given username (optional).

Load user profile: If checked, the specified user's account profile will be loaded.

Priority: Specifies the priority that the process will run at.

Install path: Used to specify the installation path of Visual Build Pro (on the remote computer) if it is installed to a different path than on the local computer (optional).

Log PsExec output: If checked, all output and errors from PsExec and cmd.exe are also included in the build output.

Notes:

•

Use of this tab requires that Visual Build Pro be installed on the remote computer (in the same drive+path as the local computer) and that the SysInternals PsExec utility be available in a path of the PATH environment variable on the local computer. See the Server.bld sample for sample steps to download PsExec and install it in the System path if not found. See this SysInternals forum post for setup for remote execution.

•	Paths and filenames entered in the various fields must be valid paths and filenames relative to the remote computer.

•	When using PsExec v1.58 or later, if 'Wait for completion' on the Project tab is unchecked and the process was successfully started on the remote computer, the process ID of the remote process will be stored in the RUNPROGRAM_PID temporary macro.