B
Administrator’s Guide
273
B
Using MCScript to Update Your
Script Files
Determining when to edit your MCSCRIPT.INI files
Network Associates strongly recommends that you do not alter your
MCSCRIPT.INI files unless you have been advised to do so by PrimeSupport,
Global Professional Services, or your company’s software engineers.
Compatibility between versions of customized scripts is not guaranteed. For
example, if you’ve altered a script to work with Management Edition v2.0, the
same script may not work with later versions of the program, as our engineers
won't have tested your script. If you are unsure about how to edit a script or if
you don't test it thoroughly, you may cause more problems than you solve.
NOTE:
Prefer to have an expert work with you to develop scripts for
your Management Edition software? See
“Getting support for
customized scripts”
for details.
Defining MCScript files
MCSCRIPT.INI files contain all of the information that the Management
Edition program must know about the anti-virus products that you want to
deploy. Each product must have a corresponding MCSCRIPT.INI file in order
to be recognized by the Management Edition program. Formatted like a
Windows .INI file and written in MCScript (Management Console scripting
language), a MCSCRIPT.INI file is used to generate a script that is interpreted
by the Update Agent on a managed machine during install, update, or
uninstall. A sample template MCSCRIPT.INI file with links to explanatory text
follows:
[ID]
Version
=4.0.2
Product
=ACMEScan
Platform
=W95
Description
=ACMEScan for Windows 95
Language
=English
InstallDir
=!C:!\Program Files\ACME\Scan
SortOrder
=51
IconFile
=VSHLDNT.DLL
ImageNo
=5
