We are utilizing VMIX 28 "Zoom Plugin" in combination with Zoom for switching/graphics in virtual and hybrid corporate events. VMIX works great with regular Zoom. When we try working with the VMIX plugin with "Zoom Events" not so much. Will not pull the participants video streams into VMIX. FAIL.

I cannot find any documentation regarding the VMIX Zoom feature and working with Zoom Events. (Not in either the VMIX or Zoom knowledge base)

Can anyone confirm that the VMIX plugin does not work with Zoom Events?  Any knowledge of a work around or any documentation to be found? Any additional insights would also be appreciated.

Thank you

C.O. Little

I'm at a loss.  I have an on-demand webinar that requires registration to view, but DOES NOT require a webinar passcode.  Here are my settings:

However, users who are registering for the webinar are being asked for a passcode after completing their registration.  This is the screen that pops up after registration (note, registrants are also not receiving a passcode via email post registration either):  

We want users to view the webinar after registering.  Can anyone help?

Could you please tell if the information provided in the post https://community.zoom.com/t5/Zoom-Events-and-Webinars/Is-there-a-way-to-access-personal-webinar-lin... is still valid?

If we would like to use personal links to join each attendee, so all attendees need Zoom accounts (although free accounts should be sufficient for this purpose)?

Привет, я собираюсь провести вебинар, который мне нужно записать и сохранить. У меня есть несколько вопросов, пожалуйста, дайте мне совет.
1. Как мне закрыть количество участников?
2. Как сделать видео максимально качественным? Можно ли добавить какое-либо стороннее приложение для улучшения видео?
3. Что означает Video SDK в Zoom и что он делает?
4. Нужно ли мне переходить на план вебинара или мне следует продолжить с планом конференции?

Заранее спасибо за вашу помощь.

Hello,

Some users in our org. experience the UAC prompts while joining to zoom webinar, and we undertand this could be related to group level policy in windows for zoom, so we looking for the  Document for listed differrences between EnforceSignInToJoin and EnforceAppSignInToJoin.
if anyone have any idea on it, you may please share with.

The feature is turned on and I cannot get a confirmation email to my work email or my personal when I register for webinars I've just scheduled. Even when in the scheduling screen and I click to "send me a preview email" those do not come either. I've checked Junk, Clutter, Spam. Nothing is coming. This is a major feature of promoting a webinar for registration.

1. Zoom Add to Webinar button for Contacts and Leads.  Zoom has an add to webinar button

• Known limitations

1. can only add up to 10 members from a listview at a time
2. cannot add members from Campaign Member related list on Campaigns directly nor can it add members from a report.
1. The button can be used to add campaign members using Contact and or Lead Listview or from the Contact or Lead record directly.  However, the button limits the number of invitees added through this feature at one time to 10.  This means if we have a listview of 50 contacts and want to add them to the Campaign we have to add them in batches of 10 to succeed anymore and those records just drop off and are not added. 

1. Zoom can accept CSV upload of members very cool functionality it will match to existing contacts or leads on email and if no match found create them as a lead and add them to the Campaign. 

• Known limitations
• Zoom app can only create 10-13 records loaded through CSV as campaign members in Salesforce successfully.  All the remaining get a Webinar Registrant record but are not successfully linked to the Campaign (no campaign member record is created)

1. Zooms code is not very open, as such we cannot even with our awesome and skilled developer create a lastmile solution to have Zoom operate the way we need.
2. Zoom Developer General App was not easy to set up required approvals and would not work beyond these limitations so we did not proceed with this attempt.