| |
|
|
|
Enterprise User Manual
Chapter 7
Hardware Inventory
The Hardware Inventory Operation provides users with up-to-date hardware configuration information. It covers the spectrum of PC platforms, from DOS to Windows XP.
Up-to-date information on hardware configurations is valuable when planning software installations and upgrades, hardware upgrades and answering support problems. A regular hardware investigation can also detect unauthorized changes, whether they are add-ons, or removals, as could happen with PC memory. Changes are highlighted when detected and recorded in comprehensive PC histories.
Performing Hardware Inventory Operations
To perform an interactive operation, select the Clients or Groups you want to work with, then double-click the appropriate Hardware Inventory Operation:
- The default Hardware Inventory Operation retrieves hardware data from the Client's Offline Area, and presents it in a Hardware Inventory Results dialog. This operation variant does not publish its results to the Database, but you can use the Publish button if you want to update the Database.
- The default Hardware (Publish) Operation automatically updates the Database without displaying the results.
- You can also submit Hardware Inventory Operations as Scheduled Jobs, enabling you to automate the updating of your Site Database.
When you submit a scheduled Job, no Hardware Inventory results are displayed. It typically publishes the data to the Database and generates Event results.Viewing Hardware Inventory Results
The Hardware Inventory Results dialog presents the Hardware asset information across a series of tabs. To view a full list of the tabs in the dialog, right-click on the tabs at the top of the dialog.
Hardware Details Dialog
Capture Date Information
When viewing the Hardware Inventory Results for a Client, the capture date is displayed in the Results dialog title bar.
You can print a formatted report using the Print button. This also allows you to save the printable report in a text file. If you want to save a text file, but you don't want to print it, click the Print dialog's Cancel.
Change Notification
Change notification is provided by red dot indication on individual tabs on the interactive Operation display, and as Hardware Inventory Events. You can click the Changes button to display a popup, which lists tabs that contain changed information.
Note that if you run the Hardware Inventory Operation interactively without publishing to the database, you can recall the current stored hardware details (see "Viewing Stored Hardware Details") and conduct a value-by-value check using the two displays side-by-side. Alternatively, if you Publish the new data to the database, the changes are held in the Changes table in the database.
Viewing Stored Hardware Details
You can view the stored Hardware Inventory data (in the Site Database) by right-clicking on a Client and choosing Hardware Details from the shortcut menu.
Hardware Details in the Console Nodes View
The top-level items of Hardware Inventory data are also displayed in the normal Nodes view in the Console.
This information is automatically refreshed after an operation, and enables you to quickly inspect the key details. The columns in the Nodes View can be resized by dragging the column heading edges, even to the point of hiding a column altogether. The column size settings are persistent, so they are restored in your next Console session.
Hardware Change History
All significant hardware configuration changes to a PC can be viewed using the following methods:
From the Changes button on the Hardware Details tab display
DBViewer enables you to view the changes affecting the selected PC. The Stored Change History view displays all changes on the selected PC; the Stored Hardware Changes view displays hardware changes only. As with all DBViewer-based views, the view supports features such as column ordering, and customizable HTML export.
From the Reports tab in the Operations view
Crystal is used to run the corresponding reports - Hardware History Summary and History Summary. These are fixed format reports, that can be run against all selected PCs.
Note that changes only appear in these reports after the results haven been published to the database.
To remove old changes from the Changes Table (by default, anything older than 60 days), double-click the Purge Old Change History Data Operation in the Console.
Job Logs and Client Logs
A Scheduled Hardware Inventory scan generates a Job Log, which can be viewed by right-clicking in the Jobs window.
The Client Log, attached to the main Job Log, lists all the Nodes and Resources which the Job attempted to process, with a status against each one.
Event Log
Changes in inventory status detected during a scan are held as Events.
Scheduled Inventory scans retain the Events in the Event Log which is accessed from the Job Log.
In common with all operations, the Event viewer allows you to organize Hardware Inventory Events by type, and by PC. For Hardware Inventory, the Event types are as follows:
Printing Hardware Details
The tabbed Hardware Inventory dialog features a Print button. This appears both from an interactive operation with the display enabled and from selecting Hardware Details from the Nodes popup menu, to retrieve stored data from the Database.
The Print button enables you to nominate a specific printer and to change printer settings, and also to save a copy of the report in a text file.
The Event list view and the Job Log list view can both be printed from the File menu.
It is also possible to export selected Events to a file using the Event Viewer shortcut menu's Log to File command.
Customizing the Hardware Inventory Operation
Hardware Inventory Operations are prepared and customized using the Customize Hardware Inventory dialog. To display this dialog, right-click on a suitable Hardware Inventory Operation in the PC-Duo Enterprise Console's Operations View, then choose Customize, and use the tabs to select the options you want to use.
General
Used to name and describe this operation. You can also specify a default Scheduler Host to use when you submit this operation as a scheduled Job.
MIF Support
Enables you to collect Inventory information for Microsoft SMS.
Reporting
Enables you to use the results from the operation to generate a report. This report can be generated in a standard format or in a user-specified format.
Hardware
This tab features the most significant options related to tailoring the various Hardware Inventory settings. The options in this tab are described in the next section.
Hardware Inventory Options
The Customize... dialog's Hardware tab features a number of options which you can modify to customize a Hardware Inventory Operation. These options are discussed below.
Hardware inventory path and file name
This option is reserved for internal use by PC-Duo Enterprise; it must not be changed from its default setting.
Update stored hardware inventory template
This option enables you to store Hardware Inventory data in the database independently in the Hardware Inventory Results table (the table HWMAIN). Such an entry in the Hardware Inventory Results table is called a template.
The hardware information collected from the Client is always be compared against the current template in the Database, to generate Hardware Inventory Events. However, unless this check box is selected, it will not overwrite the existing records in the HWMAIN table.
Update nodes database
If this option is enabled, some of the data items collected from the desktop are written to fields in the NODES table. This relates only to top-level configuration information, such as CPU type, CPU speed, memory size, network address, user name and department.
These items are commonly used to generate Dynamic Groups. Having this data in the NODES table makes the information more accessible when creating Filter Expressions for Dynamic Groups.
Display hardware inventory results
If you carry out an interactive Hardware Inventory of multiple PCs, the Console display can become congested with multiple dialogs. Deselecting this check box prevents the dialogs being displayed. (Any Hardware Inventory Events which are generated are still viewable in the Event viewer.)
Export hardware inventory data
When this check box is selected, the hardware data is exported to the Site Database's numerous hardware tables. These are the database tables typically prefixed with HW, such as HWPRINTER and HWROM.
The value in the Data expiry (days) box refers to the number of days for which this exported data is retained in the Database. For example, if a value of 60 days is specified, any data older than 60 days is replaced when new data is exported to these tables.
If a Data expiry (days) value of 0 is specified, all existing data is replaced when new data is exported, and only the most recently exported data is retained.
We recommend you select the Export hardware inventory data check box for those Hardware Inventory operations which are performed as scheduled Jobs. The numerous hardware tables are crucial to PC-Duo Enterprise's canned Reports, as the Report data is referenced from the hardware tables.
User prompting Options
The options in the User prompting section of the Hardware tab enable you to distribute User Prompt files as part of the Hardware Inventory Operation:
- Select the Refresh user prompt questions check box only if you want to distribute a User Prompt file to Clients.
- The User prompt reference path and file box holds the name of the User Prompt file which will be distributed.
- The Edit button enables you to amend the specified user prompt file using the RefEdit utility.
- The Reload button reloads the specified user prompt file, and is typically used after amending the selected User Prompt file.
- The Browse button enables you to select the User Prompt file to be distributed.
Exporting Hardware Inventory Data
If you need to generate a report containing the highest-level Hardware Inventory data, you can use the Hardware Inventory Operation itself. This operation can create a delimited file which can contain any item of inventory data. This facility can be used for any data export requirement, and not purely for report generation. This allows you to layout data exactly as you want, with actual data values for each PC being substituted for tokens in the format definition.
Using the Hardware Inventory Operation itself to generate tokenized reports means that it is possible to access many more fields than are available to Crystal Reports. You can use this facility to create a delimited file for import into an external database. When the data is created by PC-Duo Enterprise, you can use external analysis and reporting tools to further process the data.
For printed reports, the report file format can be laid out using text and space and tab characters, and the tokens placed on the page in the location you want the data printed. Anything that is not a token is printed without alteration.
You can build up your own set of Report template files to load. For data export, construct a single line template format string, with the tokens a suitable separator character. Note that commas may appear in some data items, so we recommend you use a different delimiter character in the token file.
Example tokenized report definitions are available in the Console's install directory:
- SAMPLE.FMT is an example multi-line report that shows substitution of various tokens.
- SAMPLE_EXPORT.FMT is an example delimited file, which could be used to export data for use in an external application.
Refer to the Console Help's Hardware Inventory Report Tokens topic for more information and a comprehensive list of the tokens that are available.
- Many token names are different from the corresponding field names in the Database. Token names must be in Upper Case.
If you don't want to generate tokenized reports every time you run the Hardware Inventory Operation, create a new variant of the operation configured to generate a tokenized report. You can then use this operation variant, and submit it as a scheduled Job.Repeating Scans for Unreachable Clients
Successful Hardware Inventory scans record the date of the last successful update in the $HWDATE field of each Client in the Node Properties Database. You can use this field to create a Dynamic Group which can then be used as the basis for a repeating Job.
For example, the filter expression:
SELECT DISTINCT NODENAME FROM HWUPDATE WHERE HWDATE < #$MM/DD/YY(-31)$#identifies all Clients that have not been successfully scanned for more than a month. This enables you to automatically repeat scan only those Clients whose data is out of date.
Hardware Inventory and Clients
Hardware Inventory must be run locally on each desktop PC to collect inventory data. These programs run regularly under control of parameters in the LUCLIENT.INI file and impose the absolute minimum disruption on Client desktops. They have been designed to be as efficient as possible. For more information on configuring the frequency of data collection, see "Controlling Client Behavior". The LUCLIENT.TXT file in the Client kit also contains details of all settings in the .INI file.
Inventory data is saved in encrypted files for security reasons, so that, for example, users are prevented from editing the memory size of their PC.
Client Components
The Hardware Inventory data capture process collects hardware, system software, and user-specified information from PCs using the following main programs:
CLBOOT16/32
These are the main Client boot control programs. They are responsible for initializing the Client environment (such as configuring file sharing) and sequencing all Client startup functions, some of which are done directly and the remainder are done with the supporting programs listed below. The installation procedure creates a single shortcut which runs the appropriate (16- or 32-bit) program.
LUHSETUP.EXE & LUHDWCHK.EXE
DOS-level hardware test programs, which run on all platforms. They are called from LUHBOOT.BAT and they create and update an encrypted binary file, LUHDWCHK.LOG, which contains low level inventory data.
WINCHK16/32.EXE
16-bit and 32-bit Windows hardware test programs, which provide higher-level inventory data, such as detailed network configuration, Windows display and printer settings. These programs save the resultant data in WINCHK.DAT, another encrypted binary file.
LUSMBIOS.EXE
This program extracts selected data from the BIOS of DMI enabled PCs. This approach removes the need to install DCOM on older PCs in order to use the WMI, and still collects the key items of data.
LUTINFOW32.EXE
User information collection Windows application. LUTINFOW prompts the user to enter customer-specified information such as the PC user's name, telephone number and the PC's physical location.
The questions asked, explanatory text, and default responses, can be customized during Site creation, and included in the Client Kit before Client installation. For more information, see "User Prompting".
These programs are used on all Windows platforms, with the only differences being 16-bit and 32-bit variants where required.
Hardware Inventory Capture for DOS Clients
DOS Clients, which don't ever run any type of Windows, are handled differently and require manual assistance during installation. They are not able to capture as much detail in their data.
DOS Client capture uses the following components:
LUHSETUP.EXE/LUHDWCHK.EXE
LUTINFO.EXE
A DOS version of the user-prompting program.
STARTSRV.BAT
A batch file which sequences these components. This file is also responsible for loading the file access SERVER TSR. This file must be called from AUTOEXEC.BAT, or from some other network startup procedure, once the network and redirector have been installed.
Configuring Clients for Hardware Inventory Capture
It is possible to configure the data capture process to disable some aspects entirely, to disable specific and individual tests, or to ask different questions for the user-prompting stage.
The Client installation process allows you to disable test categories if you want. This may be appropriate if you do not need to use the user prompting facility, for instance, and you can turn it off so that no questions are ever asked.
It is also possible to edit files associated with the Client installation kit to customize the DOS-level test programs precisely, and also to ask different questions of the user.
Disabling Hardware Inventory Components on Clients
PC-Duo Enterprise's Client Hardware Inventory capture components comprise the DOS-level Checker, the Windows Checker, DMI BIOS Checker, and the user-prompting program, which are normally all enabled on all Client PCs.
PC-Duo Enterprise's Client startup process is controlled by the LUCLIENT.INI file. This file is normally located in the PC's \PC-Duo Enterprise directory.
The different methods of changing this file to disable Hardware Inventory components are described below.
Performing a Custom Client Installation
The SETUP program, which is used to install the Client software on all Windows platforms, enables you to select which parts of the Hardware Inventory capture process you want to use. Normally, all capture components are enabled, but you can disable them by specifying the appropriate options when performing a custom Client Installation.
Using the Client Configuration Operation
If the Client software has already been installed, it is possible to use this operation interactively to reconfigure many PCs at once, if necessary.
Editing the LUCLIENT.INI File
You can edit this file to vary the way that the Client software starts.
Disabling the DOS-level Checker
Disabling the DOS-level checker makes all Hardware Inventory functions unavailable. If you do not need any Hardware Inventory support, you should disable the Windows checker and DMI BIOS checker to improve the Client startup speed.
To disable the DOS-level checker, set the following entry in LUCLIENT.INI:
[DOS Checker] Disabled=YesDisabling the Windows Checker
Set the following entry in the appropriate LUCLIENT.INI:
[Windows Checker] Disabled=YesDisabling the DMI BIOS Checker
Set the following in the appropriate LUCLIENT.INI:
[DMI BIOS Checker] Disabled=YesDisabling User Prompting
Set the following entry in the appropriate LUCLIENT.INI:
[User Prompting] Disabled=YesImportant Notes about Disabling Components
The DOS-level checker performs low-level tests of the hardware, which are designed to be harmless. However, it is possible for some unusual hardware/software combination to cause problems. Typically, these problems cause the DOS-level program to report an error, or in rare cases, to hang. These hangs are usually caused by other system-level software that does not respond correctly to the information requests made by the PC-Duo Enterprise checker.
The checker avoids several known bugs. It also supports a mechanism to disable precise tests if they are found to cause a problem. Disabling the tests reduces the level of detail generated, but it allows the testing process to continue.
Only disable the DOS-level checker, if you do not want to use the Hardware Inventory function at all. The checker generates the LUHDWCHK.LOG file, which is crucial to all Hardware Inventory functions.
The Windows checker programs are non-intrusive to the user and they do not make any use of potentially dangerous low-level hardware tests. It is unlikely that you will want to disable this category of tests, but, if you do, you will lose a lot of higher-level inventory data.
 Vector Networks http://www.vector-networks.com Voice: +44 (0) 1827 67333 Fax: +44 (0) 1827 67068 info@vector-networks.co.uk |
| |
|
|
|
