Radia Client Automation Enterprise InventoryManagerFor the Windows® operating systems
Software Version: 9.00
Reference Guide
Document Release Date: April 2013
Software Release Date: April 2013
Legal NoticesWarranty
The only warranties for products and services are set forth in the express license or serviceagreements accompanying such products and services. Nothing herein should be construed asconstituting an additional warranty. Persistent Systems shall not be liable for technical or editorialerrors or omissions contained herein. The information contained herein is subject to change withoutnotice.
Restricted Rights LegendConfidential computer software. Valid license from Persistent Systems or its licensors required forpossession, use or copying. No part of this manual may be reproduced in any form or by any means(including electronic storage and retrieval or translation into a foreign language) without prioragreement and written consent from Persistent Systems.
Copyright Notice© Copyright 2013 Persistent Systems, its licensors, and Hewlett-Packard Development Company,LP.
Trademark NoticesMicrosoft®, Windows®, Windows® XP, andWindows Vista® are U.S. registered trademarks ofMicrosoft Corporation.
UNIX® is a registered trademark of TheOpenGroup.
AcknowledgementsThis product includes software developed by the Apache Software Foundation(http://www.apache.org/).
This product includes cryptographic software written by Eric Young ([email protected]).
This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit(http://www.openssl.org/).
This product includes software written by Tim Hudson ([email protected]).
This product includes software written by Daniel Stenberg ([email protected]).
This product includes OVAL languagemaintained by TheMITRE Corporation ([email protected]).
Radia Client Automation Enterprise Inventory Manager (9.00)Page 2 of 90
Reference Guide
Documentation UpdatesThe title page of this document contains the following identifying information:
l Software Version number, which indicates the software version.
l Document Release Date, which changes each time the document is updated.
l Software Release Date, which indicates the release date of this version of the software.
To check for recent updates or to verify that you are using themost recent edition of a document, goto:
http://support.persistentsys.com/
This site requires that you register for a Persistent Passport and sign in. Register online at theabove address.
For more details, contact your Persistent sales representative.
Radia Client Automation Enterprise Inventory Manager (9.00)Page 3 of 90
Reference Guide
SupportPersistent Software support provides customer self-solve capabilities. It provides a fast andefficient way to access interactive technical support tools needed tomanage your business. As avalued support customer, you can benefit by being able to:
l Search for knowledge documents of interest
l Submit and track support cases and enhancement requests
l Submit enhancement requests online
l Download software patches
l Look up Persistent support contacts
l Enter into discussions with other software customers
l Research and register for software training
To access the Self-solve knowledge base, visit the Persistent Support home page.
Note: Most of the support areas require that you register as a Persistent Support user and signin. Many also require an active support contract. More information about support access levelscan be found on the Persistent Support site.
To register for a Persistent Support ID, go to: Persistent Support Registration.
Radia Client Automation Enterprise Inventory Manager (9.00)Page 4 of 90
Reference Guide
ContentsReference Guide 1
Contents 5
Introduction 7
Overview 7
Inventory Manager Terminology 7
Client Automation Prerequisites 8
Necessary Skills 8
Client AutomationModules 8
Web-Based EnterpriseManagement 8
Microsoft Implementations of WBEM 8
Inventory Manager Technology 9
Common InformationModel (CIM) 9
Web-Based EnterpriseManagement (WBEM) 9
Windows Management Instrumentation (WMI) 9
Client Automation andWBEM 10
The AUDIT Domain 11
The AUDIT Domain in the CSDB 11
AUDIT Domain Defined 11
RIMOPTS Class 13
REGISTRY Class 15
Implementing Registry Scans 17
Inventory Database Tables 17
Software and Hardware Auditing 19
Auditing Types 19
File Auditing 19
WBEM Auditing 23
WBEMObject Processing 26
Radia Client Automation Enterprise Inventory Manager (9.00)Page 5 of 90
Disabling Remnant Configuration Server Instances forWBEMObject Processing 26
Hardware Auditing 27
Successful Auditing 31
Sample Auditing 31
Configuring a Sample Audit 34
Audit Scanning Processes 37
Creating Audit Packages 39
Audit Packages or PACKAGE Class 39
Using the CSDB Editor Create/Maintain Audit Services 41
Creating a New Audit Package 42
Adding a Component to an Audit Package 46
Creating a ZSERVICE Instance 47
Configuring Timers for Audit Collection 53
The Scheduling (TIMER) Class 53
Creating a Timer Instance 57
Creating a New Timer in the AUDIT Domain 57
Specifying Timer Settings 59
Specifying ZSCHDEF 59
Specifying ZSCHTYPE 60
Specifying ZSCHFREQ 61
Specifying ZRSCCMDL 61
Specifying ZNOPING, PINGDLAY, and PINGCNT 61
Connecting the Timer to a Service 62
Audit Execution Configuration 62
Customizing the RIMOPTS Instance 63
Viewing Inventory Reports 67
Reporting Views for Inventory Reports 67
Windows Vista Readiness Reports 68
Filtering Inventory Reports with Reporting Server 69
Detail and Summary Reporting Tables 71
We appreciate your feedback! 89
Radia Client Automation Enterprise Inventory Manager (9.00)Page 6 of 90
Reference GuideContents
Chapter 1
IntroductionOverview
The Inventory Manager is an agent feature used to discover configuration information on remotecomputers. It enables centralized reporting and administration based on the discovery results.
Systems administrators use the Radia Client Automation Administrator Configuration ServerDatabase Editor (Admin CSDB Editor) to specify what inventory management data is to becollected. An Inventory connect (DNAME=AUDIT) is then run on the target computer to retrieve therequired information and send it up to the RCA server for later reporting.
For more information on reporting, refer to theRadia Client Automation Enterprise User Guide.
Inventory Manager TerminologyAgent Computer
Agent computer is the computer on the end user's desktop that has the Client Automation agentsoftware installed on it.
CIM (Common Information Model)
CIM is a standardized framework forWBEM. It is an object oriented set of schemas for cross-platform network management. Some of these objects include computer systems, devices (likeprinters and batteries), controllers (for example, PCI and USB controllers), files, software, etc.
Clean Machine
Cleanmachine is a desktop computer on which the operating system has just been installed, andno further changes have beenmade.
Client Automation agent
Client Automation agent is the Client Automation software component that is installed on the enduser's desktop computer.
Messaging Server
TheMessaging Server is the Client Automation infrastructure component that provides a commonrouting and inter-server data delivery service, especially for report-bound data. When servicing aConfiguration Server, theMessaging Server handles the delivery of Inventory, Patch, and otherdata collected from Client Automation agents to the appropriate external location. Data DeliveryAgents are used to post data directly to an SQL-compliant database using ODBC.
Reporting Server
The Reporting Server is aWeb-based interface to the reportable data captured by the ClientAutomation extended infrastructure product suite. It allows you to query the combined data in
Radia Client Automation Enterprise Inventory Manager (9.00)Page 7 of 90
Reference GuideChapter 1: Introduction
existing Inventory Manager, PatchManager, and Application UsageManager databases and createdetailed reports. You have the option of mounting an existing LDAP directory, which allows you tofilter your data using your LDAP directory levels.
Web-Based Enterprise Management (WBEM)
Web-Based EnterpriseManagement enables information such as the amount of RAM in acomputer, hard disk capacity, process type, and versions of operating systems to be extractedfrom computers, routers, switches, and other networked devices.
Windows Management Instrumentation (WMI)
Windows Management Instrumentation (WMI) is Microsoft's implementation of WBEM forMicrosoft Windows platforms.
WMI Repository
WMI repository is a central storage area designed to holdmanaged information.
Client Automation PrerequisitesThe Inventory Manager requires the following Client Automation components:
l RCA Server
l Client Automation agentn ApplicationManager with Inventory Manager feature
n Application Self-ServiceManager (optional)
l RCA Administrator CSDB Editor. This is installed as part of the RCA Administrator. For moreinformation on RCA Admin CSDB Editor, see theRadia Client Automation Enterprise CSDBEditor Online Help.
Necessary SkillsClient Automation Modules
This document assumes that the reader is familiar with the CSDB, with administering it using theCSDB Editor and the EnterpriseManager. See theRadia Client Automation EnterpriseAdministrator User Guide and theRadia Client Automation Enterprise User Guide for moreinformation.
Web-Based Enterprise ManagementThis document assumes that the reader is familiar withWeb-Based EnterpriseManagement(WBEM). Resources for familiarizing yourself withWBEM can be found at the following web site:http://www.dmtf.org/spec/wbem.html .
Microsoft Implementations of WBEMThis document also assumes that the reader is familiar withWindows ManagementInstrumentation (WMI). Information about WMI can be found at the following web site:
Radia Client Automation Enterprise Inventory Manager (9.00)Page 8 of 90
Reference GuideChapter 1: Introduction
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/w98ddk/hh/w98ddk/wmi_wp_03se.asp.
Inventory Manager TechnologyWhile an administrator with little web-based knowledge can use the Inventory Manager withsuccess, it is important to understand some of the technology behind the product. The informationthat is provided below is intended to give you a preliminary understanding of the technology behindthe Inventory Manager agent. As indicated in "Client AutomationModules" on previous page, werecommend you becomemore familiar with web-based technology.
Common Information Model (CIM)The Common InformationModel (CIM) is an object-orientedmodel, or schema, that represents andorganizes information within amanaged environment. This includes:
l Defining objects, such as computer systems, devices, controllers, software, files, people, andso forth.
l Allowing for the definition of associations, such as describing relationships between object-dependencies, component relationships, and connections.
l Allowing for the definition ofmethods, such as input/output parameters and return codes.
By using object-oriented designs and constructs, one of the goals of the CIMmodel is toconsolidate and extendmanagement standards. Some of thesemanagement standards includeSimple Network Management Protocol (SNMP) and DesktopManagement Interface (DMI).
Web-Based Enterprise Management (WBEM)Web-Based EnterpriseManagement (WBEM) is a set of management and Internet standardtechnologies developed to unify themanagement of enterprise computing environments. TheDistributedManagement Task Force (DMTF) has developed a core set of standards that make upWBEM. The core set includes a datamodel, the CIM standard, an encoding specification, xmlCIMencoding specification, and a transport mechanism, (CIM Operations over HTTP).
Windows Management Instrumentation (WMI)Windows Management Instrumentation (WMI) is theMicrosoft implementation of theWeb-BasedEnterpriseManagement (WBEM) that supports the CIMmodel as well as Microsoft-specificextensions of CIM. To put it simply, it is a set of services designed to input data into a repositoryusingWBEM providers.
TheWMI repository is a central storage area designed to holdmanaged information. It is organizedby a series of schemas that are loaded into namespaces. A namespace provides a container, ordomain, for the instances of the classes in that schema.
Note: For the purpose of this document, when we refer toWBEM, this includes WMI.
Radia Client Automation Enterprise Inventory Manager (9.00)Page 9 of 90
Reference GuideChapter 1: Introduction
Client Automation and WBEMThe Inventory Management agent queries theWBEM namespace (that is, theWBEM database)and sends the results back to the Configuration Server. All information collected by WBEM isavailable to the Inventory Manager agent. The collected information is then stored in the ODBCinventory database.
For agent computers withWBEM (Web-Based EnterpriseManagement) installed, the InventoryManager executes an HP-proprietary method (RIMWBEM) to query theWBEM namespace.
For agent computers that do not haveWBEM installed, the Inventory Manager executes HPproprietary methods to directly inspect the hardware (built into the Client Automation agent –ZCONFIG) and/or the file system (RIMSFSCAN).
Caution: Inventory Manager forWindow leverages Microsoft's Windows ManagementInstrumentation (WMI) to collect hardware and software inventory data by usingWMI queries.SomeWMI queries can traverse the network contacting other servers in the enterprise tocollect the requested information. This may result in large volumes of data being returned, andcould have a significantly negative effect on network performance. An example of this wouldbe querying all users on the network using theW32_UserAccount WMI class. Extremecautionmust be taken to understand the scope of these queries to ensure unexpected resultsdo not occur. While Inventory Manager provides an interface toWMI and its providers, itcannot control how these queries are satisfied. It is the customer’s responsibility to safeguardagainst usingWMI queries that span the network, if this behavior is not as expected.
Radia Client Automation Enterprise Inventory Manager (9.00)Page 10 of 90
Chapter 2
The AUDIT DomainThis manual is provided to assist you with installing and using the Inventory Manager. Choose theappropriate strategies suited for your enterprise needs.
The AUDIT Domain in the CSDBThe AUDIT Domain is located in the PRIMARY File of the CSDB. The AUDIT Domain contains theclasses required to:
l Configure the tasks needed to collect the inventory information.
l Manage the agent computers' assets.
AUDIT Domain DefinedThe AUDIT Domain is structured very much like the SOFTWARE Domain. The figure below showsits tree structure in the CSDB Editor.
Radia Client Automation Enterprise Inventory Manager (9.00)Page 11 of 90
Reference GuideChapter 2: The AUDIT Domain
Table below describes the classes in the AUDIT Domain.
Class Description
Application(ZSERVICE)
These are sample services distributed with the Inventory Manager. TheAUDIT.ZSERVICE instance is connected to a policy instance. A policy instancecan be an instance of the Users, Departments, orWorkgroups class. It can alsobe a customer-defined class within the POLICY Domain. Each of the sampleZSERVICE classes is connected to the PACKAGE instances.
AuditPackages(PACKAGE)
Defines what information to collect, and then what actions to take. Thesepackages would contain various audit components. A good example is an auditof running services on a desktop. The AUDIT.ZSERVICE instancemust containa connection to an AUDIT.PACKAGE instance.
BehaviorServices(BEHAVIOR)
Defines instances that enable the execution of auditing on the agent. Normally,there is no need to add or modify instances in this class.
ClientMethods(CMETHOD)
This class is used to configuremethod points for Tcl inventory scans. The baseinstance of the SCANNER Class is connected to the CMETHOD.INV_FULLinstance. This instance can be used for all inventory scans defined in theSCANNER Class.
Desktop(DESKTOP)
This class is reserved for future use.
AUDIT Domain
Radia Client Automation Enterprise Inventory Manager (9.00)Page 12 of 90
Reference GuideChapter 2: The AUDIT Domain
Class Description
File (FILE) Defines file scans, such as auditing system DLLs.
File Scanner(FILESCAN)
For UNIX® devices only, persistent component class used to configure aninventory scan. Adding File Scanner components to an audit package createsinstances of the FILESCAN Class.
File ScannerFilters(FILTER)
For UNIX devices only, persistent component class used to configure aninventory scan. Adding FILE Scanner Filters components to an audit packagecreates instances of the FILTER Class.
InventoryOptions(RIMOPTS)
Contains the attributes that offer options that control an inventory managementtask. For additional information, see the section "RIMOPTS Class" below.
InventoryScanners(SCANNER)
This persistent component class is used to configure an inventory scan. Createinstances of the SCANNER Class by adding Inventory Scanners components toan audit package.
Path (PATH) This class stores the drive and directory required to install a resource. Packagescan be relocated by updating instances of this class.
Registry(REGISTRY)
This class uses WMI to obtain a Registry scan of aWindows machine. Createinstances of the REGISTRY Class to run scans of theWindows Registry andobtain a Registry Scan report.
Scheduling(TIMER)
This class contains the instances that enable the CM administrator to set a timeron end users' computers. One or multiple auditing services can be processedwhenever the timer expires.
Virtual MgrLocation(MGRVLOC)
This class is used to specify the initial path for files being transferred to theConfiguration Server during a FILE audit.
WBEM(WBEM)
This class contains instances that define Inventory Manager scans of WMIclasses. These can include any class in theWMI database such as Win32_Services.
RIMOPTS ClassThe RIMOPTS Class is also known as the Inventory Options Class. This class contains theattributes that control an inventory management task. Table below describes these attributes.
Attribute Usage
COLLECT Audit Collection Type by selectingDiff or Full.l Select Diff to report the difference between the previous information collected
for the service and the information collected during the current agent audit. Thisis the default setting.
RIMOPTS Class
Radia Client Automation Enterprise Inventory Manager (9.00)Page 13 of 90
Reference GuideChapter 2: The AUDIT Domain
Attribute Usage
Note: The first or initial scan of the DIFF setting will be a FULL scan asdefined below. All subsequent scans will then be differenced unless theadministrator changes the setting to FULL.
l Select Full to report the information collected for the service during the currentagent connect process without differencing against the previous collection forthat service.
RUNEXEC This string indicates what actions the Inventory Manager will take on connection:l Select I to invoke collection of information when the service is installed
l Select U to invoke collection of information when the service is updated.
l Select V to invoke collection of information when the service is verified.The default settings are I andU.
ZSVCTYPE Contains code that is used internally by the Inventory Manager agent. In all cases,this value should remain I.
NAME Contains the friendly name of the instance. It is the name displayed for theinstance in the tree view of the CSDB Editor.
To apply an option expressed in the RIMOPTS instance to the inventory management task, theRIMOPTS instancemust contain a connection to an audit service.
Before beginning any tasks using the Inventory Manager, youmust enable the drag-and-dropfeature for the newly created RIMOPTS Class instances. For additional information about editinginstances, see theRadia Client Automation Enterprise Administrator User Guide.
To Enable Drag-and-Drop Connections for RIMOPTS Class Instances:
1. Open the Admin CSDB Editor and go toPRIMARY > ADMIN > Name Lists (8) (ZLIST) >CONNECT_ > CONNECT_ZSERVICE_
Radia Client Automation Enterprise Inventory Manager (9.00)Page 14 of 90
Reference GuideChapter 2: The AUDIT Domain
2. Double-click onCONNECT_ZSERVICE_TO_RULES.
3. The Editing Instance dialog box opens.
4. Set the value of the ZNAME n attribute toRIMOPTS.
The drag-and-drop feature is now available for all attributes in RIMOPTS.
REGISTRY ClassThe Registry Class uses WMI to obtain a Registry scan of aWindows machine. Most of theattributes are copied from the existingWBEM class of the AUDIT Domain, with descriptionsadjusted for registry-specific needs. For example, the PROPERTY and CNDITION attributesdefine the current Registry hive and subkey to scan, respectively. Three new Registry-specificattributes have been added to the class. They include:
l RPTCLASS – The Report Class Name in RIM.
l FORMAT – TheOutput format- requires REGISTRY (do not change).
l DEPTH – Defines the levels below the current subkey to scan.
Radia Client Automation Enterprise Inventory Manager (9.00)Page 15 of 90
Reference GuideChapter 2: The AUDIT Domain
Table below summarizes the attributes and values for the Registry Class instances. Attributes inbold are new to this class (not in theWBEM class).
Attribute Description Default Value Valid Values
ACTION Report Flags (I, N, C, D,S, D, C)
YYYYXXN Y, X, or N for eachflag.
NAMSPACE NameSpace root\default root\default – Donot change.
CLASS WBEMClass StdRegProv StdRegProv – Donot change.
RPTCLASS Report Class Name Registry A valid table name.If blank“StdRegProv” willbe used.
PROPERTY Registry hive HKEY_LOCAL_MACHINE Any Windowsregistry hive:HKEY_CLASSES_ROOTHKEY_CURRENT_USERHKEY_LOCAL_MACHINEHKEY_USERSHKEY_CURRENT_CONFIGHKEY_DYN_DATA
CNDITION Registry subkey SOFTWARE\Microsoft\InternetExplorer
Any Windowsregistry subkey.
FORMAT Output format REGISTRY REGISTRY –Donot change.
DEPTH Starting at the registrysubkey named in theCNDITION attribute,depth specifies thenumber of descendentkey levels to include inthe scan.
0 0, -1, or nSet to 0 to onlyscan currentsubkey.
Set to -1 to scanall subkey levels.
Set from 1 throughn to scan thecurrent subkey andthe specifiednumber of subkeylevels deep.
Registry Class Instance Attributes
Radia Client Automation Enterprise Inventory Manager (9.00)Page 16 of 90
Reference GuideChapter 2: The AUDIT Domain
Attribute Description Default Value Valid Values
OUTPUT Output Object Name WBEMAUDT WBEMAUDT
TYPE Scan Type (WBEM) WBEM WBEM –Do notchange.
NAME Friendly Name Default Friendly name forthis instancedisplayed in theAdmin CSDBEditor.
Implementing Registry ScansUse the following high-level procedures to create and run scans of theWindows Registry using theREGISTRY class in the AUDIT Domain.
1. Create an AUDIT.PACKAGE instance for the registry scan.
2. Right-click on the newly created AUDIT.PACKAGE instance and select Add Componentfrom the shortcut-menu.
3. Use the Add Component dialog to both create and edit a new AUDIT.REGISTRY instance is afew steps:a. Use theAvailable Components drop-down list to select Registry.
b. In theNew Component Name box, type an instance name for the new registry scan.
c. Click Add + Edit.
d. Use the Edit instance dialog tomodify the attributes, as necessary. The PROPERTY,CNDITION and DEPTH attributes define the hive, registry subkey and depth of the scan,respectively.
e. Click OK to save your changes.
The registry scan instance is automatically created and attached to the audit package.
4. Connect the audit package to an audit service.
5. Entitle the audit service for the registry scan to the appropriate machines or users.The registry scan service is deployed during the first connection to an entitled agent. During thenext connection, the registry scan inventory is collected and passed to theMessaging Server,which posts it to the ODBC database for inventory.
6. See the Registry Scan report from the Reporting Server.
Inventory Database TablesThe inventory reporting database includes the tables shown in the following figure, among others.
Radia Client Automation Enterprise Inventory Manager (9.00)Page 17 of 90
Reference GuideChapter 2: The AUDIT Domain
Standard Inventory Database – Tables
The table names denote the origin of the data that they contain. For example, the rWin_LogicalMemoryConf table will be populated with data from theWin32_LogicalMemoryConfiguration WBEM class.
Tables that begin with rWin32_ are populated with the data fromWBEM queries. Tables that do notstart with rWin32_ are populated with data from non-WBEM sources.
The recommended product for viewing Inventory is the Reporting Server. See theRadia ClientAutomation Enterprise Reporting Server ReferenceGuide for more information.
Radia Client Automation Enterprise Inventory Manager (9.00)Page 18 of 90
Chapter 3
Software and Hardware AuditingThis guide is provided to assist you with installing and implementing the Inventory Manager.Choose the appropriate strategies suited for your enterprise needs.
Auditing TypesWhen configuring your audits, it is beneficial for the administrator to understand exactly what typesof things can be audited and what the expected results from an audit will be.
The Inventory Manager allows for three types of audits:
l File auditing
l WBEM auditing
l Hardware auditing
File AuditingThe AUDIT.FILE Class instances in an audit package control the auditing function for files on theagent computer. The RIMFSCAN and the RIMDIFF methods on the agent computer perform theactual file auditing operations by specifying what files to look for. There can be one or moreAUDIT.FILE instances in an audit package. Each AUDIT.FILE instance can specify a scan for oneor more files.
See "Audit Scanning Processes" on page 37 for additional information on the RIMFSCAN and theRIMDIFF methods.
The following table summarizes the attributes in an AUDIT.FILE class instance and their effects onthe RIMFSCAN method.
Attribute Description and Examples
SCANFOR Indicate a fully qualified path and file name to search for. Wildcards arepermitted. <SystemDrive:>\WinNt\*\*.dll
ACTION TheRIMDIFF method performs actions on the files discovered on the user'scomputer during the agent connect.l Y configures RIMDIFF to perform the action.
l N configures RIMDIFF to not perform the action.The first four flags determinewhen to report that the files were found: Report on:Initial, New, Changed, Deletedl Initialmeans that the file was found during the first scan of the agent
computer.
l Newmeans that the file was found during the current scan. The file was notpresent during the previous scan.
l Changedmeans that the file was present during the previous scan and isdifferent from the file found during the current scan.
l Deletedmeans that the file was found during the previous scan. The file isnot present for the current scan.
The last three flags control the actions to take on the files detected during thecurrent scan. Action to take on discovery: Send, Delete, Custom
AUDIT.FILE Class Instances
Radia Client Automation Enterprise Inventory Manager (9.00)Page 19 of 90
Reference GuideChapter 3: Software and Hardware Auditing
Attribute Description and Examples
l Sendmeans to send the files to the Configuration Server and store them inthe location indicated by the ZRSCVLOC attribute (see "ZRSCVLOC "below).
l Deletemeans to delete the files from the user's computer.
l Custommeans to execute themethod indicated in the CUSTOM attribute.YYYYNYN –Report whenever encountered and delete the files. NNYYNNN –Report when changed or deleted and take no action. NYYNYYN –Report whenthe files are new or changed. Then send and delete the files.
OUTPUT Output object name.
TYPE Scan different file locations. Available scans are Behavior Services, Desktop,File, Path, Registry, andWBEM. File.
GROUP Optional way to identify a set of scan results. This maybe useful for querying andreporting on the audited files from the database where audit results can bestored. Games, MPEGs.
ZVERINFO Collect extended information.l Set the value to 1 to collect additional information for a file.
l Set the value to 0 to not collect additional information.In order for this data to be collected, the associated attributemust exist in theAUDIT.FILE class template. You can limit the scan to only those files that havesome particular values in their extended information. You do so by supplying avalue (either 1 or 0) for any of the associated attributes in an AUDIT.FILEinstance. This causes the scan to be filtered. Only those files whose extendedinformation data element contains the value you specify in its associatedattribute will be scanned. Extended file information consists of one oremore ofthe following data elements. The associated attribute name for the data elementis in parentheses:l (VENDOR) – The seller of the file/product
l (PRODUCT) – The name of the item for which the file is a part.
l (PRODVERS) – The version of the product which the file is a part.
l (ORGNAME) – The name of the organization.
l (INTERNAL) – The internal data element encoded in the file.
l (VERSION) – The version of the file.
l (LANGUAGE) – The language of the file.
ZRSCSTYP Server file type. This can be either Binary or Text. The administrator does not setthis.
ZRSCMFIL Manager directory location.
ZRSCVLOC The location on the Configuration Server where the files are stored because ofthe Send Action (see "ACTION " on previous page). This variable needs to be
Radia Client Automation Enterprise Inventory Manager (9.00)Page 20 of 90
Reference GuideChapter 3: Software and Hardware Auditing
Attribute Description and Examples
configured when sending a file back to the Configuration Server. The variableshould contain the name of theMGRVLOC instance that will be used to resolvethe location to store the uploaded file.<SystemDrive:>\Data\&(ZOBJPID)\&(name)
ZRSCMMEM PDS member name. This field is optional.
PRODUCT The product name. See "ZVERINFO " on previous page for more detail.
PRODVERS The product version. See "ZVERINFO " on previous page for more detail.
ORGNAME The organization name. See "ZVERINFO " on previous page for more detail.
INTERNAL The internal data element encoded in the file. See "ZVERINFO " on previouspage for more detail.
VERSION The version of the file. See "ZVERINFO " on previous page for more detail.
LANGUAGE The language of the file. See "ZVERINFO " on previous page for more detail.
VENDOR The product vendor. See "ZVERINFO " on previous page for more detail.
ZRSCCRC Resource CRC.
ZCRCINFO Collect file CRC. [Y/N] Default is N.l Set the value toY to collect CRC information for a file.
l Set the value toN to not collect CRC information.
l If blank, defaults toN.Caution: Collecting file CRC information can dramatically extend the time ittakes to collect information on the target machine.
ZMD5INFO Collect file MD5 information. [Y/N] MD5 information is a 32-character value thatcan be used to uniquely identify a file based on its content. Default is N.l Set the value toY to collect MD5 information for a file.
l Set the value toN to not collect MD5 information.
l If blank, defaults toN.
Caution: CollectingMD5 information can dramatically extend the time ittakes to collect information on the target machine.
ZRSCOBJN Persistent object name.
ZRSCPADM Administrator ID.
ZRSCSRC Resource Source, that is, Publisher.
ZINIT Not applicable at this time.
Radia Client Automation Enterprise Inventory Manager (9.00)Page 21 of 90
Reference GuideChapter 3: Software and Hardware Auditing
Attribute Description and Examples
NAME Not applicable at this time.
LOCATION Not applicable at this time.
Use the Agent Explorer to See the FILEAUDT object results as shown in following figure.
FILEAUDT Object
The FILEAUDT object contains one heap for each file discovered during the scan for the auditservice. It contains the attributes from the AUDIT.FILE class instance that controlled the scan, asdescribed above. It also contains the following attributes:
Attribute Description
ACCESSDT The date of themost recent access of this file.
ACCESSTM The time of themost recent access of this file.
ATRIBUTE A string listing the attributes of the file: R = Read only A = Archive S = System H= Hidden C = Compressed
FILEAUDT Object
Radia Client Automation Enterprise Inventory Manager (9.00)Page 22 of 90
Reference GuideChapter 3: Software and Hardware Auditing
Attribute Description
DATE The date of themost recent modification to this file.
DIRPATH The directory path of the file.
DRIVE The system drive location of the file.
FULLPATH Fully qualified path and file name of the file.
PATHCRC A unique number that indicates the CRC path used for differencing.
RESOLVE The value of M indicates that the Configuration Server resolves each heap of theFILEAUDT object individually. This value cannot bemodified.
SIZE File size in bytes.
STATUS Indicates the status of the file on the agent computer. Possible values are:l Existsmeans that this is the first time scanning for this file and it was found.
l Newmeans that this file was added to the file system of the agent computersince the last scan was performed.
l Updatemeans that this file exists in the new and previous scans. There havebeen changes to the date, time, size, and/or version.
l Deletedmeans that this file was present in the previous scan but is missing inthe new scan.
l Not foundmeans that no files were found that matched this request.
TIME The time of themost recent modification to this file.
XTENSION The file extension. This is useful for sorting and querying back-end databasetables that store the data found in this object.
WBEM AuditingUse the RIMWBEMmethod to query theWBEM namespaces to retrieve information about how asystem's hardware and software is used. The RIMWBEMmethod constructs a query from theinformation contained in an instance of the AUDIT.WBEM class. WBEM has a query engine thatprocesses the query statement and returns the query results to RIMWBEM. There is one heap inthe query result object for every discovered instance.
Caution: Inventory Manager leverages Microsoft's Windows Management Instrumentation(WMI) to collect hardware and software inventory data by usingWMI queries. SomeWMIqueries can traverse the network contacting other servers in the enterprise to collect therequested information. This may result in large volumes of data being returned, and could havea significantly negative effect on network performance. An example of this would be queryingall users on the network using theW32_UserAccount WMI class. Extreme cautionmust betaken to understand the scope of these queries to ensure unexpected results do not occur.While Inventory Manager provides an interface toWMI and its providers, it cannot control howthese queries are satisfied. It is the customer’s responsibility to safeguard against usingWMI
Radia Client Automation Enterprise Inventory Manager (9.00)Page 23 of 90
Reference GuideChapter 3: Software and Hardware Auditing
queries that span the network, if this behavior is not as expected.
An AUDIT.WBEM class instance defines a query into theWBEM namespace.
AUDIT.WBEM class instances
Following table describes the attributes of the AUDIT.WBEM instance.
AttributeName Description
ACTION TheRIMDIFF method performs actions on theWBEM namespaces (s)instances discovered on the user's computer during the agent connect.l Y configures RIMDIFF to perform the reporting action.
l N configures RIMDIFF to not perform the reporting action.The first four flags determinewhen to report that theWBEM namespaceinstance was found: Report on: Initial, New, Changed, Deleted, Scan, Delete,Customl Initialmeans that the file was found during the first scan of the agent
computer.
l Newmeans that the file was found during the current scan. The file was notpresent during the previous scan.
l Changedmeans that the file was present during the previous scan and isdifferent from the file found during the current scan.
l Deletedmeans that the file was found during the previous scan. The file is
AUDIT.WBEM Instance
Radia Client Automation Enterprise Inventory Manager (9.00)Page 24 of 90
Reference GuideChapter 3: Software and Hardware Auditing
AttributeName Description
not present for the current scan.
l Scanmeans that the file was found during the current scan.
l Deletemeans that the file was found during the previous scan. The file is notpresent for the current scan.
l Custommeans that the file was found during a custom scan.The last three flags are not applicable toWBEM audits.
NAMESPACE The name of theWBEM namespace to query or HARDWARE.
CLASS The name of theWBEM class to query or HARDWARE.
PROPERTY Specify one or more property names to be queried and reported. Use commasto separatemore than one property name. If this attribute is blank, all propertiesin the class will be queried and reported.
CNDITION An optional condition to narrow results of an audit.
OUTPUT This is the name of the object to send to the Configuration Server.
TYPE Indicates that WBEM scan is to be employed for this audit package.
NAME Friendly name for this instance. This namewill appear in the CSDB Editor's treeview to identify this instance.
Note:When the keywordHARDWARE is used in theNAMESPACE and/orCLASSattributes of AUDIT.WBEM, hardware information is collected. This information is essentiallythe same as the ZCONFIG object.
The Inventory Manager agent stores the results of aWBEM scan in aWBEM object. This objectcan be found in the service node of the agent object tree. The results are also sent to theConfiguration Server.
In addition to the attributes described in "WBEM Auditing" on page 23, theWBEM object alsocontains the following:
Attribute Description
ZOBJCID Object child ID.
ZOBJCLAS The targeted class for the audit such as ZRSOURCE or ZSERVICE.
ZOBJCRC TheCRC of all persistent and transient objects under the current node.
ZOBJDATE The last date under the current node.
ZOBJDOMN The domain name of the object.
WBEM Object Attributes in the Agent
Radia Client Automation Enterprise Inventory Manager (9.00)Page 25 of 90
Reference GuideChapter 3: Software and Hardware Auditing
Attribute Description
ZOBJID The object ID of the instance used to obtain information from the Resource file.
ZOBJNAME The instance name of the object.
ZOBJPCLS The parent class name.
ZOBJPID The parent class ID.
ZOBJRCRC The resource CRC maintained by the Configuration Server.
ZOBJRSIZ The resource sizemaintained by the Configuration Server.
ZOBJTIME The latest time under the current node.
ZRSCSRC The name of the program promoted the resource.
WBEM Object ProcessingWhen the Inventory Manager agent sends aWBEMAUDT object to the Configuration Server,processing is defined as follows:
1. At the end of the agent connect, the ZTASKEND REXX method on the Configuration Server iscalled and creates commands to invoke the QMSG executable.
2. QMSG.EXE places theWBEMAUDT objects into the Configuration Server \data\wbemdirectory, or message queue.
3. TheMessaging Server includes aWBEMData Delivery Agent (WBEM.DDA) that monitorsthis \data\wbemmessage queue and processes theWBEM objects.
4. TheWBEM.DDA is usually configured to post theWBEM objects directly to anODBC-compliant Inventory Manager database, or, it may be configured to first forward theWBEMobjects to another Messaging Server located closer to the database. In the later case, thereceivingMessaging Server posts theWBEM data to the Inventory ODBC-compliantdatabase.
5. After it is posted to the Inventory Manager database, the new WBEM information isimmediately available for query and reporting purposes through the Reporting Server.
For more information, see theRadia Client Automation EnterpriseMessaging Server ReferenceGuide.
Disabling Remnant Configuration Server Instances forWBEM Object Processing
Inventory Manager no longer supports processingWBEM objects using these instances in theCSDB:
l SYSTEM.PROCESS.WBEMAUDT
l SYSTEM.ZMETHOD.POST_WBEM
Radia Client Automation Enterprise Inventory Manager (9.00)Page 26 of 90
Reference GuideChapter 3: Software and Hardware Auditing
If these remnant instances exist or were imported into your CSDB, youmust disable anyconfigurations within them to ensure successful WBEM object processing.
Edit SYSTEM.PROCESS.WBEMAUDT and remove any connection to theSYSTEM.ZMETHOD.POST_WBEM instance.
Hardware AuditingEach time a Client Automation agent connects to the Configuration Server, information about theagent's hardware configuration is stored in the ZCONFIG object. The ZCONFIG object iscalculated and stored in the application service directory of the Client Automation agent's objectdirectory tree as follows:
ZCONFIG Object
A separate ZCONFIG object is calculated and stored for each service installed or updated duringthe agent connect. To force the transfer of the hardware information, the ZCONFIG attributemustbe set to Y in the POLICY.USER class.
POLICY.USER Class – ZCONFIG Attribute
The ZCONFIG object contains a wealth of information about the agent computer's hardware.
Radia Client Automation Enterprise Inventory Manager (9.00)Page 27 of 90
Reference GuideChapter 3: Software and Hardware Auditing
ZCONFIG Object
The ZCONFIG object stores hardware information discovered by the Client Automation agent'sstandard hardware auditingmethod. Certain types of hardware can occur multiple times. TheZCONFIG object automatically extends to allow additional information to be stored.
The following table describes the attributes that are stored in the ZCONFIG object.
Attribute Description
GATEWAY Router for your subnet.
HALCOMP Company of HAL.DLL
HALDATE Date and time of HAL.DLL
HALFNAME Original name of HAL.DLL
HALFVER Internal version of HAL.DLL
HALINAME Name of HAL.DLL
ZCONFIG Object
Radia Client Automation Enterprise Inventory Manager (9.00)Page 28 of 90
Reference GuideChapter 3: Software and Hardware Auditing
Attribute Description
HALLANG Language of HAL.DLL
HALPNAME Product name of HAL.DLL
HALPVER Product version of HAL.DLL
HALSIZE Size of HAL.DLL
IPADDR## IP address of network adapter (there can bemultiple addresses)
LADAPT## Network card (there can bemultiple network cards)
REBOOTD Last reboot date
REBOOTT Last reboot time
SUBNET## Subnet mask.
ZGATEWAY Looks at GATEWAY attribute
ZHDWBIOS BIOS type.
ZHDWCDDR Client Automation agent's CD-ROM drive letter
ZHDWCOMP Computer name
ZHDWCPU Current CPU type
ZHDWFPU Current FPU type
ZHDWIPAD The IP address of the computer
ZHDWKYBD Keyboard type
ZHDWLANA LAN adapter
ZHDWLANG Language setting
ZHDWMEM Total physical memory (RAM)
ZHDWMEMF Total freememory (RAM)
ZHDWMOUS Mouse type
ZHDWNET# Network card information (can bemultiple cards)
ZHDWNNET Number of network cards
ZHDWOS Computer's operating system and version
ZHDWOSCL Operation system classification (Workstation or Server)
ZHDWOSDB Operating system's build number
ZHDWOSOG Organization
Radia Client Automation Enterprise Inventory Manager (9.00)Page 29 of 90
Reference GuideChapter 3: Software and Hardware Auditing
Attribute Description
ZHDWOSOW Owner
ZHDWOSSR Windows 9x Sub-Version Number (i.e., A, B, C)
ZHDWPA## Printer information
ZHDWPPAR Number of parallel ports
ZHDWPPRN Number of printers available
ZHDWPSER Number of serial ports
ZHDWVIDO Video type
ZHDWVMSI MSI Version
ZHDWVRES Video resolution
ZHDWXPAG Page size
ZHWCPU01 CPU type
ZHWFPU01 FPU type
ZMODEM Modem present? Y or N
ZOBJDATE The date of the Client Automation agent connect for this service
ZOBJNAME HARDWARE_SCAN (hard coded)
ZOBJTIME The time of the agent connect
ZSUBNET The subnet mask
ZUSERID The name of the user who connected
Whenever a Client Automation agent connects to the Configuration Server, certain hardwareinformation about the subscriber is automatically forwarded to the Inventory Manager ODBCdatabase as part of theMessaging Server processing of CORE objects. The hardware informationis visible through the Reporting Server.
Radia Client Automation Enterprise Inventory Manager (9.00)Page 30 of 90
Chapter 4
Successful AuditingThis manual is provided to assist you with implementing and using the Inventory Manager. Choosethe appropriate strategies suited for your enterprise needs.
Sample AuditingTo illustrate the concepts of inventory information collection, the Inventory Manager installationcontains a set of representative audit service examples. These samples are located in thePRIMARY.AUDIT.Application (ZSERVICE) class as follows:
Sample Auditing Services
Radia Client Automation Enterprise Inventory Manager (9.00)Page 31 of 90
Reference GuideChapter 4: Successful Auditing
These sample services represent common scenarios for inventory collection andmanagement. Thebest way to develop your own audit services is to study the samples that were installed with theInventory Manager upgrade.
The sample audit services are described in the following table:
Service
Connectedto AuditPackage(PACKAGE)
Description
_BASE_INSTANCE_
This service instance is the base instance for the AuditApplication (ZSERVICE) class.
Audit MultiFiles
Audit to findand CaptureMultipleFiles
This service scans for a file name or pattern and reports thatinformation back to the administrator.
CE PDAXMLInventory
CE PDAXMLInventory
This service scans for and reports back information on installedWindows CE PDA devices. Will only report back if a device isfound.
DeleteDiscoveredApplicationComponent
Audit to Findand RemoveLocal File
This service looks for a specific file on the user's computer. If it isfound, it will be deleted.
IndividualFile Audit
Audit to Findand CaptureLocal File
This service performs an NVDM scan of the user's computer for aspecified file of an instance of the AUDIT.FILE classes.
NVDMDiscovery ofApplications
NVDMDiscovery ofApplications
Used to discover software applications that are installed on aClient Automation agent machine.
Palm PDAXMLInventory
Palm PDAXMLInventory
This service scans for and reports back information on installedPalm PDA devices. Will only report back if a device is found.
RIMReporting
RIMReporting
This service performs a scan of a systems Win32 devices suchas: Bios, Computer System, environment, keyboard, logical disk,logical memory configuration, network adapter, operating system,pointing device, printer, processor product, serial port, service,software element, and video controller.
Note: This is a very large scan andmay take severalminutes to complete.
Sample of Auditing Services
Radia Client Automation Enterprise Inventory Manager (9.00)Page 32 of 90
Reference GuideChapter 4: Successful Auditing
Service
Connectedto AuditPackage(PACKAGE)
Description
Unix FileScan Audit
UNIX FileScan Audit
This service performs a NVDM scan of the user's computer for aspecified file of an instance of the AUDIT.FILE classes on UNIXplatforms.
UnixHardwareInventory
UnixHardwareInventory
This service scans for and reports on a user's hardware on UNIXcomputers.
UnixSoftwareInventory
UnixSoftwareAudit
This service performs an audit to find UNIX-based software.
WBEMMSIBasedApplications
WBEM ScanforWindowsInstallerApplications
This service performs aWBEM scan of the user's computer forcomponents registered in theWMI database that have beeninstalled by Microsoft Windows Installer.
WBEMRunningServices
WBEM Scanfor RunningServices
This service scans the user's computer for system services thatare running at the time of the scan.
WBEM Scanfor Hardware
WBEM Scanfor SystemSoftware
This service scans for and reports on a user's hardware.
WBEM ScanwithConditionStatement
WBEM ScanwithConditionStatement
This service performs scans based on a conditional statement setin the CONDITION attribute.
WBEMStoppedServices
WBEM ScanforSTOPPEDServices
This service scans the user's computer for system services thatare stopped at the time of the scan.
WBEMSystemDrivers
WBEM ScanforWindowsSystemDrivers
This service scans the user's computer forWin 32 systemdrivers.
WBEMWindowsServices
WBEM ScanforWindowsServices
This service scans for and reports onWindows Services.
WindowsSystem DLL
AuditSystem DLL
This service scans for system DLLs and reports on them.
Radia Client Automation Enterprise Inventory Manager (9.00)Page 33 of 90
Reference GuideChapter 4: Successful Auditing
Configuring a Sample AuditAll of the examples presented can be configured for individuals, departments, work-groups, and soforth. See theRadia Client Automation Enterprise Administrator User Guide for additionalinformation onmanipulating the database components.
For documentation purposes, we will configure the sample audit service Audit Multi Files. The filetype wewill be auditing is indicated in the SCANFOR attribute within the instance. This instancedirects the Inventory Manager agent to scan for any *:\program files\*\*.exe files on theagent computer. The ACTION attribute indicates that the discovery of the file will be reported andsent to the Configuration Server for storage.
SCANFOR Attribute of the Audit Multi Files Instance
ToConfigure a Sample Audit Package:
1. If you have not already done so, start the CSDB Editor.
2. Navigate to and expand the PRIMARY.AUDIT Domain.
Radia Client Automation Enterprise Inventory Manager (9.00)Page 34 of 90
Reference GuideChapter 4: Successful Auditing
3. Double-click Application (ZSERVICE) to expand the class.
4. Scroll to and expand thePOLICY Domain.For our example, we would like all users that aremembers of theWorkgroup class to selectthis audit package from their Application Self-ServiceManager.
5. Expand the POLICY.WORKGROUPS class.
6. Select theAudit Multi Files package from the ZSERVICE class and drag it to thePOLICY.WORKGROUPS class and drop it on theDefault instance.
Radia Client Automation Enterprise Inventory Manager (9.00)Page 35 of 90
Reference GuideChapter 4: Successful Auditing
The Select Connections Attribute window opens.
7. Click Copy to add this package. The Confirm Connection dialog box opens.
8. Click Yes to confirm the connection. The Audit Multi Files package is added toWORKGRPClass.
The collection of inventory information occurs on the Inventory Manager agent computer when auser connects to the Configuration Server as follows:
Radia Client Automation Enterprise Inventory Manager (9.00)Page 36 of 90
Reference GuideChapter 4: Successful Auditing
l Through an Application Self-ServiceManager agent connect, when the user launches thatprogram.or
l Through the ApplicationManager agent when the user double-clicks theConnect icon on hisdesktop, or is scheduled or notified to connect.
The following figure shows the available Audit Multi Files package that an Application Self-ServiceManager user would see when connecting to the Configuration Server:
Application Self-Service Manager shows Audit Multi Files
When the subscriber selects and installs the Audit Multi Files package from the Application Self-ServiceManager, there are really two connections. The first connection downloads the Auditservice. The second connection sends the audit results back to the Configuration Server. The audit-related scans are done between the two connections.
Note: Some scans may take several minutes to complete. This is a normal behavior of theaudit scanning process.
Audit Scanning ProcessesUse the Agent Explorer to locate the ZSERVICE for the Audit Multi Files package in the LIBdirectory.
AUDIT_MULTI_FILES in the LIB Directory
Within the ZSERVICE, note the two objects, FILEAUDT and FILEPREV. These objects arecreated and stored in the ZSERVICE of the LIB directory whenever an audit package is installed.The FILEAUDT object contains one heap for each file discovered during the auditing scan. It alsocontains the attributes from the AUDIT.FILE instance that controlled the scan.
Radia Client Automation Enterprise Inventory Manager (9.00)Page 37 of 90
Reference GuideChapter 4: Successful Auditing
The AUDIT.FILE class instances in an audit package control the auditing for files on the agentcomputer. The RIMFSCAN and the RIMDIFF methods on the agent computer perform the actualfile auditing operations by specifying what files to look for.
Auditing with the RIMFSCAN and RIMDIFF Methods
l The RIMFSCAN method scans the Client Automation agent's file system based on the valuesin the AUDIT.FILE class instance in the audit package. It constructs an object namedFILENEW. The FILENEW object contains one heap per file discovered during the current scan.
l The RIMDIFF method compares scan results from the current scan (the scan done during thecurrent agent connect stored in the FILENEW object) with scan results from a previous scan(the scan done during a previous agent connect process stored in the FILEPREV object). It willconstruct the FILEAUDT object that is then sent to the Configuration Server. The RIMDIFFmethod then deletes the FILEPREV object and will rename the FILENEW object to FILEPREV.
For our particular example, there were 486 instances for both the FILEAUDT and the FILEPREVobject located on the Client Automation agent's computer.
Radia Client Automation Enterprise Inventory Manager (9.00)Page 38 of 90
Chapter 5
Creating Audit PackagesAudit Packages or PACKAGE Class
Once you are comfortable auditing using the sample packages provided by HP, you will probablywant to take the next step in designing your own audit packages.
By expanding the Audit Packages (PACKAGE) class, you will see the audit package instances.
Audit Package (PACKAGE) Class
A complete audit service consists of several connected instances in the AUDIT Domain. The auditpackage instance is a container that "owns" the instances connected to it. For example, open theAUDIT.ZSERVICE class and double-click the Individual File Audit instance.
Radia Client Automation Enterprise Inventory Manager (9.00)Page 39 of 90
Reference GuideChapter 5: Creating Audit Packages
Individual File Audit Instance
In the example, the Individual File Audit ZSERVICE instance "owns" the Audit to Find and Capturea Local File instance. The fact that a package instance owns a component class instancemeansthat all of the instances aremanaged as a package unit. If the package instance is deleted, all of itsowned class instances are automatically deleted as well.
Caution: Sound databasemanagement practices dictate that the component class instancesowned by a package are not connected to any other package instance.
The audit service instancemust also contain a connection to an instance of the RIMOPTS Class.Connecting an instance of the RIMOPTS Class to an audit service instance causes the expressedbehavior to be performed. Specified behaviors are listed in the following table.
Instance Description
Default Contains the base instance attributes for the RIMOPTS Class.l Collect attribute is set to Diff.
l Runexec attribute is set to IU.
l ZSVCTYPE attribute is set to I.
Differenced Audit onInstall and Update
When connected to an audit service will difference the auditedinformation on installation and when the audited target is updated.l Collect attribute is set to Diff.
l Runexec attribute is set to IU.
l ZSVCTYPE attribute is set to I.
Differenced Audit onInstall, Verify, andUpdate
When connected to an audit service, will difference the auditedinformation in initial installation, on subsequent connects, and whenupdated.l Collect attribute is set to Diff.
l Runexec attribute is set to IVU.
l ZSVCTYPE attribute is set to I.
Full Audit on Install andUpdate
When connected to an audit service, will difference the auditedinformation on installation and update.
Inventory Options (RIMOPTS) Class
Radia Client Automation Enterprise Inventory Manager (9.00)Page 40 of 90
Reference GuideChapter 5: Creating Audit Packages
Instance Description
l Collect attribute is set to Full.
l Runexec attribute is set to IU.
l ZSVCTYPE attribute is set to I.
Full Audit on Install,Verify and Update
When connected to an audit service, willl Collect attribute is set to Full.
l Runexec attribute is set to IVU.
l ZSVCTYPE attribute is set to I.
for additional information about RIMOPTS attributes.
Finally, a connection to an auditing behavior is needed.
Connection to an Audit Behavior
The audit behavior owned by the Individual File Audit ZSERVICE is connected to the BehaviorServices (BEHAVIOR) class within the AUDIT Domain.
The BEHAVIOR class in the AUDIT Domain remains unchanged from the BEHAVIOR class withinthe SOFTWARE Domain. For description of the attributes found within this class, see theRadiaClient Automation Enterprise Configuration Server Database ReferenceGuide.
Using the CSDB Editor Create/Maintain AuditServices
Wewill use the CSDB Editor to walk through the construction of a file audit. An instance of theAUDIT Domain's Audit Package (PACKAGE) Class contains information about the inventoryinformation to collect, and what action to take with that collected information.
Before beginning the creations package, you should ask yourself the following questions:
l What am I auditing for?Will it be a hardware audit, a file audit, or aWBEM object audit?
l Will I be deploying to all users, or a select few?
l Will I want this to be connected to a timer for scheduled deployment? (See "Configuring Timersfor Audit Collection" on page 53 for information about timers.)
By seeing and deploying the sample audits provided by HP, system administrators will be able tocreate and use their own auditing packages.
Radia Client Automation Enterprise Inventory Manager (9.00)Page 41 of 90
Reference GuideChapter 5: Creating Audit Packages
Caution: If you are creating aWBEM Audit Package, be aware Inventory Manager leveragesMicrosoft's Windows Management Instrumentation (WMI) to collect hardware and softwareinventory data by usingWMI queries. SomeWMI queries can traverse the network contactingother servers in the enterprise to collect the requested information. This may result in largevolumes of data being returned, and could have a significantly negative effect on networkperformance. An example of this would be querying all users on the network using theW32_UserAccount WMI class. Extreme cautionmust be taken to understand the scope of thesequeries to ensure unexpected results do not occur. While Inventory Manager provides aninterface toWMI and its providers, it cannot control how these queries are satisfied. It is thecustomer’s responsibility to safeguard against usingWMI queries that span the network, if thisbehavior is not as expected.
Creating a New Audit Package1. Go toStart > Programs > Radia Client Automation Administrator > Radia Client
Automation Administrator CSDB Editor. The CSDB Editor Security Information dialog boxopens.
2. Type a User ID and, if necessary, a password, and then click OK. The CSDB Editor windowopens.
Note: The User ID, as shipped from HP, is Admin and password is secret. This mayhave been changed during installation. Check with your security administrator to obtainyour ownUser ID and password, if necessary.
3. Double-click PRIMARY.
4. Expand theAUDIT Domain.
Radia Client Automation Enterprise Inventory Manager (9.00)Page 42 of 90
Reference GuideChapter 5: Creating Audit Packages
5. Double-click Audit Packages (PACKAGE) class.
As an example, we will create a new auditing package named Log Finder. This package willscan a user's computer for .log files, capture them, and return the results to the administrator.
Radia Client Automation Enterprise Inventory Manager (9.00)Page 43 of 90
Reference GuideChapter 5: Creating Audit Packages
6. Right-click theAudit Packages (PACKAGE)Class.A shortcut menu opens.
7. Select New Instance from the shortcut menu. The Create Instance dialog box opens.
8. Enter a new display name for the package instance. This friendly namewill appear in the treeview.
9. Enter a name for the Create a new Audit Packages (PACKAGE) instance name. This nameappears in the title bar of the list view of the CSDB Editor window when the instance isselected and opened in the tree view.
Radia Client Automation Enterprise Inventory Manager (9.00)Page 44 of 90
Reference GuideChapter 5: Creating Audit Packages
10. Click OK to continue. The new Log Finder package is added to the AUDIT.PACKAGE Class.
Once the Log Finder package is created, you will need to add its components.
Radia Client Automation Enterprise Inventory Manager (9.00)Page 45 of 90
Reference GuideChapter 5: Creating Audit Packages
Adding a Component to an Audit Package1. Right-click the Log Finder package. A shortcut menu opens.
2. Select Add Component from the shortcut menu. The Add Components dialog box opens.
3. In theAvailable Components list, select File.
Radia Client Automation Enterprise Inventory Manager (9.00)Page 46 of 90
Reference GuideChapter 5: Creating Audit Packages
4. In theNew Component Name box, enter the new component name.
5. Click Add+Edit. The component is added to the package and the Editing Instance dialog boxopens.
In the Editing Instance dialog box, you can edit the instances that will be used in your audit.
Note: Use the AUDIT.FILE Class instances to help you decide which instances youmaywant to edit.
For our example, we changed the SCANFOR attribute to C:\*\*.log. Continue to edit, line-by-line, as necessary.
6. Click OK when you are done with your edit.
7. Click Yes to save your changes.Next, you will need to create a ZSERVICE instance to contain the Log Finder package.
Creating a ZSERVICE Instance
Note:While working in the AUDIT Domain, note that the New ApplicationWizard is notavailable to connect a package to a service. You need to either copy an existing instance or
Radia Client Automation Enterprise Inventory Manager (9.00)Page 47 of 90
Reference GuideChapter 5: Creating Audit Packages
create a new one.
1. In the CSDB Editor, expand the AUDIT.ZSERVICE class in the tree view.
2. Right-click Audit Application (ZSERVICE) and a shortcut menu opens.
3. Select New Instance from the shortcut menu. The Create Instance dialog box opens.
4. Type a display and an instance name.
Radia Client Automation Enterprise Inventory Manager (9.00)Page 48 of 90
Reference GuideChapter 5: Creating Audit Packages
5. Click OK. The ZSERVICE Log Finder is added to the AUDIT.ZSERVICE class.
6. Use the CSDB Editor to connect the Log Finder package to the Log Finder service.
Once the connection to the ZSERVICE has been completed, various optional steps can be taken.
Youmight want to ask yourself the following questions:
l Will the service appear in the Application Self-ServiceManager? Should the ZSVCNAME bechanged? Should I enter additional information that may appear in the Application Self-ServiceManager?
l Will this be amandatory or optional service?
Radia Client Automation Enterprise Inventory Manager (9.00)Page 49 of 90
Reference GuideChapter 5: Creating Audit Packages
l Will the service have a certain length of time to be active?
l Do I want to confirm if the service is installed or not?
The answers to these questions can help you decide how to customize the service.
For our example, we wanted to change the service name from Unknown to Log Finder. We alsowanted tomake this service available to users in the Application Self-ServiceManager, so we havechanged the ZSVCMO attribute frommandatory to mandatory and optional. Wewould like theConfiguration Server to report back and store any .log files that are found. Therefore, we will changethe ZRSCMFIL attribute to capture and store this information on the Configuration Server'sdirectory.
Log Finder ZSERVICE Attributes
Use the CSDB Editor to connect and deploy the Log Finder audit service.
In this particular example, the user sees the new audit service in the Application Self-ServiceManager.
Radia Client Automation Enterprise Inventory Manager (9.00)Page 50 of 90
Reference GuideChapter 5: Creating Audit Packages
Log Finder in the Application Self-Service Manager
Radia Client Automation Enterprise Inventory Manager (9.00)Page 51 of 90
Reference GuideChapter 5: Creating Audit Packages
Radia Client Automation Enterprise Inventory Manager (9.00)Page 52 of 90
Chapter 6
Configuring Timers for Audit CollectionThis guide helps you install and implement the Inventory Manager. Choose the appropriatestrategies suited for your enterprise needs.
The Scheduling (TIMER) ClassThe Scheduling (TIMER) class enables the Client Automation administrator to set a timer on theClient Automation agent computer that will cause one or more audit services to be processedwhenever the timer expires. The administrator can use this method to process mandatory auditservices automatically according to a pre determined schedule.
Note: As distributed by HP, the SOFTWARE Domain also contains a Scheduling (TIMER)class. Timers can be specified in instances of either of these Scheduling (TIMER) classes andcan be connected to an Application (ZSERVICE) class instance in either the SOFTWARE orAUDIT Domain.
The following sample Timer packages are present within the AUDIT.Scheduling (TIMER) Class:
l Daily deploys a ZSERVICE everyday at the time specified.
l Weekday deploys a ZSERVICE onMondays, Wednesdays, and Fridays at a specified time.
l Weekly deploys a ZSERVICE every seven days at a specified time.
l Discover Installed Software Timer executes a ZSERVICE weekly between 8:30 am and10:30 pm. Use this particular timer in conjunction with the ZSERVICE Discovery of Applicationsthat audits the ADD/REMOVE PROGRAM part of the OS.
These sample packages can be copied andmodified, changing the time parameters to suit yourneeds. See theRadia Client Automation Enterprise Administrator User Guide for information oncopying an instance. Or, you can create a new timer instance by following the instructions given in"Creating a Timer Instance" on page 57.
Radia Client Automation Enterprise Inventory Manager (9.00)Page 53 of 90
Reference GuideChapter 6: Configuring Timers for Audit Collection
AUDIT Scheduling (TIMER) Class
Timers can be set to expire periodically (hourly, daily, weekly, monthly, or at defined intervals), on aspecific date, or at a specific time. Each Client Automation agent is installed with the Schedulerservice. This service contains an executable timer component that executes any program on theend-user desktop when a timer expires.
Typically, the Scheduler service lies dormant in the background, and wakes up once per minute tosee if a timer has expired. When a timer expires, the command line associated with the expiredtimer is executed. Normally, this command line invokes a connection to the Configuration Server todeploy or maintain a service.
The following table contains descriptions of the Scheduling (TIMER) class attributes:
Attribute Description
ZOBJPRI Sets the priority for deployment of the ZTIMEQ object. The ZTIMEQ object isdeployed relative to the other elements being deployed during the agent connect.The elements with a priority number less than the value of ZOBJPRI aredeployed before the ZTIMEQ object. A value of 90 is inherited from the base
Scheduling (TIMER) Class
Radia Client Automation Enterprise Inventory Manager (9.00)Page 54 of 90
Reference GuideChapter 6: Configuring Timers for Audit Collection
Attribute Description
instance and should not be changed.
ZSTOP Used to assign timer conditions. Indicate true to cause resolution of the instanceto be skipped. The timer is not deployed for end users. Leave blank for theinstance to be accepted, and resolution will continue.
ZSCHMODE Specifies the timer owner. We recommend you leave the default configuration ofUSER.
ZSCHDEF Indicates when the timer expires. The syntax varies depending on the frequencyof expiration that can be DAILY, HOURLY, INTERVAL, NUMDAY, WEEKDAY,andWEEKLY.
ZSCHTYPE Used only when ZSCHFREQ = PERIODIC.Set ZSCHTYPE to DEFERRED to indicate that the first time an event isattempted to be launched, it will be deferred until the next scheduled time, nomatter when the timer instance is evaluated. This was designed to handle thecase of a daily 4 A.M. (non-peak) scheduled event that is sent to the ClientAutomation agent computer during the day. If it was not deferred, it would launchduring the day instead of waiting until the next morning. Example 1:Suppose youcreate and deploy a timer with the ZSCHDEF =DAILY(&ZSYSDATE,04:00:00). If ZSCHTYPE = IMMEDIATE and it is:l Before 4:00:00, the command in the instance will be executed the same day
at 4:00:00.
l After 4:00:00, the command in the instance will be executed immediately.If ZSCHTYPE = DEFERRED and it is:l Before 4:00:00, the command in the instance will be executed the next day at
4:00:00.
l After 4:00:00, the command in the instance will be executed the next day at4:00:00.
Example 2:Suppose you create and deploy a timer with the ZSCHDEF =WEEKDAY(FRIDAY,04:00:00)If ZSCHTYPE = IMMEDIATE and it is:l Not Friday or Friday and before 4:00:00, the command in the instance will be
executed on Friday at 4:00:00.
l Friday and after 4:00:00, the command in the instance will be executedimmediately.
If ZSCHTYPE = DEFERRED and it is:l Not Friday or Friday and before 4:00:00, the command in the instance will be
executed a week later on Friday at 4:00:00.
l Friday and after 4:00:00, the command in the instance will be executed aweek later on Friday at 4:00:00.
ZSCHFREQ This attribute indicates how often the timer should expire according to thefrequency specified in the ZSCHDEF attribute.
l Once for a one-time expiration.
Radia Client Automation Enterprise Inventory Manager (9.00)Page 55 of 90
Reference GuideChapter 6: Configuring Timers for Audit Collection
Attribute Description
l Periodic for a repeated expiration.
l Random for random intervals.
ZRSCCMDL This attribute indicates the command line that is executed on the subscriber'scomputer when the timer expires.
ZSVCOID Specifies the object ID of the Application instance that this Scheduling instanceis connected to. This value is inherited from the base instance and should not bemodified.
_ALWAYS_ Stores the connections to other instances
NAME Friendly name for this instance
APPSVC Application
REQUEST Application request
DOMAIN Server's domain name
IPADDR Server's IP address/name
SOCKET Server's socket number
MGRNAME Server's name
ZCREATE Scheduler CREATE method that runs on the Client Automation agent computerThis value is inherited from the base instance and should not be changed.
ZVERIFY Scheduler VERIFY method that runs on the Client Automation agent computerThis value is inherited from the base instance and should not be changed.
ZUPDATE Scheduler UPDATE method that runs on the agent computer This value isinherited from the base instance and should not be changed.
ZDELETE Scheduler DELETE method that runs on the Client Automation agent computerThis value is inherited from the base instance and should not be changed.
RUNSYNC Sets the value of Yes or No for the synchronous timer execution. The defaultvalue is Yes.
ZNOPING Controls the automatic sensing of a network connection between the ClientAutomation agent computer and the Configuration Server. An expired time willcontinually evaluate whether communications with the Configuration Server canbe established. When communications are established, the command lineassociated with the time is executed. After executing the command line, theScheduler service resumes normal evaluation of whether the timer has expiredagain. Use this attribute when there is a possibility that the Client Automationagent will not be able to connect with the Configuration Server. This attribute isespecially useful for mobile users.
Radia Client Automation Enterprise Inventory Manager (9.00)Page 56 of 90
Reference GuideChapter 6: Configuring Timers for Audit Collection
Attribute Description
Note: To use this attribute, youmust add it to the TIMER class template.
PINGDLAY Sets the amount of time between pings in milliseconds. The default setting is2000 milliseconds.
PINGCNT Sets the number of ping attempts to bemade by the Configuration Server. Thedefault setting is 3.
This section describes how to create and configure a timer, and connect it to the service that youwant to deploy. Before creating and configuring a timer, consider the following:
l What time of day should the timer expire?
l How often do you want the timer to expire?
l Does the timer need to expire more than once?
l What should happen when the timer expires?
Creating a Timer InstanceTo create a timer in the CSDB, use the CSDB Editor to create a Scheduling (TIMER) instance inthe AUDIT Domain.
Note: As distributed by HP, the SOFTWARE Domain also contains a Scheduling (TIMER)class. Timers can be specified in instances of either of the Scheduling (TIMER) classes andcan be connected to an Application (ZSERVICE) class instance in either the SOFTWARE orAUDIT Domains.
For the purposes of documentation, the timer created will be created from within the AUDITDomain.
For additional information about the Scheduling (TIMER) class, see theRadia Client AutomationEnterprise Administrator User Guide.
Creating a New Timer in the AUDIT Domain1. From the Start menu, go toPrograms > Radia Client Automation Administrator > Radia
Client Automation Administrator CSDB Editor. The Security Information dialog boxopens.
2. Type a User ID and, if necessary, a password, and then click OK. The CSDB Editor windowopens.
Note: The User ID, as shipped from HP, is Admin and password is secret.This mayhave been changed during installation. Check with your security administrator to obtainyour ownUser ID and password, if necessary.
3. Double-click PRIMARY.
Radia Client Automation Enterprise Inventory Manager (9.00)Page 57 of 90
Reference GuideChapter 6: Configuring Timers for Audit Collection
4. Double-click AUDIT.
5. Right-click Scheduling (TIMER).Scheduling (TIMER) Class
6. Select New Instance. The Create Instance dialog box opens.
7. Type a name for the new timer instance, such as Log Audit Timer.
Radia Client Automation Enterprise Inventory Manager (9.00)Page 58 of 90
Reference GuideChapter 6: Configuring Timers for Audit Collection
8. Click OK. The timer instance appears in the Scheduling (TIMER) Class.Log Audit Timer Instance Under Scheduling (TIMER) Class
Specifying Timer SettingsWhether you have copied an existing timer or you have created a new Timer instance, you need toreview and/or customize your timer settings. See theRadia Client Automation EnterpriseAdministrator User Guide for more information on how to specify the Client Automation agent timersettings.
Specifying ZSCHDEFUse the ZSCHDEF attribute to define the time interval and date and time to execute the commandline. The syntax varies depending on the interval chosen. When configuring ZSCHDEF, theattribute is set in the following form depending on the interval.DAILY(<DATE>,<TIME>[,<LIMIT>])HOURLY(<DATE>,<TIME>[,<LIMIT>])WEEKLY(<DATE>,<TIME>[,<LIMIT>])WEEKDAY(<DAY of Week>,<TIME>[,<LIMIT>])NUMDAYS(<DATE>,<TIME>[,<LIMIT>],<Number of Days>)INTERVAL(<DATE>,<TIME>[,<LIMIT>],<Number of Seconds>)
Note: In the case of NUMDAYS and INTERVAL, the Optional parameter <LIMIT> is betweenmandatory parameters. If the optional parameter is omitted the placemust be held with adouble comma. Example:NUMDAYS: NUMDAYS(20000803,08:00:00,12:00:00,14)NUMDAYS: NUMDAYS(20000803,08:00:00,,14)
Radia Client Automation Enterprise Inventory Manager (9.00)Page 59 of 90
Reference GuideChapter 6: Configuring Timers for Audit Collection
l The value of freq can be:DAILY, WEEKLY, WEEKDAY, HOURLY, INTERVAL, NUMDAYS
l If the value of freq is DAILY, WEEKLY, HOURLY, INTERVAL, or NUMDAYS, the date is thenspecified in the following form:YYYYMMDD
l If the value of freq is WEEKDAY, the date is then specified as the name of a day of the week inall uppercase letters. This would be one of the following:MONDAY, TUESDAY, WEDNESDAY, THURSDAY, FRIDAY, SATURDAY, SUNDAY
l The values for time and limit_time are optional. They are specified in the following form:HH:MM:SS
l The value for count is optional. It is specified as an integer.
The timer expiration can also be configured on the value of ZSCHFREQ. Use "The Scheduling(TIMER) Class" on page 53 to help you determine the appropriate syntax.
Type Syntax Timer Expires
DAILY DAILY(&ZSYSDATE,24:00:00) Daily at midnight by the system'sdate.
WEEKLY WEEKLY(&ZSYSDATE,01:00:00) Every seven days at 1:00 am.
WEEKDAY WEEKDAY(Name ofWeekday*,01:00:00)
Every Name of Weekday* at 1:00AM. The weekday must bespecified in uppercase.
HOURLY HOURLY(&ZSYSDATE,08:41:00) Hourly starting at 8:41 AM on thesystem's date.
INTERVAL INTERVAL(&ZSYSDATE,08:41:00,,30) Every 30minutes starting at 8:41AM based on system's date.
NUMDAYS NUMDAYS(20000803,08:00:00,,14) Every 14 days starting on August 3,2000 at 8:00 AM.
Syntax of ZSCHDEF Attributes
Specifying ZSCHTYPEThe ZSCHTYPE controls how the timer handles the scheduled event when the agent receives theinitial TIMER definition for a service. There are two valid controls:
l IMMEDIATE will execute the command specified in the ZRSCCMDL attribute immediately ifthe date and time indicated in the ZSCHDEF attribute has passed when the ZTIMEQ object isinitially created.
l DEFERRED will defer the execution if the date and time defined in the ZSCHDEF has passedand will wait until the next occurrence to execute. This is the recommended setting.
If the time and date indicated in ZSCHDEF has not passed when the ZTIMEQ object is deployed,this setting has no effect.
Radia Client Automation Enterprise Inventory Manager (9.00)Page 60 of 90
Reference GuideChapter 6: Configuring Timers for Audit Collection
Specifying ZSCHFREQUse the ZSCHFREQ to specify whether the timer should expire once (ONCE) or repeatedly(PERIODIC) according to the frequency specified in ZSCHDEF.
Specifying ZRSCCMDLUse the ZRSCCMDL to execute a command on the subscriber's computer when the timer expires.
Use the following command line to run the audit service when the scheduled time occurs:Radskmanuid=&(ZMASTER.-ZUSE-RID),startdir=&(ZMASTER.LOCALUID),mname=&(ZMASTER.ZMGRNAME),dname=&(ZMASTER.ZDOMNAME),sname=&(ZSERVICE.ZOBJNAME)
Note: Execution causes Client Automation to launch the AUDIT service behavior,(EXECUTE.REXX) attached to the AUDIT service.
The parameters indicated in the radskman commandmay differ depending on customer specificimplementations.
Specifying ZNOPING, PINGDLAY, and PINGCNTUse the ZNOPING attribute to control automatic sensing of a network connection between theClient Automation agent computer and the Configuration Server. The default is Y. Use this attributewhen there is a possibility that the Client Automation agent will not be able to connect with theConfiguration Server such as amobile user.
See theRadia Client Automation Enterprise Administrator User Guide for more information aboutthe ZNOPING attribute.
l If the ZNOPING attribute is not in the ZTIMEQ object, or if ZNOPING is not equal toN, theScheduler service does not ping the Configuration Server.
l If ZNOPING = N, the Scheduler service will ping the Configuration Server.n If the Configuration Server is pinged successfully, the command in the ZRSCCMDL attribute
is executed. The PENDING attribute in the Client Automation agent's ZTIMEQ object is thenset toN. This indicates that the Scheduler service does not need to ping the ConfigurationServer again.
n Set ZNOPING toW if you are specifying an end limit in the ZCHDEF attribute. The Schedulerpings the Configuration Server before executing the command. If the Configuration Server isunavailable, the ZPENDING flag is set toW. If the ZSCHEDEF has a limit time, then whenthat time passes, the ZPENDING flag is set toN, and the Scheduler will not attempt toexecute the command until its next scheduled time.
n If the Configuration Server is not pinged successfully, the timer is not processed any further.The ZPENDING attribute value remains set toY. The next time the Scheduler serviceexpires, it should ping the Configuration Server again.
If ZNOPING is set toN, also use the PINGDLAY and PINGCNT attributes to further specify thetiming and number of pings between the agent computer and the Configuration Server.
Radia Client Automation Enterprise Inventory Manager (9.00)Page 61 of 90
Reference GuideChapter 6: Configuring Timers for Audit Collection
l If ZNOPING is set toN, PINGDLAY specifies the time inmilliseconds between pings. Thedefault is 2000.
l If ZNOPING is set toN, PINGCNT specifies number of ping attempts. The default is 3attempts.
Connecting the Timer to a ServiceOnce you have created your timer, youmust connect it to a service. Each subscriber that receivesthe ZSERVICE to which the timer is connected, will receive the timer information in the ZTIMEQobject the next time the Client Automation agent connects to the Configuration Server.
Use the CSDB Editor to connect the Log Audit Timer to the Log Finder ZSERVICE createdearlier in this document.
Log Audit Timer Instance Connected to Log Finder Service
Then connect the AUDIT.ZSERVICE.Log Finder to a user or group of users in the POLICYDomain.
Log Finder Attached to a User
Audit Execution ConfigurationBy default, when an Audit service is installed on an end user's computer, it executes immediatelyand reports to the Configuration Server. This can be time consuming, especially if the audit servicetype is WBEM, File Scan, or anMSI request. The audit service definitionmay also be installed at atime when an audit scan is not desirable. For example, when an end user visits the Application Self-
Radia Client Automation Enterprise Inventory Manager (9.00)Page 62 of 90
Reference GuideChapter 6: Configuring Timers for Audit Collection
ServiceManager andmandatory applications are processed as defined in the embed tagenterprisemanagement=auto.
The easiest way to approach this issue is to manipulate how and when the audit actually executes.This can be accomplished by:
l Customizing the Inventory Options (RIMOPTS) attribute.and
l Updating the embed tags in the html file for the Application Self-ServiceManager.
The following describes the steps necessary to customize RIMOPTS and update the embed tag toprevent audit execution duringmandatory application processing.
Customizing the RIMOPTS Instance1. From the Start menu, select Programs > Radia Client Automation Administrator > Radia
Client Automation Administrator CSDB Editor. The CSDB Editor Security Informationdialog box opens.
Note: The User ID, as shipped from HP, is Admin and password is secret. This mayhave been changed during installation. Check with your security administrator to obtainyour ownUser ID and password, if necessary.
2. If necessary, type a User ID and password, and then click OK. The CSDB Editor windowopens.
3. Expand thePRIMARY File and theAUDIT Domain.
Radia Client Automation Enterprise Inventory Manager (9.00)Page 63 of 90
Reference GuideChapter 6: Configuring Timers for Audit Collection
4. Create a new instance in the Inventory Options (RIMOPTS) class namedCM_AUDIT_NO_EXECUTE, and click OK. The Create Instance dialog box opens.Next, you will need to edit the Audit No Execute instance.
5. Expand the Inventory Options (RIMOPTS) class and double-click theAudit No Executeinstance.
6. Double-click theRUNEXEC attribute in the list view to edit it. Remove any attributeinformation. This will ensure that the audit service will not run during the installation,verification, or update function.
Next, determine which AUDIT service you will be adding the new RIMOPTS service to. Forexample, select the RIM_REPORTING service.
7. Right-click RIM_REPORTINGService in the AUDIT class.
Radia Client Automation Enterprise Inventory Manager (9.00)Page 64 of 90
Reference GuideChapter 6: Configuring Timers for Audit Collection
8. Select Edit Instance.
9. Locate the _ALWAYS_Contains attribute with the value of AUDIT.RIMOPTS.DIFF_INSTALL_UPDATE and change it to a value of AUDIT.RIMOPTS.AUDIT_NO_EXECUTE.
10. To define the audit service as Mandatory, locate the ZSVCMO field and set it to M. This willcause the initial TIMER definition associated with the audit service to be created on the ClientAutomation agent.
Radia Client Automation Enterprise Inventory Manager (9.00)Page 65 of 90
Reference GuideChapter 6: Configuring Timers for Audit Collection
The Audit No Execute instance is now connected to the RIM Reporting service.
This completes the steps necessary to customize RIMOPTS and update the embed tag to preventaudit execution duringmandatory application processing.
Radia Client Automation Enterprise Inventory Manager (9.00)Page 66 of 90
Chapter 7
Viewing Inventory ReportsTo view the Inventory reports:
l Go to your RCA Console.
l Click theReporting tab.
l Select the Inventory Management Reports under reporting views.
Reporting Views for Inventory ReportsThere are different types of Inventory Management Reports:
l Executive Summaries
l Operational Reports
l Hardware Reports
l Software Reports
l Readiness Reports
l Power Utilization
Inventory Management Reports
The following tables list the available Hardware and Software Reporting Views.
Radia Client Automation Enterprise Inventory Manager (9.00)Page 67 of 90
Reference GuideChapter 7: Viewing Inventory Reports
ReportingViewTypes Reporting Views
HPSpecificReports
HP BIOS Settings HP Hardware Alerts HP Hardware Alerts (Boot Events)
DetailReports
Hardware Summary Managed Devices Devices by Vendor/Model Devices by Serial# Device by Baseboard ID Device by Logical Disks Battery Information SMBIOSInformation
SummaryReports
Count by Summary Count by CPU Count by Memory Count by Operating System
BladeReports
Blade by Racks Blade by Enclosures Managed Blades
Hardware Reporting Views
Reporting View Types Reporting Views
Managed Service Reports Service Summary Service Details
Discovered Software Vendor Reportsl Discovered Software by VendorProduct Reportsl Discovered Software by Product
l Discovered Software by Product VersionApplication Reportsl Discovered Software by Application
l Discovered Software by Application Version
Managed Software Reports Vendor Reportsl Managed Software by VendorProduct Reportsl Managed Software by Product
l Managed Software by Product VersionApplication Reportsl Managed Software by Application
l Managed Software by Application Version
Software Reporting Views
Windows Vista Readiness ReportsUse the Display Options to show Windows Vista® Readiness Reports. These reports containinformation you can use to determine individual device readiness for an upgrade toWindows Vista.The Reporting Server determines Vista readiness based on the following criteria:
Radia Client Automation Enterprise Inventory Manager (9.00)Page 68 of 90
Reference GuideChapter 7: Viewing Inventory Reports
l CPU Speed
l Memory
l System Drive Total
l System Drive Free
See theMicrosoft’s support web site for additional Vista readiness information.
To Display Windows Vista Readiness Reports:
1. In the Display Options area, select Inventory Management Reports.
2. Select Readiness Reports.
3. SelectWindows Vista.
4. See the reports and charts available to determine theWindows Vista’s upgrade readiness ofyour devices. The Readiness Status and Additional Information columns contain informationabout the current level of readiness for each device.
Filtering Inventory Reports with ReportingServer
Reporting Server provides extensive filtering capabilities. To access the filters, expand InventoryManagement Filters in the Search Controls section of the Reporting Server page.
Filter types include:
l Operational Filters
l Hardware Filters
l Software Filters
l OS Filters
l Readiness Filters
l Power Assistant Filters
Inventory Management Related Data Filters
Expand each individual Inventory Management data filter to see the available filters you can applyto the current Reporting View.
Radia Client Automation Enterprise Inventory Manager (9.00)Page 69 of 90
Reference GuideChapter 7: Viewing Inventory Reports
Some filters only allow a text entry. Others have aShow available options button or magnifyingglass to open a filter lookup window.
To get help when entering filter, point to the help icon and a tooltip specifies the syntax and givesexamples.
Expand a Filter
Click themagnifying glass to open the filter lookup window.
Select the Filter
For additional information on creating filters and using the Reporting tab in general, see theRadiaClient Automation Enterprise User Guide.
Radia Client Automation Enterprise Inventory Manager (9.00)Page 70 of 90
Appendix A
Detail and Summary Reporting Tables
ActionDisplayedTable Title
Columns Queried /DisplayName Tables Queried
Applications ManagedApplications
device_id/Subscriber AppEvent
service_id/Service
ctime/Created
mtime/Modified
app_name/Application Name
event/Event
del_time/Date Deleted
ver_time/Date Verified
inst_time/Date Installed
fix_time/Date Fixed
AuditedApplications
Cim-show-apps.tsp
InstalledApplications
Installed-apps.tsp
Add/RemoveApplications
Installed-uninstalled-apps.tsp
WBEM Applications InstalledProducts
wName/Tag rCIM_Product
wVendor/Vendor
wVersion/Version
wIdentifyingNumber/SoftwareSpec
wCaption/Caption
InstalledFilesets /
wPartComponent/Fileset rCIM_SoftwareFeature
Inventory Reporting – Detailed Reports
Radia Client Automation Enterprise Inventory Manager (9.00)Page 71 of 90
Reference GuideAppendix A: Detail and Summary Reporting Tables
ActionDisplayedTable Title
Columns Queried /DisplayName Tables Queried
Elements
Packages wName/Tab rCIM_SoftwareElement
wVersion/Version
wSoftwareElementID/SoftwareSpec
wTargetOperatingSystem/TargetOS
wManufacturer/Vendor
wCaption/Caption
wInstallDate/Install Date
AuditedApplications
wCaption/Application Name rNVD_Product
mtime/Modified
CIM_Product.wDescription/type
wName/Name
wVendor/Vendor
wVersion/Version
wInstallState/Installed
wInstallDate/Date Installed
Audited Files Audited Files name/Name FileAudit
version/Version
status/Status
vendor/Vendor
product/Product
prodvers/Product Version
scanfor/Scanned
file_date/File Date
file_size/File Size
Radia Client Automation Enterprise Inventory Manager (9.00)Page 72 of 90
Reference GuideAppendix A: Detail and Summary Reporting Tables
ActionDisplayedTable Title
Columns Queried /DisplayName Tables Queried
mtime/Modified
file_type/File Type
path/Path
ConfigurationSummary forWindows
O/SConfiguration
mtime/Modified rWin32_OperatingSystem
_wOS/OS
wRegisteredUser/RegisteredUser
wOrganization/Organization
wSerialNumber/S/N
wSystemDirectory/Sys Dir
WtotalPageFileSpace/PageFileSize (mb)
Hardware manufacturerr/Manufacturer rWin32_ComputerSystemProduct
_model/Model RWin32_systemEnclosure
_wSNTag/S/N RWin32_Processor
wManufacturer,wCurrentClockSpeed/Processor
RWin32_LogicalMemoryConf
wTotalPhysicalMemory/Physical Memory (MB)
rWin32_ComputerSystem
wSystemType/System rWin32_Bios
_wBios / Bios
_wKybd/keyboard RWimd32_Keyboard
_wMouse/Mouse rWin32_PointingDevice
_wVideo/Video/Video rWin32_VideoController
Radia Client Automation Enterprise Inventory Manager (9.00)Page 73 of 90
Reference GuideAppendix A: Detail and Summary Reporting Tables
ActionDisplayedTable Title
Columns Queried /DisplayName Tables Queried
_wDriverName/Printer rWin32_Printer
_WSerialPort/Serial Ports rWin32_SerialPort
_wParallelPort/Parallel Ports rWin32_ParallelPort
NetworkAdapterinformation
Wbem-show-network.tsp
Disk DriveInformation
Wbem-show-drives.tsp
Environment Wbem-show-environment.tsp
WindowsServices
Wbem-show-services.tsp
DeviceConfiguration
Ctime/Created Device Config
Mtime/modified
Os/OS
Os_level/ OS Level
Sysdrv/Sys Drive
Sysdrv_total/ Sys Drive Size(MB)
Sysdrv_free/Sys Drive Free(MB)
Software(AGENT)
Person/Person Device Config
Organization/Organization
Language/Language
Protocol/Protocol
Timeout/Timeout
Trace/Trace
Edmsys/Sys Dir
Edmlib/Lib Dir
Edmlog/Log Dir
Radia Client Automation Enterprise Inventory Manager (9.00)Page 74 of 90
Reference GuideAppendix A: Detail and Summary Reporting Tables
ActionDisplayedTable Title
Columns Queried /DisplayName Tables Queried
Hardware Ipaddr/ IP Address Device Config
Macaddr/ MAC Address
Bios/ Bios
Cpu/CPU
Memory/Mem (MB)
Keyboard/Keyboard
Mouse/Mouse
Video/Video
N_serial/Serial(#)
N_Parallel/Parallel (#)
N_PRINTER/printer (#)
WBEM Features AuditedFeatures
wProductName/Product Name RWind32_SoftwareFeature
mtime/Modified
WInstallDate/Date Installed
wVendor/Vendor
wVersion/Version
InstalledApplications
Audited Files Show-fileaudit.tsp
InstalledApplications
WFileDescription / ApplicationName
RNVD_Installed_Apps
Mtime / Modified
WPath / Path
WoriginalFileName /Executable
WFileVersion / ExecutableVersion
WcompanyName ? Vendor
WProductName / ProductName
Radia Client Automation Enterprise Inventory Manager (9.00)Page 75 of 90
Reference GuideAppendix A: Detail and Summary Reporting Tables
ActionDisplayedTable Title
Columns Queried /DisplayName Tables Queried
WProducttVersion / Version
Add/RemoveApplications
Installed-uninstall-apps.tsp
WBEM Elements AuditedElements
mtime/Modified rWin32_SoftwareElement
wName/Name
wVersion/Version
wInstallDate/Date Installed
wManufacturer/Manufacturer
wPath/Path
PDA Devices PDA Devices mtime/Modified rNVD_PDASystem
wName/Name
wDescription/Type
wStatus/Status
WBEM PDA Config Configuration Mtime/Modified rCIM_OperatingSystem
wCaption, wVersion / OS
wFreePhysicalMemory/FreePhysical Memory (MB)
wTotalVirtualMemorySize/TotalVirtual Memory (MB)
wFreeVirtualMemorySize/FreeVirtual Memory (MB)
PDA InstalledProducts
Show-pda-inst-prod.tsp RCIM_OperatingSystem
wbem-show-environment.tsp
Environment mtime / Modified rWin32_Environment
wUserName / Account
WSystemVariable /System Variable
wName / Name
wAttributeValue / Value
Radia Client Automation Enterprise Inventory Manager (9.00)Page 76 of 90
Reference GuideAppendix A: Detail and Summary Reporting Tables
ActionDisplayedTable Title
Columns Queried /DisplayName Tables Queried
wbem-show-services.tsp
WindowServices
mtime / Modified rWin32_Services
wDisplayName / Services
wState / Status
wStartMode / Startup
wName / Name
wStartName / Logon
wDesktopInteract / Interact withDesktop
wPathName / Path
Wbem-show-network.tsp
NetworkAdapterInformation
Mtime / Modified RWin32_NetworkAdapterConf
Wdescription / Type
WIPAddress / IP Address
WMACAddress / MAC Address
Wbem-show-drives.tsp
Disk DriveInformation
Mtime / Modified RWin32_LogicalDisk
WDeviceID / Drive Letter
WDescription/Type
WfileSystem / File System
WSize / Size (MB)
WFreeSpace / Free Space (MB)
WProviderName / ProviderName
WvolumneSerialNumber / SerialNumber
Installed-uninstall-apps.tsp
Add/RemoveApplications
WDisplayName /Application Name
RNVD_Installed_Uninstall
Mtime / Modified
Radia Client Automation Enterprise Inventory Manager (9.00)Page 77 of 90
Reference GuideAppendix A: Detail and Summary Reporting Tables
ActionDisplayedTable Title
Columns Queried /DisplayName Tables Queried
WUninstallString / UninstallString
Show-pda-inst-prod.tsp
PDA InstalledProducts
Mtime / Modified Rnvd_Product
Wdescription/ Type
WStatus / Status
WVersion / Version
ActionDisplay TableTitle
Columns Queried/DisplayName
TablesQueried
Show-Config DeviceConfiguration
ctime/Created DeviceConfig
mtime/Modified
os/OS
os_level/OS Level
sysdrv/Sys Drive
sysdrv_total/Sys Drive Size(MB)
sysdrv_free/Sys Drive Free(MB)
Software person/Person
organization/Organization
language/Language
protocol/Protocol
timeout/Timeout
trace/Trace
edmsys/Sys Dir
edmlib/Lib Dir
edmlog/Log Dir
Hardware ipaddr/IP Address
General Reporting – Detailed Reports
Radia Client Automation Enterprise Inventory Manager (9.00)Page 78 of 90
Reference GuideAppendix A: Detail and Summary Reporting Tables
ActionDisplay TableTitle
Columns Queried/DisplayName
TablesQueried
macaddr/MAC Address
bios/Bios
cpu/CPU
memory/Mem (MB)
keyboard/Keyboard
mouse/Mouse
video/Video
n_serial/Serial (#)
n_parallel/Parallel (#)
n_printer/Printer (#)
Status - ApplicationEvents
ApplicationEvents
device_id/Subscriber AppEvent
service_id/Services
ctime/Created
mtime/Modified
app_name/Application Name
event/Event
status/Status
del_time/Date Deleted
ver_time/Date Verified
inst_time/Date Installed
fix_time/Date Fixed
Status - Connect Connect Status mtime/Modified DeviceStatus
duration/Duration
mrc/Return Code
reason/Reason
svc_count/Services (#)
rsrc_count/Files (#)
Radia Client Automation Enterprise Inventory Manager (9.00)Page 79 of 90
Reference GuideAppendix A: Detail and Summary Reporting Tables
ActionDisplay TableTitle
Columns Queried/DisplayName
TablesQueried
rsrc_transfer/Files Tx (#)
rsrc_transfer_size/Files Tx(Sz)
ctime/Created
Errors mtime/Modified DeviceErrors
type/Type
code/Code
reason/Reason
module/Module
object/Object
component/Component
Status - Services Service State mtime/Modified DeviceServices
serviceid/Service
svc_actv/Svc Actv
rsrc_active/Files Active (#)
rsrc_inactive/Files Inactive (#)
ver_error/Vers Err
reason/Reason
Status - Notify Notification Status device_id/Subscriber DeviceNotify
nfy_status/Status
mtime/Modified
nfy_reason/Reason
nfy_cmd/Command
ctime/Created
nfy_type/CommsType
nfy_attempts/Attempts (#)
nfy_userid/User Id
Radia Client Automation Enterprise Inventory Manager (9.00)Page 80 of 90
Reference GuideAppendix A: Detail and Summary Reporting Tables
ActionDisplay TableTitle
Columns Queried/DisplayName
TablesQueried
nfy_addr/Address
nfy_port/Port
nfy_maxretry/Max (#)
nfy_delay/Delay (s)
nfy_timeout/Timeout (s)
nfy_retry2/Retry2 (#)
nfy_retry2/Retry2 (#)
nfy_timeout2/Timeout2 (s)
Status - Summary Connect Status mtime/Modified DeviceState
mrc/Return Code
duration/Duration
svc_count/Services (#)
rsrc_count/Files (#)
reason/Reason
Agent State mtime/Modified
state/State
svc_count/Services (#)
rsrc_count/Files (#)
rsrc_error/File Err
ver_error/Vers Err
reason/Reason
Service State Status-services.tsp
Status - Detailed Connect Status same as Status Connect entries
Agent State Mtime / Modified
State / State
Svc_count / Services (#)
Rsrc_count / Files (#)
Radia Client Automation Enterprise Inventory Manager (9.00)Page 81 of 90
Reference GuideAppendix A: Detail and Summary Reporting Tables
ActionDisplay TableTitle
Columns Queried/DisplayName
TablesQueried
Rsrc_error / File Err
Ver_error / Vers Err
Reason / Reason
Service State Status-services.tsp
Errors same as Status Connectentries
ActionDisplayed Table Title Columns Queried/Display
NameTablesQueried
ApplicationEvents
Application EventHistory
device_id/Subscriber HAppEvent
service_id/Service
mtime/Modified
app_name/Application Name
event/Event
status/Status
del_time/Date Deleted
ver_time/Date Verified
inst_time/Date Installed
fix_time/Date Fixed
nvd_domain/Domain
nvd_class/Class
Connect Connect History mtime/Modified HDeviceStatus
duration/Duration
mrc/Return Code
reason/Reason
svc_count/Services (#)
rsrc_count/Files (#)
History Reporting – Detailed Reports
Radia Client Automation Enterprise Inventory Manager (9.00)Page 82 of 90
Reference GuideAppendix A: Detail and Summary Reporting Tables
ActionDisplayed Table Title Columns Queried/Display
NameTablesQueried
rsrc_transfer/Files Tx (#)
rsrc_transfer_size/Files Tx (Sz)
Errors Error History mtime/Modified HDeviceErrors
type/Type
code/Code
reason/Reason
module/Module
object/Object
State State History mtime/Modified HDeviceState
state/State
svc_count/Services (#)
ver_error/Vers Error
rsrc_count/Files (#)
rsrc_error/File Err
rsrc_active/Files Active (#)
rsrc_active_size/Files Active(Sz)
rsrc_inactive/Files Inactive (#)
rsrc_inactive_size/Files Inactive(Sz)
reason/Reason
ActionDisplayed TableTitle
Columns Queried/DisplayName Tables Queried
Show -Subscribers
ApplicationSubscribers
device_id/subscriber DeviceStatus
mtime/Modified AppEvent
llength [*]/InstalledApps (#)
Show -Applications
Applications app_name or service_id /Application Name
AppEvent
Summary Reporting
Radia Client Automation Enterprise Inventory Manager (9.00)Page 83 of 90
Reference GuideAppendix A: Detail and Summary Reporting Tables
ActionDisplayed TableTitle
Columns Queried/DisplayName Tables Queried
count (device_id)/Subscribers DeviceServices
Show - SystemDrivespace
SubscribersSystem DriveSpace
device_id/Subscriber DeviceConfig
sysdrv/Sys Drive
sysdrv_total/Sys Drive Size(MB)
sysdrv_free/Sys Drive Free (MB)
(sysdrv_free*100)/sysdrv_total /Percent Free
Show - IPAddresses
Subscribers IPAddresses
device_id/Subscriber DeviceConfig
ipaddr/IP Address
macaddr/MAC Address
WBEMConfiguration
Configuration userid/Subscriber rWin32_Bios
mtime/Modified rWin32_OperatingSystem
wCaption, wBuildNumber,wCSDVersion/OS
rWin32_LogicalDisk
wSystemDirectory/SystemDrive
rWin32_ComputerSystem
wSize/System Drive Size (MB) rWin32_Processor
wFreeSpace/System Drive Free(MB)
rWin32_LogicalMemoryConf
wSystemType/System
wManufacturer,
wCurrentClockSpeed/Processor
wTotalPhysicalMemory/PhysicalMemory (MB)
wVersion/Bios
Radia Client Automation Enterprise Inventory Manager (9.00)Page 84 of 90
Reference GuideAppendix A: Detail and Summary Reporting Tables
ActionDisplayed TableTitle
Columns Queried/DisplayName Tables Queried
Status -ApplicationEvents
Application Events device_id/Subscriber AppEvent
service_id/Service
ctime/Created
mtime/Modified
app_name/Application Name
event/Event
status/Status
del_time/Date Deleted
ver_time/Date Verified
inst_time/Date Installed
fix_time/Date Fixed
Status -Connect
Connections mtime/Modified DeviceStatus
device_id/Subscriber
duration/Duration
mrc/Return Code
reason/Reason
rsrc_transfer/File Tx (#)
rsrc_transfer_size/Files Tx (Sz)
Status - Notify Notify Queue mtime/Modified DeviceNotify
device_id/Subscriber
nfy_status/Status
nfy_reason/Reason
nfy_type/CommsType
nfy_attempts/Attempts (#)
Errors - Connect Connect Errors mtime/Modified DeviceErrors
Radia Client Automation Enterprise Inventory Manager (9.00)Page 85 of 90
Reference GuideAppendix A: Detail and Summary Reporting Tables
ActionDisplayed TableTitle
Columns Queried/DisplayName Tables Queried
device_id/Subscriber
type/Type
code/Code
reason/Reason
Errors - Notify Notify Errors mtime/Modified DeviceNotify
device_id/Subscriber
nfy_attempts/Attempts (#)
nfy_status/Status
nfy_reason/Reason
nfy_type/Comms Type
ActionDisplayed TableTitle
Columns Queried/Display Name Tables Queried
Status –MulticastServer Statistics
Multicast ServerStatistics
mtime rNVD_MulticastStatistics
userid
wDuration/TransmitDuration
wNamespace
wNbytesRej
wNbytesReq
wNbytesXmt/BytesTransmitted
wNclients/AgentsConnected
wNdevices
wNfilesRej/FilesRejected
wNfilesReq/FilesRequested
wNfilesXmt/Files
Inventory Reporting – Multicast Detail Reporting
Radia Client Automation Enterprise Inventory Manager (9.00)Page 86 of 90
Reference GuideAppendix A: Detail and Summary Reporting Tables
ActionDisplayed TableTitle
Columns Queried/Display Name Tables Queried
Transmitted
wServiceID/Service
wSourceID/MulticastSession
wSourceType
wStartTime/TransmitStart
Status – AgentDownload Statistics
Agent DownlaodStatistics
mtime RNVD_DownloadStatistics
userid/Subscriber
wDuration/TransmitDuration (sec)
wNamespace
wNbytesRcv/BytresReceived
wNbytesRej
wNbytesReq
wNfilesRej/FilesRejected
wNfilesRcv/FilesReceived
wNfilesReq/FilesRequested
wNpktsDrp
wNpktsRcv
wServiceID/Service
wSourceID
wSourceType/SourceType
wStartTime/TransmitStart
Radia Client Automation Enterprise Inventory Manager (9.00)Page 87 of 90
Reference GuideAppendix A: Detail and Summary Reporting Tables
Radia Client Automation Enterprise Inventory Manager (9.00)Page 88 of 90
We appreciate your feedback!If an email client is configured on this system, by default an email window opens when you clickhere.
If no email client is available, copy the information below to a new message in a webmail client,and then send this message to [email protected].
Product name and version:Radia Client Automation Enterprise Inventory Manager, 9.00
Document title:ReferenceGuide
Feedback:
Radia Client Automation Enterprise Inventory Manager (9.00)Page 89 of 90
Reference GuideWeappreciate your feedback!