Microsoft Teams Rooms update 4.0.76.0 going live today

[David Groom]

Microsoft Teams Rooms update 4.0.76.0 is scheduled to go live today.  As with previous releases, we'll start off by making the update available to 10% of devices and then throttle up to 100% in the next few days. [March 11, 2019 status update: 4.0.76.0 is now available to 100% of devices.]

This update includes a couple of notable fixes.  First, we're removing the casting icon and description on the Front-of-Room display when the device's Bluetooth beacon is not enabled.  (Side note: the Bring Your Own Meeting user experience affiliated with the casting icon will be enabled for users some time in the next couple months.  Thank you for your patience!)  Second, we've fixed a volume issue that occurs on MTR in Teams meeting mode.

March 18th Note: 4.0.78.0 update was released over the weekend to address the issues observed with 4.0.76.0 and the older Windows 10 Version 1703.

[jasonkennedy]

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.

[Randy Chapman]

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.

[Ilya Bukshteyn]

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

[Ilya Bukshteyn]

@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 

[Ilya Bukshteyn]

@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.

[jasonkennedy]

@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.

[Ilya Bukshteyn]

@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. 

[Shanib Rahman]

@Ilya Bukshteyn @David Groom, We are planning to ditch our on-prem s4b to go teams only but in Australia we don't get PSTN calling plans. I've setup SRS/MTR in our dev environment where I have configured Direct Routing for teams through a SBC in azure (audiocodes). We are able to make calls to and from the teams client/app. But can't figure out if its possible to user Direct Routing with SRS/MTR. can you please advise if its supported yet? Thanks

[Ilya Bukshteyn]

@Shanib Rahman MTR should support calling via Direct Routing for Teams calls / meetings, the same as any other Teams client (and assuming the O365 resource account for MTR is properly configured).  The MTR will need to be set in Teams default mode.  Please wait for our next app update (app version .78) per my message above, as well as our announcement of enabling DTMF dial pad in Teams on our service.  Both should be done very soon.  

[Lars Berlau]

@Ilya Bukshteyn 

Thanks for the reply.

it is possible to call into a compatible (must support MS-SIP, such as Pexip) VMR from MTR, using the SfB client portion of the MTR.  This should be under New Meeting, and type in the SIP URL for the meeting. 

But if you run Teams only or Teams default, will it then still work?

Thanks

[Jeremy8849]

My Polycom MSR test unit upgraded fine; but I want to test out the proximity feature. Its not clear to me how this is supposed to work. If I start a meeting close to the MSR I don't see any options to include it.

Does someone have a pointer for me to figure this out?

[Ben Dodson]

@Jeremy8849Last time I checked this feature was waiting to be enabled in the Teams client.

[Ilya Bukshteyn]

@Lars Berlau yes this will still work; we have new UX for Teams default mode, when you hit New Meeting, which is an extra button to enable you to enter a SIP URL (in which case the connection / meeting is done using the SfB client portion of the MTR app).

@Jeremy8849 Proximity join needs to be enabled in Teams desktop and mobile, which is targeted to happen in the next 4-6 weeks

[Eric Marsi]

Some of my users at my organization have been complaining about the size of the dialpad in our MTR's. Is there any plans to increase the button size so that it is comparable to Skype for Business mode? I would also love to see a camera preview button on the MTR console of the camera so we can see what the camera sees on a much larger scale instead of this small preview in the bottom right of the main display(s). 

[Ilya Bukshteyn]

@Eric Marsi we are for sure working to resize the preview window in Teams meetings.  You can also see your preview in full screen if you do a new Teams meeting or join a Teams meeting without anyone else present.  @Sohail Tariq let's look at the dial pad sizing for Teams as well.

[Eric Marsi]

@Randy Chapman @Jeff Schertz  I believe that the actual MTR application is updated by the Microsoft Store and is independent from Windows Updates. The actual application is a hidden listing in the Microsoft Store. Store Link

[James McGuire]

Are there official release notes for this version or .77?  I noticed our devices updated to 4.0.77.0.  Is there a way to sign up for delivery of release notes when new versions become available instead of having to search for them?  

Thanks.

[achitsaz]

Very curious why Teams Room Systems updates are not included in the Microsoft Roadmap.

Things like devices showing up in teams admin console for easy monitoring is huge for us (we dont use OMS) and I know is coming, but not sure on when.

Why cant the community be aware of what is on the roadmap in the same fashion as other Microsoft Products?

(We are running 4.0.77.0 using Logitech SmartDocks with Windows 1803 and testing an HP Elite Slice with 4.0.77.0 and also 1803)

[Ilya Bukshteyn]

@achitsaz support for Microsoft Teams Rooms in our Teams cloud device management admin center is scheduled for Q3 of this CY. We do cover our roadmap at key events, including in my session at the last Ignite, which is available online:
https://myignite.techcommunity.microsoft.com/sessions/65505?source=TechCommunity

the app version .77 is exactly the same as app version .76, which is what this blog post is about, except we changed the min Windows version supported to be 1709 (RS3).  App version .78 should be hitting the store very shortly with support for Win version 1703 (RS2).  Again, no feature changes.

[rodelmurex]

this update is not stable. Our rooms keeps on crashing and the surface pro generates more heat now :(

[Ilya Bukshteyn]

@rodelmurex which update exactly?  do you now have version .76 or 77?  Neither version should have anything, at all, to do with surface pro and heat.

There are also no known issues with app crashes other than the issue I highlighted above around an incompatibility between .76 and Windows 1703 (RS2).  If you are not in that config and have app crashes please contact support so we can get logs from your devices.  Thank you!

[cbright]

@Ilya Bukshteyn What is the correct avenue for support regarding MTR / SRSv2? I am still having trouble with getting OMS to work properly and I'm not sure who to reach out to?

[Ilya Bukshteyn]

@cbright typically just to contact support.  Potentially @Sohail Tariq on my team could help if you PM him.

[cbright]

Thanks @Ilya Bukshteyn . Where / how do we contact support though? Is it through the O365 admin portal with the general number? I will PM @Sohail Tariq with my question, too.  

[Ilya Bukshteyn]

@cbright yes and ask for support for Skype Room Systems v2 / Microsoft Teams Rooms.  But perhaps start with Sohail.

[Nick DiFeo]

Can you explain the new feature in the .77 update, "automatic password rotation" on the account setup screen?

[Ben Dodson]

@Nick DiFeo  There shouldn't be any additional functionality between .76 and .77, .77 just introduced Windows 1709 as the minimum version.

[Ben Dodson]

@Ilya Bukshteyn  Is there any update on the timeframe for touch and whiteboard support on FoR screens and capabilities? We have a room that could really do with this functionality and am keen to stick with the MTR solution that everyone in the business knows rather than a different 3rd party solution.

Many thanks!

[Ilya Bukshteyn]

@Ben Dodson make sure to watch the Enterprise Connect keynote next week :)    aka.ms/EC2019  

[Ben Dodson]

@Ilya Bukshteyn  sounds interesting :) Will definitely keep an eye out for it!

[achitsaz]

@Ilya Bukshteyn  thanks for the reply.  Relying on a presentation at EC or Ignite is inconsistent with the rest of Microsoft 365 and makes people feel like this product is not managed with the same care as other Microsoft releases. (having .76 fail with older versions of win 10 is a prime example)

With no indication on when conversation and content sharing will be available within Teams based meetings I struggle with communicating plans to my stakeholders like I do with ALL OTHER 365 products.  We dont' even get messages in our tenant regarding Skype or Teams rooms. 

If you want companies to really take the plunge and not feel burned like they did with v1 you have to provide an accountable roadmap.

In the meantime I will monitor this blog, as it seems like the only way to get SME level information regarding SUCH A STRONG PRODUCT. 

[Nick DiFeo]

@Ben Dodson  It's new since .64. I managed to dodge .76. Just curious what it is @Ilya Bukshteyn 

[Ilya Bukshteyn]

@achitsaz We do all of the same things related to M365 roadmap as every other product.  The issue with .76 and Windows 1703 was a bug, and again I apologize for that. App version .78 with support for Windows 1703 is working its way through the store system now.

We are planning to enable PPT control for Teams meetings on MTR, similar to what we have for SfB meetings, in H2 of this CY.

Based on customer feedback we do not currently plan to enable chat in Teams meetings on MTR. Please feel free to provide your feedback on that if you would like, and @Sohail Tariq on my team can look at that.

Thank you for your support of Microsoft Teams Rooms!

[Ilya Bukshteyn]

@Ben Dodson @Nick DiFeo We are introducing a new Automatic Password Rotation feature for MTR when used with Office 365 accounts.  This will enable the account password to be fully automatically rotated (ie. unknown to any human).  This is coming in a future release, and will only be able to be enabled via XML config for the MTR device.  The setting in the device Admin Settings screen is read only, and will show if this setting is enabled on the device.  We expect this feature to ship next quarter.

[Jed Ellerby]

@Ilya BukshteynI'd just like to say you are doing a great job of covering off so many comments in this thread, especially when a fair few are answered already in different ways earlier or in the forum! I hope you can keep this pace up as it really does help connect with end users and the fact the team have sorted the 1703 bug out so quick and the new release has already landed is great work from the team .. glad it was an easy one to solve (if even if it is a workaround)!

[Ilya Bukshteyn]

@Jed Ellerby Thank you very much for the kind words!

[Sohail Tariq]

DTMF feature is now enabled on service. It requires a reboot of Microsoft Teams Room device (aka SRS v2). You should expect to see this after tonight’s nightly maintenance reboot. To make Microsoft Teams your default outgoing client, make sure IsTeamsDefaultClient property is set to true in the configuration xml file. Thanks for your patience and support. 

[Ben Dodson]

@Sohail Tariq Great news! Will reboot and test after the weekend. Thanks for communicating the update. 

[Lars Berlau]

Does anyone have any updated userguide on Microsoft Teams Rooms

I have found this one:

https://support.office.com/en-us/article/skype-room-systems-version-2-help-e667f40e-5aab-40c1-bd68-6...

But that only covers Skype for Business.

I am planing some training on Microsoft Teams Rooms, and it would be great to have an updated

userguide...

Thanks ;)

[David Groom]

4.0.78.0 update was released over the weekend to address the issues observed with 4.0.76.0 and the older Windows 10 Version 1703.

[David Groom]

FYI... 4.0.78.0 update was released over the weekend to address issues observed with 4.0.76.0 and the older Windows 10 Version 1703.

[rodelmurex]

Anyone using surface pro 2017? 

I observe a 2hr + meeting . I found out that we're having issues with HDMI ingest on a Surface Pro 2017 again with 2 tv display. It seems this version of surface pro is giving up and app crashes drop the meeting and we will join again. Work around is to share the content on another laptop and not using the hdmi on smartdock. im using appman to monitor and as the call goes longer , the cpu usage goes up to 100% but the memory usage stays always at 46 percent.

[Ben Dodson]

@Sohail Tariq  Just looked at one of our room systems that is configured as Teams by default and after a reboot I still don't see the DTMF dial pad when calling a number. Teams is set as default within settings rather than XML, would that make a difference?

Many thanks

[Sohail Tariq]

@Ben Dodson - You should push XML setting for IsTeamsDefaultClient property set to true and then reboot the device. This is needed to make Teams default outgoing client. You should see an additional keypad button after the reboot as below:

[Sohail Tariq]

@rodelmurex - Please make sure both FoR display screens are set at 1080p. If the problem still persist, it will be very helpful to get logs to see why the CPU is at 100%. Also, what version of OS build and app version you are running on Surface Pro 2017? 

[Ben Dodson]

@Sohail Tariq  Thanks for that. We've only configured via the GUI at the moment, is their a guide to the location of and configuring XML along with options?

[Sohail Tariq]

@Ben Dodson Here is the link to Manage a Skype Room Systems v2 console settings remotely with an XML configuration file 

[rodelmurex]

i have test OS version win 10 1709 , 1803 and now 1809 skype version is .78 .  both display resolution for our 2 TV are 1080p . anyway i have collect the logs and report to microsoft.

[Keith Knowles]

@Sohail Tariq We still do not have a dial-pad when connected to a call.  Version 4.0.78.0.  I have deployed the XML config file and verified that the system is in Teams default mode.

[Ben Dodson]

@Keith KnowlesI have the same problem here, thought I was pushing the XML incorrectly. I'm wondering if it makes any difference how the coexistence mode is set for the room in the Teams admin console. @Sohail Tariq does it need to be set as Teams only or should Islands work?