Service Manager

This is the latest version of the help for Ivanti Service Manager 2018. If you cannot find some of the features described in the help, you may be using an older version of the application. To upgrade the application, click here.
To view the help for the latest version of Service Manager, click here

Getting Started with HEAT Discovery and Auditing

•Overview of Installing and Setting Up HEAT Discovery

•About Consolidation Rules

•About Message Queue Services

Overview of Installing and Setting Up HEAT Discovery

The following provides an overview of the procedures to install and configure gateways and other components.

Only administrators can perform Discovery installation tasks. After the installation, only Discovery Managers can perform inventory auditing tasks.

Ensure that you meet the prerequisites for the machine on which you will install a gateway. You can only install gateways on Windows machines. For Unix, Linux, or Mac environments, you are limited to using LanProbe for discovery. For more information, see Standard Gateway System Prerequisites and Working with LanProbe.

1.Download and install the gateway on a computer. You can install more than one gateway; however, one gateway must be configured as a central gateway.

Best Practice: Ensure that at least one gateway is configured as a central gateway since it is used for all tasks such as remote scan and deploying agents. See Working with Gateways and Home  for more information about the following:

•Gateways and basic installation.

•When to install multiple gateways and a central gateway.

•When to install a Data Center Edition gateway.

If you need to use NetScan or audit ESX servers to discover virtual machines, you must install the Data Center Edition gateway. See also Installing the Data Center Gateway.

2.After you install a gateway, you can run an Active Directory scan to scan computers on the same domain as the gateway. The scan lists all computers on the network, that are not being audited.

Best Practice: Before you start an Active Directory scan, ensure that the gateway is listed in the Active Directory, is logged in with an Active Directory account, and has the appropriate permissions to run the Active Directory query.

3.After you configure and start a gateway, you can do or one of the following:

•Deploy agents to the computers that are not being audited. This allows you to create configuration item records for each device or machine and to manage them.

•Install clients on computers that are remote or not in the intranet. If you cannot install a client agent on a computer, you can run an agentless audit on some computers. See About Running Agentless Audits.

You must enroll all mobile devices before they can be audited. Each device must have the MDI client application installed. For more information, see Working with Mobile Device Inventory (MDI).

4.Perform audits. See Using Audits. When you deploy an agent, it runs an audit. You can run additional audits, either by using the Audit Inventory quick action or by scheduling an audit. The audit returns additional information about the computer such as the software installed on the machine and any attached devices.

•Run LanProbe. See Using the Inventory Settings Workspace.

•Run Netscan to identify devices such as printers, routers, and switches.

About Consolidation Rules

For asset information that is imported, or for assets discovered by other Discovery methods, the following rules identify whether an item is new or an update.

Machines are identified using the following criteria in the order listed:

1.Fully-qualified domain name (FQDN)

2.List of MAC addresses

3.SMBios Guid

If no match is found for any of the criteria, the system treats the item being imported (or discovered) as a new device or asset.

About Message Queue Services

Discovery began using the Service Manager message queue service in Service Manager Release 2015.2 to handle discovery-related message processing tasks. The service provides administrators maximum visibility into the process, and the ability to replay messages. Messages are sent to the queue and then dispatched to the designated handler.

Previously, a Discovery client agent sent messages to the server, which were processed and later discarded. With the message queue service, messages are sent to the queue, enter the queue, are dispatched to the handler to be processed, and upon completion of the task, are moved to the journal queue.

Administrators can access the Integration Queue and Message Queue Journal workspaces to view and track messages.