분실 모드는 회사 소유 기기에서 사용할 수 있는 기능으로, 고용주는
분실한 기기를 원격으로 잠그고 보호하고 원하는 경우
직원 또는 IT 부서의 연락처 정보가 표시된 기기 화면
이를 통해 복구를 시도하는 동안 조직 및 직원 데이터를 보호할 수 있습니다.
복구 가능성을 높일 수 있습니다.
참고: 분실 모드는 기기가 손상될 가능성이 있는 경우에 유용합니다.
복구하면 기기를 복구하면 즉시 업무에 사용할 수 있으므로
이 경우 데이터 손실 및 기기 재프로비저닝 등의
작업이 필요 없습니다 Google에서는
활성화 후 분실 모드를 사용하여 기기 복구를 시도해야 합니다.
분실 모드를 사용 중이더라도 기기를 복구하지 않은 경우
원격으로 기기를 초기화하도록 권장하고 있습니다.
업무 데이터입니다.
기본 요건
기기가 회사 소유여야 합니다. 직장 프로필
Android 13 이상 및 Android 11 및
참조하세요.
분실 모드 시작
기기를 분실 모드로 전환하려면 기기에 명령어를 실행합니다.
유형
START_LOST_MODE
명령어에는 다음 세부정보 중 하나 이상이 제공되어야 합니다.
[[["이해하기 쉬움","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"]],["최종 업데이트: 2025-07-26(UTC)"],[[["\u003cp\u003eLost mode is a feature for company-owned devices that allows admins to remotely lock and display a message on lost devices to aid in recovery.\u003c/p\u003e\n"],["\u003cp\u003eAdmins can trigger lost mode with a command, providing contact details for device return; the device state changes to \u003ccode\u003eLOST\u003c/code\u003e and apps are blocked.\u003c/p\u003e\n"],["\u003cp\u003eWhen in lost mode, the device enters an alert state, ringing for 5 minutes, then transitions to a lost state, sending location updates every minute.\u003c/p\u003e\n"],["\u003cp\u003eTo take a device out of lost mode, admins can issue a command or the employee can manually enter the device password.\u003c/p\u003e\n"],["\u003cp\u003ePub/sub notifications inform admins about lost mode events like entering/exiting lost mode, location updates, and user attempts to disable it.\u003c/p\u003e\n"]]],["Lost mode remotely locks company-owned devices, displaying a custom message with contact details. To start, issue a `START_LOST_MODE` command with contact information; the device enters an alert state, then a lost state with location sharing. Admins can issue a `STOP_LOST_MODE` command to unlock, or the device password can be used to exit. Notifications via `COMMAND` and `USAGE_LOGS` pub/subs inform of device state changes and actions. After 24 hours, data wipe is recommended if not recovered.\n"],null,["# Lost Mode\n\nLost mode is a feature available on company-owned devices, allowing employers to\nremotely lock and secure a lost device and optionally to display a message on\nthe device screen with contact information for the employee or IT department.\nThis helps protect organization and employee data while attempting to recover\nthe device, and may improve the likelihood of recovery.\n\n**Note:** Lost mode is helpful when there is the chance the device may be\nrecovered, because when recovered the device can be used for work immediately,\nwith no loss of data and no need to re-provision the device. While we recommend\nthat you first use lost mode to try to recover the device, if after activating\nlost mode for at least 24 hours you still haven't recovered the device, we\nrecommend remotely wiping the device to provide the strongest protections for\nwork data.\n\nPrerequisites\n-------------\n\nA device must be company-owned; work profile is\nsupported on Android 13 and above, and fully managed devices on Android 11 and\nabove.\n\nStart Lost Mode\n---------------\n\nTo put a device into lost mode, issue a command to a device with the command\ntype\n[`START_LOST_MODE`](/android/management/reference/rest/v1/enterprises.devices/issueCommand#CommandType.ENUM_VALUES.START_LOST_MODE).\nAt least one of the following details must be provided with the command:\n\n- Lost message\n- Phone number\n- Email address\n- Street address\n\nOptionally, the IT admin can choose to provide the following:\n\n- Organization name\n\nExample: \n\n```gdscript\ncommand_body = '''{\n \"type\": \"START_LOST_MODE\",\n \"startLostModeParams\": {\n \"lostOrganization\": {\n \"defaultMessage\": \"Example Organisation\",\n \"localizedMessages\":{\n \"en-US\": \"Example Organisation\"\n }\n },\n \"lostStreetAddress\": {\n \"defaultMessage\": \"1800 Amphibious Blvd. Mountain View, CA 94045\",\n \"localizedMessages\":{\n \"en-US\": \"1800 Amphibious Blvd. Mountain View, CA 94045\"\n }\n }\n }\n}'''\n\nandroidmanagement.enterprises().devices().issueCommand(\n name='enterprises/{}/devices/{}'.format(enterprise_id, device_id),\n body=json.loads(command_body)\n).execute()\n```\n\nOnce successfully placed into lost mode, the device is locked, all apps are\nblocked, and the device's `DeviceState` is changed to\n[`LOST`](/android/management/reference/rest/v1/enterprises.devices?#DeviceState.ENUM_VALUES.LOST).\n\nA device cannot be placed into lost mode if:\n\n- The device is not an [organization-owned device](/android/management/reference/rest/v1/enterprises.devices#managementmode)\n- The device is already in lost mode\n- The device password has been reset by an IT admin in the last 12 hours\n- The employee manually exited lost mode in the last 12 hours\n- It is a [work profile on a company-owned device](/android/management/policies/work-profile#company-owned_devices) **and** the work profile is paused\n\n**Note:** Lost mode is supported in direct boot mode.\n\n### Alert State\n\nThis is the first state a device enters when put into lost mode. In this state,\nthe device rings for up to 5 minutes, giving the user an opportunity to find\ntheir device and take the device out of lost mode. The location of the device is\nnot reported during this time. \n**Figure 1.** The device showing in lost mode, in the lost and alert state.\n\nIf the device is accessed in the alert state, two options are presented:\n\n- **This is my device** - allows the employee to enter their password and take the device out of lost mode. If this occurs before the 5 minute period ends, no location data is sent from the device to the admin.\n- **I found this device** - enables someone other than the employee to stop the device ringing. This moves the device into the lost state.\n\n**Note:** The device location is only shared with the admin after the 5 minutes\nhas elapsed.\n\n### Lost State\n\nIn this state the device stops ringing and sends location updates every minute.\nLocation updates are sent as [usage\nlogs](/android/management/reference/rest/v1/BatchUsageLogEvents#lostmodelocationevent),\nto which an EMM can subscribe using [pub/sub\nnotifications](/android/management/notifications#3_create_a_subscription). \n**Figure 1.** The device showing in lost mode, reported as lost.\n\nIf the device is accessed in the lost state, up to three options are shown:\n\n- **Unlock** - allows the employee to enter their passcode and take the device out of lost mode.\n- **Call owner** - starts a phone call to the number provided in the start lost mode parameters. This option is hidden if no phone number is provided.\n- **Emergency** - allows access to the emergency dialer.\n\nStop Lost Mode\n--------------\n\nTo take a device out of lost mode, issue a command to a device with the command\ntype\n[`STOP_LOST_MODE`](/android/management/reference/rest/v1/enterprises.devices/issueCommand#CommandType.ENUM_VALUES.STOP_LOST_MODE).\nUnlike the start lost mode command, no additional information needs to be\nprovided. The device can also be taken out of lost mode manually by providing\nthe device password.\n\nExample: \n\n```gdscript\ncommand_body = '''{\n \"type\": \"STOP_LOST_MODE\",\n \"stopLostModeParams\": {}\n}'''\n\nandroidmanagement.enterprises().devices().issueCommand(\n name='enterprises/{}/devices/{}'.format(enterprise_id, device_id),\n body=json.loads(command_body)\n).execute()\n```\n\n\u003cbr /\u003e\n\nWhen the device is successfully taken out of lost mode, all apps on the device\nare unblocked and the employee can use the device as normal. The device's\napplied state resets to the state the device was in before lost mode.\n\nPub/sub notifications\n---------------------\n\nTo receive lost mode messages, like confirmation of a device entering or exiting\nlost mode, you must enable and subscribe an enterprise to the `COMMAND` and\n`USAGE_LOGS` [notification types](/android/management/notifications).\n\nThe `COMMAND` pub/sub provides information on the following events:\n\n- [`StartLostModeStatus`](/android/management/reference/rest/v1/enterprises.devices/issueCommand#startlostmodestatus) - indicates that the admin has successfully put the device into lost mode.\n- [`StopLostModeStatus`](/android/management/reference/rest/v1/enterprises.devices/issueCommand#stoplostmodestatus) - indicates that the admin has successfully taken the device out of lost mode.\n\nThe `USAGE_LOGS` pub/sub provides information on the following events:\n\n- [`LostModeLocationEvent`](/android/management/reference/rest/v1/BatchUsageLogEvents#lostmodelocationevent) - there is a location and battery update.\n- [`StopLostModeUserAttemptEvent`](/android/management/reference/rest/v1/BatchUsageLogEvents#stoplostmodeuserattemptevent) - if someone tries to take a device out of lost mode, either successfully or unsuccessfully.\n- [`LostModeOutgoingPhoneCallEvent`](/android/management/reference/rest/v1/BatchUsageLogEvents#lostmodeoutgoingphonecallevent) - if someone makes an outgoing phone call.\n\n**Note:** Actions executed by the admin trigger notifications in the `COMMAND`\npub/sub. Actions executed by the employee trigger notifications in the\n`USAGE_LOGS` pub/sub."]]
