Using Network Discovery with Desktop Inventory

Peregrine
Network Discovery
Using Network Discovery with
Desktop Inventory
Version 5.1.1
PART NO: DPND-511-EN08
Copyright © 2003 Peregrine Systems, Inc. or its subsidiaries. All rights reserved.
Information contained in this document is proprietary to Peregrine Systems, Incorporated, and may be used or disclosed only with written permission
from Peregrine Systems, Inc. This book, or any part thereof, may not be reproduced without the prior written permission of Peregrine Systems, Inc. This
document refers to numerous products by their trade names. In most, if not all, cases these designations are claimed as Trademarks or Registered
Trademarks by their respective companies.
Peregrine Systems® and Network Discovery® are registered trademarks of Peregrine Systems, Inc. or its subsidiaries.Microsoft, Windows, Windows NT,
Windows 2000, and other names of Microsoft products referenced herein are trademarks or registered trademarks of Microsoft Corporation. DB2 is a
registered trademark of International Business Machines Corp.
This document and the related software described in this manual are supplied under license or nondisclosure agreement and may be used or copied only
in accordance with the terms of the agreement. The information in this document is subject to change without notice and does not represent a
commitment on the part of Peregrine Systems, Inc. Contact Peregrine Systems, Inc., Customer Support to verify the date of the latest version of this
document.
The names of companies and individuals used in the sample database and in examples in the manuals are fictitious and are intended to illustrate the use
of the software. Any resemblance to actual companies or individuals, whether past or present, is purely coincidental.
If you need technical support for this product, or would like to request documentation for a product for which you are licensed, contact Peregrine
Systems, Inc. Customer Support by email at support@peregrine.com.
If you have comments or suggestions about this documentation, contact Peregrine Systems, Inc. Technical Publications by email at
doc_comments@peregrine.com.
This edition of the document applies to version 5.1.1 of the licensed program.
Peregrine Systems, Inc.
3611 Valley Centre Drive San Diego, CA 92130
Tel 800.638.5231 or 858.481.5000
Fax 858.481.1751
www.peregrine.com
Contents
Chapter 1
Introduction
. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5
The interaction of the components of Network Discovery and Desktop Inventory 6
The Peregrine Appliance . . . . . . . . . . . . . . . . . . . . . . . . 7
The automatic deployment of Scanners . . . . . . . . . . . . . . . . . 7
Scheduling of scan execution . . . . . . . . . . . . . . . . . . . . . 8
Collection and storage of scan files . . . . . . . . . . . . . . . . . . . 8
The Listener . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Scan file enrichment . . . . . . . . . . . . . . . . . . . . . . . . 10
Chapter 2
Setting up Network Discovery to work with Desktop Inventory . . . . . . . 11
The automatic deployment of Scanners . . . . . . . . . . . . . . . . . 12
Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Step 1: Map a drive from Windows workstation to the appliance shared
directories . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Step 2: Make Network Discovery and Desktop Inventory ‘aware’ of each other 14
Step 3: Run Scanner Generator, generate and validate your Scanner configuration
files (Windows workstation and appliance) . . . . . . . . . . . . . . 15
Step 4: Add or define a Scanner Property Group on the appliance . . . . . 15
Step 5: Define a Listener Property Group on the appliance . . . . . . . . 20
Step 6: Apply the Scanner and Listener property groups with one or more IPv4
ranges (appliance) . . . . . . . . . . . . . . . . . . . . . . . . . 22
Step 7: Submit and activate your changes . . . . . . . . . . . . . . . 23
Step 8: Deploy the Listeners to your workstations . . . . . . . . . . . . 24
Downloading the Listener programs from the appliance . . . . . . . . . 25
Install the QuickDeploy Manager Console . . . . . . . . . . . . . . . 26
Contents W 3
Network Discovery
Using QuickDeploy from the Manager Console to deploy the Agent module 27
Manually installing the Agents from a browser on the local Workstation . . 31
Chapter 3
The XML Enricher . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Operating principles . . . . . . . . . . . . . . . . . . . . . . . . . 33
The XML Enricher directory structure . . . . . . . . . . . . . . . . . . 34
Checking the status of the Enrichment process . . . . . . . . . . . . . . 36
Disk space requirement . . . . . . . . . . . . . . . . . . . . . . . . 36
Structure of the enriched xml.gz file . . . . . . . . . . . . . . . . . . . 38
An example of how the data is stored . . . . . . . . . . . . . . . . . 38
Launching the XML Enricher from the appliance . . . . . . . . . . . . . 41
Starting and stopping the XML Enricher service . . . . . . . . . . . . 41
Configuring the XML Enricher on the appliance . . . . . . . . . . . . . 42
Updating the application library used by the Enricher . . . . . . . . . . . 44
Chapter 4
Scanner Generator . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Introduction to the Scanner Generator when being used with
Network Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . 48
The components of a Scanner . . . . . . . . . . . . . . . . . . . . 48
The Scanner Generator pages . . . . . . . . . . . . . . . . . . . . . 50
Differences in the Scanner Generator pages when in appliance mode . . . . . 51
The scenario page . . . . . . . . . . . . . . . . . . . . . . . . . 51
The Appliance Location page . . . . . . . . . . . . . . . . . . . . 52
The Standard Configuration page . . . . . . . . . . . . . . . . . . 53
The Collection page . . . . . . . . . . . . . . . . . . . . . . . . 54
The Software Data page . . . . . . . . . . . . . . . . . . . . . . . 55
The Refilling tab . . . . . . . . . . . . . . . . . . . . . . . . . . 55
The Asset Number tab . . . . . . . . . . . . . . . . . . . . . . . 55
The Scanner Options page
. . . . . . . . . . . . . . . . . . . . . 56
The Scanners To Generate page . . . . . . . . . . . . . . . . . . . 58
The Generating Scanners page . . . . . . . . . . . . . . . . . . . . 58
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
4 X Contents
1
Introduction
CHAPTER
Desktop Inventory collects and maintains an up-to-date view of all
computers in your organization.
The product is able to support all inventory management projects, from the
smallest operational requirement, through to the tactical inventory and the
enterprise level strategic solution.
When used with Network Discovery, the process of maintaining an up-todate IT asset inventory can be automated.
A flexible web-based User Interface is used to configure schedules for
distribution and execution of scanners, retrieval of scan files, etc. Once
Desktop Inventory has been configured, inventory data is automatically
collected, analyzed and published both as internal reports and through a
well-structured database accessible via ODBC.
Introduction W 5
Network Discovery
The interaction of the components of Network
Discovery and Desktop Inventory
The following diagram shows at a high level the interaction of the main
components of Network Discovery and Desktop Inventory.
Management
Workstation
Peregrine Appliance
Scanner
Configuration
files
Population
Scan
Scheduler
Scan
Computer
population
Generate
Scanner
Generator
View
Windows
Viewer
Scanners for
multiple platforms
Retrieve
MIF files
SAI files
Copy
Enriched
Scans
Application
Encyclopedia
Explorer
Inventory
Database
Microsoft
SMS
Publish,
XML
Publish,
ODBC
Integration
Application
Encyclopedia
Server
Connect-It
View
ServiceCenter
6 XChapter 1—Introduction
SAI files
Import/Export
Tra
nsf
e
r
Enricher
Enrich
Inventory
Mapping
Analysis
Workbench
Analyze
Quality check
Scan
Files
WMI
AssetCenter
Built-in Java
Viewer
Using Network Discovery with Desktop Inventory
The Peregrine Appliance
The Peregrine appliance (sometimes referred to as the appliance) can be
made responsible for collecting the scan files generated by the Scanners and
storing them centrally.
The Scanners are distributed to individual computers from the appliance
using the listener. The appliance maintains a schedule dictating which
computers should be scanned and when.
When a particular computer needs to be scanned, the appliance contacts the
Listener on the computer, sends a copy of the appropriate Scanner
configuration file and a copy of the latest Scanner to the computer, executes
it, and retrieves the scan file.
Note: Listener Agents must be deployed to all computers where automatic
scan scheduling and scan file retrieval should take place. See Setting up
Network Discovery to work with Desktop Inventory on page 11 for
information about deploying the Listeners.
Retrieved scan files are stored in a directory on the appliance. A background
process, the XML Enricher, polls this directory for new scan files and
processes them so they can be added to the appliance's inventory database. It
also enriches the scan files with application data and stores these as
compressed XML files accessible from a network share.
The automatic deployment of Scanners
In most cases, the Scanners can be automatically deployed to a computer as
that computer is discovered via the network, and executed as needed.
This mechanism makes Scanner deployment an easy task, as opposed to
situations where deployment has to rely on network login scripts or manual
intervention. Thus, the accuracy and completeness of the collected inventory
data can be very high.
Important: Automatic deployment of scanners is supported on all Win32
platforms, HP/UX, Solaris, AIX and Linux. Scanners must be
deployed by more traditional means for DOS and OS/2
platforms.
The Peregrine Appliance W 7
Network Discovery
Scheduling of scan execution
It is possible to specify a schedule for computer scanning. The schedule serves
at least two purposes.
„
First, although the execution of a scan is designed to be as unobtrusive as
possible to the user of a computer, some users do notice and find it
distracting. So scans can be scheduled to run at a time of day that tends not
to conflict with users.
„
Second, the currency of the inventory depends on the frequency of scan
execution. For example, some users want the data refreshed every week,
others every month. So the frequency of scans can be specified.
Collection and storage of scan files
A Scanner writes a scan file to the local disk of the scanned computer, and the
scan file is transferred to the appliance for storage and processing. There are
a few ways in which the scan file can be transferred:
„
The appliance contacts the computer and transfers the scan file from the
computer. This is the typical case for computers that are permanently
connected to the network. The collection of scan files is scheduled and
controlled to minimize impact on the network. For example, you can
specify what times of day are appropriate for scan file collection, how
many files can be transferred in parallel, and how much network
bandwidth scan collection is allowed to consume.
Note: Collection of scan files is decoupled from the execution of a scan. You
can schedule scans for one time of day, but collect the scan files some
time later using a different schedule.
„
Some computers, for example laptops, are only occasionally connected to
the network. In this case, the scan file can be transferred whenever that
computer connects. Since the connection speed may be slow and the
connection time short, the transfer mechanism gracefully recovers when
the connection is interrupted and can be resumed when the connection is
re-established.
„
Some computers may never be network accessible to the appliance, for
reasons of network topology or security. In this case, it is the responsibility
of the administrator to transfer the scan files from such computers to the
appliance. The appliance supports an SMB network mountable drive for
this purpose. The administrator can simply mount this network drive and
copy as many scan files as required to it.
8 XChapter 1—Introduction
Using Network Discovery with Desktop Inventory
Once a scan file is transferred to the appliance, it is further processed to
recognize software applications (XML enrichment process) and added to the
inventory information stored in the Inventory Database. The resulting
enriched scan file is stored on the appliance for subsequent access by tools
such as Viewer, Analysis Workbench or Connect-It. This enriched scan file is
always stored in compressed XML format. At most one scan file for each
computer is stored, and the name of the scan file is normally derived from the
Asset Tag uniquely identifying the machine. The enriched scan files are
optionally backed up along with other appliance data.
The Listener
The Listener is installed as a service on a remote computer. This service
enables the computer to be securely controlled by managers at any given
time. In Windows NT and 2000, a manager can instantly deploy this service
on computers using the QuickDeploy function.
The Listener (occasionally referred to as the Peregrine Agent) is able to
perform tasks on a computer on behalf of Peregrine applications.
„
The Listener is available on the following platforms: Win32, HP/UX, AIX,
Solaris and Linux.
„
For security reasons, Listener communications are encrypted and
authenticated.
„
The Listener listens and performs requests for Network Discovery. For
example, it can install a Scanner, execute a scan, or transfer a scan file to
the appliance.
„
If a computer is not connected to the network, the Listener is able to detect
when a connection is established and inform the appliance. Thus the
appliance is now able to discover, scan, and collect scan files from,
computers that are only temporarily connected to the network.
The Listener component must be installed on every workstation that will be
part of the inventory process. This can be done automatically for some
Windows-based computers using the QuickDeploy feature, or it may have to
be done manually.
Once installed, the Listener is capable of communication with an installed
appliance. This communication is largely one-way, initiated by the
appliance. The Listener is not able to initiate file transfers, etc.
The Listener W 9
Network Discovery
The Listener is a shared component that is also used by Peregrine Desktop
Administration.
Further information
For further information about the Listener, refer to the Chapter 2, Setting up
Network Discovery to work with Desktop Inventory.
Scan file enrichment
The XML Enricher is a process that runs in the background on the appliance.
It automatically adds application data to new scan files, and then saves them
in the xml.gz format. This process is called scan file enrichment.
Further information
For further information about the XML Enricher, refer to The XML Enricher
on page 33.
10 XChapter 1—Introduction
2
Setting up Network Discovery to work
CHAPTER with Desktop Inventory
This chapter provides a step-by-step approach to getting started when
using Network Discovery with Desktop Inventory.
Some of the steps are carried out on the Windows workstation running
Desktop Inventory and some on the Peregrine appliance running
Network Discovery. We have indicated this where applicable.
Prerequisites
What you should have completed by now:
Setup the appliance successfully for Network Discovery and have a populated
network map.
Installed Desktop Inventory on a workstation (see the Desktop Inventory User’s
Guide for more information on how to do this).
Installed a valid Desktop Inventory license (see the Desktop Inventory Installation
and Upgrade Guide for more information on how to do this)
There are many default configurations already set up for you, and it
would be wise to choose some of these to get started.
Setting up Network Discovery to work with Desktop Inventory W 11
Network Discovery
The automatic deployment of Scanners
The Scanners can, in most cases, be automatically deployed to a desktop as
that desktop is discovered on the network, and executed as needed.
This greatly reduces the effort involved in maintaining an inventory. Since
the process is automated and does not rely on network login scripts or
manual intervention, accuracy and coverage is increased.
Automatic deployment of scanners is supported on all Win32 platforms, HP/
UX, Solaris, AIX and Linux. Scanners must be deployed by other means for
DOS, Win16 and OS/2 platforms, if applicable.
You will need to know what devices are in your network to follow this
procedure. You will be giving Network Discovery a list of IP addresses for it
to find and from which to collect scan data.
Important: You cannot automate the deployment of DOS, Win16 and OS/2
Scanners. You will need to deploy these manually.
Steps
Use the following checklist to track your progress setting up Network
Discovery and Desktop Inventory.
„
Step 1: Map a drive from Windows workstation to the appliance shared
directories on page 13.
„
Step 2: Make Network Discovery and Desktop Inventory ‘aware’ of each other
on page 14
„
Step 3: Run Scanner Generator, generate and validate your Scanner
configuration files (Windows workstation and appliance) on page 15.
„
Step 4: Add or define a Scanner Property Group on the appliance on page 15.
„
Step 5: Define a Listener Property Group on the appliance on page 20.
„
Step 6: Apply the Scanner and Listener property groups with one or more IPv4
ranges (appliance) on page 22.
„
Step 7: Submit and activate your changes on page 23.
„
Step 8: Deploy the Listeners to your workstations on page 24.
12 XChapter 2—Setting up Network Discovery to work with Desktop Inventory
Using Network Discovery with Desktop Inventory
Step 1: Map a drive from Windows workstation to the appliance
shared directories
Before implementation, you will need to make the Shared directories share
on the appliance accessible to windows.
To map a drive letter to the shared directories share on the appliance:
1 Open Windows Explorer on your workstation. Click Start, point to
Programs, point to Accessories, and then click Windows Explorer.
2 On the Tools menu, click Map Network Drive.
3 In Drive, select the drive letter to map to the shared directories.
4 In Folder, type the server and share name of the appliance, in the form of
x:\\<appliance_IP_Address>\share. For example enter:
x:\\172.22.5.2\share
Note: You can use the domain name or the IP address of the appliance.
To reconnect to the mapped drive every time you log on, check the
Reconnect at logon check box.
Support of Network Share
This share is used for several purposes:
„
Scan files for unconnected desktops are deposited to the share for
subsequent processing.
„
Enriched scan files are accessed from the share by other applications such
Viewer, Analysis Workbench and Connect-It.
„
Scanners configuration files produced by Scanner Generator are deposited
here.
The valid login name and password of a user account on the appliance is
required to access the share. Connecting to a share is supported on the
following platforms: Windows 98, ME, NT4 SP3+, 2000, XP and any other
platform supported by a Samba SMB Client.
Steps W 13
Network Discovery
Step 2: Make Network Discovery and Desktop Inventory ‘aware’ of
each other
The activation of the interoperability between Network Discovery and
Desktop Inventory requires several steps.
To make Network Discovery and Desktop Inventory ‘aware’ of each other:
1 From your management workstation, login to the appliance.
2 Go to the Home>Download page and download and run (double-click on)
the DI-ND.reg file.
When asked if the information should be added to the registry, select Yes.
3 Copy the license.reg file sent to you by Peregrine to the following directory
on the appliance:
\license\incoming
This enables the Desktop Inventory license and options in Network
Discovery.
You will now have access to Desktop Inventory related options in the
Network Discovery user interface.
4 Now launch the Desktop Inventory Viewer and check the About box. You
will see that the Network Discovery aware entry indicates that
interoperability has been enabled.
The two applications can now work with each other.
5 On the appliance, go to Status>Current Settings>Installed Licenses to verify
that the Desktop Inventory licenses are in place.
14 XChapter 2—Setting up Network Discovery to work with Desktop Inventory
Using Network Discovery with Desktop Inventory
Note: The licenses for using Desktop Inventory with Network Discovery will
be maximized at the number of devices Network Discovery is licensed for.
For example, if you have a 10,000 user license for Desktop Inventory and
a 5000 device license for Network Discovery, then only 5000 licenses will
be valid here.
Step 3: Run Scanner Generator, generate and validate your
Scanner configuration files (Windows workstation and appliance)
Two screens are different when you use the Scanner Generator in the
appliance mode. These are the first screen and the last screen and are
described in Chapter 4 of this guide.
For the purpose of this procedure, so you can become familiar with the
process, you can also use the sample Scanner configuration files supplied on
the appliance. These configuration files have already been validated.
Alternatively, follow the steps below to create a new Scanner configuration.
To start the Scanner Generator on the Windows Workstation:
X
Select the Scanner Generator entry in the Programs|Peregrine|Desktop
Inventory 7.3.0 submenu of the Start menu.
The Scanner Generator appears.
Create a scanner configuration file called Test and validate it.
Further information
See the Scanner Generator chapter in the Desktop Inventory User’s Guide for
instructions on how to generate and validate Scanner configuration files.
Step 4: Add or define a Scanner Property Group on the appliance
A Scanner Property Group is a named group of Scanner-related settings.
These settings can later be applied to one or more IP Ranges of devices to scan
(see Step 6: Apply the Scanner and Listener property groups with one or more
IPv4 ranges (appliance) on page 22).
These settings allow you to define the following:
„
Assign a name and description to the property group.
„
Choose which Scanners should be run on which devices in your network.
Steps W 15
Network Discovery
For example, if you only want to scan Linux devices in your network, you
can choose to only deploy the Linux Scanner. This setting will allow you
to deploy the correct Scanner to any particular IP range in your network.
Here are the possible options:
Scanner Configuration File for:
„
Win32
„
HP/UX
„
Linux
„
AIX
„
Solaris
„
Choose the maximum bandwidth allowed for scanner deployment.
„
Choose when:
„
Scanners are deployed or upgraded
„
Scanners are run
„
Scan files are retrieved
To define a Scanner property group:
1 From Home Base click Administration > Network Configuration > Scanner
Property Groups > Add a scanner property group.
16 XChapter 2—Setting up Network Discovery to work with Desktop Inventory
Using Network Discovery with Desktop Inventory
The Add a Scanner Property Group page appears:
2 Give the property group a name. For example, ‘Example Scan’
3 Add a description if you want to.
Steps W 17
Network Discovery
Choosing which Scanners are applied to the devices in your
network
You can select Scanner configuration files:
„
For all Scanners in one go (Win32, HP/UX, Linux, AIX, Solaris).
„
For the different platforms individually. To do this, select individual
Scanner Configuration files for each of the platforms. For example, you
may want to select the following:
Scanner type
Scanner configuration
Win32 Scanner
Test
HP/UX Scanner
Hardware only
Linux Scanner
Hardware only
AIX Scanner
Default
Solaris Scanner
Hardware only
We have supplied some predefined scanner configuration files. These are
accessible from the drop down Select from the Scanners list:
a <None> - No Scanner configuration file will be associated with the
Scanner Property Group.
b <inherit> - You can inherit Scanner configuration settings from the
parent IP range.
c <default> - This configuration uses the default inventory settings of the
Scanner Generator.
d <fastsw> - This configuration does a fast software scan of your machines
- no signaturing, file identification, etc.
e <hwonly> - This configuration does a hardware scan only of your
machines
In addition, the drop down lists also show any configuration files that you
have validated. Your Test configuration file will also appear in the list if you
carried out the Scanner configuration file validation step on page 15
correctly.
To choose which Scanners are applied to the devices in your network:
X
Select it from the drop down list, either for all Scanners or for Scanners
individually.
18 XChapter 2—Setting up Network Discovery to work with Desktop Inventory
Using Network Discovery with Desktop Inventory
Setting the bandwidth threshold
In order to avoid congestion of low-bandwidth links, it is possible to set a
bandwidth threshold here. The bandwidth threshold specifies the maximum
bandwidth that will be used when communicating with a single device for
sending the Scanner or retrieving the scan file. There are two options - you
can Set a threshold or Inherit one.
To set the bandwidth threshold:
X
Select one of the two options:
a Set - You can enter the bandwidth threshold in Kb/s Mb/s, Gb/s
b Inherit - The bandwidth threshold will be inherited from it’s parent IP
range. This is primarily of interest in networks where a large number of IP
ranges need to be configured. In this case the setting for many IP ranges
can be changed by changing the parent setting if all of the child IP ranges
have used inherit.
Examples of bandwidth thresholds have been given below:
„
Over a dial up line - 5Kb/s
„
Over a LAN - 1 Mb/s
„
Over a WAN - 10 Kb/s
Note: The default is 0/sec which means there is no limit.
Setting the frequencies of scans
It is the job of scheduling to ensure that the population is re-scanned at
regular intervals to ensure the inventory is reasonably up to date at all times.
These settings allow you to choose when scanners are run, collected, or
upgraded in your network.
To set the Frequency of the scan:
X
The frequency setting determines how often the scan will take place. You can
select from two options:
a If you select the Set button, you can enter the frequency parameters in
Weeks, Days and Hours.
b If you select the Inherit button, the frequency setting will be inherited
from it’s parent IP range.
Steps W 19
Network Discovery
Setting scan schedule properties
Some predefined scanner schedules have been supplied. These are accessible
from the drop down lists:
„
<None> - No scan schedule will be set for the property.
„
<Inherit> - You can inherit Scanner configuration settings from the
parent IP range.
„
<All the time> - The scan schedule property will be in effect all the time.
„
<Weekends> - The scan schedule property will only be in effect on
weekends.
„
<Not during working hours> - The scan schedule property will only be in
effect outside working hours.
„
<working hours> - The scan schedule property will only be in effect
during working hours (i.e. betweeen 9 am and 5 pm).
To set the Scanner upgrade schedule:
This setting determines how often the Scanners will be upgraded.
X
Select an option from the Scanner upgrade schedule drop down list.
To set the Scanner run schedule:
This setting determines when the Scanner can be run.
X
Select an option from the Scanner run schedule drop down list.
To set the Scan file download schedule:
This setting determines when the Scan file will be retrieved from the
workstation to the appliance.
X
Select an option from the Scan file download schedule drop down list.
Step 5: Define a Listener Property Group on the appliance
A Listener Property Group is a named group of Listener-related settings.
These settings can later be applied to one or more IP Ranges of devices to scan
(see Step 6: Apply the Scanner and Listener property groups with one or more
IPv4 ranges (appliance) on page 22).
20 XChapter 2—Setting up Network Discovery to work with Desktop Inventory
Using Network Discovery with Desktop Inventory
To define a Listener property group:
1 From Home Base click Administration > Network Configuration > Listener
Property Groups > Add a Listener Property Group
2 Give the property group a name. For example, ‘Windows Workstations’
3 Add a description if you want to.
4 In the Listener_receive_ports field, select Default to use the default port or
Custom to enter the port on the workstation that the Listener will be
transmitted manually.
5 Once you have done this, click the Submit button. A summary is displayed.
6 Review the changes and summary and scroll to the bottom of the page. If you
are happy with the settings, click the Activate changes button. See page 24 for
an explanation of the purpose of the Activate changes page.
Steps W 21
Network Discovery
Step 6: Apply the Scanner and Listener property groups with one
or more IPv4 ranges (appliance)
In this step we are specifying what to scan and where, by applying the
previously defined Property Groups to a set of IP address.
In this step, we use Property Sets, which are named sets of Property Groups.
You can either use an existing Property Set or define a new one consisting of
different Property Groups.
You should have a good idea of what devices are in your network.
1 From Home Base click Administration > Network Configuration > Add
IPv4 range.
Select the Add by interval option.
1 Enter the Start IP and End IP addresses for the range of computers you want
to scan.
2 In the Property Set/Group drop down list scroll down to the Scanner Group
in the list.
3 Now do one of the following:
22 XChapter 2—Setting up Network Discovery to work with Desktop Inventory
Using Network Discovery with Desktop Inventory
a Select the new Scanner Property Group you created in Step 4: Add or
define a Scanner Property Group on the appliance on page 15. (Example
Scan) and click ... to inspect a summary of the property group. To return
to the Add an IPv4 range page click the Go back to Add an IPv4 Range
link.
Note: You can select one of the many default selections provided. If none of
them suits your needs, you can select “global” for now, and then create
your own configuration that would be best suited to your IP range.
b Give the IPv4 range a name and description (optional) and specify the
settings for the various property groups. You can select one of the many
default selections provided.
- Network property groups
- Community property groups
- Scanner property groups - select Example Scan from the drop down list.
- Listener property groups - select Deploy Listener to Windows
Workstations from the drop down list. This is the Listener property group
you created on page 20.
4 Click the Submit button when you are finished. A screen appears, showing
you the options of where your range can fit into the entire network. Typically,
the first option (selected by default) is the best, but choose another option if
you feel it is necessary.
Important: The Submit button adds this change to a list of changes, but does
not activate the changes. You can make more changes if so
desired and activate them all using Activate Changes as
described in Step 7: Submit and activate your changes.
Step 7: Submit and activate your changes
1 From Home Base click Administration > Network Configuration > Activate
changes.
2 The activate changes page is displayed showing a summary of the changes
you have made.
3 Review the changes and summary and scroll to the bottom of the page. If you
are happy with the settings, click the Activate changes button.
Steps W 23
Network Discovery
The Activate changes page
The Activate Changes page allows the administrator to review all the changes
that have been made before actually having the changes take effect.
You must activate the changes to the system in order to have the changes take
effect.
You will be told how many potential devices will have to be explored, and
given a minimum exploration time (for example, “at least 33 minutes”).
Also, you will be told of any configuration problems detected. You can ignore
the warnings, but do so at your own risk.
If you decide to implement the changes you have made, activating the
changes will update your network configuration.
Step 8: Deploy the Listeners to your workstations
The previously discussed settings allow you to choose a listener port on your
desktops, through which the Listener will communicate with the appliance.
The Listener is installed onto the desktops in your network, and can upload
Scanners to desktops, execute them to collect software and hardware
information and download back the scan data to the appliance for detail
inventory of desktops.
For each of the Scanner types you will need a corresponding Listener on the
computers where it will be run in order for Scanners to be scheduled.
Note: There is no Listener for DOS and OS/2 - therefore these Scanners
cannot be automated.
Ways of deploying the Listener
„
Download the Listener agent from the appliance and manually install it
onto the computer.
„
Download the Manager Console and use QuickDeploy to install the
Listener to many computers at the same time.
24 XChapter 2—Setting up Network Discovery to work with Desktop Inventory
Using Network Discovery with Desktop Inventory
„
You could use login scripts.
„
You could also send out a company wide email instruction employees to
visit the download page on the appliance via their web browser and
download and install the listener on their own machine. For this method
to be successful, users should reach it from /download which is not
password protected (/nm/download is password protected).
Downloading the Listener programs from the appliance
To download the Listener programs from the appliance:
1 Login to the appliance.
2 From Home Base click the Download link. The Download download page is
displayed.
3 There are several Listener related files on this page:
File
Description
manager.exe
The QuickDeploy Console Manager for Windows
agent.exe
The Listener Agent for Windows
Steps W 25
Network Discovery
File
Description
listener-aix.tar.gz
The AIX Listener
listener-hpux.tar.gz
The HP/UX Listener
listener-linux.tar.gz
The Linux Listener
listener-solaris.tar.gz
The Solaris Listener
4 To download a file, click on the file link. A dialog similar to the following is
displayed.
5 Select the Save this program to disk option.
6 Navigate to the location where you want to save the file and Click save. The
installation program is saved to the specified location.
Install the QuickDeploy Manager Console
Important: You must have Administrator privilege to be able to install the
Manager Console.
The Manager Console enables you to remotely install the Listener Agent
module on one or more Windows computers.
26 XChapter 2—Setting up Network Discovery to work with Desktop Inventory
Using Network Discovery with Desktop Inventory
To install the Manager Console on your workstation:
1 Double click on the manager.exe file you downloaded in the previous
procedure. The following dialog is displayed.
2 Click Continue. The console is installed.
Using QuickDeploy from the Manager Console to deploy the
Agent module
To use QuickDeploy from the Manager Console to deploy the Agent
module:
1 From the Workstation where the Manager was installed (see previous
procedure), select Peregrine/Remote Control/Manager from the Start menu.
Steps W 27
Network Discovery
The Manager Console appears after which the QuickDeploy wizard is
launched.
2 The List of computers for deployment setting should be defaulted to Import
from an ND scan. If this is not the case click on this option.
3 Populate the Account, Domain and Password fields. That is, the NT User
having administrative rights on the target computers.
Note: This user should have enough privilege to access the c$ share and run
services on remote computers.
4 Enter the Server address (appliance name or IP address for appliance)
5 Enter the Account login and password for the appliance. For example:
„
Account: admin
„
Password: password
28 XChapter 2—Setting up Network Discovery to work with Desktop Inventory
Using Network Discovery with Desktop Inventory
6 Click the Next button to continue to the Select machines page of the Wizard.
This page presents a list of computers detected on the network and having no
agents.
7 Select the computers on which you want to remotely install the Agent
module.
Steps W 29
Network Discovery
8 Click the Next button to continue to the Confirmation page.
This page lists the names of the computers on which you want to install the
Agent module. Look at the confirmation page to check the list of selected
computers.
30 XChapter 2—Setting up Network Discovery to work with Desktop Inventory
Using Network Discovery with Desktop Inventory
9 Click the Next button to continue to the Start Deployment page.
10 Click Run to launch the remote installation of an Agent module. The length
of time it takes to deploy the Agent module depends on the number of
computers selected. You can stop the deployment process at any time by
clicking Abort.
Note: We advise you to select a small set of computers to avoid large
processing times and massive error reporting in case invalid information
was provided.
11 Click Finish after the deployment process has terminated. The status bar will
indicate that it is 100% complete.
Manually installing the Agents from a browser on the local
Workstation
Instead of using QuickDeploy, you can manually install the Agent from a
remote computer.
To manually install the Agents from a browser on the local Workstation:
1 Access the appliance Download page and click on the agent.exe file link. The
appliance Download page can be found at:
Steps W 31
Network Discovery
http://<appliance-ip>/download
2 The Web Loader is displayed.
3 Click Continue.
Important: The Agent is installed on the machine and will have a key
corresponding to the appliance it comes from. Other appliances
will not be able to talk to it.
32 XChapter 2—Setting up Network Discovery to work with Desktop Inventory
3
The XML Enricher
CHAPTER
The XML Enricher is a process that runs on the Peregrine appliance and
automatically adds application data to scan files. This process is called scan
file enrichment.
When using the XML Enricher on the appliance, it is no longer necessary to
use the Windows-based XML Enricher that is installed with PDI.
Operating principles
When the XML Enricher is running, it looks for new scan files (xml.gz or fsf
format) in a directory on the appliance every 20 seconds.
When a file is found, it processes the file using SAI (Software Application
Index) application recognition. Information about recognized applications
is added to the file data and a separate <applicationdata> section is added to
the scan file.
At the end of the process, a new enriched scan file in .xml.gz format is created
and the original scan file is deleted. If an error occurs, the original scan file is
moved to a failure directory and is not deleted.
Important: If an enriched scan file for the same asset already exists, the old
file is overwritten. The XML Enricher does not support the
storing of historical data.
The XML Enricher W 33
Network Discovery
During the Enrichment process, the Enricher also prepares the data for the
Inventory Database on the appliance. Within an hour of enrichment, data for
a computer will be available for Reports, Aggregation, etc.
Viewer and Analysis Workbench can then use this location for analysis or the
scan file can be processed by a Connect-It scenario.
The XML Enricher can also be used to re-enrich scan files that were enriched
previously. This can be useful after applying a significant update to the
application library.
The XML Enricher directory structure
The enricher uses a directory structure like the following, which resides on
the appliance.
Directory
Explanation
\scans
The base directory
\scans\deferred
The scan file is moved to this location if it is a
device that the network discovery side does not
know about yet.
This only happens when a manual scan was done
and copied to the Scans\Incoming directory.
It eventually gets moved from this directory back
to the Scans\Incoming directory.
\scans\deferred\firstscan
If the Automatically defer all new scans option was
set (see Configuring the XML Enricher on the
appliance on page 42.) the scan file is not
processed.
Instead, it is moved to this directory. Any scan files
in this directory are for the first time a scan file was
seen for a particular computer
This allows the administrator to review the asset
and application data.
When you are satisfied that the data is ok, you can
move it back to the incoming directory.
Note, that new scan files from a computer will not
be processed while a scan file for it exists in this
directory.
\scans\failed
The base failure directory. Failed scans are moved
to a sub directory of this.
34 XChapter 3—The XML Enricher
Using Network Discovery with Desktop Inventory
Directory
Explanation
\scans\failed\corrupt
Scans that cannot be read or may not be scan files
are moved here.
\scans\failed\error
When any other error occurs, scan files are moved
here.
\scans\failed\filter
The scan ends up here if it has an IP address
outside a range that has been configured to allow
scanned devices.
\scans\failed\licence
If too many scans are processed, new scans are
moved here.
\scans\failed\old
Scan files that are copied to incoming but are older
than the one already in the database are moved
here.
\scans\incoming
The incoming directory. The enricher looks for
new scan files here.
\scans\processed
The processed directory. Enriched scan files are
created here.
\scans\processed\mif
The MIF directory. If enabled, MIF files are created
here.
The XML Enricher directory structure W 35
Network Discovery
Checking the status of the Enrichment process
To check the status of the Enrichment process:
1 From Home Base click the Status>Appliance Health>Software
Environment link. The Appliance Software Environment status page is
displayed.
2 Scroll down to the Scan File Processing section.
This section shows the number of scans waiting to be processed, as well as the
number of scans that failed, grouped by failure reason.
If the number of failed scans is too high, this is indicated by an appliance
Health indicator of Warning or Alarm.
Disk space requirement
You will need to have enough free disk space on the appliance to hold all of
the scan files for your organization. As an estimate, each scan file is 200kB in
size (assuming default Scanner options were used). For example, if you are
licensed for 5000 devices, a minimum of 1GB disk will be used.
Method 1: To check how much disk space is left on the appliance using the
Device Manager:
1 From Home Base, click the Find link. The Find panel is displayed.
2 Click the Device icon
3 Enter the IP address for the appliance (you can also type in nmc) and click
Find.
4 If a match is found, a hyperlink for the match is listed in the Find window
and a Device Manager session opens automatically for the appliance.
36 XChapter 3—The XML Enricher
Using Network Discovery with Desktop Inventory
5 Scroll down to the Disk:/ setting and click on the link.
6 In the example above, 476.6 of 988.2 MB (48.23%) disk space is being used.
Method 2: To check how much disk space is left on the appliance using the
Hardware Environment status page:
1 From Home Base click the Status>Appliance Health>Hardware
Environment link. The Appliance Hardware Environment status page is
displayed.
2 Scroll down to the Disk Utilization section.
Disk space requirement W 37
Network Discovery
Structure of the enriched xml.gz file
Scanfile.dtd describes the structure of the scan file in standard DTD format.
By default this file can be found in the following location:
Program Files\Peregrine\Desktop Inventory\7.3.0\Common
Note: The file is a text file, but is easiest to read with an XML reader.
An xml.gz scan file contains a sequence of elements, each of which have
various attributes. Root elements are:
Note to
Connect-It
users
„
<hardwaredata>
„
<applicationdata>
„
<filedata>
„
<storedfiles>
„
<configurationdata>
If using Connect-It 3.0.1 or later, use the DTD to describe the format of the
scan file to Connect-It.
An example of how the data is stored
The following is an example of several sections in an xml.gz file.
<?xml version="1.0" encoding = "UTF-8" ?>
<inventory codepage="1252" locale="English (United States)" fsfmajorver="7"
fsfminorver="10">
<hardwaredata>
<hwAssetData type="shell">
<hwAssetDescription type="attrib">Dallas (15950 North Dallas Parkway) - (Pentium III, 448MHz, 256Mb)</hwAssetDescription>
<hwAssetTag type="attrib">000590 </hwAssetTag>
<hwAssetUserLastName type="attrib">tod.brown@peregrine.com</
hwAssetUserLastName>
<hwAssetUserJobTitle type="attrib">Dallas (15950 North Dallas Parkway)</
hwAssetUserJobTitle>
</hwAssetData>
<hwMemoryData type="shell">
38 XChapter 3—The XML Enricher
Using Network Discovery with Desktop Inventory
<hwMemTotalMB type="attrib">256</hwMemTotalMB>
<hwSwapFiles type="shell">
<hwSwapFiles_value type="shell_value">
<hwMemSwapFileName type="attrib">C:\pagefile.sys</
hwMemSwapFileName>
<hwMemSwapFileSize type="attrib">203</hwMemSwapFileSize>
</hwSwapFiles_value>
</hwSwapFiles>
<hwDOSMemoryData type="shell">
<hwMemConventional type="attrib">640</hwMemConventional>
</hwDOSMemoryData>
<hwCMOSMemory type="shell">
<hwMemExtended type="attrib">260724</hwMemExtended>
<hwMemCMOSTotal type="attrib">261364</hwMemCMOSTotal>
<hwMemCMOSConventional type="attrib">640</hwMemCMOSConventional>
</hwCMOSMemory>
</hwMemoryData>
</hardwaredata>
<applicationdata>
<application versionid=”1111”
publisher=”Microsoft”
application=”Word” apptype=”Office App”
version= “2000 sp2” release=”2000” os=”win” lang=”en”
licencedby=”2222”
/>
<application versionid=”2222”
publisher=”Microsoft”
application=”Office” apptype=”Office App”
version= “2000 sp2” release=”2000” os=”win” lang=”en”
/>
</applicationdata>
<filedata>
<dir name="C:\" date="2048-00-00 00:00:00" contains="-1">
<file name="AUTOEXEC.BAT" size="0" modified="2000-04-03 13:51:04" attr="a"/>
<file name="BOOT.INI" size="288" modified="2000-04-03 15:14:38" attr="rsa"/>
<file name="sd_settings.ini" size="462" msdos="SD_SET~1.INI" modified="200106-14 09:08:44" attr="a">
<verinfo name="DOS 8.3 Name" value="SD_SET~1.INI"/>
</file>
</dir>
Structure of the enriched xml.gz file W 39
Network Discovery
</filedata>
<storedfiles>
<storedfile type="storedfile" name="SYSTEM.INI" size="217" istext="1"
istruncated="0" dir="C:\WINNT\SYSTEM.INI">
<contents encoding="text">; for 16-bit app support
[386Enh]
woafont=dosapp.fon
EGA80WOA.FON=EGA80WOA.FON
EGA40WOA.FON=EGA40WOA.FON
CGA80WOA.FON=CGA80WOA.FON
CGA40WOA.FON=CGA40WOA.FON
[drivers]
wave=mmdrv.dll
timer=timer.drv
[mci]
</contents>
</storedfile>
</storedfiles>
</inventory>
An explanation of the <applicationdata> element
In an enriched XML scan file, the <applicationdata> section contains a list
of applications identified on the computer along with the version IDs.
<applicationdata>
<application versionid=”1111”
publisher=”Microsoft”
application=”Word” apptype=”Office App”
version= “2000 sp2” release=”2000” os=”win” lang=”en”
licencedby=”2222”
/>
<application versionid=”2222”
publisher=”Microsoft”
application=”Office” apptype=”Office App”
version= “2000 sp2” release=”2000” os=”win” lang=”en”
/>
/>
40 XChapter 3—The XML Enricher
Using Network Discovery with Desktop Inventory
The section of code above could be found for a computer with just two
applications on it: Microsoft Office 2000 and Word 2000 (with Service Pack
2 installed). The “licensedby” attribute indicates that MS Word is licensed
by MS Office. In other words, while both are licensable applications, this
computer requires 1 licence for Microsoft Office - with this licence, no
separate Word licence is required.
Launching the XML Enricher from the appliance
The XML Enricher is a pre-installed service. The service is enabled by default
on the appliance and will start processing scan files as soon as the Network
Configuration has been configured and activated.
Starting and stopping the XML Enricher service
Important: You must make sure that the XML Enricher is started and
configured if you want application data to be added to your scan
files.
You may sometimes want to stop and start the XML Enricher service
manually.
To manually start or stop the xml enricher service:
1 From Home Base, click Administration > System Preferences
2 Scroll down to the XML enricher entry.
3 Click Yes to start the service, or click No to stop the service.
4 Click Change to activate the desired state.
Launching the XML Enricher from the appliance W 41
Network Discovery
Configuring the XML Enricher on the appliance
To configure the XML Enricher on the appliance:
1 From Home Base, click Administration > System Preferences>Scanned
Devices. The XML Enricher Configuration page is displayed.
2 Set the options as required..
Option
Description
Application Recognition
All Files
All files are sent to the recognition engine
for processing. This is the default option.
Only Executable Files
Only executable files are sent to the
recognition engine for processing.
No Application Recognition
No files are sent to the recognition engine
for processing.
In this state, no <applicationdata> section
will be added to the scan files.
42 XChapter 3—The XML Enricher
Using Network Discovery with Desktop Inventory
Option
Description
Generate MIF Files
Always
The XML enricher will always produce
MIF files from scan files.
Never
The XML enricher will never produce
MIF files from scan files. This is the
default option.
When SMS is detected
Only scan files with a value in the
hwOSMIFPath field will cause a MIF file
to be produced (i.e. computers where the
SMS client is installed).
Automatically defer all new scans
Yes
If enabled, the following happens when a
scan file is found in incoming:
„ The scan file is looked up in the internal
database (Not the Inventory Database)
„ If the machine has never before been
scanned, the scan file is not processed or
enriched. Instead, it is moved to the
deferred/firstscan directory
„ If the machine has been scanned before,
the enricher checks if there is a scan file
with the same name in the deferred/
firstscan directory. If there is, the old
scan in the deferred/firstscan directory
is deleted and is replaced with the new
one.
This means that it is possible to control
the process if this option is enabled.
When a new computer is scanned for the
first time, the data is not added to the
database until it has been reviewed and
the scan file has been moved back to the
incoming directory.
No
This is the default option.
Merge Priority
See description below
Configuring the XML Enricher on the appliance W 43
Network Discovery
Merge Priority
This allows you to define what to use as the primary data merge keys. It is
only used when scan files are placed in the /incoming directory. If the
Scanners are automatically launched then this is not necessary.
For example, if NetBios Name and Windows Domain are chosen (both
Desktop Inventory and Network Discovery can detect these), then it will use
this information in the scan file to find the matching device in Network
Discovery.
If this was not done, then the Desktop Inventory scans would create new
devices or be merged with the wrong data.
Updating the application library used by the Enricher
When you want to update the application library, do the following:
1 Copy the complete set of SAI files to the /sai directory on the network share.
2 On the appliance, navigate to Administration>Data Management>Validate
SAI
3 Click Validate
The enricher automatically finds and loads all SAI files located in the /sai
directory when restarted.
Error messages
The following table shows the possible error messages you may come across
and what they mean.
Error message
Meaning
A ReadOnly SAI is not
allowed together with
master and national
SAIs
This happens if both a Read Only SAI and a Master SAI
and/or National SAI is found
This file does not match This happens if Master/National SAIs with different
timestamps are found.
the time stamp of the
other master or national
SAI files
This SAI type is not
allowed here
44 XChapter 3—The XML Enricher
The type of SAI file is not allowed. Not relevant for this
release.
Using Network Discovery with Desktop Inventory
Error message
Meaning
The <filename> is not a If a file is not a valid SAI file.
valid SAI
No SAI files found
No SAI files were found in the /sai share.
Only a User.Sai file
found; a Master SAI
must also exist
Only a User SAI was found. No Master SAI file was
found. For a USer SAI file to be used, a Master SAI file
must also exist.
Only one User.Sai file is Multiple User SAI files were found in the directory.
allowed
Too many SAI sets to
add a new one. Delete
some SAI sets.
There is a limit to the number of SAI sets that can reside
in the \sai directory. This limit is 10 sets.
Note: A set of SAIs consists of a group of SAI files you
want to use together.
If this limit is exceeded them this error message is
displayed. You will have to delete a set of SAIs on the
Manage SAI page:
(Home Base>Administration>Data
Management>Manage SAI).
No new SAI to validate. A new SAI has not been found in the \sai directory.
Use ApE to create new
SAI files and upload to
the \sai directory.
Cannot copy file
The file could not be copied.
Invalid name. Valid
characters are a-z, A-Z,
0-9 and underscore.
The file name uses invalid characters.
Invalid name.
Maximum length is 20
characters.
The file name is too long.
SAI set named <sai
The file name is already in use.
name> is already in use.
Cannot create directory The directory name cannot be created.
<dir name>
"Cannot copy file <file
name>
The file could not be copied.
Updating the application library used by the Enricher W 45
Network Discovery
46 XChapter 3—The XML Enricher
4
Scanner Generator
CHAPTER
In this chapter you will find information on the following topics:
„
Introduction to the Scanner Generator when being used with Network
Discovery on page 48
„
The Scanner Generator pages on page 50
„
Differences in the Scanner Generator pages when in appliance mode on
page 51
Scanner Generator W 47
Network Discovery
Introduction to the Scanner Generator when being
used with Network Discovery
The Scanner is configured and generated in Scanner Generator according to
the specifications determined in the planning stage of the inventory. Then
the Scanner is run across the computer population to collect inventory data,
automatically using the scheduling mechanism on the appliance.
Configuration file
Fixed Scanner
Output file
Automatic/
Appliance
Manual
Configured
Scanner
Executable
Scanner
Generator
Customize Scanner
Scan files
Run on computer
Figure 4-1: Summary of Scanner life cycle
The components of a Scanner
A Scanner consists of two files:
„
The Scanner executable file
This file is an executable file. It contains the constant parts of the Scanner:
„
„
strings
„
bitmaps
„
database files
„
the Scanner executable code
„
plug-ins
The Scanner configuration file
The configuration file is a binary file containing the settings for the
Scanner you are currently configuring.
48 XChapter 4—Scanner Generator
Using Network Discovery with Desktop Inventory
When the Scanners are used in the appliance mode, they read the
configuration from a separate configuration file. This is a binary file with
a .cxz extension. The typical size of the configuration file is about 3K. As
the size of the configuration file is significantly smaller than the size of the
complete Scanner, a separate Scanner configuration is useful for repetitive
inventory collection when the configuration of the Scanner has been
altered. In this case only a small configuration file is delivered to the user’s
computer to run with the original Scanner instead of delivering the entire
new Scanner.
The self-contained Scanner executable
When used in stand-alone mode, the Scanner Generator generates selfcontained Scanner executables that consist of a combination of the two files
listed above.
Introduction to the Scanner Generator when being used with Network Discovery W 49
Network Discovery
The Scanner Generator pages
The Scanner Generator is composed of a succession of pages. Each of these
pages displays information or requires user input, such as selection of
options or entry of data items.
There are two scenarios in which the Scanners can be used. This is
determined on the first page of the Scanner Generator. Depending on which
of these scenarios you select, different tab pages are displayed.
Appliance-based inventory
Scenario Page Select method for inventory implementation
Appliance
Appliance Location
Location Page
Page Set up
up where
where the appliance is
is located
located and
and which
which configuration to
to use.
use.
Collection Page Select data types to collect
Hardware Data Page Disable unwanted hardware scanning routines
Software Data Page
Select software setup mode:
Targeted directory Scan
Classic Local Drive Scan
Asset Data Page
Set up a user entry form,
refilling and asset number
options
Drives Tab
Select a pre-defined set of
drives to scan
File Scanning Tab
Select level of file detail
for data collected
Drive Selection Tab
Select detailed options for
drives
Stored Files Tab
Select stored file data to
collect
Directories Tab
Select directories to scan
Plug-Ins Tab
Select plug-in data to
User Entry Tab
Create asset questionnaire
Asset Number Tab
Set options for asset number
and creation of asset number
batch file.
Refilling Tab
Set options for data refilling
Scanner Options Page
Set up saving and UI
options, error messages
and Scanner behavior.
Scanner To Generate Page
Output Options Tab
Set a Scanner description and
output format
Generate Scanner
Configuration
50 XChapter 4—Scanner Generator
Saving Tab
Set default scan file format.
User Interaction Tab
Define how the Scanner
should interact with the user.
GUI Options Tab
Specify which pages will be
visible to the user, and the
Scanner mode.
Errors Tab
Set up customized error
messages and save to a log
file
DOS OptionsTab
Set options to control the
behavior of the DOS Scanner
Using Network Discovery with Desktop Inventory
Differences in the Scanner Generator pages when in
appliance mode
When you select the option the work in appliance mode, some parts of the
Scanner Generator User Interface change. This section highlights those
changes. For comprehensive information on the whole of the Scanner
Generator User Interface refer to the Desktop Inventory Users Guide. Only
changes from Stand-alone Desktop Inventory have been shown here.
The scenario page
On starting the Scanner Generator, the Scenario page appears.
X
Select the Desktop Inventory using Peregrine appliance option.
This option should be used to automatically collect an inventory using
scheduling and launching on the appliance.
In this mode several options in the Scanner Generator have been
preconfigured to facilitate the interoperability with between the Scanners
and the Peregrine appliance. Some options will be greyed out to indicate they
cannot be changed.
Differences in the Scanner Generator pages when in appliance mode W 51
Network Discovery
The Appliance Location page
This page will appear if you selected the Desktop Inventory using the
Peregrine Appliance option on the Scenario page.
This page is used to set-up the appliance location and the configuration to be
used for creating the Scanner file.
To set up the appliance location:
1 Enter the IP address of the appliance.
2 Enter the User Name and Password to access the appliance. The User Names
and Passwords are defined when the administrator sets up the accounts on
the appliance.
Note: The Scanner Generator automatically maps the share
“\\<Appliance_IP_Address>\share”. No drive letter is used for this
mapping. The mapping will remain active even when the Scanner
Generator is exited. If this is not desirable you can use the Windows
Explorer’s Tools->Disconnect Network Drive menu command to
disconnect from the appliance after terminating the Scanner
Generator.
3 Select one of the following configuration sources:
52 XChapter 4—Scanner Generator
Using Network Discovery with Desktop Inventory
a Use default Scanner configuration
Uses default configuration settings for the Scanner.
b Load Scanner configuration File
Reads the settings from a previously saved external configuration file
(.cxz). This file contains the configuration settings only from a previous
Scanner. Typically this file is 3 KB in size.
Click the
button and navigate to the configuration file stored on a local
disk drive or network drive.
You can drag and drop a configuration file onto this page of the Scanner
Generator to automatically load the settings from that file. The path to the
file will be shown in the field here.
4 Click the Next button to continue to the Collection page.
When the Next button is clicked, the Scanner Generator verifies that an
appliance is available at the specified IP address. If not, an error message is
displayed.
The Standard Configuration page
This page is displayed if you selected the Stand-Alone or Manual Inventory
option on the Scenario page.
Differences in the Scanner Generator pages when in appliance mode W 53
Network Discovery
The Collection page
The Collection page is used to select the computer data to be collected.
For inventories configured to use the appliance, the hardware option is
always selected and cannot be disabled as shown in the screen shot above.
54 XChapter 4—Scanner Generator
Using Network Discovery with Desktop Inventory
The Software Data page
The Software Data page is used to select the software scanning method.
This option is disabled
for appliance inventories
Combined Scan
Note: This option is disabled for appliance inventories.
The Refilling tab
In Desktop Inventory using the Peregrine Appliance mode, the Scanners
only save a local scan file, and this file is always used for refilling.
The Asset Number tab
The Asset Number tab is used to set options for managing the asset number
used to uniquely identify a computer.
Differences in the Scanner Generator pages when in appliance mode W 55
Network Discovery
The Scanner Options page
The Scanner Options page is used to set options for controlling the behavior
of the Scanner during the usual scanning process and under exceptional
conditions, as well as options for saving the inventory results.
The Saving tab
The Saving tab page is used to set options for saving the inventory results.
56 XChapter 4—Scanner Generator
Using Network Discovery with Desktop Inventory
The Appliance tab
The Appliance tab is used to choose how the scanner should behave when it
is launched from the appliance and no user is logged in to the target machine.
To define the behaviour of the Win32 scanner when no user is logged in,
select one of the available options:
1 Scan Immediately
No special action is taken by the scanner. Note that the information collected
will be limited by the fact that no user is logged in.
2 Wait until someone logs in
The scanner sleeps until a user logs in to the machine, at which point the
scanner scans the machine. Full information can be collected by the scanner.
3 Exit the scanner
The scanner terminates and does not collect a scan file.
Differences in the Scanner Generator pages when in appliance mode W 57
Network Discovery
The Scanners To Generate page
The Scanners to Generate page is used to specify which Scanners to generate
and where they should be stored.
The Output Options tab
The Output Options page is used to set up Scanner descriptions, save the
configuration to a text file if required and for appliance based inventories
only, the option to name the configuration (.cxz) file.
Note: The configuration file is saved on the appliance as well, using the same
file name as the copy specified here.
The Generating Scanners page
Once you have selected the Scanners to be generated and have clicked the
Generate button, the last page of the Scanner Generator is displayed.
Now that you have generated Scanner configuration files for the Scanners
you want. These will now have to be validated for use on the appliance.
This is necessary to ensure that the configuration options chosen are
compatible with scanners being deployed automatically.
To validate a scan configuration:
1 Choose the name of the configuration file from the drop-down list.
2 Click Validate.
If the configuration is valid, a message The configuration is now in use is
shown.
Desktop Inventory If the scanner configuration already exists, you will be
presented with the following screen.
3 Click the Continue button if you want to replace the Scanner configuration.
58 XChapter 4—Scanner Generator
Using Network Discovery with Desktop Inventory
What happens if the file is not valid
The following table lists the possible error messages you may encounter when
validating a Scanner configuration file:
Error message
Explanation
File is not a scanner configuration file; The file type is not a Scanner
configuration file (.cxz).
cannot read
Hardware detection is disabled
The Scanner configuration file has been
created with hardware detection disabled.
For a Scanner configuration file to be
valid, hardware detection must be
enabled.
Network detection is disabled
The Scanner configuration file has been
created with network detection disabled.
For a Scanner configuration file to be
valid, network detection must be enabled.
Local FSF save is disabled
The Scanner configuration file has been
created with the Local FSF save setting
disabled. For a Scanner configuration file
to be valid, this setting must be enabled.
Use of InfrTool.ini is disabled
The Scanner configuration file has been
created with the InfrTool.ini setting
disabled. For a Scanner configuration file
to be valid, this setting must be enabled.
Offsite FSF save is enabled
The Scanner configuration file has been
created with the FSF save setting enabled.
For a Scanner configuration file to be
valid, this setting must be disabled.
Differences in the Scanner Generator pages when in appliance mode W 59
Network Discovery
60 XChapter 4—Scanner Generator
Index
A
P
Activate Changes 23
Agent module 27
Appliance Location 52
application library 44
Asset Number tab 55
awareness 14
Peregrine appliance 7
Q
QuickDeploy Manager Console 26
R
B
Refilling tab 55
Remote Scanner 51
bandwidth threshold 19
BUS detection 54
S
C
Collection 54
D
disk space requirements 36
G
General tab 55
Generating Scanners 58
L
Listener 9
deploy to workstations 24
download from appliance 25
Listener Property Groups 20
apply to IP range 22
O
Options 56
scan deployment
automatic 12
scan execution 8
scan files
collect and store 8
enrichment 10
scan frequency 19
scan schedule properties 20
scanfile.dtd 38
scanner components 48
scanner deployment
automatic 7
Scanner Generator 15, 47
from the appliance 51
pages 50
Scanner Options 56
Scanner Property Groups 15
apply to IP range 22
Scanners to Generate 58
Index W 61
Network Discovery
setting up Network Discovery and Desktop Inventory 11
Software Data 55
Standard Configuration 53
W
Welcome page 51
X
XML Enricher 33
application library 44
configuring 42
directory structure 34
enrichment process status 36
launching from the appliance 41
xml.gz file 38
62 X Index
September 16, 2003