Wipe and re-enroll a device

Wiping and re-enrolling Google meeting room hardware returns the device to its original (factory) settings, completely and permanently deleting all user data and settings. Wiping and re-enrolling a device might be necessary if:

  • The device was previously enrolled and associated with a G Suite domain and you want to re-enroll the device with a different domain.
  • You want to delete all user settings and data and set up the device from the beginning.
  • You want to re-enroll a device that was previously deprovisioned.

Steps to reset devices

Hangouts Meet hardware and Chromebox for meetings

Return a Chromebox to its original (factory) state

  1. Attach a wired USB keyboard to the device.
  2. Turn off the Chromebox.
  3. Put a paperclip (or pushpin) into the recovery button hole.
    Here is where they are on Asus, Dell,  AOPEN, and Acer Chromebox models:

    Asus Chromebox (CN65)


    Asus Chromebox (CN62)

    Asus Chromebox factory reset button

    Dell Chromebox
    Dell Chromebox recovery button hole

    AOPEN Chromebox
    AOPEN Chromebox recovery button

    Acer Chromebox

  4. Press down the recovery button with a paperclip while turning on the device.
  5. Press Ctrl+D.
  6. Press the recovery button with the paperclip again.
    The device restarts and displays a red exclamation point.
  7. Press Ctrl+D.
    The Chromebox restarts and starts the transition to Developer mode. This clears all local data and takes approximately 10 minutes.
    Note: ​If Forced re-enrollment is enabled for the device, you'll see a note that Developer mode is blocked. This shortens the wipe process, and still allows for re-enrollment when the device automatically restarts in Verified mode.
  8. At the startup screen, press the space bar, then press Enter to restart the device and return to Verified mode.
  9. If you're using a managed Chromebox for your school or business, follow the steps to enroll the device. If you're using Chromebox for meetings, proceed to the steps below.

Devices previously deprovisioned

  1. Sign in to your Google Admin console.

    Sign in using your administrator account (does not end in @gmail.com).

  2. From the Admin console Home page, go to Device Management and then Google meeting room hardware.

    To see Device Management, you might have to click More controls at the bottom.

    Some features may require having the Google meeting room hardware with Calendar privilege.

     
  3. Confirm your device is in Pending state.
    On the top left, click the drop-down list and select All to see a list of all devices.  
  4. (Optional) If the device is in deprovisioned state, select the device and then click More Actions and then Move to Pending

Re-enroll a Chrome device as Hangouts Meet hardware or Chromebox for meetings

  1. Attach a wired USB keyboard to the device.
  2. Wait for the setup screen to appear but do not complete the screen.
    This setup screen is for the Chrome OS, not for the Chromebox for meetings setup.
  3. Press CTRL+ALT+H to enter Chromebox for meetings mode.
  4. Select Yes when asked "Are you sure you want to set up this device to run Hangout Meet?" 
  5. Complete the Basic Enrollment.
Chromebase for meetings

Return a Chromebase for meetings to its original (factory) state

  1. Attach a USB keyboard to the device.
  2. Put a paperclip (or pushpin) into the recovery button hole while turning on the device.
    The recovery button hole is located on the back of the Chromebase.
  3. Press Ctrl+D.
  4. Press the recovery button with the paperclip again.
    The device will restart and the screen will display a red exclamation point.
  5. Press Ctrl+D.
    The Chromebase will restart and start the transition to Developer mode. This clears all local data. The deletion takes approximately 10 minutes.
  6. After this process is completed, press the space bar at the startup screen.
  7. Press Enter to return to Verified mode.
    The device will restart and re-enter Verified mode.

 

Device-specific wipe instructions

Select your Chrome device below for instructions. If your device isn't listed, follow the generic steps that apply for any Chromebook or Chromebox.

Lenovo X131e Chromebook
  1. Turn off the device and remove from AC power.
  2. Remove the battery for 5 seconds and then reinsert it.
  3. While the device is still off hold Esc+Refresh+Power.
    After a few seconds, the screen will display a yellow exclamation point (!).
    Note: ​If Forced re-enrollment is enabled for the device, you'll see a note that Developer mode is blocked. This shortens the wipe process, and still allows for re-enrollment when the device automatically restarts in Verified mode.
  4. Press Ctrl+D to begin Dev mode, then Enter.
    The screen displays a red exclamation point.
  5. Press Ctrl+D, then Enter.
    The Chromebook deletes its local data, returning to its initial state. The deletion takes approximately 15 minutes.
  6. When the transition completes, press the space bar, then press Enter to return to Verified mode.
  7. Enroll the Chromebook before signing in to it.
Samsung Series 5 Chromebook

Enroll a Samsung Series 5 Chromebook after a user signs in

  1. Turn off the Chromebook.
  2. Locate the black cover with a SIM card icon, on the right side of the device next to the USB port.
  3. Open the black cover and gently move the switch underneath it to the right (toward the USB port) using a paper clip or a pen tip.
    Moving the switch to this position puts the Chromebook into Developer mode.
  4. Start the Chromebook. The screen displays a sad face icon rather than starting up immediately.
  5. Press Ctrl+D to begin the wiping process.
    If you don't press Ctrl+D, the process starts automatically after 20 seconds. The Chromebook begins returning to its initial internal state. The process takes about 5 minutes. Do not turn off the Chromebook during the wiping process. The sad face icon appears again when the process is complete.
  6. Press Ctrl+D again, or wait for 20 seconds.
    The initial sign-on screen appears.
    Note: ​If Forced re-enrollment is enabled for the device, you'll see a note that Developer mode is blocked. This shortens the wipe process, and still allows for re-enrollment when the device automatically restarts in Verified mode.
  7. Turn off the Chromebook.
  8. Return the switch from step 3 to its original position (away from the USB port, which is Normal mode) and close the black cover.
  9. Start the Chromebook.
  10. Enroll the Chromebook before signing in to it.
Samsung Series 5 550 Chromebook

Enroll a Samsung Series 5 550 Chromebook after a user signs in

  1. Turn off the Chromebook.
  2. Locate the Kensington® lock port, on the right side of the device next to the USB port.

  3. Gently move the switch held within the lock port to the right (away from the USB port and towards the monitor) using a paper clip or a pin.
    Moving the switch to this position puts the Chromebook into Developer mode.
  4. Start the Chromebook.
    The screen displays a sad face icon rather than starting up immediately.
  5. Press Ctrl+D to begin the wiping process.
    If you don't press Ctrl+D, the process starts automatically after 20 seconds. The process takes about 5 minutes. Do not turn off the Chromebook during the wiping process. The sad face icon appears again when the process is complete.
  6. Press Ctrl+D again or wait for 20 seconds.
    The initial sign-on screen appears.
    Note: ​If Forced re-enrollment is enabled for the device, you'll see a note that Developer mode is blocked. This shortens the wipe process, and still allows for re-enrollment when the device automatically restarts in Verified mode.
  7. Turn off the Chromebook.
  8. Return the switch from step 3 to its original position (toward the USB port, which is Normal mode).
  9. Start the Chromebook.
  10. Enroll the Chromebook before signing in to it.
Samsung Series 3 Chromebox
  1. Attach a USB keyboard to the device.
  2. Turn off the Chromebox.
  3. Locate the Kensington lock port on the back of the device next to the power port.

  4. Gently move the switch held within the lock port away from the power port using a paper clip or a pin.
    Moving the switch to this position puts the Chromebox into Developer mode.
  5. Start the Chromebox.
    The screen displays a sad face icon rather than starting up immediately.
  6. Press Ctrl+D to begin the wiping process.
    If you don't press Ctrl+D, the process starts automatically after 20 seconds. The process takes about 5 minutes. Do not turn off the Chromebox during the wiping process. The sad face icon appears again when the process is complete.
  7. Press Ctrl+D again, or wait for 20 seconds. The initial sign on screen appears.
    Note: ​If Forced re-enrollment is enabled for the device, you'll see a note that Developer mode is blocked. This shortens the wipe process, and still allows for re-enrollment when the device automatically restarts in Verified mode.
  8. Turn off the Chromebox.
  9. Return the switch from step 3 to its original position (toward the power port, which is Normal mode).
  10. Start the Chromebox.
  11. To enroll the device, choose an option:
AOPEN Chromebase
  1. Attach a USB keyboard to the device.
  2. Turn off the Chromebase.
  3. Put a paperclip (or pushpin) into the recovery button hole.
    AOPEN Chromebase reset pinhole
  4. Press down the recovery button with a paperclip while turning on the device.
  5. Press Ctrl+D.
  6. Press the recovery button with the paperclip again.
    The device restarts and displays a red exclamation point.
  7. Press Ctrl+D.
    The Chromebase restarts and starts the transition to Developer mode. This clears all local data and takes approximately 10 minutes.
    Note: ​If Forced re-enrollment is enabled for the device, you'll see a note that Developer mode is blocked. This shortens the wipe process, and still allows for re-enrollment when the device automatically restarts in Verified mode.
  8. At the startup screen, press the space bar, then press Enter to restart the device and return to Verified mode.
  9. If you're using a managed Chromebase for your school or business, follow these steps to enroll the device.
LG Chromebase
  1. Attach a USB keyboard to the device.
  2. Turn off the Chromebase.
  3. Put a paperclip (or pushpin) into the recovery button hole on the back of the device.

    LG Chromebase recovery button hole

  4. Press down the recovery button with a paperclip while turning on the device.
  5. Press Ctrl+D.
  6. Press the recovery button with the paperclip again.
  7. The device will restart and the screen will display a red exclamation point.
  8. Press Ctrl+D.
    The Chromebase will restart and start the transition to Developer mode. This clears all local data. The deletion takes approximately 10 minutes.
    Note: ​If Forced re-enrollment is enabled for the device, you'll see a note that Developer mode is blocked. This shortens the wipe process, and still allows for re-enrollment when the device automatically restarts in Verified mode.
  9. After this process is completed, press the space bar at the startup screen. Press Enter to return to Verified mode. The device will restart and re-enter Verified mode.
  10. If you're using a managed Chromebase for your school or business, follow these steps to enroll the device.
Acer Chromebase for meetings

Return a Chromebase for meetings to its original (factory) state, follow these steps:

  1. Connect the mouse and keyboard to the device.
  2. Put a paperclip (or pushpin) into the recovery button hole while turning on the device.
    The recovery button hole is located on the back of the Chromebase device.
  3. Press Ctrl+D.
  4. Press the recovery button with the paperclip again.
    The device will restart and the screen will display a red exclamation point.
  5. Press Ctrl+D.
    The Chromebase will restart and start the transition to Developer mode. This clears all local data. The deletion takes approximately 10 minutes.
  6. After this process is completed, press the space bar at the startup screen.
  7. Press Enter to return to Verified mode.
    The device will restart and re-enter Verified mode.
Was this article helpful?
How can we improve it?