<< Click to Display Table of Contents >> Navigation:  Modules > Asset Management > Client Operations - Workstation Data Assistant > Updating Versions

Most WDA modules are set to run on a given schedule, or are set to load at system start up.  Such modules are set up as tasks, which are then placed on appropriate schedules.  Those tasks that define how often and when to run the module also defines another task that is used to actually install the module.  Each time the scheduler goes to run a module based on its schedule, it checks the version of the module that has been defined in the linked install task.  If the version defined does not equal the version that is physically installed, the scheduler will pull down the proper version and install it.  This behavior only happens if the Auto-update box is checked in the module's schedule task definition.

Some modules are not intended to be run on a schedule, such as the ESI Console and the Scheduler itself.  However, it is necessary to push newer versions of these modules periodically.  Modules that run on schedules will update themselves.  Modules that do not must be pushed out as a task that is only set to run once (this is different than putting a task on the Run Once schedule).  Modules may also be pushed by putting their install task on the Run Once schedule, however the Run Once schedule requires the target machine's asset number.  If such a task had to be pushed out to all machines, it would require an inordinate about of work to stage the records in the Run Once schedule.  Instead, create a new install task for the module and the version to be installed and set the task to run once using the How to run setting.  Then simply put that task on the normal schedule that is used by all machines.  The task will be run only once on all machines to which the schedule applies, and since the task is an install task, the only thing that will happen is that the module will be updated to the correct version (or installed for the first time).