Purpose
To have a better understanding of the Custom Action process and why things may fail or be an issue.
Overview
- If you create a custom patch and classify it as a Custom Action the (Custom Action scan/Null patch scan) will now find two missing patches.
- All Custom Actions and Custom Patches run as the Local SYSTEM account.
- Custom Actions and Custom Patches can not have any windows requiring user interaction.
- Test your commands and files before trying a Custom Action.
- All files pushed in Custom Actions will be located in the sandbox (%PATHTOFIXES%)
- Custom Actions can be used to push multiple files to the target machine
- Custom Actions can execute multiple files
- Test your Custom Action before adding triggers
Affected Products
Ivanti Patch for Windows 9.3x
Shavlik Patch 9.2x