You are currently viewing Ivanti Endpoint Manager software distribution requested through Ivanti Neurons for ITSM self-service portal

Ivanti Endpoint Manager software distribution requested through Ivanti Neurons for ITSM self-service portal

Often, I receive questions about the integrations used in Ivanti Automation. I already described the integration between Ivanti Automation and Ivanti Neurons for ITSM (formally known as ISM). But in this blog, we will go a step further.

What if you can install software from the Ivanti Endpoint Manager requested by the self-service portal of Ivanti Neurons for ITSM?

What is needed to accomplish this masterpiece of integration? Please read this blog, which describes the prerequisites, software, add-ons, and configurations.



IA – Ivanti Automation
EPM – Ivanti EndPoint Manager
ISM – Ivanti Service Manager (new name Ivanti Neurons for ITSM)
API – Application Programming Interface
BO – Ivanti Neurons for ITSM Business Object
SOAP – Simple Object Access Protocol
WSDL – Web Services Description Language


Ivanti acquired a lot of IT companies over the years. Think about RES Software, MobileIron, Cherwell, etc.

Ivanti customers from either of these companies acquired are also buying other Ivanti products and need integrations between the products.

With Ivanti Automation, we can build these integrations. Ivanti Automation comes from the acquired company RES Software and is an incredible tool for automating IT processes but also for integrations between Ivanti products or 3rd party software.

With EPM, we can install software packages for EPM agents, and ISM has a self-service portal that allows users to request all kinds of business-related stuff.

This blog describes how users can request business software to be installed on their devices. This process can even require approval and/or license approval when needed.

Process steps:

  • The user requests a product to install.
  • ISM sends the request to IA (REST API).
  • IA executes the Runbook with the provided information.
  • IA Runbook executes the EPM API to start the Software Distribution (API & WSDL)
  • When EPM finishes the installation, the EPM API reports this back to IA (API).
  • IA sends a completion of the software installation back to ISM to close the request.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.