
Secunia.com 43
SPS Concepts and Terminology
The Secunia CSI user should become familiar with the concepts and
terminology described in this section.
What does a SPS package consists of?
The package consists of two parts; applicability rules and SPS
package. The applicability rules are used by WSUS to only execute the
package on computers that are applicable for the selected package.
The SPS package consists of the payload that is then executed on the
computer.
The image on the right hand side illustrates the conceptual structure
of a SPS package. The following sections will explain in greater detail
all the components that make a SPS package.
Applicability Rules
The applicability rules are rules used to decide whether or not a package should be offered to a
client. These rules are as follows:
IsInstallableApplicabilityRule – Obtains the rules for determining whether or not
this item is installable on a given computer. It generally consists of paths and version
information of relevant files.
IsInstalledApplicabilityRule – Obtains the rules for determining whether or not this
item is already installed on a given computer. It generally consists of keys and value
information of relevant registry keys.
IsSupersededApplicabilityRule – Obtains or sets the rules for determining whether
or not this item is superseded by another update on a given computer. It generally
consists of paths and version information of relevant files.
SPS Package
The SPS package must always consist of at least one file that is placed at index “0”, this is the
execution flow script, and any additional files will be numbered accordingly in ascending order.
The execution flow script is either JScript (JavaScript), VBScript or Powershell script; by default
a JavaScript example is provided in the SPS Package Creation Wizard.
The script will be automatically extracted from the SPS package and executed. Based on the
execution flow more files can then be extracted and executed from the SPS package,
referenced by their index order.
Execution Flow Script
This execution flow script is always executed. This is the file with index 0, and as such it will
always be the first to run.
In the execution flow script you can define any other files to be extracted and executed. The
default execution flow template that is provided in the SPS Package Creation Wizard will
extract the first file supplied in the package with the specified silent parameters (usually this is
the patch file provided by the vendor). Any other files added to the package will NOT be
extracted or executed when using the example script.
If you create your own execution flow, no user interaction is available. To make your execution
flow totally unattended, use log files accordingly for easy troubleshooting.
Files
The SPS package supports additional files besides the execution flow script. The added files will
have array indices from 1 to n where the first file will have index 1, and the additional files are
numbered in ascending order.
Commenti su questo manuale