Ivanti Service Manager connector

The Service Manager connector gathers data about devices and users from Ivanti Service Manager (ISM) using the Service Manager SOAP API. When users or devices have a ticket associated with them, information about the ticket is also included.

The connector imports data from Service Manager to Neurons. If you want to import data from Neurons to Service Manager, see Import Discovery Data from Ivanti Neurons in the Service Manager help.

  • BIOS UUID
  • Computer location
  • Device ID
  • Host name
  • Discovery ID
  • Domain name
  • Device name
  • Last policy sync date
  • Last software scan date
  • LDAP location
  • Login name
  • MainBoard OEM Name
  • Primary owner
  • Username
  • System OEM name
  • Identity type
  • Asset tag
  • BIOS date, version, and manufacturer
  • Serial number
  • Service tag
  • SMBIOS version
  • UEFI enabled
  • OS and OS version
  • Drivers
  • Total memory
  • Storage type, manufacturer, serial number, and size
  • Logical drive storage, available storage, format, type
  • Memory slot number, size, description, form factor, manufacturer, asset tag, part number, speed, and type
  • Processor manufacturer, name, count, speed, model, and serial number
  • Network adapter vendor, model, description, driver
  • Display adapter type, model, RAM, description, and manufacturer
  • Connected monitors' serial numbers, manufacturers, and dates of manufacture
  • MAC address
  • IP address
  • Subnet mask
  • Manufacturer and model
  • Has battery
  • Chassis type
  • Board name
  • Express service code
  • Software titles, versions, sizes, and manufacturers
  • When users or devices have a ticket associated with them, information about the ticket is also included

When you use a connector for Service Manager, the connector server should be installed in a location where it can contact both the Service Manager server and the Neurons server. For additional information about making sure Service Manager installed on-premise is set up correctly, see Configuring ISM On-prem to connect to Cloud.

A Service Manager connector has the following options:

  • Connector name. A name for the connector.
  • Connector server name. The name of the connector server that this connector is associated with. Each connector can only be associated with one connector server. If you added the connector to a specific connector server, this field may be populated for you. Otherwise, you can select the connector server from the list.
  • Server name. The IP address or DNS name of the Service Manager server. If your instance of Service Manager is on premises, you must add /HEAT to the Server Name. For example: servername.example.com/HEAT
  • Tenant ID. The tenant ID (also known as the tenant URL) for your instance of Service Manager. The Tenant ID is the same as the "TenantURL” field in the Tenants business object in the Service Manager Configuration database.
  • Username and Password. Credentials to log in to Service Manager. We suggest you use a service account that doesn't need the password changed frequently.
  • Role name. A role assigned to the username that has permissions to view and edit all objects. This can be either a default role or a custom role, as long as it has the correct permissions.
  • Repeats. How often the connector should gather data.
  • Start time. The time of day the connector should start running. To minimize the impact on your network and applications, we recommend that connectors generally run at night or on weekends.
  • Active. Whether the connector is active or not. While the connector is active, it runs according to the schedule you create. If you clear the check box, the connector is inactive and will not gather data until the check box is enabled again and the connector is saved.
  • Action Credentials. The credentials used to send actions from Neurons to Service Manager. If your instance of Service Manager is on premises, you may need to add /HEAT to the Server Name. For example: servername.example.com/HEAT

For details on configuring or using connectors, see Setting up connectors.