Specifying [Commands] Keys - McAfee MANAGEMENT EDITION 2.5 Administrator's Manual

Specifying [Commands] keys

The [Commands] section contains the install and uninstall scripts for the
product. You can choose from among four basic sets of keys:
• General non-indexed keys (ScriptVersion, ServerOnlyFlag,
WorkstationOnly, HasAvScanner, and Unique). These keys define
additional product attributes that are important to the install/uninstall.
• Indexed macro assignment keys (Macro). These keys define macros used
in the install/remove script. Predefined macros can also be used in the
scripts, but will not appear in this list.
• Indexed installation script keys (PreInst). These keys define a series of
commands that initiate actions by the Update Agent to install the product.
• Indexed uninstallation script keys (PostRem). These keys define a series
of commands that initiate actions by the Update Agent to remove the
product (can be used during both uninstallation and version upgrade
scenarios).
General non-indexed keys
ScriptVersion
The ScriptVersion key specifies the version number of the script associated
with the product and helps you determine whether the script in the file is
newer than an existing script. The version number should be incremented
when the script is changed.
ServerOnlyFlag and WorkStationOnly
The ServerOnlyFlag and WorkStationOnly keys are only relevant for
products intended for use on Windows NT. If the ServerOnlyFlag key is set to
TRUE, the product cannot be put on a Windows NT WorkStation. Likewise, if
the WorkStationOnly key is TRUE, the product cannot be installed on a
Windows NT Server (e.g., the VirusScan program for Windows NT has the
WorkStationOnly key set to TRUE).
ServerOnlyFlag=TRUE or FALSE
WorkStationOnly=TRUE or FALSE
HasAvScanner
The HasAvScanner key should be either WorkStationOnly or FALSE. If it's
not present, the console assumes the value is FALSE. If it's set to TRUE and if
the product contains an on-demand scanner, you can initiate a remote scan
from the Management Console on any machine that has the product installed.
Using MCScript to Update Your Script Files
Administrator's Guide 279