Microsoft Teams Rooms update 4.0.76.0 going live today

jasonkennedy  and everyone else, two quick updates:
1. a new app version, .77, which requires a minimum Windows version 1709 (RS3), should be in the app store shortly (it is published and pending certification now).

2. We identified the code causing the issue on Windows 1703 (RS2) and have resolved the problem in an app version .78. We will be doing a full validation pass on that version and Windows 1703 (RS2) tomorrow and will then publish to the store assuming it passes. We expect this version to be in the store later this week.

Again, our sincere apologies for the issue with app version .76 and Windows 1703. 

Ilya Bukshteyn Thank you for the update on the situation with .76 version. We are stable for now and will wait for the updated release.

jasonkennedy , everyone else, please accept our apologies for this issue, which seems is specific to this version of the app (.76) and Windows 1703 (RS2).

We are working as quickly as possible to fully identify and mitigate the issue.

In the meantime we have halted Store updates. We will also make the previous version (.64) available in the store (although this will take a couple of hours). We are pulling app version .76 from the store, and will republish a version .77 asap which will require Windows 1709 (RS3) at a minimum. We will then publish a version .78 with support for Windows 1703 (RS2) as soon as we have an identified fix.

Please note that we do expect that future releases (beyond .78) of our MTR app will require Windows 1709 (RS3) as a minimum. Our goal on an ongoing basis is to support Windows versions going back one year (from the date we support a given version for MTR).  We will provide more information on this in a future post to this community.

If you have MTR devices which have hit this issue your current mitigation options, until we can release a fix, are:
1. Roll back to the .64 app version (using a restore image from Logitech or other vendors or from the store once .64 available there in a couple of hours) or

2. Update Windows to 1709 (RS3) or 1803 (RS4) which are both supported (note Windows 1809, RS5, is not yet supported for MTR).

Aside from the above, you can also wait for an updated version of the app with a fix to support Windows 1703, which we will release as soon as we have the fix completed and fully validated. 

Again we sincerely apologize for this issue.

Randy Chapman to your issues / questions, I've listed some comments below. Please note that the Yealink MTR is still in preview and not officially released.

• I still don't have a dial-pad while in meetings

Per my messages above, the Teams meeting DTMF dial pad support, and video pin / unpin, are both dependent on our cloud service being updated. That should happen very soon and I will post here when it does. 

• Still no self view when not in a meeting.  I can hit the equalizer icon on the lower right to expose the PTZ controls and move the camera, but I have no idea what it is seeing or if moving it is moving it to the right place.  Until I join a meeting.  Then I can use the PTZ control to move the camera and zoom, but my self view is still only 2x3 inches in the right hand rail.  Would be nice if it was the same size as the far end video.

We are working on a UX update in Q2 of this CY which will increase the size of the local video preview to be the same size as remote video in our gallery layout. More local preview options will come in Q3 and beyond.

• The volume on my device resets to 50% after I do anything.  If I place a call, or join a meeting, or go into the settings menu and back to the main screen.

50% is our default volume on MTR today. We will be adding a feature to set default volume by device in the device settings / XML. This is targeted at an upcoming release in the next few months.

• I still can't start a new meeting from the device and invite an existing Teams contact.  It only seems to search for users that are internal (or hybrid) to the org.  Even though the contacts have migrated across from SfBO.  If I enter a whole SIP address for an external contact, it just says unable to find the user.  This is the same with add participants while in a meeting.

That is sounding like an issue in your environment. When you hit Add Participants the device should be searching the GAL for the O365 tenant it is logged into. Please feel free to follow up with support and/or Sohail_Tariq 

All of the below sound like you are having issues with Teams guests and MTR?  We have seen one of your issues before, where guests show up with OID instead of name in the MTR roster, and are investigating that (it has proven to be somewhat illusive).  We will look at all of the below further. Sohail_Tariq Greg Baribault 

• Again, another problem with guests vs email addresses.  If I send an invite from another tenant and enter the SIP address signed into my MTR, I get a different experience depending on how I set up the meeting. 

Not understanding your issue here please feel free to provide more info.  Generally you can add an MTR to any calendar invite with a Teams meeting. 

• If I use the Meetings app in Teams and enter the SIP address it only finds the guest user.  And the meeting takes a while to show up on the MTR calendar view.

Still not sure I understand this.  You should be able to add an MTR to any scheduled team meeting by using its email address. Not sure where SIP is coming into the picture here. 

• If I send from Outlook, it does, because I'm not forced into choosing the guest user.  As far as Outlook is concerned, it is just an email address.  In that case, the meeting invite shows up immediately on the MTR.  Even before I accept the meeting.  And I can just click join.

Yup, that is our desired / "by design" experience

• When I join from the inviting tenant it shows that the MTR user is online, even though it isn't signed in to the guest tenant.  And I can click the elipses to place a call to the MTR user.  The MTR gets an incoming meeting join toast and I can join.  Once it is joined, the contact in Teams changes from SIP address to org ID - e.g. 8:orgid:529b0g49-7dec... - and shows that the user is outside the org.

I believe the issue here is showing OID in the MTR roster? We have seen that before and are investigating.

• I also dropped the MTR out of the meeting to see if the invite ever showed up in the calendar and it did.  Then I click joined again from the invite and the user in the inviting tenant shows up as the name and not an org ID.

• When I share in the Teams meeting (from the inviting org), the default layout is presentation only in single screen mode.  I have to tap layout mode to get the right rail with self and far end video.  Would be nice if the default was content and video rail.  I haven't tried dual screen mode.

We changed our default layout on single screen systems to be content only when someone is presenting, based on customer feedback.  Dual screen systems will always show content on one screen and video on the other.  We can look at adding a setting by device for default content layout in single screen if others think this would be important.  Sohail_Tariq 

jespinoza84  jasonkennedy also reported that updating Windows beyond 1703, to 1803, addresses the issue. We are investigating. 

My Yealink MTR upgraded over the weekend. 

• I still don't have a dial-pad while in meetings
• Still no self view when not in a meeting.  I can hit the equalizer icon on the lower right to expose the PTZ controls and move the camera, but I have no idea what it is seeing or if moving it is moving it to the right place.  Until I join a meeting.  Then I can use the PTZ control to move the camera and zoom, but my self view is still only 2x3 inches in the right hand rail.  Would be nice if it was the same size as the far end video.
• The volume on my device resets to 50% after I do anything.  If I place a call, or join a meeting, or go into the settings menu and back to the main screen.
• I still can't start a new meeting from the device and invite an existing Teams contact.  It only seems to search for users that are internal (or hybrid) to the org.  Even though the contacts have migrated across from SfBO.  If I enter a whole SIP address for an external contact, it just says unable to find the user.  This is the same with add participants while in a meeting.
• Again, another problem with guests vs email addresses.  If I send an invite from another tenant and enter the SIP address signed into my MTR, I get a different experience depending on how I set up the meeting. 
• If I use the Meetings app in Teams and enter the SIP address it only finds the guest user.  And the meeting takes a while to show up on the MTR calendar view.
• If I send from Outlook, it does, because I'm not forced into choosing the guest user.  As far as Outlook is concerned, it is just an email address.  In that case, the meeting invite shows up immediately on the MTR.  Even before I accept the meeting.  And I can just click join.
• When I join from the inviting tenant it shows that the MTR user is online, even though it isn't signed in to the guest tenant.  And I can click the elipses to place a call to the MTR user.  The MTR gets an incoming meeting join toast and I can join.  Once it is joined, the contact in Teams changes from SIP address to org ID - e.g. 8:orgid:529b0g49-7dec... - and shows that the user is outside the org.
• I also dropped the MTR out of the meeting to see if the invite ever showed up in the calendar and it did.  Then I click joined again from the invite and the user in the inviting tenant shows up as the name and not an org ID.
• When I share in the Teams meeting (from the inviting org), the default layout is presentation only in single screen mode.  I have to tap layout mode to get the right rail with self and far end video.  Would be nice if the default was content and video rail.  I haven't tried dual screen mode.

We were able to resurrect our devices from the blue splash screen hang by breaking out of the skype autologin, login as local admin and update them to Windows version 1803. Both of our failed boxes were still running 1703. Perhaps this new version of the Meeting app is not compatible with the older windows build. Hope this helps.

Samuel GAZEAU - Updating one of our units to 1809 fixed it. 

Will probably have to halt all updates to the units until this is resolved.

I've received the updates on my Logitech SmartDocks SRS tablets but now, 5 of them didn't working. I have the blue skype screen, it freeze during 2 minutes and it reboot.

I have an error on event viewer : DesktopAPIService.exe version 4.0.76.0 failed !

Have you an idea to repair it ?
Thanks a lot