15.2 Enhancements for Asset Management (TIPWeb-IT)

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

Release Overview

Highlights include:

• Mosyle MDM Integration

Mosyle MDM Integration

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

Key Capabilities

• MDM field synchronization: Automatically imports device properties, including device name, MAC address, last seen date, latitude/longitude, OS version, and MDM status.
• Nightly sync via API: A read-only job runs every night to keep asset data current. Devices are matched by serial number.
• On-demand sync: District administrators can initiate a one-time sync from the "Mosyle Integration Settings" screen to validate credentials or fetch the latest data.
• Field mapping: Mosyle 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 Mosyle

The Mosyle MDM integration currently supports eight device fields in Asset Management. At this time, external IP is not provided through the Mosyle API.

Setup and Authorization

Enablement Prerequisites

• Mosyle admin rights: You must have full administrator access in Mosyle, including permission to create users, roles, and API tokens.
• Mosyle subscription: Mosyle Manager Premium is required to enable API integration.
• Mosyle API-based administrator account: The district must create an API-only administrator and generate an API token that allows read access to devices for Frontline Asset Management.
• Frontline Asset Management access: You must be a District Administrator in Frontline Asset Management to configure integrations.

Setup and Verification

1. Log in to Frontline Asset Management with District Administrator rights.
2. Under Management, select Integration Settings > Mosyle Integrations.
3. In the Access Token field, paste the API key with device-read access, generated from the Mosyle manager console.
4. In the API Username/Email field, paste the API-based administrator account email from the Mosyle manager console.
5. In the API Password field, paste the API-based administrator account password from the Mosyle manager console.
6. Click Save to verify the Mosyle credentials entered.
7. Click Initiate One-Time Sync to run the first sync manually.

Mosyle Integration Status

The "Mosyle Integration Status" grid gives administrators a clear view into recent sync activity between the Mosyle MDM and Frontline Asset Management, including job status, logs, and error tracking.

Real-Time Sync Log

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 (for example, "DataImported," "Queued," "Processing," "Error")
• Notes – Summary information for failed jobs or flags for issues requiring attention
• Clipboard Icon – Click to open a step-by-step breakdown of sync activity for that job

When you click the log icon for a sync job, you will see a timestamped list of every step in the process, including:

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

Monitoring, Verification, and Data Access

Nightly Sync Logic

• Runs once every night
• Matches devices by serial number (i.e., no serial, no update)
• Duplicate serial numbers trigger a warning and are skipped.

Verifying a Sync

• Check the "Job History" grid for "Completed" status.
• Compare values with Mosyle if needed.
• Open a tag record and confirm that MDM fields are populated.

Viewing MDM Data

Known Limitations

• Duplicate serial numbers 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 availability of the data from Mosyle’s APIs.
• Detailed import reports are not supported at this time (e.g., synced 100 devices; 50 were skipped due to duplicate serial numbers).
• Integration is read-only; no changes are written back to Mosyle (e.g., no OU changes or provisioning or deprovisioning).
• Integration does not currently support audit workflows.
• Some data points may be blank if Mosyle does not supply them for a given device type.
• No CSV download of device import information is yet available to see which serial numbers were updated, skipped, or not found.

Previous Releases

The following are release notes for prior releases.