The Zenith Infotech SAAZ platform includes a Job functionality that can be used to create custom software deployment jobs. This function is simpler, and thus less powerful, than A.S.E. scripting, but it can be useful for deploying software to multiple computers at a site, for example.

Zenith provides a decent Job Management Training Guide in PDF format on their partner portal. I just wanted to note a couple things I didn't see documented:

More...

Zenith Infotech's SAAZ platform allow you to set up jobs to run on client machine, e.g. for installing software. The jobs run as user LOCAL SYSTEM. Deploying a SAAZ job can take 15-30 minutes, which is too long to wait between test runs. So how does one open a command prompt as user LOCAL SYSTEM for testing? Adi Otlean provides the answer near the end of this post:

1. Open a command prompt and type
   sc create CmdSvc binpath= "cmd /K start" type= own type= interact
sc start CmdSvc
   Attempting to start the service will fail with error 1053 because CMD doesn't have any service-related code. However it will also open a new CMD window running as LOCAL SYSTEM.
2. Do your testing in the new CMD window.
3. When you're done, you might want to get rid of the service:
   sc delete CmdSvc

Thanks Adi

The Zenith Infotech Advanced Scripting Engine (A.S.E.) provides a framework for deploying scripts written in Zenith's OEM version of Automise 3 Professional. Scripts can be deployed once on demand or, using templates, on a recurring schedule.

A.S.E. scripting is still fairly new in the Zenith offering, and definitely takes some getting used to. Here are a few things that I've learned along the way. I'll cover five topics:

Script Parameters
INI Files
Helper Scripts
ITS Variables and the SAAZ Extended Database
When Scripts Run
MD5 Checksums

More...