總覽
透過集合功能整理內容
你可以依據偏好儲存及分類內容。
零接觸註冊機制可讓機構預先設定所購買的企業裝置。預先設定的裝置可自行完成開箱即用佈建作業，讓機構能簡化裝置部署作業。零接觸註冊機制的其他優點包括：
- 客戶 IT 管理員不需要為個別裝置進行佈建，因為系統可自動為購買的裝置設定設定檔。
- 客戶隨時都能掌控自己的裝置，即使在恢復原廠設定後也一樣。
- 使用者：收到裝置盒後，只需登入即可。
主要利害關係人
裝置經銷商
在銷售履行程序中，核准的裝置經銷商會將裝置 (使用序號、硬體 ID 和其他裝置 ID) 指派給客戶的零接觸註冊帳戶。經過核准的零接觸經銷商可以聲明擁有權的裝置，可使用額外的裝置保護服務。詳情請參閱「裝置保護」一文。
企業客戶
使用 Android 裝置的企業客戶 (也稱為客戶或公司) 可使用零接觸註冊帳戶存取零接觸註冊入口網站。客戶可以在入口網站中執行下列操作：
- 查看經銷商指派給他們的裝置。
- 建立、編輯及刪除裝置設定。
- 將設定套用至裝置。
- 為之後新加入零接觸註冊機制的任何裝置選取預設設定。
- 管理入口網站存取權。
- 新增或移除經銷商。
指派設定給裝置後，裝置就能自行佈建：
- 裝置會下載並安裝客戶選擇的裝置政策控制器 (DPC) 應用程式。
- DPC 應用程式會使用客戶的設定資料，為裝置進行佈建。
如果您是企業，且有意透過零接觸註冊機制購買及設定裝置，請參閱企業客戶的說明中心。
使用 ChromeOS 裝置的企業客戶不會使用零接觸註冊入口網站。而是可以在 Google 管理控制台中設定裝置管理功能。
企業行動管理服務 (EMM) 供應商
EMM 供應商可將零接觸註冊入口中的部分功能新增至管理主控台，為客戶提供單一裝置管理服務。這些功能包括：
- 建立、編輯及刪除裝置設定。
- 將設定套用至裝置。
- 為之後新加入零接觸註冊機制的任何裝置選取預設設定。
如要進一步瞭解如何以 EMM 支援這些零接觸註冊功能，請參閱「Customer API 的運作方式」。
零接觸註冊機制工作流程範例
- 客戶向經銷商購買裝置。
- 經銷商建立新的客戶零接觸註冊機制帳戶*。
- 經銷商將裝置指派給客戶。
- 客戶為企業建立 EMM 設定*。
- 客戶將購買的裝置對應至 EMM 設定*
- 經銷商會將裝置運送至使用者所在地。
- 使用者開啟新裝置。
* - 不適用於 ChromeOS 裝置。
方法 1：整合零接觸註冊機制和 Knox 部署計畫
Android 常見經銷商資料庫支援註冊 這些製造商的 Android 裝置，以及 Samsung 裝置。建議您在下列情況下使用此程式庫：
- 貴機構未整合 Samsung 的 KDP 或零接觸註冊功能，且
- 貴機構販售或打算販售 Samsung 裝置。
非 Samsung 裝置：程式庫和零接觸註冊機制入口網站
經銷商可以使用通用 Android 經銷商程式庫或入口網站，為這些製造商的裝置支援零接觸註冊機制。視貴機構的需求而定，您可以使用其中一種或兩種。
您可以透過網路入口網站管理客戶和他們的零接觸註冊裝置。有了這個程式庫，您就能將零接觸註冊機制整合至貴機構現有的銷售或服務工具。下表比較了您可能使用入口網站和 API 執行的作業。
| 經銷商工作 |
傳送門 |
媒體庫 |
| 新增、編輯及聲明裝置 |
|
|
| 新增客戶 |
|
|
| 新增供應商 |
|
|
| 與現有工具整合 |
|
|
| 匯入及匯出 CSV 檔案 |
|
|
| 管理貴機構的使用者 |
|
|
| 新增、編輯及刪除裝置中繼資料 |
|
|
您的客戶也會使用相同的入口網站，將購買的裝置對應至 EMM 設定。如要進一步瞭解如何完成表格中列出的任務，請參閱「運作方式」或經銷商入口網站指南。
啟動入口網站
Samsung 裝置：Library 和 Knox 入口網站
通用 Android 經銷商程式庫提供單一整合功能，可用於零接觸註冊，以及 Samsung 裝置的 KDP。屬於 KDP 的經銷商可以使用這個程式庫，利用客戶的 Knox 客戶 ID 新增 Samsung 裝置，並將裝置指派給企業客戶。
客戶可使用 KME 入口網站建立裝置設定，並套用至指派給他們的 Samsung 裝置。詳情請參閱「運作方式」。
選項 2：整合零接觸註冊機制
經銷商 API 和零接觸註冊機制入口網站
這個經銷商 API 和零接觸註冊入口網站支援這些製造商的 Android 裝置註冊作業，以及相容的 ChromeOS 裝置。如果符合下列情況，建議您使用這個 API：
貴機構可以使用經銷商 API 或入口網站，為這些製造商的裝置支援零接觸註冊機制。視貴機構的需求而定，您可以使用其中一種或兩種。
您可以透過網路入口網站管理客戶和他們的零接觸註冊裝置。您可以使用 API，將零接觸註冊機制整合至貴機構現有的銷售或服務工具。下表比較了您可能使用入口網站和 API 執行的作業。
| 經銷商工作 |
傳送門 |
API |
| 新增、編輯及聲明裝置 |
|
|
| 新增客戶 |
|
|
| 新增供應商 |
|
|
| 與現有工具整合 |
|
|
| 匯入及匯出 CSV 檔案 |
|
|
| 管理貴機構的使用者 |
|
|
| 新增、編輯及刪除裝置中繼資料 |
|
|
客戶可透過客戶入口網站，將購買的裝置對應至 EMM 設定。如要進一步瞭解如何完成表格中列出的工作，請參閱經銷商入口網站指南或運作方式 Reseller API 指南。
啟動入口網站
經銷商的註冊流程
下列三個階段列出了貴機構導入零接觸註冊機制時，可預期完成的事項。
階段 1：準備
- 簽署零接觸註冊機制經銷商協議。
- 取得主管核准，並訓練客戶服務團隊。
- 與 Google 共同決定推出日期。
- 規劃共同行銷機會。
階段 2：整合
- 在銷售和客戶服務流程中加入零接觸註冊機制。
- 將銷售點 (POS) 系統與零接觸註冊轉售商 API 整合，自動為客戶聲明裝置擁有權。
第三階段：推出
- 與 2 位客戶執行前測。
- 為所有客戶提供零接觸註冊機制。
請造訪 Android Enterprise 合作夥伴入口網站，開始使用零接觸註冊機制。
瞭解詳情
如要進一步瞭解全代管 Android 裝置，請參閱「全代管裝置」。進一步瞭解 ChromeOS 企業管理。如果您不是經銷商，請參閱 Android Enterprise 說明瞭解詳情。
除非另有註明，否則本頁面中的內容是採用創用 CC 姓名標示 4.0 授權，程式碼範例則為阿帕契 2.0 授權。詳情請參閱《Google Developers 網站政策》。Java 是 Oracle 和/或其關聯企業的註冊商標。
上次更新時間：2025-07-25 (世界標準時間)。
[null,null,["上次更新時間：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."]]
