Script packaging is a powerful feature which allows you to easily dispatch the execution of local scripts onto a single machine or a group of machines and receive a consolidated report of console outputs. The Script Packages feature is accessible from any computer by expanding it and using the Script Packages node, or, via the context sensitive menu.

This feature can be used to run the following script types:

  • Batch (.bat)
  • VB Script (.vbs)
  • Powershell (.ps1)

NOTE: Goverlan can push PowerShell scripts without having to enable the Remote WinRM, however the machine must have the set-execution policy for scripting as RemoteSigned.

Defining Script Packages

Before you can execute a script package on a remote machine, you must define it. To do so, right-click on the Script Packages node of any computer and selectManage Scripts to open the Goverlan Object Manager.

Deploy Windows Batch and VB scripts remotely

  • To share (or unshare) a script object with other Goverlan users on your network, select it and click on the Deploy WIndows Batch and VB Scripts remotely button. See Team Sharing for more information.

Script Package Properties

  1. Enter the script object's name and description.

  2. Run Path - Specify the full path of the script package for this object. The script can be located on your machine or in a network share.

  3. Transfer Methods - Select The run path is accessible from the remote machines if the path specified points to a network share, or, Transfer the program to the following directory then run from local path to have Goverlan first transfer the script package onto a temporary location on the target machines and then run it from there.

    If you select to transfer the script first, you can modify the destination folder on the target machines. Note: The destination path may contain environment variables but they will be resolved using the System Variable set (not the User Variable Set).

    If the script package has external dependencies, enable the Transfer the entire parent directory option. The dependencies must be located at the root of the parent folder.

    Enable Delete file(s) after execution if you wish to clean up the transferred files once the script is completed.

  4. Execution - Select the credentials to use to execute the script package. Note: If the script is run directly from a network share, you cannot select Run As Local System since this account doesn't have network access.

    Enable Hide execution window to prevent the user interface from being displayed on the target machine during execution.

  5. Output - Configure the execution time out value and decide if you want Goverlan to kill the script process if a time out occurs.

    If the script package has reporting or error console output, enable the Record console output to option and configure an output text file path. The console output of the script for all machines will be compiled into that output file. Goverlan automatically opens it at the end of the execution.

  6. Click on Ok.

Running Script Packages

Once you have configured your script packages, you can easily dispatch their execution on a single machine or a selection of multiple machines.

  • To run the script packages on a single machine, expand the Script Packages node under the desired machine and double click on the script package to execute.

  • To run the script package on multiple machines, use the [CTRL] or [SHIFT] key to select two or more machines in the main view or in the Search result list, right-click on the mouse, expand the Script Package sub-menu and select the script package to execute.