Home » Executing Custom Scripts

Executing Custom Scripts

Endpoint Central provides options for configuring almost all the user configurations from remote. In addition to the configurations that are supported by Endpoint Central, administrators can also write their own scripts that could be run on the user machines for accomplishing specific configurations. The scripts could be any of the following:

  • Batch file (.bat or .cmd)

  • In any other language hosted by Windows Script Host (WSH), such as VB Script, JScript, Perl, REXX, and Python.

Note: The script engines for languages like Perl, REXX, and Python, must be registered with Windows. You can also execute single line commands, add dependent files and enable logging, to analyze the output of the script after execution.

Step 1: Name the Configuration

Provide a name and description for the custom script configuration.

Step 2: Define Configuration

The table given below lists the parameters that have to be provided for defining the configuration.


Parameter Description

Execute Script from

You can execute the script either from repository or as a command line.

Script Name*

The script that has to be added/removed in the user machines needs to be chosen from the script repository. It is mandatory to add the script to the script repository for this to work.

Script Arguments

The arguments that have to be provided while executing the scripts.

Dependency files

The required dependency files for execution of the script needs to be added.

Exit Code

Specify the exit code, which should be returned, when the script has been executed successfully


Specify the frequency for this script to be executed, like only once, during every user logon, during subsequent user logon for specified number of times or all user logon until a specified time period.

Step 3: Define Target

Using  the Defining Targets procedure, define the targets for deploying the Custom Script Configuration.

Step 4: Deploy Configuration

Click the Deploy button to deploy the defined Custom Script Configuration in the targets defined.

To save the configuration as draft, click Save as Draft.