Remote Powerwash, Wipe Users, and Reboot Chrome OS Devices in Bulk

Q: Does Remote Powerwash unenroll the Chromebook from my domain?

REMOTE_POWERWASH removes all user profiles, device policies, and enrollment policies, reverting the Chromebook to an unenrolled factory state unless the device is configured for forced or auto-enrollment in your Google Workspace admin settings. If forced re-enrollment is enabled, the device will automatically re-enroll upon connecting to the network. If you only want to clear local user profiles and caches while keeping device policies and domain enrollment intact, use WIPE_USERS instead.

Q: Can I issue different commands to different devices in the same batch?

Yes. You can set some rows to Reboot and other rows to Remote Powerwash in the same spreadsheet. SheetOps processes each row according to its selected command.

SheetOps Google Sheets Add-on

This guide is for the official SheetOps add-on. Install it to manage Google Workspace at spreadsheet speed.

Install Add-on

Resetting shared student laptops before standardized testing, clearing stale user caches, or powerwashing returning fleet devices in the Google Admin Console requires navigating individual device profiles. SheetOps lets IT administrators issue bulk remote commands including Remote Powerwash, Wipe Users, and Reboot across entire device rosters directly from Google Sheets.

Understanding Chrome OS Remote Management Commands

Google Workspace allows administrators to send cloud-queued instructions directly to enrolled Chrome OS hardware:

REMOTE_POWERWASH: Performs a factory reset, removing all data including user profiles, device policies, and enrollment policies. The device reverts to a factory state with no enrollment unless it is subject to forced or auto-enrollment.
WIPE_USERS: Clears all local user profile data and cache while preserving device policies and enterprise enrollment.
REBOOT: Instantly restarts active devices upon their next network check-in.

SheetOps interacts with the Google Admin Directory REST API's issueCommand endpoint to queue commands in parallel across hundreds of selected devices.

Google Admin Console vs. GAM vs. SheetOps for Remote Commands

Operational Feature	Admin Console UI	GAM CLI	SheetOps
Command Execution	One device at a time from detail pages	Terminal commands piped through CSV	Instant spreadsheet dropdown selection
Multi-Command Flexibility	Cannot mix commands in a single view	Requires separate terminal scripts per action	Assign different commands per row in one sheet
Status Feedback	No inline batch receipt	Terminal stdout scrollback	Real-time change log with command audit string
Post-Execution Safety	No cell state tracking	CLI history only	Auto-clears command cell after queueing

How to Bulk Issue Remote Commands to Chrome OS Devices

1. Export Target Hardware or Paste Serial Numbers

In Google Sheets, go to Extensions → SheetOps → Chrome OS Devices:

Fetch with Filters: Export devices by OU, date registered, last synced or notes.
Just the Sheet: Generates an empty Chrome OS sheet. Paste serial numbers directly into the Serial Number column.

2. Choose a command in the Remote Command Column

Locate the Remote Command (or Command) column:

Select the desired action from the dropdown:
- Wipe Users: Erases user profiles while keeping device policies and domain enrollment intact.
- Remote Powerwash: Factory resets the device, removing all data, device policies, and enrollment policies (re-enrolls automatically if forced/auto-enrollment is enabled).
- Reboot: Triggers a restart on target laptops.
Drag the fill handle down to apply the command across multiple rows. Selected cells highlight yellow.

3. Activating Checkboxes for Remote Fleet Execution

Mark the checkboxes in the Apply Changes column for all hardware rows requiring remote instructions.

4. Monitoring Remote Command Queue Status

SheetOps dispatches issueCommand API calls:

Command dropdown cells are automatically cleared to prevent duplicate transmissions.
The Change log column logs the exact command delivery status:
- ✓ Command issued: REMOTE_POWERWASH (Pending device sync) on success.
- ✗ Error: Device unreachable or invalid ID if the device cannot be resolved.

Remote Fleet Maintenance Tips

State Exam Preparation: Run Wipe Users across OUs 24 hours before standardized testing to eliminate cached login tokens and temporary files.
End-of-Year Turn-In: Issue Remote Powerwash as student laptops are checked in. If forced re-enrollment is configured, the laptop will automatically re-enroll when powered on and connected to Wi-Fi.
Kiosk Reboot Cycling: Keep digital signage and kiosk Chromeboxes fresh by scheduling a bulk Reboot command across your kiosk inventory sheet.

Frequently Asked Questions (FAQ)

Does Remote Powerwash unenroll the Chromebook from my domain?

REMOTE_POWERWASH removes all user profiles, device policies, and enrollment policies, reverting the Chromebook to an unenrolled factory state unless the device is configured for forced or auto-enrollment in your Google Workspace admin settings. If forced re-enrollment is enabled, the device will automatically re-enroll upon connecting to the network. If you only want to clear local user profiles and caches while keeping device policies and domain enrollment intact, use WIPE_USERS instead.

When does the remote command take effect on the device?

Commands execute the moment the device connects to the internet and checks in with Google's servers. If the device is currently offline or asleep, the command stays queued until it is powered on.

Can I issue different commands to different devices in the same batch?

Yes. You can set some rows to Reboot and other rows to Remote Powerwash in the same spreadsheet. SheetOps processes each row according to its selected command.

Last updated: August 26, 2026

Ready to manage Workspace at spreadsheet speed?

Install SheetOps from the Google Workspace Marketplace today and start performing bulk directory updates, onboarding, and audits directly inside Google Sheets.

Get SheetOps Now