Guide

How to Update Firmware on Many Meeting Rooms at Once

Updated

To update firmware on many meeting rooms at once, use the device vendor's cloud management portal (Logitech Sync, Poly Lens, Yealink Management Cloud Service, Neat Pulse) or your platform's admin center to group rooms, push the update to a small pilot group first, then schedule the rest for after hours. Most portals can also enable automatic updates on a schedule once you trust them.

How to Update Firmware on Many Meeting Rooms at Once
Update firmware across many meeting rooms with vendor cloud portals and your platform's admin center: group rooms, pilot first, then roll out after hours.

Which tool updates what

Device type Where updates come from
Logitech devices Logitech Sync (and, for room software, the platform)
Poly devices Poly Lens
Yealink devices Yealink Management Cloud Service (YMCS) or Device Management Platform
Neat devices Neat Pulse, with Neat also pushing updates over the air
AVer cameras AVer's management tools and IP web interface; see AVer camera firmware update
Teams Rooms on Android and Teams Panels Teams admin center (device firmware and Teams app), and the Teams Rooms Pro Management portal with a Pro license
Teams Rooms on Windows Windows Update and Microsoft Store for the app; OEM tools for peripherals; see update Teams Rooms
Zoom Rooms appliances Zoom admin portal; see update Zoom Rooms
Google Meet hardware Managed automatically by Google; see Google Meet hardware updates

On Android-based Teams Rooms and Zoom Rooms devices, platform-approved firmware is sometimes pushed by the platform rather than the vendor portal. Check each vendor's guidance for which tool should own updates, so two tools aren't fighting.

Step by step

  1. Enroll every room in the right portal. Record room name, location, model, serial and current firmware. See what is a device management portal.
  2. Group rooms by site, model and platform. Updates often differ by model.
  3. Read the release notes. Note required order (some devices need an intermediate version) and known issues. See Teams Rooms release notes.
  4. Pick a pilot group: 2 to 5 rooms of each model, including one heavily used room.
  5. Update the pilot after hours and test calls, content sharing and the touch controller the next day.
  6. Wait a few days for user reports.
  7. Schedule the rollout in batches, by site or time zone, outside meeting hours.
  8. Check results in the portal: devices that failed, went offline or stayed on the old version.
  9. Turn on automatic updates with a maintenance window, if your change process allows it.
  10. Keep a record of versions per room for support.

Common mistakes

  • Updating during the workday. Devices reboot and can be offline for several minutes or more.
  • Skipping the pilot. A bad release then hits every room at once.
  • Mixing management tools that both try to control firmware.
  • Firewalls blocking update servers. Devices show "update failed" or never check in. See Teams Rooms network requirements.
  • Forgetting peripherals. The bar may update, but the touch controller, mic pods or cameras may need their own updates.
  • Pulling power mid-update. Can leave a device needing recovery. See Teams Rooms reset and recovery.

Make updates easier from the start

More background: firmware management for room devices and how to secure meeting room devices.

Managing a growing fleet? Tell us your rooms and brands and we'll help you standardize on fewer models.

Related guides

All how-to guides →

Outfitting several rooms, or reselling? Get a volume quote or apply for wholesale pricing →

Popular right now

Popular picks

Get a quote