This model is enabled by the Command item in the local update configuration file (ateupdloc.cfg) for each workstation. The file is installed by default with the option enabled, and can be disabled either by removing the file entirely, or by commenting out the item within the file. (The latter is a more durable way of disabling it, since an update will re-install the default file if it is not present.) Some of the issues relating to this model are discussed below:
Each individual workstation has its own individual configuration file: Although this provides the maximum flexibility for power users, it is inconvenient for central administration. If you want to have anything other than the default configuration on several workstations, by far the easiest approach is to avoid this model entirely and use the Site model. Otherwise, a compromise is to maintain a single copy of the ateupdloc.cfg file on the server and then sync it to the clients whenever you change it. (ATEUPDATE.LIT provides a /S switch for this purpose.) Another possibility is that the workstations at the site may all be configured to share a common OPR: directory on the network, thereby sharing a common configuration file.
Defining a update version other than the very latest: The default configuration file points to the default web update control file on the MicroSabio server. That file doesn't necessary specify the very latest available version, but it still may specify a version newer than you are comfortable with. In this case, you must provide your own web update control file. This is basically how the Group model works, i.e. the off-site administrator manages the web update control file on their own web server.
