Automations

An Automation includes a package of approved scripts (actions), as well as configurations that define when and how those scripts are executed on an endpoint device. The action can be set to run automatically when a sensor goes off, or it can be run manually by the end user, or it can be run by a SysTrack Administrator.

An Automation contains Actions. The Actions are the executable scripts. Actions can be any kind of executable file, such as batch scripts, PowerShell scripts, Java scripts, or Node scripts. The endpoint must be capable of running these kinds of scripts. To create these Automations, several steps must take place:

1. Automations must be uploaded at Configure > Automations and Collection Extensions > Action Builder.

2. Actions are automatically virus scanned.
   

   TIP: This process can take up to five minutes. If the scan finds issues, you will not be able to save the Action. Contact Lakeside if you are unable to get an Action uploaded. The scanner can be strict to protect our customers.

3. The actions must be approved and enabled at Configure > Automations and Collection Extensions > Action Governance.

4. An automation must be created to kick off the initial Action script.

NOTE: The configuration that contains the new action must be pushed down to the Agent in order for the Automation to run. You can do this at Configure > Administration > Select the machines > Read Configuration. This will automatically push within a day of the machine turning on. To debug, push the code manually.