Search
Clear search
Close search
Google apps
Main menu

Manage settings for Chrome devices for meetings

Use the Google Admin console to view, modify, and update settings for Chrome devices for meetings. You must have G Suite administrator credentials to sign in and access the settings.

If you aren't a G Suite customer you can enroll devices on your domain, but you can't view or change any Chrome devices for meetings settings or associate the unit with a calendar. Learn more.

Common settings
Change settings for specific devices
  1. Sign in to the Google Admin console.
  2. Click Device management.
  3. On the left, click Chrome devices for meetings.
  4. Click Chrome devices for meetings.
  5. On the left, select the organizational unit to which you want the settings to apply. A list of the devices enrolled in your domain appears 
  6. (Optional) To change the settings for more than one device, check the box next to each of the devices and click More Actions to:
  7. (Optional) To change the settings on a single device, click a device name to:
Change settings for all devices

You can also apply the following settings to all Chromebox for meetings devices in your domain:

  1. Sign in to the Google Admin console.
  2. Click Device management.
  3. On the left, click Chrome devices for meetings.
  4. Click Settings and policies.
  5. Select the organizational unit to which you want the settings to apply.
  6. On the settings and policies page, you can change the following settings:
    • Auto Update Settings—Specifies whether devices automatically update to new versions of ChromeOS.

      When the release channel is set to stable, the Auto Update Setting is disabled and is not configurable. The Hangouts application will manage the OS updates to ensure high reliability and stability of the Chrome devices for Meetings.

    • Release Channel—Specifies release channel for devices.
    • G Suite or your Domain Administrator Contact Details—Specifies email addresses and mobile phone numbers.
    • Delivery Status Alerts—Specifies method of delivery for alerts (email / SMS).
    • Logs and Reporting: Troubleshooting and Diagnostics— Specifies if and how device logs are generated, forwarded to admins and sent to Google for troubleshooting. 
      • Emails sent will not contain Device / Call  logs or Diagnostics.
      • Check the Receive feedback via email box to deliver user feedback reports. The reports are sent to any email addresses that you designate under G Suite or Your Domain Administrator Contact Details.
    • Device Reporting—Specifies if devices enrolled in your domain report their state.
    • Anonymous Metric Reporting—Specifies whether or not metrics are sent to Google.
    • Scheduled Reboot—Specifies the number of days before the device is rebooted.
    • Call a Phone—Specifies whether or not the Call a Phone feature is enabled.
    • Time Zone—Specifies whether device keeps its current timezone or is set to local zone.
    • Custom Wallpapers—Upload custom wallpapers to your devices. For instructions, see Upload custom wallpapers.
    • Timed Reboot—Specifies the local time at which the devices will reboot, otherwise the default option chooses the least interruptive time to reboot.
  7. At the bottom, click Save. Settings typically take effect within minutes but might take up to an hour to propagate through your organization.
Monitor status of devices and peripherals

Monitor status of devices

If you don't see any text and grayed out icons, that means that the device status is unknown. To fix a device with an unknown status, restart the unit. 
You can search for units that are online or offline using the “is” prefix. In the search box, type is:online or is:offline.

If a device is online:

  • You'll see a green circle next to the status column in the Admin console.
  • When you click on the device, you will see DEVICE ONLINE.

If a device is offline:

  • You'll see a red circle next to the status column in the Admin console. 
  • When you click on the device, you will see DEVICE OFFLINE.

Monitor if peripherals (camera, microphone, and speaker) are online

For the best experience we recommend you use Google-supported peripherals. You can install other peripherals, but this may result in impaired performance and such devices are not supported.

  1. Sign in to the Google Admin console.
  2. Click Device management.
  3. On the left, click Chrome devices for meetings.
  4. Click View and manage Chrome devices for meetings.
  5. Select the device you want to view. The following icons indicate whether a peripheral is connected, disconnected or unsupported on a meeting device.
    • Yes indicate that the peripheral is connected and working correctly.
    •    indicates that the peripheral is connected but not supported. Click Device health to see detailed information, for example you can see if an alternative supported peripheral is connected and available to use.
    •  Rejectedindicates there is a problem with the peripheral. 
    • When an icon is grayed out, it means the peripheral isn't online

Monitor issues with peripherals

If a problem is discovered with one or more peripherals connected to a device, click Device health to get detailed information on the type of problem with your peripheral. You can also run diagnostics to help resolve issues.

Microphone-speaker

A microphone-speaker is reported as two devices, even when it's a single unit. When a microphone-speaker device is connected it appears in the event history as two separate devices, a microphone and a speaker.

Supported peripherals

Audio in 

Manufacturer Device name
Acer Chromebase for meetings bdw-rt5650: Internal Mic
Jabra Jabra SPEAK 410
RevoLabs FLX UC 500

 Audio out

Manufacturer Device name
Acer Chromebase for meetings bdw-rt5650: Speaker
Jabra SPEAK 410
RevoLabs FLX UC 500

Camera

Manufacturer Device name
Logitech HD Pro Webcam C920
  HD Pro Webcam C920 (046d:082d)
  Webcam C930e
  Webcam C930e (046d:0843)
  ConferenceCam (CC3000e)
  PTZ Pro Camera (046d:0853)
  HD WebCam (064e:9405)
  UVC Camera (046d:0823)
Vaddio RoboSHOT 12 USB

 

Was this article helpful?
How can we improve it?