Step 1: Verify ISE–MDM Integration
Ensure ISE is configured to connect to your MobileIron API and polling is enabled. This is critical for ISE to query the MDM for device registration status
In ISE’s MDM settings, click Test Connection—confirm it successfully retrieves dictionary attributes like RegisterStatus. If this fails, ISE cannot verify device state .
Step 2: Confirm Device Registration Completeness
ISE’s RegisterStatus logic is strict:
The device must have the MDM profile certificate installed, have checked in at least once, and have responded to MDM queries.
In MobileIron, ensure the iPad shows as compliant and registered in Mobile@Work with the profile and certificate fully applied.
If MobileIron shows green checkmarks but ISE still lists "not registered," it may indicate ISE pulled status before the check-in finished.
Step 3: Force a Sync & Re-Test ISE
On the iPad, open Mobile@Work → Settings → Force Check-in.
In ISE, click Test Connection again to confirm API communications.
Re-authenticate the iPad to the network and check ISE logs for posture or MDM status updates.
Re-syncing ensures ISE gets the latest RegisterStatus from MobileIron
Step 4: Adjust Polling Interval & Timing
If ISE polls infrequently, it may miss updates after registration. MobileIron typically checks in every few hours.
In ISE MDM settings, set the polling interval to a value less than or equal to half the MobileIron check-in interval .
Step 5: When Issues Persist
Re-import MobileIron’s SSL certificate into ISE so trust is intact .
Confirm the MobileIron account used by ISE has API access permissions to read device posture and status
Review MobileIron logs to ensure RegisterStatus and compliance data are exposed to ISE.
