Introduction
In some projects, you may need to record device information that is not available from your primary inventory source in ManagementStudio. For example, you might need to track critical devices located behind a firewall. In such cases, project administrators can manually import device information using an Excel source file. This article outlines the fields available for device import.
For more information on data imports, refer to the Data Importer article.
Available Device Fields
The following table describes the fields that can be included when importing devices via Excel:
| Field Name | Description | Required? |
|---|---|---|
DeviceId | Unique identifier generated by ManagementStudio when a device is imported. Creating a New Device: Leave this field blank when importing new devices. ManagementStudio assigns a DeviceId during the import.Updating an Existing Device: Provide the DeviceId to ensure the import updates the correct device. To obtain DeviceIds for existing devices:- Navigate to the Devices module in ManagementStudio. - Click Select All on the toolbar. - Use the Copy dropdown and select Export to Excel All. ![]() | Yes, when updating existing devices |
HostName | The network-assigned name of the device. | Yes, when importing new devices |
Domain | The network to which the device belongs. | Yes, when importing new devices |
AssetTag | An identifier or tag used for asset tracking. | Yes, when importing new devices |
Start Date | Date the deployment unit starts. | No |
Device Type | Classification grouping (e.g., Laptop) for processing purposes. | No |
Operating System | Software platform running on the device (e.g., Microsoft Windows 7 Enterprise). | No |
Process Status | Internal process status for the device. | No |
Service Pack | Updates, fixes, or enhancements delivered in a single installable package. | No |
Process | Device’s current process. Set during import to override the default (e.g., set to 5. Scheduling instead of default 1. Identified). | No |
Sub Process | Device’s sub-process, used in conjunction with Process to ensure correct categorisation (e.g., if Process is 5. Scheduling, Sub Process can be Scheduling Queue or On Hold). | No |
Migration Type | Type of device migration (e.g., Kiosk, Normal). | No |
Status | Current status of the device. | No |
Deployment Unit | Deployment unit the device belongs to. | No |
Priority | Device priority: typically Low, Medium, or High. Used to record device importance. | No |
DU Location | Location details for the deployment unit. | No |
Assigned To | Person assigned to this device within the project. | No |
Migration Slot Start | Device migration start date. | No |
Make | Manufacturer of the device (e.g., Lenovo). | No |
Migration Slot End | Device migration end date. | No |
Model | Model of the device (e.g., ThinkPad T450). | No |
Processor | Device’s processor (e.g., Core i5, Pentium). | No |
Memory | Immediate-access storage size (e.g., 8GB). | No |
Architecture | System architecture (e.g., 32-bit, 64-bit). | No |
Build Version | Device build version (e.g., 19041.804). | No |
IP Address | Unique network identifier (e.g., 172.16.254.1). | No |
Mac Address | Unique network interface identifier (e.g., 00-14-22-01-23-45). | No |
SM Bios Guid | Data structure for management information produced by the BIOS. | No |
Further Support
If you require further assistance, visit the ManagementStudio Service Desk to search the knowledge base or to raise a support ticket.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article
