Antidote with windows vista, Repository, Antidote delivery manager and windows commands – Lenovo ThinkPad Edge 15 User Manual

Page 142

Advertising
background image

3. Execute netsvcinst /install /inf:"c:\program files\common files\lenovo\pfdinst\netsf.inf"

/cid:"lgl_tvtpktfilter".

4. Execute netsvcinst /install /inf:"c:\program files\common files\lenovo\pfdinst\netsf_m.inf"

/cid:"lgl_tvtpktfiltermp".

Antidote with Windows Vista

For 64bit Windows Vista the registry location is HKLM\SOFTWARE\WOW6432Node\Lenovo\Rescue and
Recovery\ADM Repository The repository path for the mailbox is set in the registry at the following location:
HKLM\SOFTWARE\Lenovo\Rescue and Recovery\ADM

For 64-bit Windows Vista the installed folder location is C:\Program Files (x86)\Lenovo\Rescue and
Recovery\ADM. Issue a CD command to C:\Program Files\Lenovo\Rescue and Recovery\ADM.

When running any of the Antidote commands in Windows Vista (32 or 64 bit) you must have elevated admin
privileges, otherwise the values will go to an incorrect registry location.

Repository

The repository function runs on each system and periodically checks for new messages from the
administrator. It checks at a scheduled time interval or at the occurrence of several interesting events (for
example, boot, resume from suspend or hibernate, detection of a new network adapter, and assignment of a
new IP address). The repository function looks for messages in a set of directories, in a Windows share
location, such as \\machine\share\directory, at HTTP URLs, and at FTP URLs . If more than one message is
found, it processes them in “directory sort by name” order. Only one message is processed at a time. A
message is only processed successfully once. If processing a message fails, by default, it is not attempted
again, but retrying on failure can be specified in the message itself.

A message must be packaged by an administrator before being placed in a directory to be processed by
the repository function. To create the package, the administrator places all of the files that constitute the
message into a directory (or its subdirectories). One of the files must be named go.rrs the primary command
script. The administrator can optionally use a signature key for this message, but if used the key must be
available to all of the target systems. The repository function checks the package for integrity, checks the
signature if supplied and unpack all of the files into a local directory before executing go.rrs.

The primary command script file (go.rrs) follows the syntax of a Windows command file. It might contain
legitimate Windows commands and any of the commands listed in the following section. Also, a Python
command interpreter is installed as part of the Rescue and Recovery environment, so Python scripts might
also be called from the go.rrs script.

At the end of execution of the script, all files unpacked from the message is deleted, so if files are required
after the script exits (for example, installing a patch on reboot) the files must be moved out of the message
directory.

Each system has a configuration of repositories to check. It might be appropriate for the IT administrator
to divide the population of systems into groups and assign different repositories (network shares) to each
group. For example, systems might be grouped geographically by proximity to a file server. Or, systems
could be grouped by function, such as engineering, sales, or support.

Antidote Delivery Manager and Windows commands

The Antidote Delivery Manager system provides several commands to facilitate the operation of the system.
In addition to the command to create messages and adjust settings, there are commands to control
networking, determine and control operating system state, examine XML files from system inventories, and

134

Rescue and Recovery 4.23 Deployment Guide

Advertising