Join Teams work meetings from Microsoft Teams (free) and vice versa

on
Microsoft Teams (Free) users can currently join Teams for work (or school) meetings only as guests, which requires them to use a browser and results in a sub-optimal experience. The new feature rolling out will allow these users to join Teams for work (or school) meetings in one click, without being redirected to the browser or asked to fill in their name/surname. They will also be able to continue collaborating with the meeting organizer and other participants via meeting chat after the meeting.  The feature will work in the opposite way as well, so Teams for work (or school) will just as easily be able to join meetings hosted by a Teams Free user with one click. This is associated with Roadmap ID: 167326
0

So you think you have QOS enabled your Lync?

on
Well think again……

We had a very interesting workshop with one of Microsoft’s PFEs this week, and the focus of this workshop was deep diving into Voice in Lync 2013.

One important aspect of Voice is the implementation of CAC and QOS in the customer network, end to end. Followers of my blog will know I am strong supporter the end-to-end user experience. As a part of this, my strategy is to try to convince all my customers to implement both QOS and CAC (implementing one without the other could actually worsen the experience for the end user).

Newsflash: Some of work you do to implement these function could be “slightly” in vain. With Lync 2013 CU came Lync mobility with the possibility to join audio, video and conference through WLAN on the mobile device. This is great, and I use it a lot. However, as I have suspected, and now confirmed; Mobile clients do NOT support CAC (nor are there any QoS mechanisms on the devices).

A consequence of this is over-subscription of the capacity configured in your network, and all clients in the subnets where mobile clients exist can all suffer bad quality. Seeing how popular the mobility has become, this can turn out to be a challenge for many a administrator.

I still believe you should implement QOS and CAC wherever possible, but now we have to be aware of the mobile “surprise”, and try to calculate this into the rest of your scheme. Let’s all hope Microsoft will look for a way to enable QOS and CAC for mobile devices (They have for common area phones, so why not the mobile devices?). I did not get a clear list of all devices not supporting CAC, but I will post an update once I can get hold of such a list.


Anybody else with a thought on how to handle the subject, or even better, experience from a deployment where this has been an issue?

Comments

Post a Comment