Automatic Enrollment of Windows Devices Using Ivanti

Introduction

The Ivanti Endpoint Manager is a client management tool that helps gather detailed device data, automate software and OS deployments, and fix user issues. This article outlines the steps to deploy the Windows Application (MSI Installer) and enroll devices using Ivanti Endpoint Manager.

This article provides a detailed guide to enrolling Windows devices using Ivanti in three steps:

Prerequisites

Before beginning, provide the UPN suffixes to an HP Service Expert or Business Partner and have the Company PIN. For additional information, refer to the article - Prerequistes for Installing HP Insights Windows Application

1: Downloading and Preparing the Software

Download the device software from https://workforceexperience.hp.com/software.
Download the Windows Application (MSI Installer) and extract the .zip file.
1. For detailed information, refer to the article - Installing Windows Agent (MSI Installer).
Create and assign the Windows Application in Ivanti Endpoint Manager.

2: Using MSI distribution packages

Ivanti supports MSI installation with full status reporting and MSI package recognition. The MSI distribution package type is Ivanti Endpoint Manager's preferred software distribution method. Understanding the MSI parameters will help set up MSI packages.

3: Using MSI Command Line Parameters With Software Distribution

In the above screen, replace the placeholder `companypin` with the actual pin.

When installing an MSI distribution package, Ivanti uses the MSI API calls. MSI installations use two different types of command-line parameters:

Option Parameters

They are the switches used by the Microsoft installation tool, Msiexec.exe. For example, the /q switch is a common switch for Msiexec that silences an unattended installation.

In the Distribution package-properties dialog box, enter MSI option parameters in the Command line field of the Install/Uninstall options pages.
Select the checkbox next to the field to validate the command line.
1. Additional information on Msiexec options can be found at: https://support.microsoft.com/en-us/kb/227091.

Property Reference Parameters

Property references, or public properties, are specific to the MSI file. The parameters are passed to the MSI installation APIs directly. They can be used in the Command line field of an MSI distribution package’s Install/Uninstall options.

The syntax of property references is PROPERTY=VALUE. A common property reference is the Transforms property. This is the property that calls up a .mst (transform) file. More information on property reference parameters can be found at: https://support.microsoft.com/en-us/kb/230781.

The information on an application’s public properties can be obtained from the software installation documentation, the application’s official Website, or by contacting the software vendor directly.

Running an MSI silently

In Ivanti, running an MSI silently is automatically handled under the Install/Uninstall options for a distribution package. To run an MSI silently, go to the Install/Uninstall options page for the desired distribution package and click Quiet mode, no user interaction.

Automating an MSI installation

For many MSI’s, silencing the MSI also automates the installation. In such cases, to automate an MSI installation, select Quiet mode, no user interaction in the distribution package.

Sometimes a property reference is required for the installation to be complete. In such cases, the MSI installer will prompt for a value. During an automated installation, no such prompt will occur. The MSI installation will fail with the standard MSI error 1603, a fatal error during installation. Required public properties should be assigned a value in the distribution package’s Command line field.

Using a transform file with an MSI installation

Answer files for MSI’s are called transform files and end with a .mst extension. Not all MSI installations need a transform file; however, a transform file can be used if there are too many property references that need their values changed or assigned. If supported by the application, an answer file may be created to pass all property reference parameters. Ivanti Endpoint Manager 2018.3 added a transform file generator. For more information, see MSI transform generator.

If a transform file is required but not provided during the installation, error 1603, a fatal error during installation will result. Often the software vendor will have the information needed or a tool to create a transform file for their specific MSI.

Handling reboots with an MSI installation

Ivanti handles MSI reboots using the Agent settings page in the scheduled task properties. Ivanti will automatically pass both the REBOOT=REALLYSUPPRESS and the /NORESTART parameters when Never reboot is selected in the delivery method.

The Always reboot option passes the /FORCESTART parameter.

Reboot only if needed allows the MSI to handle the reboot. If feedback is enabled, the user can be prompted to reboot. It is important to know that MSI supports custom actions. If a custom action initiates a reboot, Ivanti Endpoint Manager can’t prevent this.

MSI Checklist

Ensure the following:

The correct version of the installation files is obtained, including the MSI and all additional files, for a volume license deployment
The information from the software vendor on how to automate and silence the software installation and configuration, and how to handle reboots is obtained
What public property parameters are needed to pass the MSI is known
Whether this MSI needs a transform file to install is known and if so one is created

Contact Us

For any assistance, create a support case or email [email protected]