Category filter
Asset Tag Automation: Syncing Physical IDs with MDM Metadata
1. Overview
Asset Tag Automation refers to the structured process of associating a physical identification sticker (Asset Tag) with its corresponding device record within the Hexnode UEM console. In manual environments, IT teams often maintain separate spreadsheets for asset tags and hardware serial numbers. This can result in “Data Drift,” where physical inventory records do not match the device inventory maintained in the UEM portal.
Hexnode provides a native Asset Tag field under Device Attributes, allowing administrators to store and manage asset identifiers directly within the device record. When populated via supported methods (manual update or bulk editor), this field becomes searchable through the Global Search and visible on the Device Details page. This supports centralized inventory tracking and simplifies audit workflows.
2. Automation Logic
Hexnode manages asset identifiers using Device Attributes, which can be updated via:
- Edit Device Attributes (Remote Action)
- Bulk CSV upload
The functional logic operates as follows:
- If: A device is enrolled and visible under the Manage → Devices section with its hardware identifiers (e.g., Serial Number).
- And: An administrator updates the Asset Tag field using either CSV bulk import.
- Then: Hexnode updates the Device Info section of that endpoint record.
Wildcard Usage:
Hexnode supports specific system wildcards (including %assettag%) in certain configuration contexts. Wildcard availability depends on platform and policy scope. Administrators must verify wildcard support in the specific configuration they are applying.
3. Implementation Workflow
Step 1: Create a Custom Attribute
Hexnode includes a built-in Asset Tag attribute by default under the device information section. No additional configuration is required to use the native field.
If extended metadata is required (e.g., department-specific tracking), administrators may create a Custom Attribute.
For Custom Attributes (Optional):
- Navigate to: Admin → Custom Attributes.
- Click Add Custom Attribute.
Configuration requirements:
- Attribute Type: Device
- Attribute Name: Alphanumeric characters and underscores only.
- Default value: Automatically populated value until manually updated; supports wildcards.
- Data Type: Text (recommended for asset labels containing prefixes).
Once created, the Custom Attribute becomes available across device records and reporting.
Step 2: Bulk Mapping via CSV (For Existing Hardware)
Hexnode supports bulk updating of device attributes using the Edit Device Attributes action.
Prepare a CSV file containing:
- A static device identifier (Serial Number or Device ID).
- Corresponding Asset Tag values.
Procedure:
- Navigate to Manage → Devices.
- Select target devices.
- Click Actions → Edit → Edit Device Attributes.
- Choose the Upload CSV option.
- Map the CSV columns appropriately.
- Execute the action.
This updates the Asset Tag field for the selected devices.
4. Visibility, Search & Reporting
| Feature | Action / Configuration | Expected Result |
|---|---|---|
| Global Search | Enter the Asset Tag value in the search bar at the top of the console. | Returns the associated device record. |
| Device Info Tab | Open device under Manage → Devices. | Asset Tag appears under Device Information. |
| Custom Reports | Reports → Device Reports → Include Asset Tag column. | Generates exportable inventory data including asset identifiers. |
The Asset Tag field is included in device inventory exports and can be leveraged during audit and compliance reviews.
5. Troubleshooting Matrix
| Issue | Root Cause / Resolution Check |
|---|---|
| Data Mismatch | Ensure mapping is performed using a stable identifier such as Serial Number or Device ID. Avoid MAC address (may randomize) and IMEI (cellular-only). |
| Asset Tag Not Updating | Confirm CSV column mapping during bulk upload and ensure devices were properly selected before executing the action. |
| Rename Not Reflecting | Confirm wildcard syntax (%assettag%) is supported in that rename context. Perform Scan Device or restart (if OS rename required). |
6. Audit Checklist
Before deploying across Device Groups, confirm:
- The Asset Tag field (native or Custom Attribute) is properly configured.
- CSV bulk update has been tested on a limited device set.
- Devices reflect correct values under Device Information.
- Global Search successfully retrieves devices using Asset Tag.
- Reports include the Asset Tag column where required.
- Rename actions (if implemented) are validated in supported platforms.