Ivanti Neurons for MDM connector

The Ivanti Neurons for MDM connector feeds the Portail ZAPP CMDB with the devices managed by Ivanti Neurons for MDM (formerly MobileIron Cloud): Windows PCs and Macs enrolled in the MDM, smartphones and tablets. Portail ZAPP calls the Neurons for MDM API directly: no agent needs to be installed. The screens are reserved for administrators; the Ivanti Neurons for MDM entry is in the Administration › Connectors and automation menu.

This connector is separate from the Ivanti Neurons connector, which reads the inventory of the Ivanti Neurons platform. You can use either or both: a computer managed by both is not duplicated (see below).

What is imported

At each collection, the connector reads the enrolled devices of the chosen device space and creates or updates, in the CMDB:

• for a Windows PC or a Mac: a Computer — name, serial number, Brand and Model, operating system and version, memory, Wi-Fi MAC address and IP address, Primary user (their email address);
• for a smartphone or a tablet (iOS, Android): a Mobile device — name, serial number, brand and model.

A device retired or wiped from the MDM is neither created nor updated.

A known device is not duplicated:

• a computer already imported by another source (Ivanti Neurons, Intune, GLPI…) is matched by its serial number, MAC address or name, and its fields are completed;
• a mobile device is matched by its serial number;
• manufacturers' generic serial numbers ("Default string", "To Be Filled By O.E.M."…) are never used for matching.

Applications: if the Installed applications of computers option is ticked, each PC's applications are imported into the CMDB, except system applications. Disk details are not available.

Primary user: Portail ZAPP looks for the account of the user that the MDM associates with the computer, by their email address, then by their MDM identifier. If no account matches, or if several accounts match, the field is not changed.

Before creating a source

In Neurons for MDM, an administrator creates an OIDC client for an account allowed to read devices. They get:

• the client ID;
• the client secret.

Also note the cluster host: the console address, for example eu1.mobileiron.com for a European tenant.

In Portail ZAPP, save the client secret's value in the Secrets vault: the source refers to that secret by its name, never by its value.

Creating a source

The Neurons for MDM sources page lists the sources with their name, slug, the host called, their schedule and their state. Click + New source and fill in:

• Name and Slug (short identifier; it can no longer be changed after creation);
• Cluster host: eu1.mobileiron.com by default;
• Client ID;
• Secret: pick the secret in the list. If the list is empty, the create one link leads to the secrets vault;
• Device space: leave it empty to read the tenant's default space;
• Installed applications of computers: tick it to import each PC's applications (system applications excluded). The collection takes longer: one call per computer;
• Timeout per call: in seconds, from 5 to 300 (60 by default);
• Schedule (cron, optional): the collection frequency, chosen with the assistant. Without a schedule, the source is only collected by Synchronize now.

Click Save. An invalid entry is reported and nothing is saved.

Testing, synchronizing

On the source page:

• Test connection asks Neurons for MDM for a token, reads the device space and one device; on success, the number of devices announced is shown. Nothing is imported.
• Synchronize now starts a collection in the background; reload the page to see its result in the Last collection box (status, devices imported, errors). The button is also in the source list.

Enabling, editing, deleting

• The button in the Enabled column (Yes / No) enables or suspends the source and its scheduled collection. A suspended source does not synchronize.
• Edit opens the source page; emptying the schedule removes the scheduled collection.
• The trash can deletes the source and its collection, after confirmation. Devices already imported stay in the CMDB.

Error codes

A failed collection, or a refused connection test, shows a code:

A collection that finds no device succeeds, with 0 devices.