16.2 Enhancements for Asset Management (TIPWeb-IT)

Frontline Education is pleased to announce the latest enhancements for Asset Management (formerly TIPWeb-IT), which includes Jamf School MDM integration.

Jamf School MDM Integration

Frontline Asset Management version 16.2 now officially supports Jamf School MDM integration. This release continues our commitment to flexible MDM connectivity and improves device visibility by syncing key device data directly from the Jamf School API.

This document outlines key capabilities, setup information, feature scope, and usage tips to help users understand and use this functionality effectively.

Key Capabilities

• MDM Field Synchronization: Automatically imports device properties including Device Name, MAC Address, Last Seen Date, OS Version, and MDM Status.
• Nightly Sync via API: A read-only job runs every night ensuring asset data stays current. Devices are matched by serial number.
• On-Demand Sync: District Administrators can initiate a one-time sync via the Jamf School Integration Settings screen to validate credentials or fetch latest data.
• Field Mapping: Jamf School MDM fields are mapped to Asset Management system-defined fields, viewable in the Tags Grid, Tag Information modal, and applicable reports.

Data Fields Pulled from Jamf School

The Jamf School MDM integration currently supports 8 key device fields into Asset Management. At this time, Internal IP and MDM status are not provided though the Jamf School API. 

Setup & Authorization

Enablement Prerequisites:

• JAMF School Administrator Access – You must have administrative access to your JAMF School instance to retrieve API credentials.
• JAMF School API Access Enabled – API access must be enabled within JAMF School settings.
• Asset Management Access – You must be a District Administrator in Frontline Asset Management to configure integrations.

Setup & Authorization:

Follow the steps below to configure the JAMF School integration.

1. Retrieve API Key from JAMF School
   • Log in to JAMF School.
   • Scroll down and select Organization. 
   • Click Settings. 
     
   • In the left-hand menu, scroll down and select API. 
      
   • Click Add API Key.   
     
   • Enter a name for the key. 
   • Assign Read-Only access. 
     
   • Click Apply.
   • Copy the generated API Key.
2. Retrieve Network ID and Domain
   • From the JAMF School dashboard, navigate to: Devices > Enroll Devices  
   • Select Enrollment Options.   
     
   • Scroll to On-Device Enrollment (iOS/macOS).   
     
   • Here you will find: Network ID and Enrollment URL. 
     

Setup & Verification:

1. Log in to Frontline Asset Management with District Administrator rights.  
2. Under Management, click Integration Settings > JAMF School Integrations.  
   • In the Domain field, enter your JAMF School subdomain only. Example: If your URL is https://abc.jamfcloud.com, enter abc
   • In the Network ID field, paste the Network ID from your JAMF School instance.
   • In the API Key field, paste the API Key generated from JAMF School.
3. Click Save to verify the JAMF School credentials entered.  
4. The integration will automatically begin syncing after saving credentials. 

Note: If the Domain, Network ID, or API Key are incorrect or left blank, an error message will display below the field that is either incorrect or missing. 

Jamf School Integration Status: 

The JAMF School Integration Status grid provides visibility into sync activity, including job status, logs, and errors.

The integration grid includes a real-time sync log that displays:

• Started – The date and time the sync began.
• Job ID – A unique identifier for each sync attempt.
• State – Status of the sync (e.g., DataImported, Queued, Processing, Error).
• Notes – Displays summary information for failed jobs or flags issues requiring attention.
• Clipboard Icon – Click to open a detailed breakdown of sync activity for that job.

When you click the log icon for a sync job, you’ll see a timestamped list of steps in the process, including:

• Queued
• Processing
• Authenticated
• DataExtracted (device count shown)
• DataUploaded
• DataTransformed
• DataImportInitiated
• DataImported

Note: If a job fails, the State will indicate Error, and the Log will show which step failed (e.g., Failed to extract data, Access token invalid, or Upload failed) for faster troubleshooting. 

Monitoring, Verification & Data Access     

Nightly Sync Logic

• Runs once every night.
• Matches devices by serial number; no serial, no update.
• Duplicate serials trigger a warning and are skipped.

Verifying a Sync

1. Check the Job History grid for Completed status.
2. Compare values with Jamf School if needed.
3. Open a tag record and confirm MDM fields are populated.

Viewing MDM Data 

Known Limitations

• Duplicate serials are skipped.
• Devices must pre-exist in Asset Management; the sync does not create assets.
• Some data fields may not be populated depending on device type or API availability of the data from Jamf School’s APIs.
• Detailed Import Reports are not supported at this time (e.g. synced 100 devices, 50 were skipped due to duplicate serial number)
• Integration is read-only; no changes are written back to Jamf School (e.g., no OU changes or provisioning/deprovisioning).
• Integration does not support audit workflows currently.
• Some data points may be blank if Jamf School does not supply them for a given device type.
• No CSV download of device import information is available yet to see which serials were updated, skipped or not found. 

Previous Releases

The following are release notes for prior releases.