IBM Tivoli and Cisco User Manual page 423

The attributes that are generated by the Security Compliance Manager client are
always present, and are known as innate attributes. These attributes, presented
in Table 8-7, cannot be overridden by user settings.
Table 8-7 Innate remattribute tag usage
Attribute Example
client.alias scmclient
client.dhcp false
client.fingerprint a3:55:e5:62:2a:db:52:93:
3b:c2:22:38:44:53:bf:02
client.id 1
client.root C:\PROGRA~1\IBM\SC
M\client
os.arch x86
os.name Windows 2000
os.version 5.0
win.build 2195
win.product Microsoft Windows 2000
win.sp Service Pack 4
win.version 5.0
All other attributes come from either the HANDLER_ATTRIBUTES parameter of
the policy collector or the local handlers.properties file. In both of these locations
attributes are specified in key-value pairs, separated by an equals sign (=). In
general, attributes are used to control the configuration and behavior of the
remediation subsystem, but they can also be used to provide general
Description
The client's alias. This may be null if
the client is not a DHCP client
Indicates whether the client is a DHCP
client.
The client's globally unique fingerprint.
The client's unique identifier as set by
the server.
The root of the client installation.
The processor architecture of the client
as reported by Java.
The host OS name as reported by
Java.
The host OS version as reported by
Java.
The build version of Windows as
reported in the CurrentBuildNumber
registry key.
The name of the Windows product as
reported in the ProductName registry
key
The Service Pack of the Windows
product as reported in the CSDVersion
registry key.
The version of Windows as reported in
the CurrentVersion registry key.
Chapter 8. Remediation subsystem implementation
405