Stay organized with collections
Save and categorize content based on your preferences.
This reference lists the allowed values used to identify Android devices by
zero-touch enrollment. Both the APIs and portal's CSV importing check values
against the lists in this reference.
To help avoid errors when you claim devices for a customer, you
identify each device using a hardware ID or
metadata and the manufacturer's name. A combination of values helps prevent
provisioning the wrong device because of a mistyped ID.
Manufacturers
To identify the correct manufacturer value to use, ask the device manufacturer,
or use adb to query the
value from the device with the following command:
console
adb shell getprop ro.product.manufacturer
.
Models
To identify devices by serial number zero-touch enrollment uses a
combination of the device's serial number, manufacturer, and model. The APIs and
CSV import check that both the model value and manufacturer value are from a
launched device.
Learn more
To learn more about identifying devices and see examples of these values used in
API calls, read the Identifiers guide.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2024-12-13 UTC."],[[["\u003cp\u003eZero-touch enrollment uses specific values to identify Android devices, as referenced in this guide for both APIs and CSV imports.\u003c/p\u003e\n"],["\u003cp\u003eDevice identification requires a combination of hardware ID or metadata with the manufacturer's name to help ensure the correct device is provisioned.\u003c/p\u003e\n"],["\u003cp\u003eThe correct manufacturer value can be obtained by contacting the device manufacturer directly or by using the \u003ccode\u003eadb shell getprop ro.product.manufacturer\u003c/code\u003e command.\u003c/p\u003e\n"],["\u003cp\u003eIdentifying devices by serial number for zero-touch enrollment involves the device's serial number, manufacturer, and model, all of which must be from a launched device.\u003c/p\u003e\n"]]],["Device identification for Android zero-touch enrollment involves using hardware IDs or metadata paired with the manufacturer's name. The manufacturer's name can be obtained through the device manufacturer or via the `adb` command. When using a serial number, both the manufacturer and model must be valid. APIs and CSV imports validate these values against a list. For more details and examples, refer to the provided \"Identifiers\" guide.\n"],null,["# Android manufacturer names\n\nThis reference lists the allowed values used to identify Android devices by\nzero-touch enrollment. Both the APIs and portal's CSV importing check values\nagainst the lists in this reference.\n\nTo help avoid errors when you claim devices for a customer, you\n[identify](/zero-touch/guides/identifiers) each device using a hardware ID or\nmetadata and the manufacturer's name. A combination of values helps prevent\nprovisioning the wrong device because of a mistyped ID.\n\nManufacturers\n-------------\n\nTo identify the correct manufacturer value to use, ask the device manufacturer,\nor use [adb](https://developer.android.com/studio/command-line/adb) to query the\nvalue from the device with the following command:\n`console\nadb shell getprop ro.product.manufacturer`\n.\n\nModels\n------\n\nTo identify devices by serial number zero-touch enrollment uses a\ncombination of the device's serial number, manufacturer, and model. The APIs and\nCSV import check that both the model value and manufacturer value are from a\nlaunched device.\n\nLearn more\n----------\n\nTo learn more about identifying devices and see examples of these values used in\nAPI calls, read the [Identifiers](/zero-touch/guides/identifiers) guide."]]