System Software Manager (SSM) User’s

Guide

October 2005
This guide provides a functional overview of System Software Manager and a comprehensive
guide to its installation, configuration, and implementation.
 © Copyright 2002-2005 Hewlett-Packard Development Company, L.P.
The information contained herein is subject to change without notice.
Microsoft, MS-DOS, Windows, and Windows NT are trademarks of Microsoft Corporation in the U.S. and other
countries. Intel is a trademark or registered trademark of Intel Corporation or its subsidiaries in the United States
and other countries.
The only warranties for HP products and services are set forth in the express warranty statements accompanying
such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall
not be liable for technical or editorial errors or omissions contained herein.
This document contains proprietary information that is protected by copyright. No part of this document may be
photocopied, reproduced, or translated to another language without the prior written consent of Hewlett-Packard
Company.

Å WARNING: Text set off in this manner indicates that failure to follow directions could result in bodily
harm or loss of life.

Ä CAUTION: Text set off in this manner indicates that failure to follow directions could result in damage to
equipment or loss of information.

System Software Manager (SSM) User’s Guide

Fourth Edition (October 2005)

Third Edition (February 2005)
Second Edition (August 2004)
First Edition (August 2002)
 About This Guide

This guide provides a functional overview of System Software Manager and a comprehensive
guide to its installation, configuration, and implementation.

Text Conventions
This document uses the following conventions to distinguish elements of text:

COMMANDS,FOLDER NAMES,and DRIVE Commands, folder names, and drive letter

LETTER DESIGNATORS designators are shown in uppercase.

<variable> Variables or placeholders are enclosed in angle

brackets and italicized. For example, replace
<pathname> with the appropriate path, such as
C:\windows\system. When typing the actual
value for the variable, omit the brackets.

[optionalparameters] Optional parameters are enclosed in square

brackets. When specifying the parameters, omit
the brackets.

“literal value” Command line text that appears inside

quotation marks should be typed exactly as
shown, including the quotation marks.

Type When you are instructed to type information,

type the information without pressing the Enter
key.

Enter When you are instructed to enter information,

type the information and then press the Enter
key.

System Software Manager User’s Guide iii

About This Guide

iv System Software Manager User’s Guide

 Contents

About This Guide

1 Getting Started
What is System Software Manager? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–1
System Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2
Installing and Running SSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–2
Components of SSM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–3
SSM.EXE - Installer Stub . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–3
SSM.CAB - Support Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–3
SSM.BIN - Settings file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–3
SSMCVA.MDB - Update Information Database (UID) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–3
SSM Log file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–3
SSM TRACE file. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–4
Features of SSM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–4
Device Driver Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–4
System ROM BIOS Flash Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–4
BIOS Settings and Replicated Setup (/REPSET) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–4
Customized Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1–4

2 Modes of Operation
Administrative Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–1
Update Information Database (UID) Performance Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . 2–3
Update Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–3
Displays Cancel Option for Low bandwidth Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–3
Reads Settings from SSM.BIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–3
Creates or Copies the Update Information Database (SSMCVA.MDB) . . . . . . . . . . . . . . . . . . 2–3
Queries the Update Information Database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–4
Performs Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–4
Performs Replicated Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–4
Updates Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2–4

3 Package Deployment
Can I Use SSM to Deploy Customized Software Updates? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–1
What is a CVA File? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–1
Additional Requirements for Software Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–1
Post-Operating System Silent Installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–1
Detectable Deliverable Version. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–1
Controlled Reboot of System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2
Installation Recovery. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2
Installation Mechanism Must Support Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3–2

System Software Manager User’s Guide www.hp.com v

 Contents

Customized Packages Must Reside in a Unique Subfolder of the File store . . . . . . . . . . . . . . . 3–2

4 BIOS Configuration
Replicated Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–1
Helpful Hints: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–2
BIOS Configuration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4–3

5 Using SSM with Commercial Software Distribution Systems

HP Client Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–1
Altiris Deployment Solution, SMS, and Others. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5–1

A File Store
File Store Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–1
Adding Custom Packages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–1
File store examples . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A–1

B Command Line Parameters

Command Line Syntax. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–1
Administrative Mode. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–1
Update Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–1
Command Line Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B–1

C Log File Description

Log File Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C–1

D Custom CVA Files

CVA Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D–1
Field Definitions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D–2
Language Abbreviations for Use in Custom CVA Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D–4
Sample CVA File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D–9
Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D–10

E Error Codes
Locating Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E–1
Administrative Mode Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E–1
Update Mode Errors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E–1
CVA Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E–4

F Troubleshooting

System Software Manager User’s Guide www.hp.com vi

 1
Getting Started

What is System Software Manager?

System Software Manager (SSM) is a free utility that enables you to
■ Deploy software update packages and system ROM updates from a single file store to
multiple desktop, workstation, and notebook computers simultaneously;
■ Replicate BIOS settings across multiple client computers;
■ Run reports to compare software updates awaiting deployment against machines on the
network, so that you can identify those PCs in need of updates;
■ Create and deploy customized update packages.
SSM complements software delivery products by making it easy to create distributable update
packages and target those update packages to the applicable systems.
SSM can be integrated with a variety of software installation and delivery mechanisms, such as
the use of a logon script, software distribution application such as Altiris Deployment Solution,
email, or local execution.
Download the latest version of System Software Manager from www.hp.com/go/ssm. Software
updates (SoftPaqs) supported by SSM are easily identified by the following icon:

System Software Manager User’s Guide 1–1

Getting Started

System Requirements
System Requirements

Minimum Hardware and Software

Server Client

Windows 2000 Professional, or Windows XP Windows NT 4 Professional Workstation, or

Professional Windows 2000 Professional, Windows XP
Professional, Windows XP Professional x64, or
Windows PE.*

Internet Explorer 4.01 or later Internet Explorer 4.01 or later

*
BIOS setting management is supported under Windows PE. SSM version 2.00 does not support
BIOS Flash under Windows PE. To flash the BIOS under Windows PE, use the latest version of
HPQFlash 3.x series. HPQFlash 4.0 does not support Windows PE.

✎ Ifenvironment,
you have deployed HP Client Management Interface Software Provider (HPCMISP) in your
please update to the latest version prior to using SSM. There is an intermittent
BIOS setting modification interaction issue with HPCMISP version 1.00 Rev A and SSM.

Installing and Running SSM

SSM has many powerful command line options and usage models. The most basic steps to use
SSM are outlined here. Refer to Appendix B, “Command Line Parameters” for a complete list of
command line options.
1. Download the SSM SoftPaq from www.hp.com/go/ssm.
2. Run the SSM SoftPaq to extract the SSM program and support files to a directory.
3. Create and share a directory on the server that will be used as the file store. (Example:
c:\SSMFS shared as \\MyServer\SSMFS.)
4. Copy SSM.EXE and SSM.CAB to the file store.

✎ Tosuchhelpas \\MyServer\SSMFS\Video\Intel
organize the file store, create subfolders with meaningful names to hold each SoftPaq,
Extreme 2\sp27392.exe

5. Place all SSM-supported SoftPaq files in the file store created in step 3. Each customized
package must be located in separate subdirectories. Refer to Chapter 3, “Package
Deployment” for more information about Custom Packages.
6. On each client computer, run SSM in Update Mode by specifying the UNC path to the
filestore on the command line:
\\MyServer\SSMFS\SSM.exe \\MyServer\SSMFS /Accept /Report
This step updates the system software (BIOS and drivers) on the client according to the
contents of the filestore.

1–2 System Software Manager User’s Guide

 Getting Started

7. A log file of actions performed may be viewed in the user’s TEMP directory. A quick method
to view the log file on the client system is to click Start > Run then enter
%temp%\%computername%.htm.
8. Review the log file to view the list of software applicable to the system, updates performed,
and any errors. If no errors are found, the log file will not include an Error section. Refer to
Appendix C, “Log File Description” for more information.

Components of SSM
This section covers the various SSM modules and their functions. There are two modes of
operation: “Administrative Mode” and “Update Mode.” Refer to Chapter 2, “Modes of
Operation” to determine which mode is most appropriate for your purposes.

SSM.EXE - Installer Stub

The installer stub allows SSM to be installed locally on the client system. This reduces the need
to download and expand the CAB support file each time SSM is executed. It also performs some
bandwidth detection and offers the cancel update option if the appropriate command line switch
is used.
SSM.EXE <File storePath> /INSTALL /CANCEL:<Numeric Value>[<,MODEM>]

SSM.CAB - Support Files

The SSM.CAB file contains the support files needed by SSM. These consist of the Microsoft
Data Access Object (DAO) DLLs, drivers to support ROM flash and device detection, and the
SSMMain executable.

SSM.BIN - Settings file

The SSM.BIN file is created when SSM is run in Administrative Mode. It contains runtime
settings and encrypted setup password. All settings in SSM.BIN may be overridden by command
line parameters. Refer to Appendix B, “Command Line Parameters” for more information.

SSMCVA.MDB - Update Information Database (UID)

The UID (SSMCVA.MDB file) contains information about the software updates in an SSM file
store (network file share or directory). The network share or directory with software updates is
called a file store. The UID is created in the file store by running SSM in Administrative Mode
on the server.
If SSM is running in Update Mode and a UID is not present in the file store, SSM will scan the
file store and build a temporary UID. Having a UID in the file store reduces network traffic and
improves performance by condensing the relevant file store information into a single file.
The file CCMCVAResults.XML contains the UID data in a different format for use with HP
Client Manager.

SSM Log file

SSM will create a log file or prepend an existing log file after updating the machine. The log file
is created in the user's TEMP directory and is optionally copied to the centralized log file path
specified on the command line or SSM.BIN file. Refer to Appendix C, “Log File Description”for
more information.

System Software Manager User’s Guide 1–3

Getting Started

SSM TRACE file

When /DEBUG is used on the command line, SSM will append a file in the user’s TEMP
directory. This is useful when debugging SoftPaq CVA problems.

Features of SSM
Device Driver Updates
When searching for updates, SSM detects the current installed hardware configuration and
selects only the appropriate drivers for installation. The file store may contain multiple video,
NIC, and audio drivers, but SSM will install only the updates that are appropriate.

System ROM BIOS Flash Support

SSM detects the platform and BIOS version of the target system, then selects the appropriate
ROM BIOS update package from the file store. If a newer BIOS is available, then SSM will flash
the new BIOS on the system and optionally reboot the system. The new BIOS is not effective
until the system is rebooted.

BIOS Settings and Replicated Setup (/REPSET)

BIOSConfigUtility.exe can create a BIOS settings text file that may be edited and used with SSM
as a template for deployment to other computers. Refer to Chapter 4, in section “Replicated
Setup” for more information. SSM version 1.70 added support for select notebook BIOS setting
including boot order and Wake on LAN settings. Refer to Chapter 4, “BIOS Configuration”for a
list of which BIOS options are available on each system.

Customized Packages
If a particular SoftPaq does not contain the exact information or configuration information that is
desired, a customized package may be created. Create a subdirectory containing the customized
packages and package description file (.CVA). If the target system is out of date, SSM will copy
the files from the file store to a temporary directory on the local system and install the
customized package. Refer to Chapter 3, “Package Deployment” for more information.

1–4 System Software Manager User’s Guide

 2
Modes of Operation

Administrative Mode
Use Administrative Mode to configure options that will be used to simultaneously update
multiple networked client computers. Administrative Mode lets you
■ Set specific runtime options for the utility when updating client computers
■ Create a read-only network share for the file store
■ Create a centralized read-write network share in which to store log files
■ Encrypt setup password in a configuration file
■ Build the Update Information Database on the server (If a UID is present, it must be rebuilt
each time a SoftPaq is added or removed from the file store.)
To run Administrative Mode complete the following steps:
1. Create a directory to be used as a file store (e.g., c:\\SSMFS). This is where the updates will
be stored and accessed by client computers. SSM will share this directory with read access to
everyone.
2. Copy SSM.EXE and SSM.CAB to the root of the file store.
3. Place all SoftPaqs or customized packages in the file store.
4. Double-click SSM.EXE to launch SSM in Administrative Mode.
5. Read the license agreement and click Next to proceed. A Welcome dialog displays a brief
introduction to the steps required to configure SSM using Administrative Mode.

✎ Have the following information handy:

■ Location of the file store where updates are to be kept
■ Location of the centralize log file directory
■ Setup password (if one is set on client computers).

6. Click Next. The location of the file store and default share name will be displayed.
Optionally you can specify a different file store and share name.
7. Click Next. A dialog is displayed to remind you to copy all SoftPaqs to the file store before
proceeding.
8. Click Next. The Additional Client Options dialog is displayed.

System Software Manager User’s Guide 2–1

Modes of Operation

9. Click the check box next to each client option you want to specify:
❏ Reboot client upon completion of upgrades

After applying updates, reboot client computer so that updates will take effect.
❏ Display update status bar on client system

Display a status bar on client system so that individual users can see progress and
completion of updates.
❏ Create centralized log file share

Create a log file for each client on a centralized share. If checked, you will be prompted
to enter the folder and share name for the centralized log files.
❏ Force to update clients systems

Apply "updates" to client system, regardless of whether the client system has a newer
version of the software already installed.
10. Click Next. (If you have opted to create a centralized log file share, you will be prompted to
enter the folder and share name for the centralized log files. Click Next.)
11. Click Next. (If you want to use a setup password for all client systems, click the check box
and click Next. A warning is displayed. Click OK. You will be prompted to enter a setup
password. Setup passwords are used only for system ROM BIOS updates and system BIOS
setting updates.)

✎ Ifcomputer,
you specify a setup password, it must match any setup password already set on the client
and all client computers must use the same setup password. It is a good idea to record
the password in a safe place for future reference. Additional passwords may be specified on the
SSM command line. SSM will determine which password is the correct one to use.

12. Click Next. SSM displays a summary of all operations performed.

13. Click Next. Indicate if you want SSM to check the HP Web site for updated CVA files when
building the update information database. CVA files are occasionally updated on the HP Web
site to indicate support for new computers or correct minor problems with the CVA file. SSM
obtains CVA files in the following order: from the ftp site, from CVA files in the existing file
store, then from within SoftPaqs in the file store.

✎ If/NOCVAUPDATE
you modify CVA files in the file store, either write-protect the CVA file or use the
option to prevent overwriting the modified CVA file.

14. Click Build Database to begin building the software update database.
15. Click Finish to complete the process. SSM creates the SSM.BIN file.
You must rebuild the database each time you add or remove a SoftPaq from the file store.
Administrator Mode lets you rebuild the database manually. Refer to “Update Information
Database (UID) Performance Considerations” for more information. The software update
database can be rebuilt quickly by executing the following from the command line:
SSM /AM_BLD_DB

2–2 System Software Manager User’s Guide

 Modes of Operation

Update Information Database (UID) Performance

Considerations
Update Mode uses information from the database to determine which software is applicable for a
specific client system. The database is built using information from the CVA files located in the
file store. The CVA specifies what languages, devices, and platforms a given SoftPaq supports.
SSM will attempt to match EXE and CVA files in the file store. If a CVA file does not exist for a
given SoftPaq EXE file, SSM will optionally attempt to download the CVA file from the hp.com
Web site. SSM will then extract the CVA from the SoftPaq.
SoftPaqs should be stored in the file store exactly as downloaded; they should not be run, or
extracted, within the file store. It is recommended that you put the SoftPaq files in subdirectories
with meaningful names, such as \\MyServer\SSMFS\Video Intel Extreme 2\sp27392.exe.
Customized packages should be extracted and stored in their own subfolder under the file store
with a CVA file. Refer to Appendix D, “Custom CVA Files” for detailed information on setting
up a customized CVA file.
You must rebuild the database each time you add or remove a SoftPaq from the file store.
Administrator Mode lets you rebuild the database manually. If a database file does not exist,
Update Mode rebuilds the database each time SSM is run. This takes a little longer than running
Update Mode with a database in the file store. Refer to “Update Mode” for more information.
The update database can be rebuilt by executing the following from the command line:
SSM /AM_BLD_DB

Update Mode
Update Mode updates the client system from the file store. It is invoked by specifying the file
store location as a command line parameter. Refer to Appendix B, “Command Line Parameters”
for detailed information on command line parameters. This section describes what happens
during Update Mode.

Displays Cancel Option for Low bandwidth Users

If Update Mode is executed with the optional /CANCEL parameter, SSM will determine if
user-initiated cancellation of updates is permitted for all users or just those connecting with
Dial-Up Networking and displays the Cancel dialog if permitted.

Reads Settings from SSM.BIN

SSM searches the file store for the file SSM.BIN. The BIN file contains settings chosen during
Administrative Mode and encrypted setup password. The BIN file also indicates that the
administrator accepts the license agreement. The BIN file is optional. The license agreement may
be accepted by using the /ACCEPT command line parameter. All other options may be specified
on the command line.

Creates or Copies the Update Information Database

(SSMCVA.MDB)
SSM can operate without a pre-built Update Information Database (UID), but performance is
greatly improved with a pre-built UID. This method is slower, but ensures that the database is
always up-to-date. SSM searches for a pre-built UID in the path specified on the command line.

System Software Manager User’s Guide 2–3

Modes of Operation

If the database is found, SSM will copy it locally and use it. If the database is not found, SSM
will build a temporary database. SSM scans the file store for EXE files and CVA files. For any
EXE files that do not have a corresponding CVA file, SSM will then attempt to extract a CVA
file. If the file store is across the network then this causes additional network traffic. Once all the
CVA files have been extracted, SSM creates a temporary database from the CVA files. After the
update process is complete, the temporary database is deleted.

Queries the Update Information Database

SSM uses information from the Update Information Database to determine what updates are
available and the revision levels of the software in those updates. It queries the database for
packages that match the specific device, platform, operating system, and language of the current
system. The results are considered possible updates.

Performs Updates
SSM then compares the revision level of the possible updates to the existing software. Only those
update packages that are newer than what is currently installed will be updated on the client
system unless the /FORCE option is used. SSM executes the packages in the order in which they
appear in the database. Multiple file stores may be used to install packages in a particular order.

Performs Replicated Setup

If a replicated setup command (/REPSET) is specified on the command line, SSM will configure
the BIOS settings according to the file. This feature is supported on HP desktop, workstation,
and notebook computers. Replicated Setup options include things such as boot order, removable
media write disable, asset tag, and ownership tag. Refer to Chapter 4, in section “Replicated
Setup” for more information.

Updates Log File

A log file in HTML format is created for tracking purposes. By default, the log is stored in the
current user's temporary folder on the client system, unless a different location is specified in the
command line. If the Create centralized logfile share option is selected when running
Administrative Mode, the log will be copied to the specified logfile share on the server.
An optional progress indicator is displayed throughout the update process; do not restart the
computer while SSM is running, unless you are prompted to do so.

2–4 System Software Manager User’s Guide

 3
Package Deployment

Can I Use SSM to Deploy Customized Software

Updates?
System Software Manager (SSM) requires detailed information about each software component,
in the form of a package description (CVA) file. In addition, any software to be deployed using
SSM must meet the requirements described in this chapter. To create a customized software
update (custom deliverable) you will need to
1. Create a CVA file for each deliverable and specify the required parameters in the CVA file.
2. Store the CVA file and related software components in a separate subfolder of the file store.

What is a CVA File?

The package description (CVA) file describes the deliverable. It contains the name of the package
and description. It also indicates which languages, systems, and devices are supported. It is a
plain text file similar to a Windows .INI file. SSM supports SoftPaq packages containing an
embedded package description (CVA) file, and customized packages stored in a subfolder with a
customized CVA file. You can create a customized CVA file using any text editor, such as
Notepad. Refer to Appendix D, “Custom CVA Files” for detailed information needed to create
your own CVA files.

Additional Requirements for Software Packages

Post-Operating System Silent Installation
All drivers supported by SSM must have post-OS installation mechanisms. This means that they
must have a self-contained executable setup program (such as an InstallShield program, a batch
file, etc.). If the deliverable requires changes to INF files, they need to be encompassed within an
executable that can be run by SSM. SSM's only function is to detect the hardware and software
and run a single command specified by the CVA file.

Detectable Deliverable Version

To allow SSM to determine if a specific deliverable version is installed on a system, the
deliverable must have a significant file. The significant file is used to determine if the software is
already installed and if so, which version is installed. The significant file must always have the
correct version in its resource header. Any time the Version and Revision of a deliverable change,
the value in the resource header of this significant file MUST change.

System Software Manager User’s Guide 3–1

Package Deployment

Controlled Reboot of System

All packages must support a controlled reboot of the system. This means that they cannot reboot
the system by default. If the vendor delivers an installation mechanism that requires a reboot, use
SSM's /REBOOT option. This allows multiple packages to be installed with a single reboot at
the end of the process. If the application reboots the system, SSM may not compete successfully
while waiting for the application to finish and may leave temporary files on the client system.

Installation Recovery
Any installation mechanism provided must be able to gracefully recover from a failed installation
(such as not enough disk space, etc.), by exiting without requiring user interaction. The ability to
log errors is recommended.

Installation Mechanism Must Support Upgrades

The installation mechanism must support upgrading from previous versions.

Customized Packages Must Reside in a Unique Subfolder of the

File store
Each customized package supported through SSM must reside in its own separate folder within
the file store. Its associated CVA file must have a unique name and must reside in the root of this
unique subfolder. Refer to Appendix A, “File Store” for additional information about the
structure of the file store.

3–2 System Software Manager User’s Guide

 BIOS Configuration

4
BIOS Configuration

The BIOS configuration feature of SSM lets you create standard configuration settings and
deploy them across the enterprise. By creating a configuration text file with only the setting you
want to change, you can deploy it to all systems in the enterprise. If a particular system does not
support the specified setting, it will be ignored.
BIOS configuration is supported on most high end commercial HP desktops, notebooks, and
workstations. There are a few notable exceptions that do not support BIOS configuration
including dx5150, xw5000, xw8000, D510 e-PC, TC1000, and TC1100. See the HP Product
Compatibility link on www.hp.com/go/ssm for detailed level of support for each system.

Replicated Setup
To create, save, and deploy the configuration settings, complete the following instructions:
1. Run the program BIOSConfigUtility.exe provided in the SSM download package, using the
/GETCONFIG:CONFIG.TXT command line paramter.
2. Copy the file, CONFIG.TXT to the SSM file store.
3. Edit the file CONFIG.TXT. Remove properties that you do not want to change. Modify the
other properties.

✎ Some properties, such as model and manufacturer, are read-only.

The following CONFIG.TXT example shows a configuration file that changes some properties.
English
Asset Tracking Number
CORPTAG001ABCDEF
Removable Media Boot
Enable
*Disable
Removable Media Write
Enable
*Disable
Enter Ownership Tag
Property of company XYZ.
Boot Order
Network Controller
PnP Device#1
Hard Drive (C:)
CD-ROM Drive
IDE CD-ROM Drive

System Software Manager User’s Guide 4–1

BIOS Configuration

Multibay Device (A: or CD-ROM)

Diskette Drive (A:)
USB device
Cover Lock
Unlock
*Lock

✎ The * indicates current selection.

9. Run SSM with the following command line:
SSM <File Store UNC Path> /REPSET:<UNC Path> CONIG.TXT
Example:
SSM \\MyServer\SsmFs /REPSET:\\MyFileServer\SsmFs\CONFIG.TXT

Helpful Hints:
■ This /REPSET functionality is supported on select commercial desktop, workstation, and
notebook systems. Supported settings vary by model.
■ The first line must be English
■ The settings are indented with a tab character. Indenting with space characters will not work.
■ There is no space between /REPSET: and the filename.
■ The exact strings for some boot devices may vary between models. For example, the network
controller for Boot Order was identified with the tag PNP Device #1 on 1998 model Deskpro
EN systems and Network Controller on newer systems. If your environment includes a mix
of systems, then ensure that all known values for a particular boot device are placed together
in the list relative to the next type of boot device. See example above. Note that CD-ROM is
specified several different ways.
■ Asset Tag and Ownership Tag cannot be set to blank strings.

4–2 System Software Manager User’s Guide

 BIOS Configuration

BIOS Configuration Utility

A Windows based BIOS configuration utility is provided in the SSM SoftPaq. This command
line utility provides an easy method to get the current configuration and make changes. It also
has the ability to establish, modify, and remove the BIOS setup password. The utility can be
deployed independent of SSM with a corresponding configuration file.

✎ Execute BiosConfigUtility.exe with the /HELP option to display usage syntax.

To determine which BIOS Settings are supported on other hardware, Run the program
BIOSConfigUtility.exe provided in the SSM download package, using the
/GETCONFIG:CONFIG.TXT command line paramter.
BIOS settings may also be managed through WMI by using the HP Client Management
Interface. See Softpaq SP30918 or visit www.hp.com/go/easydeploy for more information.

System Software Manager User’s Guide 4–3

BIOS Configuration

4–4 System Software Manager User’s Guide

 Using SSM with Commercial Software Distribution Systems

5
Using SSM with Commercial Software
Distribution Systems

HP Client Manager
There are several common methods used to integrate SSM into commercial software distribution
systems. The first and easiest is to use HP Client Manager (HPCM) by Altiris. This free platform
management solution has fully integrated SSM directly into the product. For a free download,
visit www.hp.com/go/EasyDeploy.
HPCM is a scalable solution that provides the ability to schedule delivery of SoftPaqs to
applicable systems throughout the enterprise with an easy to use interface. Low bandwidth
connections and seldom connected systems are supported with bandwidth throttling and check
point restarting.

Altiris Deployment Solution, SMS, and Others

If you don’t want to use HPCM, and another commercial software distribution system is already
in use in your enterprise, then use the commercial software distribution system application to
copy SSM.EXE and SSM.CAB along with the file store contents to the target system and execute
SSM. This ensures that there are no network interruptions while SSM is updating the target. This
method works well with products such as Altiris Deployment Solution, Microsoft Systems
Management Server, and other commercial software distribution systems.
Another option is to use the commercial software distribution system to remotely execute SSM
without copying the files to the target system. For this method to be efficient, ensure that SSM
has been run in admin mode to create an Update Information Database file (SSMCVA.MDB) in
the filestore. Otherwise, SSM may have to copy each SoftPaq over the network to the target
system to extract the SoftPaq information (CVA) file to determine the SoftPaq properties.
Another drawback of this method is that some software deployment applications can only launch
programs in the context of the local system account which does not have domain network file
share rights. The /INSTALL command line parameter is also recommended with this method to
prevent SSM.CAB from being copied over the network with each run.
For more information see the HP Client Manager Product Guide on the Web at
www.hp.com/go/EasyDeploy.
Altiris Deployment Solution can be used to copy an SSM file store to be repackaged and
deployed through Deployment Server. For more information see the Rapid Install User Guide on
the Altiris support documentation Web site, www.altiris.com/support/documentation.

System Software Manager User’s Guide 5–1

Using SSM with Commercial Software Distribution Systems

5–2 System Software Manager User’s Guide

 A
File Store

File Store Structure

The file store is a folder in which the software update packages are stored. It may be located on a
local hard drive or CD, or it may be located on a network share accessible to the client
computers. The file store itself may be read-only, but the location where the log files are to be
stored must be read/write. The file store must be structured as follows:
\[file store]
The file store folder contains SoftPaqs (not expanded), CVA files, and (in some cases)
configuration files. For example:
SP1111.EXE
SP1111.CVA
SP2222.EXE
SP2222.CVA
SP2222.CFG
\[file store]\[unique subfolder(s) for software package]
For each customized deliverable, there must be a unique subfolder within the file store. Each
subfolder contains the individual components of the software deliverable and a customized CVA
file. Refer to Appendix D, “Custom CVA Files” for detailed information needed to create a
customized CVA file.

Adding Custom Packages

Create a unique subfolder under the file store for each customized package. For each customized
package, there must be a custom CVA file located in the root of the package subfolder. The CVA
filename must also be unique to that package.

File store examples

Example 1: Linear file store
/FileStore
SPxxx1.exe
SPxxx2.exe

Example 2: Nested file store

/FileStore
/ROMS
SPxxx3.exe
SPxxx4.exe

System Software Manager User’s Guide A–1

File Store

/Drivers
SPxxx5.exe
SPxxx6.exe

Example 3: File store with customized packages

/FileStore
/Custom1
xxxx.CVA
Setup.exe
Other files and folders
/Custom2
xxxx2.CVA
Setup.exe
Other files and folders

A–2 System Software Manager User’s Guide

 B
Command Line Parameters

Command Line Syntax

Administrative Mode
SSM (no parameters specified)
SSM /AM_BLD_DB (to rebuild the database from the command line) where the current
directory is the root of the file store

Update Mode
SSM <file store UNC path> /parameters
SSM executes in Update Mode when it is launched with the file store path as a parameter and
/AM_BLD_DB is not specified.

Command Line Parameters

Parameter Modes Description

/ACCEPT or /A U Accept the license agreement. This allows SSM to be

used in Update Mode without the file SSM.BIN file.

/AM_BLD_DB A Silently rebuilds the Update Information Database in

Administrative Mode.

/CANCEL: <Numeric U Allows a user to cancel an update. Enables a BEGIN

Value>[,MODEM] and CANCEL button on the client screen. The numeric
value is a timeout in seconds before SSM starts the
update process. The MODEM flag allows this to take
effect only when a modem connection is detected, and is
intended for supporting mobile users.

/CURSETUPPASSWORD:”pwd” U Specifies the BIOS Setup password to use when

or /CSPWD:”pwd” performing BIOS setting updates or BIOS flash updates.
Multiple /CURSETUPPASSWORD occurrences may be
specified on the command line.

✎ BIOS passwords are converted from ASCII to English

keyboard layout scan codes. For mapping table
execute the utility BIOSConfigUtility.exe to display
usage.

/DEBUG or /D U, A Provides additional information in the log file and

records database build problems in the file
ERROR_LOG.TXT.

System Software Manager User’s Guide B–1

Command Line Parameters

Parameter Modes Description

/DoNotSetPasswordFromBinFile U If a system does not have a setup password then the

or /NOBINPWD password provided in Administrative Mode that is stored
in the SSM.BIN file will be used only to unlock the
hardware for updates and will not be used to install a
setup password on systems that do not have one.
Options specified on the command line override the
SSM.BIN file options.

/FORCE or /F U Bypasses software version detection and installs all

packages that match the hardware installed on a system,
regardless of version or date. It is useful when an update
was interrupted, or to ensure that all clients are at the
same revision for a deliverable.

✎ This parameter does not force installation of the

driver, only execution of the installation program. If
the setup program of the software update itself
performs version checking and does not install, then
the driver is not installed.

/INSTALL U Causes the installer stub to create a subfolder on the

client and install a portion of the SSM engine and the
support files in that folder. It will also create a set of
registry flags with data regarding the current installation.
In a network file store share environment, this eliminates
the need for SSM.EXE to copy and extract SSM.CAB
each time it runs.

/LOG: <path> U Specifies a UNC path location of the client log file. The
command line parameter overrides UNC path specified
in Administrative Mode. The filename will be appended
automatically, based on the computer name.

/NEWSETUPPASSWORD:”pwd” U Specifies the new setup password. This will modify any
or /NSPWD:”pwd” existing passwords. If a password is on the system, the
correct password must be provided by using the
/CURSETUPPASSWORD or /CSPWD parameters.

✎ BIOS passwords are converted from ASCII to English

keyboard layout scan codes. For mapping table
execute the utility BIOSConfigUtility.exe to display
usage.

/NOCVAUPDATE or /NU A Used with /AM_BLD_DB. Check the hp Web site for
files that do not have an associated CVA file.

/NODIALOG or /S U Suppresses the progress dialog; overrides the /TITLE

parameter.

/NOLOG U Suppresses creation of the log file; overrides the /LOG

parameter.

/REBOOT or /RB U Reboot the machine if updates were performed.

B–2 System Software Manager User’s Guide

 Command Line Parameters

Parameter Modes Description

/REPORT or /R U Allows Administrator to determine what updates are

available without making any changes to the client
system. SSM performs detection and generates a log file,
but does not execute any update packages.

✎ SSM does not report possible REPSET BIOS changes.

/REPSET: <Path and Filename> U Specifying this command line switch will cause SSM to
copy the appropriate file to the local client and utilize
the Replicated Setup/Security Settings component to
configure the client with these settings.

/RUNONCE U Causes SSM to clear itself from the RUNONCE registry

key. This command line switch is used as part of a
preinstall package.

/TIMEOUT: <Numeric Value> or U Overrides SSM's default timeout of fifteen (15) minute
/TO:<Numeric Value> before aborting execution of a deliverable. The numeric
value is the number of minutes for SSM to wait before
killing the update packages installer.

✎ A value of 0 means wait indefinitely on the package,

and is not suggested.

/TITLE: <"Title"> or /TI:<“Title”> U Specifies the title for the slider bar dialog box (must be
specified in quotes).

<UID> U Universal naming convention (UNC) path and filename

for the Update Information Database. This must be a
fully-qualified path or a path that is relative to the
location of SSM.exe.

System Software Manager User’s Guide B–3

Command Line Parameters

B–4 System Software Manager User’s Guide

 C
Log File Description

A log file in HTML format is created for tracking purposes. By default, the log is stored in the
temporary folder on the client system, unless a different location is specified in the command
line. If the Create centralized logfile share option is selected when running Administrative
Mode, the log will be copied to the specified logfile share on the server. It is named according to
the name of the client computer and has an .HTM extension. Creation of the log file can be
suppressed altogether.
The log file contains the following information:
■ Date and time the log file was generated and the name of the computer that the update was
performed on.
■ Possible Updates: Lists the device identifiers and update packages that have been found in
the database that could potentially be updated on the client system.
■ Updates: Lists the devices and update packages used to update the client system.
■ Errors: Lists errors that occurred during the detection and upgrade process. This section of
the log is generated only if errors occurred.
■ Client Information: Lists the Machine ID, system ROM version, system serial number and
Asset Tag information.
■ Detected Devices: Lists any PCI or Plug and Play device IDs found in the system, along with
ROM name and date and system identifier.
Refer to the log file to get the system ID information when generating CVA files.
For example, if DOMAIN\Jsmith is the current user on a Windows 2000 machine named
COMPUTER1, then the log file will be located in the file C:\DOCUMENTS AND
SETTINGS\JSMITH.DOMAIN\LOCAL SETTINGS\TEMP\COMPUTER1.HTM
The system environment variables TEMP and COMPUTERNAME are useful for locating the log
file.

Log File Example

This log file shows that SSM has found a possible ROM update, but that the system ROM is
already current.
Log file generated on 07/20/05 05:59:54 PM for N410C
■ SSM Version: 2.00 A2 (2.0.0.2)
■ Parameters: /TEMP:"C:\DOCUME~1\ADMINI~1.J2\LOCALS~1\Temp\SSM1F.tmp"
/SSMFS:"C:\hpcmi" c:\hpcmi /a /debug
Possible Updates
■ Update 1: HP Client Management Interface Software Provider - Version: 1.00 A
(SP30918.CVA)

System Software Manager User’s Guide C–1

Log File Description

Updates Performed
Client Information
■ System Manufacturer: Compaq
■ System Product: Evo N410c
■ System Version:
■ Base Board Manufacturer: Compaq
■ Base Board Product: 07F0
■ Base Board Version: KBC Version .
■ Machine ID: 0x07F0
■ BIOS Release Date: 12/15/2003
■ BIOS Version: 686A2 Ver. F.14
■ System Serial Number: J24P000P1262
■ Asset Tag:
■ OS: WIN2000 - SP4
■ LANG: US
Detected Devices
■ Device 0: ACPI\ACPI0003\2&DABA3FF&0
■ Device 1: ACPI\FIXEDBUTTON\2&DABA3FF&0
■ Device 2: ACPI\PNP0000\4&1D6F7EAE&0
■ Device 3: ACPI\PNP0100\4&1D6F7EAE&0
■ Device 4: ACPI\PNP0200\4&1D6F7EAE&0
■ Device 5: ACPI\PNP0303\4&1D6F7EAE&0
■ Device 6: ACPI\PNP0401\5&19BE56DF&0
■ Device 7: ACPI\PNP0501\5&19BE56DF&0
■ Device 8: ACPI\PNP0700\5&19BE56DF&0
■ Device 9: ACPI\PNP0800\4&1D6F7EAE&0
■ Device 10: ACPI\PNP0A03\2&DABA3FF&0
■ Device 11: ACPI\PNP0A06\4&1D6F7EAE&0
■ Device 12: ACPI\PNP0B00\4&1D6F7EAE&0
■ Device 13: ACPI\PNP0C01\2&DABA3FF&0
■ Device 14: ACPI\PNP0C02\0
■ Device 15: ACPI\PNP0C02\1
■ Device 16: ACPI\PNP0C02\2
■ Device 17: ACPI\PNP0C04\4&1D6F7EAE&0
■ Device 18: ACPI\PNP0C0A\1
■ Device 19: ACPI\PNP0C0A\2

C–2 System Software Manager User’s Guide

 Log File Description

■ Device 20: ACPI\PNP0C0A\3

■ Device 21: ACPI\PNP0C0A\4
■ Device 22: ACPI\PNP0C0B\0
■ Device 23: ACPI\PNP0C0B\1
■ Device 24: ACPI\PNP0C0B\2
■ Device 25: ACPI\PNP0C0D\2&DABA3FF&0
■ Device 26: ACPI\PNP0C0E\2&DABA3FF&0
■ Device 27: ACPI\SMCF010\5&19BE56DF&0
■ Device 28: ACPI\SYN0100\4&1D6F7EAE&0
■ Device 29: ACPI\THERMALZONE\C1DF
■ Device 30: ACPI\THERMALZONE\TZ1_
■ Device 31: ACPI_HAL\PNP0C08\0
■ Device 32: DISPLAY\DEFAULT_MONITOR\5&F0818&0&10000000&01&00
■ Device 33: DISPLAY\DEFAULT_MONITOR\5&F0818&0&10000002&01&00
■ Device 34: DISPLAY\MS_0003\5&F0818&0&10000081&01&00
■ Device 35:
IDE\DISKIC25N040ATCS04-0________________________CA4OA71A\5&333FC7D6&
0&0.0.0
■ Device 36: ISAPNP\READDATAPORT\0
■ Device 37: PCIIDE\IDECHANNEL\4&13D66266&0&0
■ Device 38: PCIIDE\IDECHANNEL\4&13D66266&0&1
■ Device 39:
PCI\VEN_1002&DEV_4C59&SUBSYS_00B40E11&REV_00\4&45A7597&0&0008
■ Device 40:
PCI\VEN_1033&DEV_0035&SUBSYS_00B40E11&REV_41\4&139E449D&0&10F0
■ Device 41:
PCI\VEN_1033&DEV_0035&SUBSYS_00B40E11&REV_41\4&139E449D&0&11F0
■ Device 42:
PCI\VEN_1033&DEV_00E0&SUBSYS_00B40E11&REV_02\4&139E449D&0&12F0
■ Device 43: PCI\VEN_104C&DEV_AC50&SUBSYS_0000FE00&REV_02
■ Device 44:
PCI\VEN_104C&DEV_AC50&SUBSYS_00B40E11&REV_02\4&139E449D&0&18F0
■ Device 45:
PCI\VEN_11C1&DEV_045C&SUBSYS_22018086&REV_00\4&139E449D&0&21F0
■ Device 46:
PCI\VEN_8086&DEV_1229&SUBSYS_22018086&REV_09\4&139E449D&0&20F0
■ Device 47:
PCI\VEN_8086&DEV_2448&SUBSYS_00000000&REV_42\3&61AAA01&0&F0
■ Device 48:
PCI\VEN_8086&DEV_2485&SUBSYS_00B40E11&REV_02\3&61AAA01&0&FD

System Software Manager User’s Guide C–3

Log File Description

■ Device 49:
PCI\VEN_8086&DEV_248A&SUBSYS_00B40E11&REV_02\3&61AAA01&0&F9
■ Device 50:
PCI\VEN_8086&DEV_248C&SUBSYS_00000000&REV_02\3&61AAA01&0&F8
■ Device 51:
PCI\VEN_8086&DEV_3575&SUBSYS_00000000&REV_04\3&61AAA01&0&00
■ Device 52: PCI\VEN_8086&DEV_3575&SUBSYS_00B40E11&REV_04
■ Device 53:
PCI\VEN_8086&DEV_3576&SUBSYS_00000000&REV_04\3&61AAA01&0&08
■ Device 54: PNP0000
■ Device 55: PNP0100
■ Device 56: PNP0200
■ Device 57: PNP0303
■ Device 58: PNP0401
■ Device 59: PNP0501
■ Device 60: PNP0700
■ Device 61: PNP0800
■ Device 62: PNP0A03
■ Device 63: PNP0B00
■ Device 64: PNP0C01
■ Device 65: PNP0C04
■ Device 66: PNP0E03
■ Device 67: PNP0F13
■ Device 68: ROOT\ACPI_HAL\0000
■ Device 69: ROOT\COMPOSITE_BATTERY\0000
■ Device 70: ROOT\DMIO\0000
■ Device 71: ROOT\FTDISK\0000
■ Device 72: ROOT\LEGACY_ADPU160M\0000
■ Device 73: ROOT\LEGACY_AFD\0000
■ Device 74: ROOT\LEGACY_AHA154X\0000
■ Device 75: ROOT\LEGACY_AIC78U2\0000
■ Device 76: ROOT\LEGACY_AIC78XX\0000
■ Device 77: ROOT\LEGACY_ALKERNEL\0000
■ Device 78: ROOT\LEGACY_AMSINT\0000
■ Device 79: ROOT\LEGACY_BEEP\0000
■ Device 80: ROOT\LEGACY_CLNTMGMT\0000
■ Device 81: ROOT\LEGACY_CPQDFW\0000

C–4 System Software Manager User’s Guide

 Log File Description

■ Device 82: ROOT\LEGACY_CPQDTCT\0000

■ Device 83: ROOT\LEGACY_CPQFWS2E\0000
■ Device 84: ROOT\LEGACY_CQCPU\0000
■ Device 85: ROOT\LEGACY_CQ_MEM\0000
■ Device 86: ROOT\LEGACY_DISKPERF\0000
■ Device 87: ROOT\LEGACY_DMBOOT\0000
■ Device 88: ROOT\LEGACY_DMLOAD\0000
■ Device 89: ROOT\LEGACY_EABFILTR\0000
■ Device 90: ROOT\LEGACY_FIPS\0000
■ Device 91: ROOT\LEGACY_GPC\0000
■ Device 92: ROOT\LEGACY_IPSEC\0000
■ Device 93: ROOT\LEGACY_IRDA\0000
■ Device 94: ROOT\LEGACY_KSECDD\0000
■ Device 95: ROOT\LEGACY_MNMDD\0000
■ Device 96: ROOT\LEGACY_MOUNTMGR\0000
■ Device 97: ROOT\LEGACY_NDCPRTNS\0000
■ Device 98: ROOT\LEGACY_NDIS\0000
■ Device 99: ROOT\LEGACY_NDPROXY\0000
■ Device 100: ROOT\LEGACY_NETBT\0000
■ Device 101: ROOT\LEGACY_NETDETECT\0000
■ Device 102: ROOT\LEGACY_NULL\0000
■ Device 103: ROOT\LEGACY_PARTMGR\0000
■ Device 104: ROOT\LEGACY_PARVDM\0000
■ Device 105: ROOT\LEGACY_PCIIDE\0000
■ Device 106: ROOT\LEGACY_QL1080\0000
■ Device 107: ROOT\LEGACY_QL10WNT\0000
■ Device 108: ROOT\LEGACY_QL1240\0000
■ Device 109: ROOT\LEGACY_RASACD\0000
■ Device 110: ROOT\LEGACY_SPARROW\0000
■ Device 111: ROOT\LEGACY_SYMC810\0000
■ Device 112: ROOT\LEGACY_SYMC8XX\0000
■ Device 113: ROOT\LEGACY_SYM_HI\0000
■ Device 114: ROOT\LEGACY_TCPIP\0000
■ Device 115: ROOT\LEGACY_VGASAVE\0000
■ Device 116: ROOT\LEGACY_WANARP\0000
■ Device 117: ROOT\MEDIA\MS_MMACM

System Software Manager User’s Guide C–5

Log File Description

■ Device 118: ROOT\MEDIA\MS_MMDRV

■ Device 119: ROOT\MEDIA\MS_MMMCI
■ Device 120: ROOT\MEDIA\MS_MMVCD
■ Device 121: ROOT\MEDIA\MS_MMVID
■ Device 122: ROOT\MS_IRDAMINIPORT\0000
■ Device 123: ROOT\MS_IRMODEMMINIPORT\0000
■ Device 124: ROOT\MS_L2TPMINIPORT\0000
■ Device 125: ROOT\MS_NDISWANIP\0000
■ Device 126: ROOT\MS_PPTPMINIPORT\0000
■ Device 127: ROOT\MS_PTIMINIPORT\0000
■ Device 128: ROOT\PARALLELCLASS\0000
■ Device 129: ROOT\SYSTEM\0000
■ Device 130: ROOT\SYSTEM\0001
■ Device 131: SMCF010
■ Device 132:
STORAGE\VOLUME\1&30A96598&0&SIGNATUREF625F625OFFSET7E00LENGTH9
502F6200
■ Device 133:
SW\{A7C7A5B0-5AF3-11D1-9CED-00A024BF0407}\{9B365890-165F-11D0-A195-002
0AFD156E4}
■ Device 134:
SW\{CD171DE3-69E5-11D2-B56D-0000F8754380}\{9B365890-165F-11D0-A195-0020
AFD156E4}
■ Device 135: USB\ROOT_HUB20\5&3D1D651&0
■ Device 136: USB\ROOT_HUB\5&2AABC05A&0
■ Device 137: USB\ROOT_HUB\5&3B1D093B&0

C–6 System Software Manager User’s Guide

 D
Custom CVA Files

Sometimes it is necessary to modify a package description (.CVA) file to meet specific needs.
This section defines the more relevant fields used by SSM. CVA files may be modified for
existing SoftPaqs or for customized packages. A customized package is a directory in the file
store that contains a CVA file and the files the package setup files.
There are several key points to remember about CVA files.
■ If a customized package is created, remove the SoftPaq= line from the CVA file.
■ For a non-SoftPaq customized package, all files in the directory and subdirectory of the CVA
are transferred as a unit during installation. Do not put customized packages in the top level
of the file store.
■ If the CVA file and setup files are packaged with Packaged For The Web to create a single
package file, the CVA filename must be the same as the Packaged for the Web file name.

CVA Syntax
[CVA File Information]
CVAVersion=<CVA file version>

[Software Title]
US=<Software Name/Title in US English>
[US.Software Description]
<General description of the software>
[General]
Version=<Software Version>
Revision=<Software Revision>
Pass=<Software Pass Number>
[DetailFileInformation]
<FileName>=<Root of folder>\relative path, <Major Version>, <Minor Version>,
<Major Revision>, <Minor Revision>

[SupportedLanguages]
Languages=<Comma Separated language values as described by the 2 letter
designator>
[Operating Systems]
<OS code>=<Minimum Service Release on which the package works on this OS>
[System Information]
SysID1=<System ID for the 1st system on which this deliverable operates>
SysName1=<Marketing name of the system><Comma separated list of models>
SysIDn=<System ID for the nth system on which this package operates>

System Software Manager User’s Guide D–1

Custom CVA Files

SysNamen=<Marketing name of the system><Comma separated list of models>

[Devices]
<PnP/PCI Device ID>=<Marketing designation of the device>
<PnP/PCI Device ID>=<Marketing designation of the device>
[Install Execution]
SilentInstall=<Relative path of Install executable> <command
line parameters>

Field Definitions
[CVA File Information]
CVAVersion=<CVA File Version>
Optional
This field has no effect on SSM functionality; however, if used properly, keeps track of changes
made to the CVA file. The value is an integer that can be incremented each time changes are
made to the CVA file.

[Software Title]
US=<Software Name/Title in US English>
Required. (Maximum = 40 characters.)
This field identifies the software update.

[US.Software Description]
<General description of the software approved by marketing>
Recommended.
This is a brief description of the software, in English.

[General]
Version=<Software Version>
Required.
This is a free-form text value. It usually follows the form: <Major version>.<Minor
version>

Revision=<Software Revision>
Required.
The revision of the software. If the revision of the software is irrelevant, then leave this key
empty.

D–2 System Software Manager User’s Guide

 Custom CVA Files

Pass=<Software Pass Number>

Required.
The pass/build number of the software. If the pass/build number information is irrelevant, then
leave this key empty.

[DetailFileInformation]
<FileName1>=<Root folder>\relative path, <Major Version>, <Minor Version>,
<Major Revision>, <Minor Revision>
Required.
To allow SSM to determine if a specific package version is installed on a system, the package
must have a significant file that will always be present and that will always have the correct
version in its resource header (this file may, for example, be the main .EXE file, .DLL, or .SYS
file). Any time the version and revision of a package change, the value in the resource header of
this significant file MUST also change.
SSM uses this information to determine whether the version of the software update is newer than
the version installed on the client computer. Therefore, the [DetailFileInformation] section
needs to describe the file that contains the version information in the resource header.
To determine the version of the package programmatically, the major and minor version as well
as major and minor revision numbers must be entered, separated by commas. This information is
the same information contained in the VS_VERSION_INFO field located in the [File Version]
section of the significant file. The DWORD value for major and minor revision is located in the
[File Version] section and is listed as hex numbers in the form
0x0000,0x0000,0x0000,0x0000. The version information needs to be entered in this
format.
The root of the folder is one of the following values:

Value Description

<WINDIR> The main Windows folder on the target system

(e.g. C:\WINDOWS or C:\WINNT).

<WINSYSDIR> The Windows system folder on the target system

(e.g. C:\WINDOWS\SYSTEM or
C:\WINNT\SYSTEM32).

<WINDISK> The drive letter of the disk containing the

Windows folder (e.g. C:).

<WINSYSDISK> The drive letter of the disk containing the

Windows System folder (e.g. C:).

<WINSYS16DIR> On a Windows NT target system, the 16-bit

System folder.

<ProgramFilesDir> The Program Files folder on the target system

(e.g. C:\PROGRAM FILES).

System Software Manager User’s Guide D–3

Custom CVA Files

Value Description

<CommonFilesDir> The Common Files folder on the target system

(e.g. C:\PROGRAM FILES\COMMON FILES).

<FONTDIR> The folder on the target system where the

Windows fonts folder is located (e.g.
C:\WINDOWS\FONTS).

For the Windows NT Matrox Graphics Controller drivers this section would look like this:
[DetailFileInformation]
mga64.dll=<WinSysDir>,0x0003,0x0000,0x0002,0x0000
or
[DetailFileInformation]
mga.sys=<WinSysDir>\drivers,0x0003,0x0000,0x0002,0x0000
A ROM version is designated with the name of the file to be the name of the ROM image CAB
file and the version in the form:
ROM, <ROM Family>,<Month>,<Day>,<Century>,<Year>
If a ROM flash utility is provided (HpFlash32, CpqFlash, PhoenixFlash) and specified on the
SilentInstall= line, then the ROM filename and family fields are not used. Note that the version
values are in decimal, whereas the version values for applications are in "0x__" hex format.
For a 686T2 ROM, this section would be:
[DetailFileInformation]
686T2.CAB=ROM,686T2,10,02,19,98

[SupportedLanguages]
Languages=<Comma Separated language values as described by the 2 letter
designator>
Required.
This key contains a comma-delimited list of languages that the software supports. Each language
is specified by a 2-character code; for example, US is US English, IT is Italian. This key lets
SSM know on which localized operating systems this software can be installed.
If the deliverable supports all languages, then GLOBAL may be specified.

Language Abbreviations for Use in Custom CVA Files

Language Abbreviations for Use in Custom CVA Files

0x0416 BR Portuguese - Portuguese (Brazilian)

0x0816 BR Portuguese - Portuguese (Standard) (default to BR)

0x0804 CH Chinese (PRC) Simplified

0x1004 CH Chinese (Singapore)

0x0405 CS Czech - CSY

D–4 System Software Manager User’s Guide

 Custom CVA Files

Language Abbreviations for Use in Custom CVA Files (Continued)

0x0406 DK Danish - Danish

0x0c0c FC French - Canadian

0x040b FI Finnish - Finnish

0x080c FR French - Belgian

0x040c FR French - French (Standard)

0x100c FR French - Swiss

0x0408 GK Greek - ELL

0x0c07 GR German - Austrian

0x0407 GR German - German (Standard)

0x0807 GR German - Swiss

0x040e HU Hungarian - HUN

0x0410 IT Italian - Italian (Standard)

0x0810 IT Italian - Swiss

0x0411 JP Japanese

0x0412 KR Korean

0x0812 KR Korean (Johab)

0x0813 NL Dutch - Belgian (Flemish)

0x0413 NL Dutch - Dutch (Standard)

0x0414 NO Norwegian - Norwegian (Bokmal)

0x0814 NO Norwegian - Norwegian (Nynorsk)

0x0415 PL Polish - PLK

0x0419 RU Russian

0x0819 RU Russian - Moldavia

0x041D SE Swedish - Swedish

0x041B SL Slovak

0x2c0a SP Spanish - Argentina

0x400a SP Spanish - Bolivia

0x340a SP Spanish - Chile

System Software Manager User’s Guide D–5

Custom CVA Files

Language Abbreviations for Use in Custom CVA Files (Continued)

0x240a SP Spanish - Columbia

0x140a SP Spanish - Costa Rica

0x1c0a SP Spanish - Dominican Republic

0x300a SP Spanish - Ecuador

0x100a SP Spanish - Guatemala

0x0c0a SP Spanish - Modern sort

0x180a SP Spanish - Panama

0x3c0a SP Spanish - Paraguay

0x280a SP Spanish - Peru

0x380a SP Spanish - Uruguay

0x200a SP Spanish - Venezuela

0x080a SP Spanish - Mexican

0x0c0a SP Spanish - Spanish (Modern)

0x040a SP Spanish - Spanish (Standard/Traditional)

0x041E TH Thai

0x041f TR Turkish - TRK

0x0404 TW Chinese (Taiwan)

0x0409 US English - American

0x0c09 US English - Australian

0x0809 US English - British

0x1009 US English - Canadian

0x1809 US English - Ireland

0x040f US Icelandic - Icelandic

0x1409 US English - New Zealand

0x0000 US Default

D–6 System Software Manager User’s Guide

 Custom CVA Files

[Operating Systems]
<OS Code>=<Minimum Service Pack Release>
This section lists operating systems for which the software is intended on which it can run. Each
operating system is specified by its code as follows (each code is a unique version of the
operating system):
WIN95 (Windows 95)
WIN98 (Windows 98)
WINME (Windows ME)
NT40 (Windows NT 4.0)
WIN2000 (Windows 2000)
WINXP32P (Windows XP Professional and Home Edition)
NONE (OS-independent)
Packages must also specify the minimum version service pack release. For example, a driver may
only work on Windows NT 4.0 Service Pack 3 or higher, in which case the CVA file would
contain NT40=SP3. A value MUST be present after the equal sign for each operating system.
There should be only ONE entry for each operating system.
Acceptable values for <Minimum Service Pack Release> are as follows:
OEM (Original OEM release of an operating system
OSR0 (Windows 95 retail release)
OSR1 (Windows 95 OSR1)
OSR2 (Windows 95 OSR2 )
OSR21 (Windows 95 OSR 2.1)
OSR25 ( Windows 95 OSR 2.1)
SP1 (Service Pack 1 [for Windows NT or Windows 98])
SP2 (Service Pack 2)
SP3 (Service Pack 3)
SP4 (Service Pack 4)
SP5 (Service Pack 5)
If the software is OS-independent, as would be the case for ROMPaqs, there should be only one
entry in this section:
NONE

[System Information]
SysID{AnyUniqueTag}=<System ID>
SysName{AnyUniqueTag}=<Marketing name>
Required.

System Software Manager User’s Guide D–7

Custom CVA Files

The SysID{AnyUniqueTag} key (where n is a number, 1 through n, assigned to each SysID and
SysName pair) specifies a System ID information for each computer on which software updates
are to be deployed. System ID may be specified in either of two formats, system ID hexadecimal
format, or SMBIOS format. The hexadecimal format is 0xXXXX. For example, the system ID
of Deskpro EN system is 0x0400. The hexadecimal machine ID is listed in the SSM log file.
The SMBIOS format is of the syntax:
SysID{AnyUniqueTag}=<SysMan>,<SysProd>,<SysVer>,<BoardMan>,<BoardProd
>,<BoardVer>
The fields represent the SMBIOS System (record type 1) and SMBIOS Baseboard (record type
2) manufacturer, product, and version fields. Any blank field is considered a wildcard (*) "don't
care." At least one of the six fields must be non-blank. SMBIOS data is available in the SSM log
file.
The SysName key specifies the Product Marketing Name, and associated models for each
computer on which software updates are to be deployed.

[SoftPaq]
SoftPaqNumber=
The SoftPaq number of the software. For custom packages delete this line.

[Devices]
<Device ID>=<Marketing name of the device>
This section lists the Device ID and the Marketing Names of devices with which the software
deliverable is associated, if any. In general, this section is required only for device driver
software. PCI IDs may be expressed in two, three, or four-part names that follow the convention
in the Windows Registry (also displayed in the SSM log file).
SSM searches the list of devices currently present in the system as noted by the SSM log file for
the specified <Device ID> substring. If the <Device ID> substring is not found in the list of
devices on the system, the deliverable is not a possible update for the system.

[Install Execution]
SilentInstall="<Relative path and Install executable>" <command line
parameters>
Required.
This field contains the relative path, within your package folder structure, of the installation
program as well as the command line parameters (if any) required to perform a silent installation
of the software while the OS is running. Enclose the relative path and filename in quote
characters if long file name path is used.
If there is questions of how SSM parsed the command line, use the /DEBUG switch then look in
the log file to see the exact command SSM executes.
Examples:
SilentInstall=setup.exe -s
SilentInstall=disk1\setup.exe -s /parameter:"45x32"
SilentInstall="Long file name\install program.exe" -s /parameter:"45x32"

D–8 System Software Manager User’s Guide

 Custom CVA Files

Sample CVA File

Here is a sample custom CVA file that launches Notepad with the CVA file.
[CVA File Information]
CVA Version=1
CVASyntaxVersion=1.0L

[Software Title]
US=Notepad Test File

[US.Software Description]
Launches notepad with some parameters to use as a test for SSM.

[General]
Version=5.12.01.2508
Revision=E
Pass=6

[DetailFileInformation]
;
; Version 5.12.01.2508 of notepad.exe is from Windows 2000.
;
notepad.exe=<WINSYSDIR>,0x0005,0x000c,0x0001,0x09cc

[SupportedLanguages]
Languages=GLOBAL

[Softpaq]
;
; Ensure that SoftpaqNumber= is blank or deleted for custom packages.
;
SoftpaqNumber=
SupersededSoftpaqNumber=

[Operating Systems]
;
; Specify the languages here or NONE for all operating systems.
;
;WIN95=OSR2
;WIN98=OEM
;WINME=OEM
;NT40=SP3
;WIN2000=OEM

System Software Manager User’s Guide D–9

Custom CVA Files

;WINXP32P=OEM
;
;NONE

[System Information]
;
; Two formats are supported. System ID (0x0538) and
; SMBIOS based system ID information. If no system ID information
; is specified then this deliverable will be installed on all
; platforms.

SysID_538=0x0538
SysName_538=Armada M700

SysID_700=Compaq,,,,M700,
SysName_700=Armada M700

SysID_VL420=Hewlett-Packard,,VL420,,,
SysName_VL420=Hewlett-Packard VL420

[Devices]
;
; If the deliverable is a driver that required specific hardware,
; the specific all the supported PCI ID's here.
;
; ven_8086&dev_2445=ADI SoundMax Integrated Digital Audio
; ven_8086&dev_2415=ADI SoundMax Integrated Digital Audio

[Install Execution]
;
; In this example we will replace the traditional call to "Setup.exe"
; with "NotePad" and use the CVA file name as a parameter.
;
; SilentInstall="SETUP.EXE" -silent
;
SilentInstall="Notepad.EXE" notepad.cva
Install="SETUP.EXE"

Errors
SSM is not a CVA verification tool, and only performs rudimentary checks on the validity of the
data in the CVA file. Refer to Appendix E, “Error Codes” for detailed information about error
messages that may be encountered related to the CVA file. If errors occur, SSM excludes that

D–10 System Software Manager User’s Guide

 Custom CVA Files

software component from the Update Information Database (UID) and does not deploy it. SSM
continues processing the next CVA file. Use the /DEBUG command line option to record
potential CVA file errors to the file ERROR_LOG.TXT while building the database:
SSM /AM_BLD_DB /DEBUG
See also %TEMP%\%computername%.ssmtrace for helpful debug information.

System Software Manager User’s Guide D–11

Custom CVA Files

D–12 System Software Manager User’s Guide

 E
Error Codes

Locating Error Messages

If errors occurred when running SSM on the client computer, the log file will contain a section
called [Errors]. If there were no errors, this section will not exist in the log file. To locate errors:
1. Click Start > Search > For Files or Folders...
2. In the Containing text: box, type [Errors].
3. Click Search Now.

Administrative Mode Errors

To operate in Update Mode, the SSM.CAB file must be present in the file store. After the
Administrator selects the file store folder, the wizard checks for the existence of the SSM.CAB
file under the file store folder. If the SSM.CAB file does not exist in the file store folder, it
searches for the SSM.CAB file and, if found, displays a list of the SSM.CAB file(s)found. Select
the CAB file you want to copy to the file store then click Next.
If the search for the SSM.CAB file failed, SSM displays a message that the SSM.CAB file is
required in the file store folder and identifies the file store folder as: D:\SSMFILE STORE. Click
Finish to terminate and reinstall System Software Manager.
If SSM is executed on an unsupported operating system (Microsoft Windows 3.x or Windows
NT Workstation 3.5X), SSM displays an error message and terminates.
Use the /DEBUG command line option to record potential CVA file errors to the file
ERROR_LOG.TXT while building the database:
SSM /AM_BLD_DB /DEBUG

Update Mode Errors

In Update Mode, SSM may display a dialog if it encounters a problem with the database access
objects (DAO). If this happens then SSM log file will indicate that there were no possible
updates.
All other errors are placed in the log file, and described in the table below.

Error Message Description

SSM is for use on Windows 95/98 and You have tried to execute SSM on an
Windows NT 4.0 or greater. - SSM Exit unsupported operating system (Windows 3. X or
Windows NT 3.5 X).

Failed to initialize client information. SSM was Detection failed. SSM was unable to obtain
unable to determine asset information on the device information on the client. This error
client system. Device detection will fail, as well. indicates a driver interaction issue.

System Software Manager User’s Guide E–1

Error Codes

Error Message Description

User does not have correct privileges to update SSM was unable to elevate its privilege to
system - SSM Exit. perform updates. The elevated privilege is
achieved through the trusted client portions of
the administrative wizard.

SSM support CAB component not found - SSM SSM was unable to find the CAB support file
Exit. and aborted execution. This error does not occur
if SSM is installed locally through the /INSTALL
command line switch.

Unable to extract cab file. The support CAB file is corrupted and cannot be
expanded. This error does not occur if SSM is
installed locally through the /INSTALL
command line switch.

Cannot set the setup password with error code The value in this error message indicates the
<value>. reason the setup password could not be set. The
lower byte of <value> is the ROM return code.
(80= Invalid password because it was too long,
86=command not supported)

ROM Flash Error code <value> <symbol_name> SSM was unable to flash the system ROM. The
error code indicates the reason for the failure.
This is sometimes the result of incorrect
passwords (F6 ERROR_LOCKING_MEMORY).

<Update Package Title> has no installer. The specified update package has a blank
SilentInstall entry in its CVA file.

Unable to open <SoftPaq Filename> SSM expands SoftPaq files before executing the
installer for the update. If that expansion fails,
this message is entered in the log file. If this is a
custom deliverable, ensure that the SoftPaq=
line in the CVA file is removed.

Unable to expand ROMPaq <SoftPaq Filename> SSM is expecting a ROM BIOS SoftPaq, but was
unable to expand the files.

<Update Package Title>: Failed to terminate in a SSM waits 15 minutes before terminating an
timely manner. update package's installer. If the installer is
terminated, this message is entered into the log
file.

<Update Package Title>: Returned exit code This message is placed in the log when an
<value> update issues an exit code that is non-zero.This
may or may not represent a failed install since
many updates return non-zero exit codes. The
exit code is update-specific; refer to the
documentation provided with the update to
determine what the exit code means.

E–2 System Software Manager User’s Guide

 Error Codes

Error Message Description

<Update Package Title>: Failed to spawn This message indicates that the installer for the
command line (<update package installer update failed to execute properly, and may be
command line with arguments>) with error corrupted.
(<value>)

Can't update the replicated setup settings. The setup password does not match. The
replicated setup/security settings module returns
this message when the system attempts to modify
configuration settings on a client system using an
incorrect password.

F6 ERROR_LOCKING MEMORY The setup password is not correct.

Evo 600c (686DF) BIOS must be updated to Self-explanatory.

10/17/2001 before upgrading to newer BIOS.
Download SP21459.EXE and SP21459.TXT.

Password is set, but no password provided in An attempt to flash the ROM BIOS failed.
SSM.BIN.

RMSET File not found: <Filename> The file specified with the RMSET option was
not found.

Failed to initialize client information. The required device driver could not be loaded
and system information could not be obtained.
This may occur if there is a driver version conflict
or SSM does not have administrative rights.

System Software Manager User’s Guide E–3

Error Codes

CVA Errors
Use /DEBUG in Administrative Mode, then check the file ERROR_LOG.TXT to see these
errors.
CVA files are formatted like the INI files found in Windows. SSM uses standard Windows calls
to read the data from these files. Syntax errors in a heading or a tag field will result in that field
being ignored. A syntax error in the data portion of the tag may result in improper execution of
the deliverable, or a misspelled title in the log file.
A syntax error in the Language field or the Operating System fields will result in the whole CVA
file being rejected.

Error Message CVA Section Description

No key file information. DetailFileInformation The entire section was omitted.

DetailFileInformation is required for
the package to be considered SSM
compliant.

Key filename is invalid. DetailFileInformation Key filename is not specified or is not

valid. At least one key filename must
be specified.

Key file path is invalid. DetailFileInformation Path for the key file is not provided or
is not valid.

Major version information is DetailFileInformation The major file version data was
invalid. omitted.

Minor version information is DetailFileInformation The minor file version data was
invalid. omitted.

Major revision information is DetailFileInformation The major file revision data was
invalid. omitted.

Minor revision information is DetailFileInformation The minor file revision data was
invalid. omitted.

Failed to commit transaction on SSM was unable to add the data from
record add. the current CVA file to the Update
Information Database. This is a
catastrophic error; you must delete the
Update Information Database and
attempt to rebuild it.

Database transaction error on SQL: SSM was unable to make the

<Error Text> appropriate system calls to talk to the
UID. This is a catastrophic error; you
must delete the UID and attempt to
rebuild it. This also indicates an
operating-system level interaction
issue.

E–4 System Software Manager User’s Guide

 F
Troubleshooting

Problem Cause Solution

Error log contains errors, but Silent installation programs for This is not necessarily an error.
drivers installed properly. some drivers return a non-zero
return code upon completion. SSM
expects a return code of zero.

Controller is not detected by SSM. SSM only detects PCI or Plug and
Play controllers.

SSM ran, but driver was not Driver was uninstalled before Uninstalling the driver may not
updated. running SSM. have deleted all of the driver files
from the hard drive. SSM tries to
determine which version is
installed; remaining files may
indicate that the driver is still
installed. Look for the file name in
the [DetailFileInformation] of
the CVA file for driver update.
Delete the driver file from the hard
disk.

Need to uninstall SSM. Delete SSM components are only installed To remove the client components,
SSM.EXE, SSM.CAB, and the file on client systems when the delete the SSM folder and all files
store. /INSTALL switch is used. The within it.
components are stored in a folder
named SSM on the same drive as
the operating system.

System Software Manager User’s Guide F–1

Troubleshooting

Problem Cause Solution

Deliverable does not appear as a CVA file is not SSM compliant. Rebuild the database with the
“possible update.” /DEBUG switch:
SSM.EXE c:\Filestore /DEBUG
/AM_BLD_DB
then examine the file
%TEMP%\%COMPUTERNAME
%.SSMTRACE for clues. SSM will
reject CVA files that do not have
required fields.

One or more of the CVA fields do The list of Possible Updates is

not match the current system. determined by matching the system
ID, operating system, language,
and device IDs. Run SSM with the
/DEBUG switch and examine the
SSMTRACE, CVA and log files for
clues to determine which field does
not match.

F–2 System Software Manager User’s Guide