Microsoft Teams Rooms July Update

Published Jul 17 2019 11:35 AM 89.8K Views
Microsoft

Microsoft Teams Room app update 4.0.105.0 is now rolled out via Windows store. This app update includes various client and service features for Microsoft Teams Room devices.

App rebranding to Microsoft Teams Room

Skype Room System V2 app is now rebranded to “Microsoft Teams Room” as announced previously in this blog post. This rebranding brings room devices a step closer to alignment with Teams calling and meeting experiences and makes UI consistent across Teams clients for all your users. Apart from name changes in the store, this update brings Teams brand color, iconography and theme to Microsoft Teams Room devices.

 

image.png

Theme updates

With this update, Microsoft Teams Room devices console are updated to Microsoft Teams look and feel and themes only apply to Front of room displays but not on meeting room console. This greatly enhances readability of controls on the console as well as make sure color-contrast requirements for accessibility are met. We understand company branding on the console is important to our customers and we will enable adding company logo on console in future releases.

 

image.png

 

In meeting call controls

In meeting call controls for Teams calls/ meetings are now updated to using same familiar universal bar as in Teams PC/ Mobile clients. Please note that this is a Teams service-based rollout and doesn’t require client build 4.0.105.0. However, we recommend updating to newer client build so you can get latest Teams client bug fixes and updates.

 

image.png

Rate my call

We are also rolling out a call quality rating experience similar to the PC and mobile Teams clients after a call or meeting so you can let us know how your call went. This is a great way for participants to provide feedback about the quality of the audio and video of their calls and meetings to your company’s IT and to Microsoft. Microsoft uses this data to ensure that we continue to provide high quality calling and meeting experiences across the ecosystem of Teams personal and shared devices. This dialog dismisses automatically after few seconds if no rating was provided.

 

image.png

 

Microsoft Whiteboard support

We have also completed the rollout of Microsoft Whiteboard across Teams client including Microsoft Teams room devices. Microsoft Teams Rooms can now receive and render Microsoft Whiteboard on the front of the room displays when shared from PC/ Web/ Mobile Teams client. Support for starting a whiteboard session from Microsoft Teams Rooms will be added in future releases. If you have /or add touch front of room displays you can contribute to the shared Microsoft Whiteboard in the room to collaborate with remote participants.

 

image.png

 

To ensure you can use Microsoft Whiteboard in Microsoft Teams Rooms, make sure Microsoft Whitebaord Web is enabled for your tenant. Instructions here

 

In order to configure a front of room display as touch device (provided the display supports touch), you should login using Administrator account on Microsoft Teams Rooms device and then use settings for “Calibrate the screen for pen or touch input” to calibrate additional touch displays in the room.

 

image.png

Windows 10 version 1809 update

We are doing intensive testing of our software across our meeting room hardware to ensure a high quality reliable experience, therefore we  do not recommend updating Microsoft Teams Rooms devices to Windows 10 Version 1809 due an compatibility issues found with Microsoft Teams Room client. We are actively testing Windows 10 Version 1903 and support for 1903 will be added in future releases.

 

Let us know what you think!

Try the new features on your Microsoft Teams Room and provide feedback via User Voice or vote for existing ideas to help us prioritize the requests. We read every piece of feedback that we receive to make sure that the Microsoft Teams Room experience meets your needs.

https://aka.ms/mtruv

 

- Sohail Tariq, Program Manager, Microsoft Teams Rooms

325 Comments
Contributor

@Ilya Bukshteyn  thanks.  No problem I get it.  Looking forward to some of the things I'm assuming will get announced / launched at Ignite based on some of the session's I've seen posted.

Regular Visitor

Hi, please let me know if you plan to modify the function of the layout button. Our current issue is that we have a presentation device permanently connected to the MTR system having only one screen. This results the video coming from that input is always shown locally on MTR using 90% of the screen during the call, no matter if there is something connected to it or we plan to share it with the remote side. The ideal operation of the layout button would be to be able to toggle between the following modes (local video can be in PIP in all cases):

- show content only

- show far site only

- show content in large and far site video in small

- show far site in large and content in small

This is a basic feature standard video devices like Cisco or Polycom can do since years. I know this would not be an issue with dual screen systems, but in our case we have to use only one screen.

Microsoft
Yes we plan to add more layout options in Teams Meetings on MTR in CY20.
Occasional Contributor

@Ilya Bukshteyn 

Our devices now updatet to Win 10 1903, but after restarting they are asking for some data protection settings and service settings (see attached screen).

Is it possible to avoid these messages? Users don't know what to do with this settings when they join the meeting room in the morning. I cannot check every room every day, if there was a new win10 build....

IMG_8389.jpg

Senior Member

@Daniel Jelinek , What edition are you using? Pro, Enterprise? Are you using the recommended group policy settings? We have over 20 teams room units on 1903 and have not seen this message.

I did not do an in place upgrade, but used the sccm task sequence for room units, wiping and re-installing windows with the latest Teams Room update. This works great, and is low maintenance. The only issue I have is the occasional surface frying due to the poor ventilation on the Ploycom and Logitech designs. We loose about 1 surface per year so far due to this. This has prompted up to move to the HP Slice.

Microsoft
Jonathan is correct, you should not be seeing any messaging from Windows if configured correctly.
Contributor

We've experienced this experience on all of our units.  We are using the recommended enterprise settings from the website, and have a mix of room systems that were either a) re-imaged using the notes from the doc site, or b) taken straight from the box.

 

As a side note, regular workstations that are being managed by SCCM, and imaged with our own image have not seen this experience.

 

Senior Member

@Dustin Halvorson, Did you use the recommended answer file for sysprep? It looks like from @Daniel Jelinek's screen shot that user OOBE is not getting skipped. 

Contributor

@Jonathan Orton  I'd have to look, but the 8-10 units we have that were taken directly from the box, and installed on the wall, we would have never gone through the sysprep/imaging process.  For the regular user, who has a regular customized 'enterprise' image, of course all of that is set and we never see those experiences.

 

Regular Visitor

About Microsoft Teams Rooms 4.2.4.0.

Can you please clarify requirements for the latest Microsoft Teams Rooms 4.2.4.0? I had no problems installing previous versions but now with 4.2.4.0 it says "A prerequisite for an installation could not be met (error 0x80073cfd).

I'm still using Windows 1709 and have doubts if it can be related to Windows version?

 

clipboard_image_0.png

Microsoft
This is indeed related to Windows version. You are using a 2 year old Win 10 release. We only support two releases of Windows back at any given time.
Microsoft
Occasional Contributor

@Jonathan Orton @Ilya Bukshteyn 

The devices are Running Windows 10 IoT and were preconfigured from our distributor. In fact, i did not change any settings, because i thought they were configured correct. 

 

Which GPO Settings do you mean? Who knows the correct settings for hiding this messages? The truth about not joining the systems to the domain, was the fact that when domain joined, the systems were extremely slow.

 

In fact i cannot use the unattended.xml settings, because we are not re-imaging the devices.

 

Thanks for your help.

Occasional Contributor

@Jonathan Orton @Ilya Bukshteyn 

We are facing the same issue. Our devices received Win 10 1903 over the weekend which put the devices into OOBE dialog mode and asking for user input about preferences regarding speech recognition, pen usage, location services,... 

All devices had been deployed with out-of-the box Win 10 by the vendor (Lenovo), no re-imaging, no domain join, MTR app manually configured. 

Following the advise on the version page we have not overridden any GPO settings or used SCCM or third party management with regard to Windows updates.

So, how can we hide these upgrade dialogs and keep the devices operational after upgrades?

Thank you!

Senior Member

@Daniel Jelinek@Harald Rau  I would advise you NOT use the OS pre-installed on the units. Who knows what is going on, for instance we received one unit that was pre-configured for another organizations domain! You should re-image, and if you do not have an imaging solution you can use the Installation Media Script to create a flash drive for installation found here: https://docs.microsoft.com/en-us/microsoftteams/room-systems/console#Reimage
The script includes a sysprep answer file that disables OOBE user mode, which bypasses all those questions you are being asked about pen, location etc. Sysprep is the only way I know of to get rid of those messages. You can see this by looking at the answer file included on the Flash Drive Imaging solution. Although Feature updates are supported, I have been re-imaging them, the beauty of SCCM, a few clicks and 80 minutes later the units are re-imaged, then all I have to do is sign into all of them.

IoT is only support if it is Enterprise, we just use Enterprise (not IoT Enterprise) which has been solid for us, so make sure that is the case. IoT LTSB for instance is not supported as noted here: https://docs.microsoft.com/en-us/MicrosoftTeams/room-systems/srs2-lifecycle-support

If the units are slow after joining your domain it is most likely because other group policy settings are hitting the unit that should not, or you have other issues with your domain. These units should be placed in an inheritance disabled OU, so they do not get any GPO's that they should not. Also your Default Domain policy should be minimal, as these settings will still hit the units. We additionally set up QoS settings to ensure the units have network priority over other devices on the network.

I searched, but cannot find the GPO settings recommended for the units, Maybe @Sohail Tariq  or @Ilya Bukshteyn could point you to the correct article regarding GPO's? But I got them from a MS article. They include auto admin sign in, and power settings etc.

I hope this helps guys! Good luck!

Senior Member

Hi, MS experts, does the latest Teams Rooms 4.2.4 disable the PC/NUC sleep mode? this did work in the previous release, 4.0.105 or earlier, but not working on 4.2.4, is it a fix or something else? thanks.

Occasional Contributor

@Jonathan Orton @Ilya Bukshteyn 

 

Ok, joining to the domain with all other policies blocked is an option, this may resolve the "slow" issue. But honestly, not every customer of us who is using Teams Rooms, has a software deployment solution like SCCM. And especially for a central meeting room system i don't want to have additional work with feature upgrades. The customers buy such a system to have a stable and user friendly system which is just managing himself as far as possible. Re-imaging with every build of windows is not the solution i think, especially if the have no SCCM.

 

I found the following article. This looks like it could work even for the 1903 oobe problems.
https://winaero.com/blog/disable-privacy-experience-windows-10/

 

And the article from MS for the GPO setting is this one, but there is nothing about disabling OOBE.
https://docs.microsoft.com/de-de/microsoftteams/room-systems/room-systems-v2-operations#configuring-...

 

I will try now to set the local GPO on my non-domain joined systems (of course if you have many devices joining the domain and setting gpos is more effective).

Occasional Contributor

Thanks, @Jonathan Orton for sharing all this help!

We try to manage the units following the modern client architecture approach: units are not domain-joined or LAN-connected, instead joined to AAD and enrolled to Intune MDM to be enable us to push device policies down to the units and grant cloud-access via conditional access based on the device compliance state.  So re-imaging and SCCM are not options for us.

When we receive the units we use the build-in factory reset to make sure the devices have a clean OS installation, ready for the MTR configuration. 

 

The device itself decides when to pull an OS update, triggered by Microsoft, so it should continue to behave like a true kiosk device and just bypass the OOBE mode to stay operational after updates. That really needs to become a build-in feature.

Occasional Contributor

@rickydeng Haven't seen the issue, but maybe a gpo is overwriting the setting mentioned here:
https://docs.microsoft.com/de-de/microsoftteams/room-systems/room-systems-v2-operations#configuring-...

 

 

Occasional Contributor

@Harald Rau Have you seen my solution for the oobe problem:


I found the following article. This looks like it could work even for the 1903 oobe problems.
https://winaero.com/blog/disable-privacy-experience-windows-10/

Frequent Visitor

Hi Teams Professionals

 

At our company we are on an evaluation process to launch MS-Teams for our conferencing. In this phase we got 2 different devices to run, Logitech Tap, Lenovo ThinkSmart Hub. Everything is ok so far, but we are hardly trying to get audio in presentation mode to the conference. With desktop app it works fine since last updates by sharing system sounds. But in MTR this option is missing when plug an HDMI fom Latop/PC to the Logitech or Lenovo.

MTR versions are 4.2.4.0 on both devices.

Windows 10 Pro 1903

Will it be able in one of the further releases?

 

Many thanks

Oliver

Microsoft
@Rolias, unfortunately we have not had a chance yet to implement "share system audio" on the HDMI ingest in MTR. That is for sure on our backlog. We are hoping to get that done in Q1CY20.
Regular Visitor

Guys,
Does anyone know how to run command prompt with administrative privileges in MTR user session? Previously in Windows 1709 I used Windows button on attached keyboard. But seems in 1903 it doesn't work anymore.

P.S. Forgot that Win+Tab still works. The question is removed

New Contributor

@Rolias Hey Oliver, are you looking for this one? https://support.office.com/en-us/article/share-system-audio-in-a-teams-meeting-dddede9f-e3d0-4330-87...

 

If you want to share system audio when you’re in a meeting room with a Teams device in it:

  1. Join the meeting from your personal device by selecting Audio off when you join the meeting, which will automatically mute not only your microphone but also any audio playing from the teams meeting to prevent echo.

  2. Select Share in your meeting controls and then Include system audio

It works in Teams meetings but not with Skype.

Super Contributor

@Sohail Tariqyou wrote earlier:

 


Please see OS version support section of the Microsoft Teams Rooms docs:

 https://docs.microsoft.com/en-us/microsoftteams/room-systems/srs2-lifecycle-support

 


The table on the page says, 1809 should be skipped. But has there been some changes lately on this? As now I can see from my device update section, that you are offering 1809 to these devices?

clipboard_image_0.png

 

 

 

Contributor

I am not sure if this is the correct channel to post this question, but did I read previously that a future rooms app update would introduce native wireless content sharing? By that I mean, when a participant is physically located in a Microsoft Teams meeting room, they could connect directly to the meeting room device (Yealink MVC800) and share content? So the meeting room device would be creating its own wireless network.

Super Contributor

Hey MTR Product Team,

Can you please help user with one very very small issue on the MTRs

 

When you make a call to person or in our case to another room, you try to search it. This leads us to the following problem:

MTR Search too short1.jpg

 

The results field is showing only the first 26 characters from disaplay name. Meaning, when we are using the street addresses on the name, users are unable to define what is the correct participant to call as they all looks the same.

 

When looking for the [Invite] / [Cancel] buttons and see how wide they are, and stealing valuable space from the search, I only could wish this could be fixed. The best option is to move the buttons below the search field and then having much wider the search results.

 

Senior Member

Hi All
Today we try to do an ad hoc meeting directly from MTR device and we found that there is no possibility to invite a group nor send invitation for a channel which works fine from standard teams client.  It is by design or it should work from MTR ?

The environment is hybrid with AD and Exchange on prem.

 

 

Microsoft
This is by design as of today.
Occasional Contributor

When you have a larger number of participants in a meeting and you want to mute/unmute individuals via the touch panel, the scroll down control of the participants lists seems to be broken such that you can't mute someone from the bottom of the list. The scroll down will immediately jump back to the top of the list before you can pick some one from the bottom. 

Microsoft

@Harald Rau, We have not seen this issue. Please help with repro steps and logs so we can look into this. 

Contributor

@Sohail Tariqhas support for Windows 1909 just been released? It's appeared on our lab MTR and I'm now wondering if it's rolling out everywhere? Is it formally supported yet as I've not heard much on it, and is it an issue to upgrade?

 

https://docs.microsoft.com/en-us/microsoftteams/room-systems/srs2-lifecycle-support

 

Version Availability date Microsoft Teams Rooms support status Microsoft Teams Rooms Minimum application version Recommended OS build

19092019-11-12Currently validating,
Not Recommended

 

Jed

Microsoft

@Jed Ellerby , Windows 10 1909 release is still under validation and not recommended to use with Microsoft Teams Rooms. If you are being offered an update to 1909, it may be due to policy override on the device by Admins using group policies or an external management program/ service you may be using to manage these devices.  

Super Contributor

 


@Sohail Tariq wrote:

@Jed Ellerby , Windows 10 1909 release is still under validation and not recommended to use with Microsoft Teams Rooms. If you are being offered an update to 1909, it may be due to policy override on the device by Admins using group policies or an external management program/ service you may be using to manage these devices.


Would it be possible Sohail for  you to share a bit more the information about the policy override? How MTR controls what release it should try to get from updates, and what policy that could be overrided?

Super Contributor

@Harald Rau 

May I ask what on which scale of participants you have seen this kind of behaviour?

Occasional Contributor

@Petri X 

I believe it must have been 15 or so participants. Just enough to enforce a scroll down control to be displayed at the participants list.

Contributor

@Sohail Tariqthe MTR in this case is not domain joined so no domain GPO policies affecting the Windows updates, or any other update mgmt. solution. However, we have changed the quality and feature update timers (this is a lab testing device) which I bet has impacted it:

 

Lab Testing Built MTR

DeferQualityUpdates = 1 (enabled)

QualityUpdatesDeferralInDays = 30 days

DeferFeatureUpdates =  1 (enabled)

FeatureUpdatesDeferralInDays = 30 days

 

Standard MS Built MTR

DeferQualityUpdates = 0 (disabled)

QualityUpdatesDeferralInDays = 0 days as immediately applied

DeferFeatureUpdates =  1 (enabled)

FeatureUpdatesDeferralInDays = 154 days

 

So, the standard deployment would avoid a feature update (Windows 1909) for 154 days once approved and I guess we have hit a 30 day window and it has deployed on the lab MTR. Does that sound correct @Sohail Tariq ? It shows 1909 is ready to roll later in 2020 unless you do something special to defer it I guess.

 

Jed

Microsoft

@Jed Ellerby , FeatureUpdatesDeferralInDays is what we use. Default is 154 days and we don't recommend changing it. If everything goes well with our validation, we expect 1909 be available in 2020, else one of the app updates will override this value. Hope this helps. 

Senior Member

hi all,

 

do you have encounter the onscreen keyboard which is not appearing? i have to connect a usb keyboard and it will appear. rebooting ,reset the app wont help. i am using the new version.

Contributor

We still see the on screen keyboard issue (no keyboard appearing) on some systems, HP Slice in this particular case. The MTR is running all the latest OS and app versions and used to be fine, so it's something that appeared during an update cycle. A reboot is the only fix that has been identified so far.

Senior Member

@rodelmurex@Jed Ellerby, Yes this still seems to be an issue sometimes. A reboot usually fixes it. Also you can touch in the text box, the on screen keyboard does not appear, then leave that screen, go back and touch the text box again sometimes works.

Senior Member

Anyone else having issues with the UAC prompts not showing up? Seems to have happened in out environment after the Dec 1903 patching. If I click settings, I can hear the UAC prompt sound, but the UAC window does not appear. If I go into another screen, like clicking on create a new meeting the previous UAC prompt will come to the front. I am not sure what is causing this issue, but it seems related to Windows 10 Kiosk mode. 

@Sohail Tariq, Any other reports of this? Can you add this to the bug list? I have tried re-imaging a device and the issue still persists. 

Senior Member

for onscreen keyboard issue, i manage to resolve it using the below. Delete and add . So far so good for now.

 

Seems issue with the new update 4.3.23.0 for Lenovo hub. Surface pro not affected.

 

  1. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\TabletTip\1.7
  2. Delete this Dword - EnableDesktopModeAutoInvoke
  3. Re-add again this DWORD with same value 1 - EnableDesktopModeAutoInvoke
Senior Member

@rodelmurex is your Lenovo hub still working correctly with the keyboard auto invoke after recreating the registry key? We have this issue with some of our HP Slice G2 units and the reg fix has not worked.

 

 

Senior Member

@Sohail Tariq@rodelmurex on our HP slice i have found that if you unplug the touch screen (USB-C) then plug in again the keyboard pops up as it should.
This is leading me to think that there is a problem with the USB drivers? Does any one else have the same problem with their units thats resolved when they unplug/re-plug the touch screen in.

Cheers all

Super Contributor

Apologies if this was asked before - I would like to control updates to the Teams app on our MTRs.  What is the name of the app on the Windows Store?

Contributor

What about the recording control on the MTR. we still havent see that released?

Microsoft

@bjones96 , Recording control from MTR is delayed to H2 CY2020 to allow better management of recorded videos from the room.

@David Phillips What system do you have?  If it's an OEM, then you won't see the "Skype Room System" app in the app store.  It will be updated in the background.

Contributor

@Sohail Tariq sorry what does h2cy2020 mean?  Thanks. Also what about integration in mtr with zoom etc? Thanks. 

Version history
Last update:
‎Jan 26 2021 10:22 AM
Updated by: