Hey, 

I am having an issue where Proximity sharing prompts users for sharing codes rather then allowing them to direct share from the Zoom app like in the past. It has been very frustrating for our users. Did a Zoom app update break this feature?

I am seeing this behaviour with: Poly x30 , Poly X50 with TC8 and TC10 controllers. 

The devices are all on the same network as our users. Nothing has been changed in terms of configuration on our network.

Any ideas?

We use NDI to stream via OBS Studio. In Room settings "Separate audio" is selected, because we need isolated audio for each source. When participant shares their screen ("Share sound" is selected), I hear sounds on the device where Zoom Rooms and OBS are running, but there is no sound in OBS from NDI source.

We use: Widows 11, latest versions of Rooms, OBS and obs-ndi plugin. I don't know if this is related to software version because we didn't need to use screen share audio before.

Is there any solution or at least advice on how we can get sound from screen share NDI source?

We use Dell OptiPlex 7090s to run our Zoom Room software in our conference rooms. The devices are managed by our firm and one of the policies require that the password be changed every 120 days. We've been trying to find a way to automate this process. What we've found is that we can send a powershell command to all of our identified Zoom Rooms to force the password of the machine to update to our new standard. 

When we push the command, the password successfully changes. However, when we restart the PC the Zoom Room gets unassigned and we have to re-pair the pc to its Zoom Room. Has anyone come across this before or know why this is happening? 

One of our Zoom Room controllers was stolen, so we replaced it (both Mac minis). We removed the old controller from the Zoom Room devices page, and confirmed the new one shows up instead.

However, after some time, the controller disconnects from our account saying "this room is no longer available it is now in use in another location", and the old controller reappears under the Devices page for the Zoom Room.

We're assuming the stolen one is being turned on and automatically reconnecting to Zoom Rooms and kicking off our current one. Is there a way to permanently prevent this old controller from pairing with our account?

Using latest Zoom update v6.0.4 (38135) on an MS Surface 3 with a 64-bit Windows 10 Home system (build 19045.7355) the Annotate function comes on immediately upon Screen Share initiated by a participant. The participant engages Remote Control of their screen. There is no way to "turn off" the Annotate, thus, there is no way for the Host's mouse pointer to navigate the remote screen but instead only draws on it.

This needs to be fixed immediately as it is a critical feature and workflow for many users.

I am wanting to switch our Zoom room Controllers from Ipads to Androids.  I have a Galaxy A9+ android tablet running android 14, One UI ver 6.0.  When Zoom Rooms Controller app is installed it all works, but it i not hiding the built in android functions at the bottom that minimizes apps, closes apps ect.  I for the life of me cannot find an option to hide all this so normal users cannot accidentally minimize/close the zoom room app as its running.   Is this just how the Androids are and I'm stuck with it? Can they be more like an Ipad where nothing is available but the zoom room app and all that responds.  I have searched the zoom rooms controller app settings to no avail.