Please note that MDM integrations are only available with the Lifecycle/Standard billing plan and are currently accessible by request only. For more information, reach out to support.
This article includes the following topics
- 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, then under Integrations click on Connections.
- Here, you can view the available MDM solutions for connection. To link an MDM solution to Velory, simply click Connect next to your chosen option.
- By clicking Connect, you'll be asked to enter your MDM provider's details to link it to your account. Clicking the Read more link will take you to the MDM provider's page, where you'll find detailed instructions on how to retrieve the required information. It's super simple, we promise!
- Once the API key and subdomain are entered and you click Connect, a new connection will be created. It may take about 2 minutes for all devices to be fetched and matched from the MDM provider. After that, devices will be automatically synced every night. So easy!
How it works
Once your Hexnode MDM solution is connected, you can access the connection details and view a dedicated dashboard filled with valuable insights such as devices enrolled and unmatched devices.
Enrolled & Unmatched Devices
You can view Enrolled Devices and Unmatched Devices by clicking on the respective sections within the connection page. This will redirect you to the Hardware Table, with relevant filters applied for better viewing.
In the hardware view, you can filter devices by their status—whether they are enrolled or unmatched—to quickly get an overview.
Data Import
You can edit the Data Import section by simply checking or unchecking the boxes to select which data should be included or excluded during synchronization, default synchronization is done at 6.30am (Stockholm time). By default, all fields are enabled. If you deactivate any field, it will be excluded from future imports starting with the next scheduled sync.
Here’s some extra explanations of some of them:
Model |
The model description of the device |
MDM enrollment date |
The time when the device was first connected with the MDM system |
Last check in |
The last time the device connected with the MDM system |
Device OS |
The operating system’s version in use on the device |
Supervised |
The device has been enrolled automated in the MDM system |
Battery health |
The battery health status, which has the following values: non-genuine The battery isn’t a genuine Apple battery. normal The battery is operating normally. service-recommended The system recommends battery service. unknown The system couldn’t determine battery health information. unsupported The device doesn’t support battery health reporting. |
Total storage capacity |
The total storage capacity of the Device
|
Available storage capacity |
The current storage availability of the Device |
User full name |
The assigned user name from the MDM system |
On a device’s detail page, you’ll find lots of useful information. What you see depends on which data points you've chosen to enable or disable in the connection settings. If nothing is turned off, all the data will be displayed on the device page.
Additional reports
Along with the information available in Velory for the MDM integration, you can also access a customizable report dashboard. This dashboard provides valuable insights, including asset and MDM comparisons as well as enrollment statistics. If you enable the connection and would like the additional report, please contact support@velory.com, and we’ll assist you in setting it up.
Disconnect
To disconnect the MDM solution, simply click the Disconnect Hexnode button on the details page.
When the connection is disabled, all MDM information is removed from Velory, including on the connection page, hardware overview, device details, and CSV export. If you need a record of the data before disconnecting, you can perform a CSV export to capture which devices were linked to which MDM system.
Questions and Answers
How does Velory read information from the customer’s tenant? |
Velory accesses your device information from Hexnode via API. The customer provides Velory with an API key which also regulates what permissions are granted. |
What access is given to the app registration? |
The API key created in Hexnode regulates permissions. It is also possible to opt-out for certain data being transferred when setting up the connection in Velory. |
How does Velory store the information from the customer’s tenant? |
The information is stored in Velory’s database and the customer can control what fields allow us to save from the Hexnode connection page |
How does Velory authenticate against the customer’s tenant? |
Authentication is performed with the API key provided by the customer |
How does Velory store authentication details? |
We encrypt the API key and store it in the Velory database. |