Hello,
Thank you for reaching out to Hexnode Connect! I completely understand your concern; managing devices on a strict bandwidth budget is challenging, and unexpected data spikes can certainly be alarming.
I’d like to help clarify how our location tracking works and offer some insight into what might actually be happening here.
To address your team’s theory: a single Scan Device Location ping consumes roughly 5KB of data. Even with highly frequent tracking intervals throughout the month, this action is incredibly lightweight and is significantly lower than the 200-300MB range you are seeing.
I want to assure you that the Hexnode app’s routine background syncs and core operations are not the cause of a data surge of this magnitude. When carriers report high data usage under an MDM app, it is almost always indicative of large data movement commands being routed through the MDM, rather than the app’s baseline functionality.
I highly recommend re-assessing the data usage patterns and recent action histories for that specific set of devices. The data leak is likely stemming from:
- App Installations or Updates: Pushing large enterprise applications or app updates to these devices.
- OS Updates: Automated or forced OS updates being downloaded.
- File Syncing: Pushing heavy media files, documents, or scripts to the devices via Hexnode.
Next troubleshooting steps:
Take a look at the Action History in your Hexnode portal for the devices in question during the timeframe reported by your carrier. Check if any bulk app deployments or OS update policies were executed.
We are always here to help you get to the bottom of this. Please feel free to reach out if you have any further queries, need assistance looking through your portal logs, or if you’d like to share any ideas and feedback here on Hexnode Connect.
Best regards,
George,
Hexnode UEM
5 Views
