Home
Microsoft

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.

155 Comments
Microsoft

Please note that this release also  includes support for two new Teams features, local video pin / unpin (makes a remote attendee full screen in an MTR room), and DTMF dial pad for Teams (so the MTR can be switched to do Teams calls by default). These features will show up when enabled in our cloud service as well, which should be very soon.

Occasional Contributor

How do MTR devices get updated versions?  Will MTR devices auto update once it is available? 

New Contributor

We have a few Hub500 That needs to be updated , how can we get access to this release ?

The updates are automatic, but throttled as David stated in the post meaning each unit has a 1 in 10 chance of getting the update right now.  The way it's works is that the device automatically checks in with Windows Updates services (assuming windows Update has not been disabled on the device) but the server will only grant 10% of the requests to upgrade.  Over time Microsoft will reduce/remove the throttling so that all update requests will be serviced.

New Contributor

Thanks @Jeff Schertz 

 

Occasional Contributor

Thanks @Jeff Schertz .  Definitely looking forward to some of the things mentioned above such as local video pinning.  And the volume issue, assuming that you mean that it always reverts to middle volume no matter how many times you turn it down.  Another one I'd like to see is the local video in a meeting not being the size of a grain of sand in the bottom right corner of the screen.


Microsoft

@Randy Chapman we addressed a volume issue specifically for Teams meetings on MTR. We have a backlog item for setting / changing default in-meeting volume per device. We also have some UX changes coming in a later release which will improve the local video preview window, and later this year we will add settings to select whether to hive preview or make it S/M/L per room.

Microsoft

I thought I'd post a quick reminder on how MTR updates are handled.  As noted to @Divesh Nathoo in a separate thread, MTR devices receive Windows updates via Windows Update while the MTR app itself receives updates via the Microsoft Store.  Availability of updates are checked daily during the device maintenance cycle.  I don't have the precise default time on hand, but it's set to something like 2 or 3am so as not to interrupt usage during business hours.  This update scenario assumes a direct connection to the Internet.

Occasional Contributor

Thanks @Ilya Bukshteyn and @David Groom .  I know the MTR has to start somewhere and what is there is really rather good.  But a few improvements are needed IMO.  I am patiently waiting for Bluetooth Beaconing for instance.  I think that will be awesome.  My unit is on the internet all the time so will get updates as soon as they are available.  I'm gonna check the version every hour for the next few days ;).

Microsoft

@Randy Chapman BT Beaconing is already enabled in MTR.  You're waiting now for an upcoming Teams release (desktop and mobile) to enable receiving the beacons. This is live in pre-release rings and should hopefully come to the GA ring in the next 4-6 weeks.  What other few improvements do you see as needed asap?

Occasional Contributor

@Ilya Bukshteyn I figured I'd be waiting for the desktop client update.  Thanks for the timeline.  At least I know now.

Self-view when not in a meeting is one

Self-view that isn't microscopic (as I said above) is another

Invite external or anonymous participants to meet now or scheduled meetings

The dial pad seems to be defaulting to US format by default.  If I type in a number it tries to put the first three digits in brackets like a US area code

Microsoft

@Randy Chapman Showing preview when not in a meeting is a new one for me, we'll need to investigate that.  We for sure know the feedback on the preview size and are working on that.  You should already be able to invite external / anonymous participants to Teams meetings without issues, and they can join even in a browser without a download.  The dial pad number formatting issue is not one I'm aware of so will look into it.  Are your overall Windows internationalization settings set correctly for your geo?  We should be reading number format from there.  @Sohail Tariq fyi

Occasional Contributor

@Ilya Bukshteynis great to see DTMF coming, we are in the process of migrating from SfB to Teams so it'll be great to get the rooms over as well. Do you have any details on the local video pin/unpin as I've not knowingly seen this mentioned before.

 

Many thanks and keep up the great work!

Microsoft

@Ben Dodson sure, our normal video layout today on MTR is up to 4 remote participants up in a 2x2 display, and everyone else on a "sitting row" in the bottom. The 4 participants in the 2x2 are the most recent active speakers.  Now on an MTR you can select a person from the roster and pin them, which means their video will always be full screen, and everyone else will be on the sitting row, regardless of who is speaking. This is a "local pin" so only changes the layout in the one MTR room, not for everyone else in the meeting.

 

Thank you for your support and use of Microsoft Teams Rooms!!!

Occasional Visitor

Two of my Polycom MSR 300s received this update today which left them stuck at a skype login splash screen. Rebooting them did not help. I ended up using the recovery tool to reset them as the repair option did not help. How can I stop these devices from receiving this update again now that they are back on 4.0.64.0?

 

Thank you

Senior Member

@jasonekennedy you should be able to turn off Microsoft Store updates in Windows 10 to prevent the TRS from updating.

Occasional Contributor

@Ilya Bukshteyn  Many thanks for that explanation, I understand now.

Senior Member

With the removal of the casting icon and description, will the MTR phone number start displaying again on the front display?  We found our employees like the convenience of it being displayed there, in addition to the tablet.  It would be great to see it come back.

 

Do we know when the MTR will be enabled to support wireless content sharing?  We'd really like to get rid of the separate wireless display adapters in our rooms, and have them integrated into the Skype/Teams experience.

Microsoft

@Jason Harris Hmmm, I don' think we brought back the phone number, but adding @Sohail Tariq to double check.

 

Our wireless content sharing approach / path is through Teams "casting" which is going to build on the proximity based meeting join feature you reference above. We will be making this more streamlined and quicker / one-touch in H2 of this CY.

Senior Member

@Ilya BukshteynThanks - any chance the Surface Hub and MTR experience for wireless content sharing / Teams casting will converge?  We're hoping for something more standardized, since right now we have two different user experiences for wireless content sharing if it's a MTR room vs a Surface Hub room.  

Occasional Contributor

@Ilya Bukshteyn I changed Windows settings to UK and the dialing format is the same.  It isn't a problem.  Once I dial the last digit the brackets and dashes go away and, crucially, it dials the number.  Here it is side by side with a fake mobile number.

2019-03-06_09-30-28.jpg

Occasional Contributor

@David Groom does this update fix the bug where the dial pad is no longer available in SRS systems after you join a scheduled meeting?

 

Occasional Contributor

@Ron Prague  Is that when it is in Teams by default mode? We've only ever seen it when in Teams mode, Skype mode is fine. It looks like that fix is in this release but waiting for it to hit one of our devices to confirm.

Microsoft

@Jason Harris Surface Hub is a totally different device and experience. This blog and my comments are all for MTR.  

Occasional Contributor

@Ben Dodson Yeah, that's the issue, it persists if the device is in Teams or SFB primary mode for us for any meeting in Teams however.  SFB meetings work fine in both modes.

 

That one issue is the last blocker I have to pushing forward with retiring SFB this year.

Microsoft

@Ben Dodson @Ron Prague  yes this release should now enable dial pad in Teams meetings

Regular Visitor

Hello @David Groom @Ilya Bukshteyn I am trying to get the Azure Log Analytics to work properly with MTR / SRSv2, but think I have an issue with the custom fields. All dashboard tiles are blank except for the number of restarts pane. Are there any support avenues where someone could look into this with me? Thanks!

Occasional Visitor

Hi People- I am interested in how you can now @mention people in teams via MS Flow. Has anyone tested out this new feature? would really like to use this! 

Senior Member

@Ilya Bukshteyn is possible to call an external VMR from the Microsoft Teams Rooms, when using Teams?

for instance if customers needs to have a meeting with someone on a legacy video system, they would like to call an external VMR,

for instance Pexip. I can´t make it work on my system, but I am not sure if my IT have blocked it or if it is not possible yet.

It works fine when it is Skype for Business.

 

Thanks!

 

Microsoft

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

Occasional Contributor

A feature that would be good to have is to see upcoming appointments for the room when you are in a Skype or Teams call. We have often experienced  uncertainty of the rooms availability if a meeting is running late. Might also be solved as a pop-up on the console 5 or 10 minutes before a new meeting starts.

Occasional Contributor

@David Groom@Ilya Bukshteyn  do you have any more details on what the volume issue was on MTR? We have had low volume issues (not loud enough) with approved SRS peripherals (in SfB calls) so would like to understand if there has been any change in this area .. guessing not from the earlier comments?

 

The low volume we experience is one of judgement rather than a scientific measurement but the general feel is that if we use the built in speaker (say HP Slice) or add on a Trio as a USB peripheral, it can drive only smaller rooms of say 5-8 person. We have speaker options for bigger rooms of course but it seems to fall short of what we would expect (had expected to be comfortable for 10-16), yet the Trio on it's own is probably capable of driving a larger room.

Microsoft

@Ivar Engen so if I understand correctly the suggestion is to be able to see upcoming scheduled meetings on the MTR console while in a call, correct?  I like that idea; @Sohail Tariq we should please add that to the backlog.

 

@Jed Ellerby the issue was with inconsistent volume settings in calls / meetings between SfB and Teams meetings on MTR. So does not sound like what you are describing.  The built-in audio on both the HP Slice G2 and the Lenovo Hub 500 is only intended and certified for small rooms, up to about the size you are describing (such as 5-8 people).  Larger AV peripherals for MTR, such as the Trio or the new Logitech Rally System should easily be able to support larger rooms up such as 10-16 person rooms. We have been using MTR rooms with Trio in our internal medium and large rooms for two years now with positive results (we do use sat mics with the Trio in rooms larger than about 12 people). 

Occasional Contributor

Correct @Ilya Bukshteyn, great if this could be included in future GUI updates!

 

Contributor

We have now received version 4.0.76.0 on our Lenovo Thinksmart 500. What do we have to do to get the new "Teams Rooms" user interface displayed?

Occasional Contributor

@Guido Peter  You should just be able to go into settings and change to Teams (default) and Skype for Business. The MTR will then restart and show the Teams interface. 

Contributor

@Ben Dodson As you can see in the attached image, I have the same 3 options like before the upgrade.IMG_20190311_122200.jpg

Regular Visitor

I've received the updated on the 2 test units I have in my office (Logitech SmartDocks) but still cannot get the dialpad to appear after dialing a 3rd party conference line (DTMF dial pad).  I am in Teams default mode and was wondering if there is any other setting that needs to be changed or if this is a cloud side feature that hasn't been enabled yet.  Any help would be appreciated since this is the last holdout before rolling out a couple dozen of these devices to meeting rooms in my organization.  Thank you.

Occasional Contributor

@Guido Peter  I think the actual front screen UI is the same, just if you start a meeting/call it will be Teams-based. 

Occasional Contributor

@SSleeper I think from @Ilya Bukshteyn’s original post it is waiting for it to be enabled on the cloud service side. Hopefully this happens soon as it is the only thing holding us back from changing to Teams mode. 

Microsoft

@SSleeper @Ben Dodson There is no UX change on the console screen. In our MTRs internally we use the purple theme once devices are enabled for Microsoft Teams; theme settings are also under Settings on the console.  You will see the Teams meetings UX once the MTR joins a Teams meeting.

@SSleeper you should be seeing the dialpad now in Teams default mode. Can you please follow up with support and/or @Sohail Tariq on my team?

Occasional Visitor

Since moving to 4.0.76.0 I also have a number of rooms that have disappeared from OMS and are stuck on the Skype splash screen.  Do we know what is causing the issue?  Is there a team working on a resolve?  I have 167 units that upgraded recently.  I need to understand what has caused the issue and how best to resolve it.  Any assistance would be greatly appreciated.

Senior Member

@Ilya Bukshteyn @SSleeper  @Sohail Tariq I can also confirm that I have no dial pad after connecting to a phone call which is required for entering conference PINs or similar. 

file-10.jpegfile1-2.jpeg

Microsoft

@Keith Knowles  @SSleeper  I was incorrect above. The DTMF feature and video pin / unpin are both dependent on a cloud service change / feature flag. We're checking now on where that is in terms of getting enabled.  Should be very soon and we'll post here when confirmed.

 

@Steve_Esposito we're investigating your report. What does "skype splash screen" mean exactly?  Is that the splash screen when the MTR app is starting up?  

Senior Member

@Ilya BukshteynThank you for the quick update, I look forward to that feature being implemented so I can remove the physical phone from the table in my rooms. 

Senior Member

Having the same issue as @Steve_Esposito - Updated to 4.0.76.0 on Saturday at 2am. It automatically signs into the Skype account and gets stuck at a blue window. If you close the blue window, it attempts to reload but gets stuck again.

 

The program Microsoft.SkypeRoomSystem.exe version 4.0.76.0 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel.
 Process ID: 22cc
 Start Time: 01d4d81dba12cb23
 Termination Time: 4294967295
 Application Path: C:\Program Files\WindowsApps\Microsoft.SkypeRoomSystem_4.0.76.0_x64__8wekyb3d8bbwe\Microsoft.SkypeRoomSystem.exe
 Report Id: 747c8451-1426-4a30-8c08-4f6c21ff9cf5
 Faulting package full name: Microsoft.SkypeRoomSystem_4.0.76.0_x64__8wekyb3d8bbwe
 Faulting package-relative application ID: App
Application: DesktopAPIService.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.UnauthorizedAccessException
   at System.StubHelpers.StubHelpers.GetWinRTFactoryObject(IntPtr)
   at Microsoft.SkypeTeam.NativeUtils.RRegistryHelper..ctor()
   at DesktopAPIService.DesktopAPIService+<ThreadProc>d__10.MoveNext()
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
   at System.Threading.ThreadPoolWorkQueue.Dispatch()

Faulting application name: DesktopAPIService.exe, version: 4.0.76.0, time stamp: 0x5c795d8d
Faulting module name: KERNELBASE.dll, version: 10.0.15063.1478, time stamp: 0x7789680f
Exception code: 0xe0434352
Fault offset: 0x0000000000065a98
Faulting process id: 0x2b5c
Faulting application start time: 0x01d4d81f41b707df
Faulting application path: C:\Program Files\WindowsApps\Microsoft.SkypeRoomSystem_4.0.76.0_x64__8wekyb3d8bbwe\DesktopAPIService\DesktopAPIService.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report Id: e264aa21-5244-41f9-bd4b-01070d59684f
Faulting package full name: Microsoft.SkypeRoomSystem_4.0.76.0_x64__8wekyb3d8bbwe
Faulting package-relative application ID: App

 

srserrro.jpg

Regular Visitor

@Ilya Bukshteyn Thank you for the quick updates.  I'm loving how engaged eveyone here is to take care of this issue.  Makes me feel a little more reassured with the decision to go with Teams for a meeting room platform.  I know its not perfect yet but having engaged resources goes a long way to making this a great platform.

Microsoft

@SSleeper thank you for both the kind words and especially for betting on Microsoft Teams Rooms!

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

Senior Member

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