Notification

Duet AI is now Gemini for Google Workspace. Learn more

Make a bulk update to multiple Google Meet hardware devices by uploading a modified fleet data export file

Google Meet hardware supports bulk updates of certain settings based on an uploaded CSV file of your fleet data export.  This feature is designed to make it easier to change individual device settings across many devices rather than having to rely on doing so individually or by using bulk actions (limited to 50 devices at a time). Learn more about these options.

The bulk update method can also be used to change the organizational unit of your devices, though it cannot be used to change organizational unit settings directly.

Note: There is no way to undo changes to your fleet made via bulk update. We strongly recommend you read this article carefully and take proper precautions to ensure that your fleet is not modified in unintended ways.

Change individual device settings for unlimited devices with a bulk update via CSV upload

  1. Sign in to your Google Admin console.

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

  2. Go to Menu and then Devicesand thenGoogle Meet hardwareand thenDevices.
  3. Click upload  to bulk update devices.
  4. Read the instructions and recommendations carefully and click Continue.
  5. Download the latest version of your fleet data export file.
  6. Make your desired changes to those fields that are editable. Remove any rows for devices that you are not planning on modifying.
  7. Save it as a CSV file.
  8. Upload the CSV file and inspect the generated log file for any errors. You can also inspect the audit logs to verify the changes.

Recommended precautions when using this feature

  • Always save a clean copy of your fleet data export file that can be used to reupload to undo unintended changes.
  • Because it can take up to an hour or more to process many changes across large numbers of devices, you should ideally run bulk updates during off hours for your organization, when other admins are unlikely to be making changes as well that could possibly conflict.
  • Limit who in your organization has access to the Manage devices admin privilege (required for most updates that can be made using this feature).
  • Limit who in your organization has access to the Manage organizational unit settings admin privilege (required when moving devices between OUs).
  • Delete any rows from your fleet data file that you do not want to update to ensure that you don’t make an unintended change (not including devices in your update will not delete devices from your fleet – the only way to delete devices is to deprovision them, which is not possible using this feature).
  • Delete any columns from your fleet data file that do not contain your changes (other than deviceId, which is the primary key and must be included so we know which device to process your changes for).
  • Inspect your log file carefully for possible formatting errors.
  • Watch for unsupported settings on certain devices. Android-based devices from Poly, for example, do not support certain settings that exist on ChromeOS-based devices and may throw an error if you try to modify an unsupported setting.
  • View the audit log to see which changes were made to ensure that the outcome of your bulk update matches your expectations.

Formatting

Proper formatting of values is essential to a successful bulk update. The best way to ensure you use proper formatting is to view your fleet data export file to see how settings are represented. The table below contains a list of all columns, whether they are modifiable or not, and the expected formatting for each.  

Failure to use proper formatting correctly may result in errors or unintended changes, described below.  

If an unexpected column is detected or if a column appears twice, the update will result in an error and no changes will be processed. 

All files must include the deviceId column as it is the primary key and required for identifying the device you want to update. If your file is missing this column, it will result in an error and no changes will be processed. 

If changes are detected to columns that are not modifiable, they will be skipped during processing but other valid changes will be processed. If a value or values for a modifiable column is unrecognized or incorrectly formatted, they will be skipped during processing but other valid changes will be processed (and those problematic rows / columns will be highlighted in the error dialog). 

Column Modifiable Formatting
adminConsoleUrl No  
deviceId No  
deviceName Yes Any string, can also be blank
status No  
orgUnitPath Yes /parentOU/childOU1/childOU2
Must include first backslash, must not include trailing backslash
model No  
serialNumber No  
lastEnrollmentTime No  
annotatedAssetId Yes Any string, can also be blank
annotatedUser Yes Any string, can also be blank
note Yes Any string, can also be blank
annotatedLocation Yes Any string, can also be blank
assignedCalendarResourceEmail No  
assignedCalendarGeneratedResourceName No  
assignedRoomResourceName No  
assignedRoomBuilding No  
assignedRoomFloor No  
lastPeripheralReport No  
connectedCameras No  
connectedSpeakers No  
connectedMicrophones No  
connectedTouchControllers No  
connectedRemotes No  
defaultCamera Yes

Any string, though you should copy and paste exact peripheral name from connectedSpeakers or selectedSpeaker column to ensure successful match (without quotes)

Not supported for Android-based devices

defaultSpeaker Yes

Any string, though you should copy and paste exact peripheral name from connectedSpeakers or selectedSpeaker column to ensure successful match (without quotes)

Not supported for Android-based devices

defaultMicrophone Yes

Any string, though you should copy and paste exact peripheral name from connectedSpeakers or selectedSpeaker column to ensure successful match (without quotes)

Not supported for Android-based devices

selectedCamera No  
selectedSpeaker No  
selectedMicrophone No  
chromeVersion No  
bootMode No  
osVersion No  
firmwareVersion No  
wifiMacAddress No  
ethernetMacAddress No  
lastSync No  
ipAddresses No  
volumeDefaultMode Yes

smart
preset
unsupported

Attempts to change the value for a device that does not support this setting will fail.

volumeLevel Yes

Integer [0-100]

Must be populated if volumeDefaultMode is set to ‘preset’ otherwise will result in an error.

Will be ignored if volumeDefaultMode column is missing or present but set to ‘smart’.

whiteboardingMode No  
videoConferencingMode No  
pairedMeetHardwareDeviceId No  
occupancyDetection Yes

on
off
unsupported

Attempts to change the value for a device that does not support this setting will fail.

softwareAudioProcessing Yes

on
off
unsupported

Attempts to change the value for a device that does not support this setting will fail.

denoiser Yes

on
off

setHomeMode Yes

on
off
unsupported

Attempts to change the value for a device that does not support this setting will fail.

thirdPartyControlApiUrl Yes

Any string, can also be blank

Attempts to change the value for a device that does not support this setting will fail.

thirdPartyControlWebUiUrl Yes

Any string, can also be blank

Attempts to change the value for a device that does not support this setting will fail.

integrationId No  
eolDate No  
connectionStatusNo No  
ipAddressEthernet No  


 

 

Was this helpful?

How can we improve it?
Search
Clear search
Close search
Google apps
Main menu