Setting up a Webinar in Teams

By -

 

Microsoft Teams now lets users set up a Webinar. The difference between a Teams Meeting and a Webinar is that the user MUST register in advance for the Webinar before getting the link to the meeting. This can be very helpful if you want to control the meeting by knowing your audience before starting.

To create a webinar, open the Calendar in our Teams client, then in the top right corner, click the dropdown menu beside New meeting and select  Webinar.




We now see that we have the options at the top menu, under Require registration: (None, for people in your org or  For Everyone)

NOTE: For everyone is disabled in tenants by default and must be enabled globally. It will be greyed out here if so.

To set this as a Teams Administrator, in Teams PowerShell run the command:

Set-CsTeamsMeetingPolicy -AllowMeetingRegistration True

 



Select first who you want to register, then Add title, Required presenters, time and date and details.

Remember, this is like a Live Event invite and is only used for the presenters. This is NOT for the attendees.

At the top, now click on View registration form



Now fill in the required details you want to send to the Attendees, the time and date must be filled in here as it is NOT taken from the original invite as the original invite may show the time you wish the presenters to be present but the registration will show the START TIME of the event.



You can Upload an image at the top for your invite and enter a Description for your event.

Below this you can  + Add speaker and give a bio for each one for your attendees to see.

On the right hand side you will see the details that users must enter to register. You can add some custom options under + Add field





Once ready, click on Copy registration link and share this via a distribution method of your choice – newsletter or email for example.



Once a user clicks on the registration link, they must add the details you required. 


 


Then they will get an invite with a link like the following:


 

The presenter can check on who has registered at any time by opening the event in their calendar and clicking on the Registration icon



This will download an excel file showing you the following details:


A good video is available here for the end user side: https://www.microsoft.com/en-us/videoplayer/embed/RWCMe2?pid=ocpVideo0-innerdiv-oneplayer&postJsllMsg=true&maskLevel=20&market=en-us

Comments

Post a Comment

Popular posts from this blog

Teams Device Health Monitoring and Reporting

By -
Image
 Microsoft have snuck in a nice new feature into the Teams Admin Center (TAC). We now see a new Notifications and Alerts  menu tree and below this Rules. When we go in here, we find only a single Default  Device State Rule with no option to create any new rules (yet at least...) When we edit this rule, we can see that we now have an option to monitor specific devices (think meeting room devices, collaboration bars etc.. here) Under Device users  we click on +ADD  then enter the name of the account, or accounts if you are monitoring multiple devices, associated with the device, such as the resource account. Then under Actions  we can choose either Channel alert  - to have a nice alert sent to our Teams Channel   OR Webhook  to use webhooks for alerting. Finally ensure to select Active  then Save. Once set up this will take maybe 15 mins to replicate and set up. Then once a device has gone offline, the alert will be sent "Immediately", however it seems to take between 5-10 mins
Read more

Unassigned Numbers in Microsoft Teams using Audiocodes SBC

By -
Image
Unlike Skype for Business, Microsoft Teams does not natively support the handling of Unassigned numbers in the system. So if someone leaves your organisation and you remove the number from them and someone tries to call it, the call will drop. Technically, Teams will return a "404 Not Found" back to the SBC and back on to the telco. What we can do here is to then assign the 404 error to a Route, change the Destination Number (to a call queue or to your main Reception number for example) and route it back to Teams. To do this there are a few simple steps: Step 1 – Create an Alternative Reasons Set Step 2 – Configure existing Teams IP Group to use the SBC Alternative Routing Reason Set Step 3 - Create new IPG Step 4 – Create a new route in IP-to-IP Routing Step 5 - Manipulate Numbers Step 6 – Test  Step 1 – Create an Alternative Reasons Set The first thing we need to do is create an " Alternative Routing Set ", we find this under Setup >> Signaling & Media &
Read more

Skype for Business Edge Server replication troubleshooter

By -
Image
Many times in Skype for Business/Lync the main issue I come across is the deployment is that the edge server(s) fails to replicate. We see this when we run the command in Skype for Business Management Shell : Get-CsManagementStoreReplicationStatus and we see that the edge servers have False and no LastStatusReport or ProductVersion is shown as below. There are a number of things which can cause this and I am going to list them here. Try them in order here as this will contain the most common to the least common issues I found. Ø   Routing Ø   Firewall rules Ø   DNS suffix Ø   DNS (Local and LAN) Ø   Registry entries for SCHANNEL Ø   Certificates A check we can use to see if the replication is working can be done by trying to connect to the following URL from the Front End Server whish hosts the CMS: https://edgeinternalfqdn.domain.ie:4443/Replicationwebservice You should get the following screen: Without this response there is an issue,
Read more