Ivanti Endpoint Manager connector

The Endpoint Manager connector gathers data about devices from Ivanti Endpoint Manager (EPM).

The Endpoint Manager connector requires SQL Server 2012 or newer as the database for Endpoint Manager. SQL Server 2016 is recommended.

The following fields must all exist in order for the device to be imported:

  • Host name
  • Physical address
  • IP address
  • Last hardware scan date

All of the information in the inventory scan is imported, including:

  • Agent State
  • AMT Information
  • Asset Info
  • Battery
  • BIOS
  • BitLocker Information
  • Browser
  • Bus
  • Clustering
  • Compliance State
  • Configuration Files
  • Database
  • Detected Patch and Compliance Definitions
  • Diagnostic Data
  • Docker
  • Environment
  • Field Replaceable Unit
  • Firmware Vital Product Data
  • Hardware Vital Product Data
  • Health
  • iPAQ
  • IPMI Management Channel
  • JAMF Information
  • Keyboard
  • LANDesk Management
  • LaunchPad
  • LDAP Groups
  • LDAP User
  • Leasing Information
  • Local Users and Groups
  • Location
  • Manufacturer Parts
  • Mass Storage
  • Memory
  • Mobile Broadband
  • Mobile Devices
  • Modems
  • Motherboard
  • Mouse
  • Network Adapters
  • Network
  • OS
  • Owner
  • Partner Tools
  • Patch and Compliance scan summary
  • PDA
  • Point-of-Sale Peripherals
  • Ports
  • Power Management
  • Printers
  • Processor
  • Remote Access Controller
  • Resources
  • Scheduled Task
  • Security
  • Sensors
  • Server Manager
  • Software
  • Storage Cards
  • System
  • Video
  • Warranties

When you use a connector for Endpoint Manager, the connector server should be installed in a location where it can contact both the Endpoint Manager core server and the Neurons server. You should not run the Endpoint Manager connector while database maintenance is happening.

An Endpoint 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.
  • SQL Server name. The IP address or DNS name of the server where the Endpoint Manager database is running. If you need to specify a port, append it after the server name, with a comma (no spaces) between the two items.
  • SQL database. The name of the Endpoint Manager database.
  • Username and Password. Credentials to access the Endpoint Manager database. The account must have read and write privileges.
  • Authentication. The type of authentication.
  • Import devices from Asset Control. If you are using Asset Control, include the devices in the import. Asset Control is a Data Analytics tool. For more information, see the Data Analytics help.
  • 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 Ivanti Neurons uses to perform actions and queries on device or people records. The types of available actions and queries will depend on your specific work environment. The core server credentials must have privileges on server where Endpoint Manager is installed, and the Endpoint Manager credentials are to access the application itself. Members of the LANDESK Administrators User Group typically satisfy both credentials requirements.

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