It's possible to add to your JetPatch scripts library binary and executable files and run them on your endpoint servers. The process is similar to adding a script to the scripts library and then adding a task which will run that script.
- Access JetPatch console and go to System > Scripts. Create a script
- Select 'Binary executable' as your run type
- Select the script source (one-liner / upload file) and save script
- Once you have a binary executable file, you can create a task using that script. Please note that the task source can be a script, an execution line or both. The default execution line is:
@file @param1=default1 @param2=default2
Here's an example with Firefox MSI (source)
MsiExec.exe /i "@file" /qnAnother example with Remote MG (source)
MsiExec.exe /i @file /qn
- Silent install instructions vary per vendor, please check vendor site or a site like this one.
If you need to modify the default execution line, change the task source to 'both' and afterwards, select the Execution type: Shell Script / Windows Batch file / Binary executable. Make sure that you select the relevant execution line for your script
- To execute the task on the endpoints go to JetPatch's main menu and navigate to Endpoints > Management. Use the filters to select the endpoint you would like to run the task on (you can use the checkbox to check all endpoints / specific endpoints from the table current view).
- Click on 'Select action > Run task' and select the task you have created. Click on 'Run Task'. Please note you can also schedule the task time.
- To view the task output, navigate to Endpoints > Activities filter by the task and click on the eye-iconto view full details.
How to understand the execution results?
There are several ways to understand the task results. First you should see what's the task status. It can either fail or succeed and in other cases it's still in-progress. The next thing you should check is the exit code. Usually, when the task status is 'succeed' and the exit code is '0' it means that the task is completed successfully.
In other cases, where the task has failed, the exit code is usually attached to the related error. You can learn more on exit codes for built-in tasks (scripts and tasks which are managed by JetPatch) here.
If the tasks are external (uploaded by the user), you can always go to the script library, view the script and exit code and see the reason for failure.
Moreover, we highly recommend to check the task output (using the eye-icon) to get the full details on the activity.