Purpose

The purpose of this document is to show how to run an executable using a custom action. This can be useful if you have an executable such as a patch or a program installer that cannot be installed via the normal Ivanti processes. By using a custom action to run the executable, you can install the patch or program on multiple machines at once saving time and resources.

Overview

Because Ivanti will use a similar process as when you manually run the executable in a command prompt on the client machine(s), we highly recommend testing out the command to run the executable in a system account command prompt on the client machine(s) (please check out this document How To Test SYSTEM Account Permissions ) before trying to run the executable through a custom action. Once you have verified that the command properly runs the executable through the system account command prompt of a client machine outside of Ivanti, you should be able to use the same command into the custom action in your deployment template.

1. Move your executable file to one of your client machines then navigate to the file location in a local system account command prompt.

2. Run the correct command to run your desired executable. For my example, I will run the installation for 7-zip:

7z1602-64.exe /s

Please note that in order for an executable to be run correctly through a custom action, the executable must run silently and therefore a silent installation switch (in this case "/s") will be required. Also Ivanti does not provide any information for installation of products outside of our supported product list specified here: Ivanti Patch for Windows Servers Supported Products.

3. Place a copy of your executable on the console machine then open up your console, go to New > Deployment Template, and name the template.

4. You will need to enter in two custom action tasks for this operation. Navigate to the Custom Actions tab in your deployment template and click New to enter in your first task.

5. Leave steps 1 and 2 default in the Custom Action window then select Push File for step 3 and browse to the location of the console on your console for step 4. This completes your first task.

6. For your second task, leave steps 1 and 2 default in the Custom Action window then select After all patches for step 3 and enter in the command that you tested in your local system command prompt (in this case 7z1602-64.exe /s) in step 4. Then click Save to save your custom action tasks and deployment template.

7. You can scan your target machine with a regular patch scan template or, if you do not want to deploy any patches with your executable, simply use the null patch scan mentioned in steps 1-3 here How To: Reboot Target Machines with Using the Custom Actions Patch Type in a Custom Scan Template . After scanning, deploy with the deployment template you created.

Affected Product(s)

Ivanti Patch for Windows Servers 9.x

Shavlik Protect 9.2