概览
使用集合让一切井井有条
根据您的偏好保存内容并对其进行分类。
借助零触摸注册，组织可以预配置其购买的企业设备。预配置的设备开箱即用，可让组织简化设备部署。零触摸注册的其他优势包括：
- 客户 IT 管理员无需为单个设备预配，因为可以为购买的设备批量自动设置配置。
- 客户始终掌控自己的设备，即使在恢复出厂设置后也是如此。
- 最终用户收到包装好的设备后，只需登录即可。
关键利益相关方
设备转销商
在销售履单流程中，获得批准的设备转销商会将设备（使用序列号、硬件 ID 和其他设备标识符）分配给客户的零触摸注册账号。已获批准的零触摸设备转销商可以为设备申请额外的设备保护服务。如需了解详情，请参阅设备保护。
企业客户
使用 Android 设备的 Enterprise 客户（也称为客户或公司）使用其零触摸注册账号访问零触摸注册门户。客户可以在该门户中执行以下操作：
- 查看转销商分配给他们的设备。
- 创建、修改和删除设备配置。
- 将配置应用于设备。
- 为日后添加到零触摸注册的所有设备选择默认配置。
- 管理门户访问权限。
- 添加或移除转销商。
为设备分配配置后，设备可以开箱即用：
- 设备会下载并安装客户选择的设备政策控制器 (DPC) 应用。
- DPC 应用使用客户的配置数据预配设备。
如果您所在的企业有意通过零触摸注册功能购买和配置设备，请参阅面向企业客户的帮助中心。
拥有 ChromeOS 设备的企业客户无需使用零触摸注册门户。而是可以在 Google 管理控制台中配置设备管理。
企业移动管理 (EMM) 提供商
EMM 可以将零触摸注册门户中提供的一些功能添加到其控制台中，为客户提供一个集中管理设备的平台。相关功能包括：
- 创建、修改和删除设备配置。
- 将配置应用于设备。
- 为日后添加到零触摸注册的所有设备选择默认配置。
如需详细了解如何作为 EMM 支持这些零触摸注册功能，请参阅 Customer API 的运作方式。
零触摸注册工作流程示例
- 客户从转销商处购买设备。
- 转销商创建新的客户零触摸注册账号。*
- 转销商向客户分配设备。
- 客户为其企业创建 EMM 配置。*
- 客户将所购设备映射到 EMM 配置。*
- 转销商将设备配送到最终用户所在地。
- 最终用户开启新设备。
* - 不适用于 ChromeOS 设备。
选项 1：与零触摸注册和 Knox 部署计划集成
通用 Android 转销商库支持注册 这些制造商以及三星的 Android 设备。如果满足以下条件，我们建议您使用该库：
- 贵组织尚未与 Samsung 的 KDP 或零触摸注册集成，并且
- 贵组织销售或计划销售三星设备。
非三星设备：库和零触摸注册门户
作为转销商，贵组织可以使用通用 Android 转销商库或门户，为这些制造商的设备支持零触摸注册。您可以使用其中一种或两种，具体取决于贵组织的需求。
您可以通过该网站门户管理客户及其零触摸注册设备。借助该库，您可以将零触摸注册集成到贵组织现有的销售或服务工具中。下表比较了您可以使用门户和 API 执行的任务。
| 转销商任务 |
传送门 |
库 |
| 添加、修改和声明设备 |
|
|
| 添加客户 |
|
|
| 添加供应商 |
|
|
| 与现有工具集成 |
|
|
| 导入和导出 CSV 文件 |
|
|
| 管理贵组织的用户 |
|
|
| 添加、修改和删除设备元数据 |
|
|
您的客户还可以使用同一门户将所购设备映射到 EMM 配置。如需详细了解如何完成表格中列出的任务，请参阅运作方式或转销商门户指南。
发布门户
三星设备：库和 Knox 门户
通用 Android 转销商库可为零触摸注册和三星设备的 KDP 提供单次集成。属于 KDP 的转销商可以使用该库添加三星设备，并使用客户的 Knox 客户 ID 将其分配给企业客户。
您的客户使用 KME 门户创建设备配置，并将其应用于分配给他们的三星设备。如需了解详情，请参阅运作方式。
方案 2：与零触摸注册集成
转销商 API 和零触摸注册门户
此转销商 API 和零触摸注册门户支持注册这些制造商的 Android 设备以及兼容的 ChromeOS 设备，如果满足以下条件，建议使用此 API：
作为转销商，贵组织可以使用转销商 API 或门户为这些制造商的设备支持零触摸注册。您可以使用其中一种或两种，具体取决于贵组织的需求。
您可以通过该网站门户管理客户及其零触摸注册设备。借助此 API，您可以将零触摸注册集成到贵组织现有的销售或服务工具中。下表比较了您可以使用门户和 API 执行的任务。
| 转销商任务 |
传送门 |
API |
| 添加、修改和声明设备 |
|
|
| 添加客户 |
|
|
| 添加供应商 |
|
|
| 与现有工具集成 |
|
|
| 导入和导出 CSV 文件 |
|
|
| 管理贵组织的用户 |
|
|
| 添加、修改和删除设备元数据 |
|
|
客户使用客户门户将所购设备映射到 EMM 配置。如需详细了解如何完成表格中列出的任务，请参阅 Reseller 门户指南或 运作方式 Reseller API 指南。
发布门户
转销商初始配置
下列三个阶段列出了贵组织在开始使用零触摸注册功能时预计要完成的工作。
第 1 阶段：准备
- 签署零触摸注册转销商协议。
- 获得领导层批准并培训您的客户服务团队。
- 与 Google 商定发布日期。
- 规划联合营销机会。
第 2 阶段：集成
- 在销售和客户服务流程中添加零触摸注册。
- 将销售终端 (POS) 系统与零触摸注册转销商 API 集成，以便为客户自动声明设备。
第 3 阶段：发布
- 面向 2 位客户开展试行发布。
- 面向所有客户提供零触摸注册。
请访问 Android Enterprise 合作伙伴门户，开始使用零触摸注册功能。
了解详情
如需详细了解完全受管的 Android 设备，请参阅完全受管的设备。详细了解 ChromeOS 企业管理。如果您不是转销商，请参阅 Android Enterprise 帮助了解详情。
如未另行说明，那么本页面中的内容已根据知识共享署名 4.0 许可获得了许可，并且代码示例已根据 Apache 2.0 许可获得了许可。有关详情，请参阅 Google 开发者网站政策。Java 是 Oracle 和/或其关联公司的注册商标。
最后更新时间 (UTC)：2025-07-25。
[null,null,["最后更新时间 (UTC)：2025-07-25。"],[[["\u003cp\u003eZero-touch enrollment allows organizations to preconfigure purchased enterprise devices, enabling automatic provisioning right out of the box and streamlining device deployments.\u003c/p\u003e\n"],["\u003cp\u003eResellers assign devices to customer accounts, enabling customers to manage configurations, view assigned devices, and apply settings through the zero-touch enrollment portal.\u003c/p\u003e\n"],["\u003cp\u003eEnterprise customers can utilize the zero-touch enrollment portal to manage devices, create device configurations, select a default configuration, and manage portal access, or can do it through EMM provider consoles.\u003c/p\u003e\n"],["\u003cp\u003eResellers can integrate with zero-touch enrollment through either the Common Android Reseller Library or the Reseller API and portal, depending on whether or not they are selling Samsung devices, or both Android and ChromeOS.\u003c/p\u003e\n"],["\u003cp\u003eThe zero-touch enrollment process involves resellers assigning devices, customers creating configurations, and end-users receiving devices that provision themselves upon being turned on.\u003c/p\u003e\n"]]],["Zero-touch enrollment streamlines enterprise device deployment by allowing preconfiguration. Resellers assign devices to customer accounts, and customers create and apply configurations via a portal. End users only need to sign in upon receiving their device. Devices download and install the customer's chosen device policy controller (DPC) app and provisions the device. Resellers can manage customers, devices, and integrate the system into sales tools using an API or portal. EMM providers can integrate features into their consoles to provide customers with a single point for managing devices.\n"],null,["# Overview\n\n**Zero-touch enrollment** lets organizations preconfigure the enterprise devices\nthey purchase. Preconfigured devices provision themselves out-of-the-box,\nenabling organizations to streamline their device deployments. Additional\nadvantages of zero-touch enrollment include:\n\n- **Customer IT admins** don't need to provision individual devices because a config can be automatically set for purchased devices in bulk.\n- **Customers** stay in control of their devices at all times---even after factory resets.\n- **End users**, after receiving a boxed device, just need to sign in.\n\n*** ** * ** ***\n\nKey stakeholders\n----------------\n\n### Device resellers\n\nAs part of their sales fulfillment process, approved device resellers assign\ndevices (using a serial number, hardware ID, and other device identifiers) to\ntheir customers' zero-touch enrollment accounts. Approved zero-touch resellers\ncan claim devices with additional device protection service. See\n[Device protection](https://www.android.com/enterprise/enrollment/) for details.\n\n### Enterprise customers\n\nEnterprise customers (also called *customers* or *companies*) with Android\ndevices use their zero-touch enrollment accounts to access the zero-touch\nenrollment portal. Within the portal, customers can:\n\n- View the devices assigned to them by their reseller(s).\n- Create, edit, and delete device configurations.\n- Apply configurations to devices.\n- Select a default configuration for any devices added to zero-touch enrollment going forward.\n- Manage portal access.\n- Add or remove resellers.\n\nAfter a device is assigned a configuration, the device can provision itself\nout-of-the-box:\n\n1. The device downloads and installs the customer's chosen device policy controller (DPC) app.\n2. The DPC app, using the customer's config data, provisions the device.\n\nIf you're part of an enterprise interested in purchasing and configuring devices\nthrough zero-touch enrollment, see the help center for\n[enterprise customers](https://support.google.com/work/android/answer/7514005).\n\nEnterprise customers with ChromeOS devices do not use the zero-touch enrollment\nportal. Instead they can configure the management of their devices in the\n[Google Admin Console](https://admin.google.com).\n\n### Enterprise mobility management (EMM) providers\n\nEMMs can add some of the features available in the zero-touch enrollment portal\nto their consoles to provide their customers with a single point for managing\ndevices. These features include:\n\n- Create, edit, and delete device configurations.\n- Apply configurations to devices.\n- Select a default configuration for any devices added to zero-touch enrollment going forward.\n\nFor details on how to support these zero-touch enrollment features as an EMM,\nsee [how the Customer API works](/zero-touch/guides/customer/how-it-works).\n\n*** ** * ** ***\n\nExample zero-touch enrollment workflow\n--------------------------------------\n\n1. **Customers** purchase devices from **resellers**.\n2. **Resellers** create new customer zero-touch enrollment accounts.\\*\n3. **Resellers** assign devices to **customers**.\n4. **Customers** create EMM configs for their enterprise.\\*\n5. **Customers** map purchased devices to EMM configs.\\*\n6. **Resellers** ship the devices to **end user** locations.\n7. **End users** turn on their new device.\n\n\\* - not required for ChromeOS devices.\n\n*** ** * ** ***\n\nOption 1: Integrate with zero-touch enrollment and the Knox Deployment Program\n------------------------------------------------------------------------------\n\nThe [Common Android Reseller Library](/zero-touch/guides/reseller-library/how-it-works)\nsupports enrolling Android devices from\n[these manufacturers](/zero-touch/resources/manufacturer-names) as well as\nSamsung. We recommend using the library if:\n\n- Your organization hasn't integrated with Samsung's [KDP](https://www.samsungknox.com/en/knox-deployment-program) or zero-touch enrollment, AND\n- Your organization sells or plans to sell Samsung devices.\n\n### Non-Samsung devices: Library and zero-touch enrollment portal\n\nAs a reseller, your organization can use the Common Android Reseller Library or the\nportal to support zero-touch enrollment for devices from\n[these manufacturers](/zero-touch/resources/manufacturer-names). You might use\none or both depending on your organization's needs.\n\nThe web portal allows you to manage your customers and their zero-touch\nenrollment devices. With the library, you can integrate zero-touch enrollment\ninto your organization's existing sales or service tools. The following table\ncompares tasks you might perform using the portal and API.\n\n| Reseller task | Portal | Library |\n|---------------------------------------|--------|---------|\n| Add, edit, and claim devices | | |\n| Add customers | | |\n| Add vendors | | |\n| Integrate with existing tools | | |\n| Import and export CSV files | | |\n| Manage your organization's users | | |\n| Add, edit, and delete device metadata | | |\n\nYour customers also use the same portal to map their purchased devices to EMM\nconfigs. To learn more about how to complete the tasks listed in the table, read\n[How it works](/zero-touch/guides/reseller-library/how-it-works) or the\n[Reseller portal guide](/zero-touch/guides/portal).\n\n[Launch portal](https://enterprise.google.com/android/zero-touch/resellers)\n\n### Samsung devices: Library and Knox portals\n\nThe Common Android Reseller Library provides a single integration for zero-touch\nenrollment and, for Samsung devices,\n[KDP](https://www.samsungknox.com/en/knox-deployment-program). Resellers\nbelonging to [KDP](https://www.samsungknox.com/en/knox-deployment-program) can\nuse the library to add Samsung devices and assign them to enterprise customers,\nusing their customers' Knox Customer IDs.\n\nYour customers use the\n[KME](https://www.samsungknox.com/en/solutions/it-solutions/knox-mobile-enrollment)\nportal to create device configurations and apply them to the Samsung devices\nassigned to them. To learn more, read\n[How it works](/zero-touch/guides/reseller-library/how-it-works).\n\nOption 2: Integrate with zero-touch enrollment\n----------------------------------------------\n\n### Reseller API and zero-touch enrollment portal\n\nThis Reseller API and the zero-touch enrollment portal supports enrolling\nAndroid devices from\n[these manufacturers](/zero-touch/resources/manufacturer-names) as well as\n[compatible ChromeOS devices](https://support.google.com/chrome/a/answer/10130175?#identify_compatible)\nand is recommended if:\n\n- Your organization has already integrated with the [Samsung Knox Deployment Program](https://www.samsungknox.com/en/knox-deployment-program) (KDP) to support [Knox Mobile Enrollment](https://www.samsungknox.com/en/solutions/it-solutions/knox-mobile-enrollment) (KME), OR\n- Your organization doesn't sell or plan to sell Samsung devices, OR\n- Your organization sells or plans to sell both Android and ChromeOS devices.\n\nAs a reseller, your organization can use the Reseller API or the portal to\nsupport zero-touch enrollment for devices from\n[these manufacturers](/zero-touch/resources/manufacturer-names). You might use\none or both depending on your organization's needs.\n\nThe web portal allows you to manage your customers and their zero-touch\nenrollment devices. With the API, you can integrate zero-touch enrollment into\nyour organization's existing sales or service tools. The following table\ncompares tasks you might perform using the portal and API.\n\n| Reseller task | Portal | API |\n|---------------------------------------|--------|-----|\n| Add, edit, and claim devices | | |\n| Add customers | | |\n| Add vendors | | |\n| Integrate with existing tools | | |\n| Import and export CSV files | | |\n| Manage your organization's users | | |\n| Add, edit, and delete device metadata | | |\n\nYour customers use the customer portal to map their purchased devices to\nEMM configs. To learn more about how to complete the tasks listed in the table,\nread the [Reseller portal guide](/zero-touch/guides/portal) or the\n[How it works](/zero-touch/guides/how-it-works) Reseller API guide.\n\n[Launch portal](https://enterprise.google.com/android/zero-touch/resellers)\n\n*** ** * ** ***\n\nReseller onboarding\n-------------------\n\nThe three stages below list what you can expect to complete as your organization\nonboards into zero-touch enrollment.\n\n### Stage 1: prepare\n\n- Sign the zero-touch enrollment reseller agreement.\n- Get leadership approval and train your customer support team.\n- Decide with Google on a launch date.\n- Plan co-marketing opportunities.\n\n### Stage 2: integrate\n\n- Include zero-touch enrollment in your sales and customer support processes.\n- Integrate point of sale (POS) systems with zero-touch enrollment reseller APIs to automatically claim devices for customers.\n\n### Stage 3: launch\n\n- Run a pilot launch with 2 customers.\n- Offer zero-touch enrollment to all your customers.\n\nVisit the [Android Enterprise Partner Portal](https://www.androidenterprise.dev)\nto get started with zero-touch enrollment.\n\n*** ** * ** ***\n\nLearn more\n----------\n\nTo learn more about fully managed Android devices, see\n[Fully managed device](/android/work/requirements/fully-managed-device). Learn more about\n[enterprise management for ChromeOS](https://chromeenterprise.google/os/). If\nyou're not a reseller, see the\n[Android Enterprise Help](https://support.google.com/work/android/answer/7514005) for more information."]]
