[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["没有我需要的信息","missingTheInformationINeed","thumb-down"],["太复杂/步骤太多","tooComplicatedTooManySteps","thumb-down"],["内容需要更新","outOfDate","thumb-down"],["翻译问题","translationIssue","thumb-down"],["示例/代码问题","samplesCodeIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-03-26。"],[],[],null,["# Device management overview\n\nDevices running Android 5.0 or higher support device management modes, enabling\nenterprise IT admins to set device policies on enrolled managed devices. The\ndevice policies available to a device management app might depend on the type of\nmanagement mode used for enrollment. While a few device management APIs (see\n[`DevicePolicyManager`](https://developer.android.com/reference/android/app/admin/DevicePolicyManager)\nfor a full set of API elements) might have applications beyond enterprise use,\nmost are designed for use in corporate environments to be deployed with [Android\nEnterprise solutions](https://www.android.com/enterprise/).\n\nHow Android Enterprise works\n----------------------------\n\nAndroid Enterprise uses the device policy controller (DPC) app to enforce device\nmanagement policies. An [enterprise mobility management (EMM) solutions\nprovider](https://androidenterprisepartners.withgoogle.com/emm/)\nsupplies customers with device management solutions, which typically include an\non-device device policy app (DPC app) and a cloud-based EMM console. Enterprise\ncustomers can enroll devices and apply management policies to the devices they\nenrolled using the EMM console.\n\nA DPC app can run in profile owner mode on personal and corporate-owned devices,\nor in device owner mode on corporate-owned devices.\n\nAndroid Enterprise device management modes\n------------------------------------------\n\nAndroid Enterprise uses these device management modes:\n\n- **Fully managed device** (also referred to as *device owner mode* ): A DPC\n app is set as a [device owner](#fully-managed) during setup and it manages\n an entire device. This type of device management can be used only on\n organization-owned (company-owned) devices that are used for work.\n\n- **Work profile** (also referred to as *managed profile mode* ): A DPC app is\n set as a [profile owner](#work-profile) and it manages only the work profile\n on a device, which can also have a personal profile. This type of device\n management can be used on a personal device or an organization-owned device.\n\n### Fully managed device provisioning (device owner provisioning)\n\nAndroid comes with a broad set of management features that allow organizations\nto configure devices for everything from corporate employee use, to factory or\nindustrial environments, to customer-facing signage and kiosk purposes. With\n[device owner\nprovisioning](/docs/compatibility/13/android-13-cdd#3911_device_owner_provisioning)\n(fully managed devices), organizations can enforce Android's [full range of\nmanagement\npolicies,](https://developers.google.com/android/work/requirements/fully-managed-device)\nincluding device-level policies that are unavailable to work profiles.\n\nA Fully managed device:\n\n- Contains only work apps and data.\n- Is visible to the organization.\n- Is managed by the organization.\n\nDevice owner provisioning can be performed only during the out-of-box setup (or\non a factory reset device) and should be provisioned only on devices that are\nowned by an enterprise. This is typically achieved by verifying unique device\nidentifiers (such as an IMEI or a serial number), or by using a dedicated set of\ncorporate accounts that are authorized for device enrollment. After device owner\nprovisioning completes successfully, the DPC app is set as the [device owner\napp](https://developer.android.com/reference/android/app/admin/DevicePolicyManager.html#isDeviceOwnerApp(java.lang.String)).\n\nFully managed devices are particularly well suited for [dedicated\ndevice](https://developer.android.com/work/dpc/dedicated-devices)\nuse cases where a device is typically [locked to a single app or set of\napps](https://developer.android.com/work/dpc/dedicated-devices/lock-task-mode)\n, such as check-in kiosks or digital signage. Android supports several device\nowner enrollment methods such as QR code-based enrollment, NFC based enrollment,\ncorporate accounts, or cloud-based enrollment. EMM solutions developers can\nrefer to [Key provisioning differences across Android\nversions](https://developers.google.com/android/work/play/emm-api/prov-devices#Key_provisioning_differences_across_android_releases)\nfor details.\n| **Note:** The device owner can be set only on an unprovisioned device. If `Settings.Secure.USER_SETUP_COMPLETE` has ever been set, the device is considered provisioned and the device owner can't be set. The device must be factory reset before it can be provisioned again.\n\n### Work profile provisioning (profile owner provisioning)\n\n[Profile owner\nprovisioning](/docs/compatibility/13/android-13-cdd#3912_managed_profile_provisioning)\nenables the user to have both a work profile (managed profile) and a personal\nprofile on a device. This type of device management can be used on an\norganization-owned device or a personal device. Profile owner provisioning can\nbe performed during the out-of-box setup (used for organization-owned devices) or initiated after out-of-box setup on a device with a\nprimary profile (bring-your-own-device type enrollment),\ndepending on the type of device and enrollment method supported by the\norganization. In devices provisioned with a work profile, the DPC has control\nonly over the work profile (work apps and data) and not the personal profile.\nDevice policies are enforced only on the work profile with some exceptions, such\nas enforcing the lock screen, which is applicable across the device.\n| **Note:** There might be a few additional policies enforceable on organization-owned devices with a work profile compared to personal devices with a work profile.\n\nDuring profile-owner provisioning, the framework copies the DPC app into the\nmanaged profile and calls the `ADMIN_POLICY_COMPLIANCE` intent handler on the\nwork profile user. When work profile provisioning is complete, work badged app\nicons appear in the launcher. After profile owner provisioning completes\nsuccessfully, the DPC app is set as the [Profile Owner\napp](https://developer.android.com/reference/android/app/admin/DevicePolicyManager.html#isProfileOwnerApp(java.lang.String)).\nAndroid supports various work profile enrollment methods such as QR code-based\nenrollment, NFC-based enrollment, accounts, or cloud-based enrollment. EMM\nsolutions developers can refer to [Key provisioning differences across Android\nversions](https://developers.google.com/android/work/play/emm-api/prov-devices#Key_provisioning_differences_across_android_releases)\nfor details.\n\nResources\n---------\n\n- [Android Enterprise Developer Overview](https://developers.google.com/android/work/overview)\n- [Android Management API (for EMMs)](https://developers.google.com/android/management)"]]