👉 Note! MDM integrations are only available on the Standard and Pro billing plans and require activation upon request. Please contact Velory Support for more information.
🧠In this guide:
- How to connect Hexnode MDM with Velory
- How it works
- Additional Reports
- Disconnect
-
Questions and Answers
How to connect Hexnode MDM with Velory
Go to your profile in the navigation bar and click on Settings.
Under Integrations, select Connections.
Here, you’ll see the available MDM solutions. Click Connect next to Hexnode to begin the integration process with Velory.
When you click Connect, you’ll be asked to enter your MDM provider details. The Read more link will take you to Hexnode’s support page with step-by-step instructions. It’s super simple – we promise!
Once you’ve entered the API key and subdomain, click Connect. It may take up to 2 minutes to retrieve and match all devices from Hexnode. After that, synchronization will occur automatically every night.
How it works
Once Hexnode MDM is connected, you’ll see the connection details on an overview page containing information about:
- Devices that are enrolled
- Devices that are unmatched
Enrolled & Unmatched Devices
Within the connection page, you can click on Enrolled Devices or Unmatched Devices to go directly to the Hardware Overview with relevant filters applied.
You can also apply additional filters directly in the hardware view based on device status.
Data Import
In the Data Import section, you can choose which information should be included during synchronization. All fields are enabled by default. Synchronization occurs daily at 6:30 AM (Stockholm time).
Uncheck any fields you don’t wish to import – changes take effect from the next scheduled sync.
Available data fields
-
Model – Device model description
-
MDM enrollment date – The time the device was first enrolled in the MDM system
-
Last check-in – The last time the device connected to the MDM system
-
Device OS – Operating system version
-
Supervised – Indicates whether the device was automatically enrolled
-
Battery health – Battery health status:
-
non-genuine – Not a genuine battery
-
normal – Operating normally
-
service-recommended – Battery service recommended
-
unknown – Battery status could not be determined
-
unsupported – Device does not support battery health reporting
Read more in Apple’s official documentation
-
non-genuine – Not a genuine battery
-
Total storage capacity – Total storage capacity of the device
-
Available storage capacity – Available storage space on the device
-
User full name – Assigned username from the MDM system
All activated fields will be visible on the respective device’s detail page.
Additional Reports
You can access a customizable reporting dashboard which includes:
- Asset comparisons between Velory and Hexnode
- Device enrollment statistics
If you want to activate this report, please contact us at support@velory.com and we’ll help you get started.
Disconnect
To disconnect Hexnode, click Disconnect Hexnode on the connection page.
When the connection is removed, all MDM-related information will be deleted from Velory, including:
- The connection page
- Hardware overview
- Device details
- CSV exports
If you wish to keep a copy of the data before disconnecting, export it as a CSV file.
If the connection is inactive, try disconnecting and reconnecting. If the status doesn’t update, please contact Support for assistance.
Questions and Answers
Question | Answer |
How does Velory retrieve information from the customer’s tenant? |
Through Hexnode’s API using the API key provided by the customer. The API key also controls permission levels. |
What access is granted to the app registration? |
The API key controls which permissions are granted. You can also opt out of certain data fields during the Velory setup. |
How does Velory store the information from the customer’s tenant? |
The data is stored in Velory’s database. Customers can choose which fields are saved. |
How does Velory authenticate against the customer’s tenant? |
Authentication is performed using the customer-provided API key. |
How are authentication details stored? |
The API key is encrypted and securely stored in the Velory database. |