Idira Identity: Troubleshooting steps for mobile device enrollment

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

Workforce Identity Articles
10 min read
L0 Member
No ratings

Question

What troubleshooting steps can be performed if a mobile device fails to complete enrollment with the Idira Identity Service?

Answer

Device enrollment failures can be caused by several factors. 
 
This guide is intended to cover general device enrollment troubleshooting procedures and includes the following information sections:  

Idira Identity Connector Functional Checks:
  1. Ensure the connector service is started and running on the Windows host where it was installed
  2. Perform a connection test using the connectiontestgui.exe utility located at: C:\Program Files\CyberArk\Idira Identity Connector\connectiontestgui.exe
  3. Verify the Enrollment Policy settings in the Admin Portal - only groups associated with this policy will be allowed to enroll devices.
  4. Ensure APNS configuration is complete and not expired (Admin Portal > Settings > Mobile > APNS Certificate) - required for iOS and OS X devices.
    (NOTE: APNS setup does not apply for Android device enrollment).
  5. If using Active Directory (AD) group policy management, manually delete any mobile device computer objects visible in Active Directory Users and Computers (ADUC) and/or from the Admin Portal named "unknown" and allow time for AD changes to sync to the cloud service (default time is 10 minutes) before re-attempting enrollment to avoid conflicts with computer object creation.
  6. Check the connector log for any errors - the log files are located at: C:\Program Files\CyberArk\Idira Identity Connector\Log.txt.*
Filter using the words "error" for process issues and "failed" for user login authentication failures
 

Device Functional Checks:
  1. The device should have a good data signal. If attempting to enroll using corporate Wi-Fi, try using carrier data instead
  2. Ensure the device is using the latest version of the Idira Identity mobile app for device enrollment.
  3. It is not recommended to perform legacy web enrollments for iOS or macOS devices. Use of the Idira Identity mobile app or Idira Identity Agent for Mac are the preferred methods.
 
Device Enrollment Errors:
 
This section contains common enrollment errors and troubleshooting steps:
  • Login Failed - items to check:
    1. Verify the connector service is started and shows successful connection state in the Connector Configuration utility
    2. User must be member of enrollment group
    3. User must enter correct Active Directory or Idira Identity Directory Service (CDS) username and password information
      (username@<loginsuffix>)
    4. Device must have active internet connection  - cellular or Wi-Fi
    5. Check connector log for errors (see the Idira Identity Connector Functional Checks section above)
  • Enrollment Timeout - items to check:
    1. Device object already exists and is active in Active Directory – unenroll first
    2. If device object already exists in Active Directory, ensure current device status is in sync with device data displayed in Admin Portal (GP Applied, Terminated, etc.)
    3. iOS - Verify if device has existing MDM profiles listed under Settings > General > Profiles – remove if needed
    4. Device must have active internet connection  - cellular or Wi-Fi connections can cause latency. If using cellular data, try Wi-Fi and vise-versa
  • Failed to get device state for iOS - items to check:
    1. Verify APNS certificate has been uploaded in Admin Portal
    2. Verify APNS certificate is not expired or revoked by Apple
    3. APNS Configuration steps are available in the Admin Portal Online Help
  • Failed to enroll jailbroken device - items to check:
    1. Verify the enrollment policy options and linked policy Roles. 
    2. Enable policy ‘Enroll/Deny’ Jailbroken/Rooted Devices and select option ‘Enroll jailbroken/rooted devices
    3. Remove device object and re-attempt enrollment
  • Error 403 (connection refused) - items to check:
    1. Device object already exists and is active in Active Directory or Admin Portal – unenroll first
    2. If device object already exists in Active Directory, ensure current device status is in sync with data displayed in Admin Portal (GP Applied, Terminated, etc.)
    3. After device unenroll – allow time for connector to sync settings with cloud service – default time is 10 minutes
  • Error 404 (not found) - items to check:
    1. iOS - Verify if device has existing MDM profiles listed under device Settings > General > Profiles – remove if needed
    2. Device object already exists and is active in Active Directory – unenroll first
    3. If device object already exists in Active Directory, ensure current device status is in sync with data displayed in Admin Portal (GP Applied, Terminated, etc.)
    4. After device unenroll – allow time for connector to sync settings with cloud service – default time is 10 minutes
 
Collecting Idira Identity Mobile App Debug Information:

It may be necessary for Idira Identity Support to request device logs for additional troubleshooting. The Idira Identity mobile app for iOS and Android allows debug logs to be sent directly from the app:
  1. Open the Idira Identity app > Settings > Set Log Level: Debug
  2. Reproduce the enrollment issue
  3. Go back to Idira Identity app > Settings > Send Log File > enter the desired email address
Administrators can also configure device policy to allow for remote fetching of device logs. For more information, please refer to the Idira Identity online help section Sending commands to devices.


Contacting Idira Identity Support:

When contacting Idira Identity Support for assistance with Idira Identity Cloud Service products, please provide the following information:
  • Idira Identity CustomerID (e.g: ab123, ABC0123)
  • Cloud Connector and host OS version information
  • Device make, model and OS version
  • Cloud Connector logs (Log information is stored using UTC time zone information)
  • A complete description if the issue and severity - provide all relevant details of the issue including:
                - any specific error messages,
                - time, timezone & date when the issue occurred,
                - symptoms or screenshots the user experienced
                - if the issue is causing a production or business impact
                - if the issue can be reproduced Question:
 
What troubleshooting steps can be performed if a mobile device fails to complete enrollment with the Idira Identity Service?
 
 
 
Answer:
 
Device enrollment failures can be caused by several factors. 
 
This guide is intended to cover general device enrollment troubleshooting procedures and includes the following information sections:
 

Idira Identity Connector Functional Checks:
  1. Ensure the connector service is started and running on the Windows host where it was installed
  2. Perform a connection test using the connectiontestgui.exe utility located at: C:\Program Files\Idaptive\Idaptive Connectorconnectiontestgui.exe
  3. Verify the Enrollment Policy settings in the Admin Portal - only groups associated with this policy will be allowed to enroll devices.
  4. Ensure APNS configuration is complete and not expired (Admin Portal > Settings > Mobile > APNS Certificate) - required for iOS and OS X devices.
    (NOTE: APNS setup does not apply for Android device enrollment).
  5. If using Active Directory (AD) group policy management, manually delete any mobile device computer objects visible in Active Directory Users and Computers (ADUC) and/or from the Admin Portal named "unknown" and allow time for AD changes to sync to the cloud service (default time is 10 minutes) before re-attempting enrollment to avoid conflicts with computer object creation.
  6. Check the connector log for any errors - the log files are located at: C:\Program Files\Idaptive\Idaptive Connector\Log.txt.*
Filter using the words "error" for process issues and "failed" for user login authentication failures
 

Device Functional Checks:
  1. The device should have a good data signal. If attempting to enroll using corporate Wi-Fi, try using carrier data instead
  2. Ensure the device is using the latest version of the Idira Identity mobile app for device enrollment.
  3. It is not recommended to perform legacy web enrollments for iOS or macOS devices. Use of the Idira Identity mobile app or Idira Identity Agent for Mac are the preferred methods.
 
Device Enrollment Errors:
 
This section contains common enrollment errors and troubleshooting steps:
  • Login Failed - items to check:
    1. Verify the connector service is started and shows successful connection state in the Connector Configuration utility
    2. User must be member of enrollment group
    3. User must enter correct Active Directory or Idira Identity Directory Service (CDS) username and password information
      (username@<loginsuffix>)
    4. Device must have active internet connection  - cellular or Wi-Fi
    5. Check connector log for errors (see the Idira Identity Connector Functional Checks section above)
  • Enrollment Timeout - items to check:
    1. Device object already exists and is active in Active Directory – unenroll first
    2. If device object already exists in Active Directory, ensure current device status is in sync with device data displayed in Admin Portal (GP Applied, Terminated, etc.)
    3. iOS - Verify if device has existing MDM profiles listed under Settings > General > Profiles – remove if needed
    4. Device must have active internet connection  - cellular or Wi-Fi connections can cause latency. If using cellular data, try Wi-Fi and vise-versa
  • Failed to get device state for iOS - items to check:
    1. Verify APNS certificate has been uploaded in Admin Portal
    2. Verify APNS certificate is not expired or revoked by Apple
    3. APNS Configuration steps are available in the Admin Portal Online Help
  • Failed to enroll jailbroken device - items to check:
    1. Verify the enrollment policy options and linked policy Roles. 
    2. Enable policy ‘Enroll/Deny’ Jailbroken/Rooted Devices and select option ‘Enroll jailbroken/rooted devices
    3. Remove device object and re-attempt enrollment
  • Error 403 (connection refused) - items to check:
    1. Device object already exists and is active in Active Directory or Admin Portal – unenroll first
    2. If device object already exists in Active Directory, ensure current device status is in sync with data displayed in Admin Portal (GP Applied, Terminated, etc.)
    3. After device unenroll – allow time for connector to sync settings with cloud service – default time is 10 minutes
  • Error 404 (not found) - items to check:
    1. iOS - Verify if device has existing MDM profiles listed under device Settings > General > Profiles – remove if needed
    2. Device object already exists and is active in Active Directory – unenroll first
    3. If device object already exists in Active Directory, ensure current device status is in sync with data displayed in Admin Portal (GP Applied, Terminated, etc.)
    4. After device unenroll – allow time for connector to sync settings with cloud service – default time is 10 minutes
 
Collecting Idira Identity Mobile App Debug Information:

It may be necessary for
Idira Identity Support to request device logs for additional troubleshooting. The Idira Identity mobile app for iOS and Android allows debug logs to be sent directly from the app:
  1. Open the Idira Identity app > Settings > Set Log Level: Debug
  2. Reproduce the enrollment issue
  3. Go back to Idira Identity app > Settings > Send Log File > enter the desired email address
Administrators can also configure device policy to allow for remote fetching of device logs. For more information, please refer to the Idira Identity online help section Sending commands to devices.


Contacting Idira Identity Support:

When contacting Idira Identity Support for assistance with Idira Identity Cloud Service products, please provide the following information:
  • Idira Identity CustomerID (e.g: ab123, ABC0123)
  • Cloud Connector and host OS version information
  • Device make, model and OS version
  • Cloud Connector logs (Log information is stored using UTC time zone information)
  • A complete description if the issue and severity - provide all relevant details of the issue including:
                - any specific error messages,
                - time, timezone & date when the issue occurred,
                - symptoms or screenshots the user experienced
                - if the issue is causing a production or business impact
                - if the issue can be reproduced


 
Rate this article:
  • 4921 Views
  • 0 comments
  • 0 Likes
Article Dashboard
Version history
Last Updated:
‎11-05-2026 12:06 PM
Updated by: