Bulk device registration

Administrators can register a large group of devices using a CSV file that contains the information required for bulk registration. This method is best for the following scenarios:

  • Adding a large number of devices
  • Rolling out multiple devices into a production environment
  • Using web-based registration (for details, see “Web-based registration for iOS and macOS devices” in the Ivanti EPMM Device Management Guide for iOS.)

After the registration CSV file has been imported, Ivanti EPMM completes the following tasks:

  • Creates specified local user accounts, if they do not already exist.
  • Finds specified LDAP user accounts.
  • Initiates the registration process.

This section contains the following topics for bulk registration:

See Registration considerations for points to consider before using this registration method.

Prerequisites for bulk device registration

Verify that the following conditions exist before using bulk device registration:

  • LDAP users specified in the CSV file must be available for selection. Local users that have not been created already will be created as part of the Bulk Registration process.
  • The User Portal role must be assigned to the users.
  • The following information must be available for the device:
    • Phone number (if any)
    • Country
    • Platform

You can register devices using temporary passwords.

Ivanti EPMM does not support creating both a bulk enrollment record and a single device record for the same user. Only a bulk enrollment or a single add device enrollment should be used for a user, not both.

Refer to Bulk device registration for details on how to create a CSV file to use for bulk registration.

Registering multiple devices

For most platforms, the bulk registration method results in user notification by SMS and email. PDA users are notified by email. The SMS contains a live URL link. The email includes a URL, instructions, and the information the user will need to enter during registration. The user can click the live URL in the SMS or enter the URL directly into the device browser to complete the registration process.

If the user does not respond within 48 hours, Ivanti EPMM sends a reminder. After 120 hours, the registration expires. This expiration interval is configurable in Settings > System Settings > Users & Devices > Registration in the field Passcode Expiry. The maximum value is 4320 hours (6 months).


  1. From the Admin Portal, go to Devices & Users > Devices.
  2. Click Add > Multiple Devices to open the Adding Multiple Devices window.
  3. Use the Browse button to select the CSV file containing the bulk registration data.

    You can also select the Sample CSV File button in the to start with a sample file and input the content. Refer to the fields in the Bulk device registration CSV file requirements for details.

    If an LDAP OU or Group is part of the Space criteria, the users in the comma-separated values (CSV) file will be matched against it. From the Devices & Users > Devices > Add Multiple Devices menu, enter a CSV file and click Apply to see the restricted list of users. If the user isn’t in the OU or group, “User not found” displays in the Message column for that user.

  4. Click Import File > Apply.
  5. Review the status columns to confirm that each entry was successfully imported.
  6. If any items failed, scroll to the right and hover over the Message column to display more information.

Bulk device registration CSV file requirements

Note the following requirements when entering your bulk registration content into a CSV file:

  • Local user IDs cannot contain spaces. Spaces are allowed for LDAP users.
  • The Platform field is case sensitive. Enter only uppercase letters in this field.
  • Phone numbers cannot contain spaces or non-numeric characters.
  • Maximum recommended number of device entries per spreadsheet is 2000. Bulk device registration could fail when using a comma-separated values (CSV) file with more than 2000 device entries.

Each line in the file must contain the following fields, separated by tabs or commas, in the following order.

Table 18.   Fields in the bulk device registration CSV file
Fields Description

User ID

Specifies the user ID for either an existing local user, a local user to be created, or an LDAP user that can be looked up as an LDAP user on the configured LDAP server. Spaces are not supported for local users.
Example: jdoe

Country Code

Specifies the country code corresponding to the phone number.
For PDAs, such as the iPod touch, enter 0 in this field.
Example: 1


Specifies the phone number (without country code.)
For PDAs, such as the iPod touch, enter PDA.
Example: 4085551212


Specifies the service provider name. This field is not required for PDAs, such as the iPod touch, or for countries having a country code other than 1. See Services > Operators for a list. If the operator does not appear in this list, contact Ivanti Technical Support.
Example: Sprint


Specifies a character indicating the operating system. Use the following character:

  • A: Android
  • I: iOS
  • L: macOS
  • E: Windows and Windows Phone

Entries are case sensitive.
If the specified platform has been disabled for registration, then the registration will fail. For details, see the section “Specifying eligible platforms for registration” in the Ivanti EPMM Device Management Guide for your operating system.
Example: A


Specifies phone ownership. Use the following characters:

  • C: Company
  • E: Employee

Example: C


Specifies the identity source of the user name. Use the following characters:

  • D: Directory (LDAP)
  • L: Local

Entries are case sensitive.
Example: D

First Name

If the Source field contains “L”, provide the user’s first name.
Example: John

Last Name

If the Source field contains “L”, provide the user’s last name.
Example: Doe


If the Source field contains “L”, provide the user’s email address.
Example: [email protected]


Specifies the password to set for a new local user account. If you do not intend to use this field or the user is an LDAP user, then you can leave it blank.
Example: p@$sW0rd

Device Language

Optional. Specifies the language to use for communicating with the device user if the device has not reported its locale.

  • de - GERMAN
  • en - ENGLISH
  • es - SPANISH
  • fr - FRENCH
  • it - ITALIAN
  • ja - JAPANESE
  • ko - KOREAN
  • nl - DUTCH
  • pl - POLISH
  • ro - ROMANIAN
  • ru - RUSSIAN
  • sk - SLOVAK
  • zh - CHINESE Simplified (Default)
  • zh_tw - CHINESE Traditional (Taiwanese)

Example: ja-JP

User Display Name

Optional. Specifies an alternate name used to identify the device user. If you leave this field blank, then the display name will have the following format:
Firstname Lastname
Example: Smith, Ken

Notify User

Specifies whether to send an email concerning registration status to device users. For example, if you are in possession of the phone, and notifying the user about registration activities is not necessary, then set this option to FALSE. Specify TRUE if the device is in the owner’s possession.

Serial Number

Lists device serial numbers.

Notify User by SMS

Optional. Specifies whether to send an SMS regarding registration status to devices. Set this option to FALSE if you are in possession of the device, or if sending bulk SMS messages would be too costly. Set to TRUE if you want to notify device users of their registration status via SMS. If set to true, the device must have a phone number registered with Ivanti EPMM.

This field is enabled by default.

Include Apple Device Enrollment Only Registration Pin (TRUE or FALSE)

For iOS and macOS devices only.

Specifies whether to enable PIN-based, anonymous enrollment using Apple Device Enrollment.

For more information about anonymous Apple Device Enrollment, see “Creating Apple Device Enrollment profiles” and “Assigning Apple Device Enrollment devices to an enrollment profile en masse” in the Ivanti EPMM Device Management Guide for iOS Devices.

Include Android Corporate Device Enrollment Only Registration Pin (TRUE or FALSE)

For Android devices only.

Specifies whether to enable PIN-based registration enrollments for Android Corporate devices.

For more information, see "Registering Android devices" in the Ivanti EPMM Device Management Guide for Android and Android Enterprise devices.