Remote Access in Pro Portal not working with Public Preview R3.6
When I try to use Remote Access via the Pro Portal, I can connect to the MTR but the image is flashing. I cant seem to have a stable session with the MTR. The screen will go to black for around 5 seconds, then it shows what is on the screen for less then 1 second. I tried it on 2 MTR devices that I have in our labo but the issue remains. When I revert the option for Public Preview back to off, I am able to connect and use Remote Access via the Pro Portal without any issue. We are using MTRoW and have the latest updates.Teams Room System Autopilot deployment does not work - Error Code: 6, 0x80180014
Problem: We are attempting to deploy our Microsoft Teams Room (MTR) systems, some of which are already in use, using Windows Autopilot in self-deploying mode. Despite following the official guide, we keep encountering errors. https://learn.microsoft.com/en-us/microsoftteams/rooms/autopilot-autologin Procedure: Device: Certified Intel NUC, previously in use. Installation: Windows 11 Pro installed. Autopilot Import: Device imported into Autopilot. Group Assignment: GroupTag "MTR-ConsoleName" assigned. Dynamic Group: Device appeared in the Dynamic MTR group. Assignments: Deployment Profile and ESP (Enrollment Status Page) assigned. Teams Room Update App: Deployed via Intune, assigned to the MTR group, and integrated into the ESP. LAPS: Local Administrator Password Solution (LAPS) is active. Teams Rooms Pro Console: Device appeared and was assigned to a resource account with a Teams Room Pro license. Error Description: After the setup process, we consistently encounter an error during device registration for mobile management: Error Code: 6, 0x80180014 Attempts to resolve the issue: Deleted the device completely from Intune and Autopilot and re-added it. Created a custom Device Restriction Policy to allow all devices in the group. Additionally, during one attempt where the error did not occur, Teams failed to set up automatically. Questions: Why does error 6, 0x80180014 occur during device registration for mobile management? Are there specific requirements or settings beyond the official guide that need to be considered? What steps can be taken to ensure that Teams sets up automatically when the registration error does not occur? Objective: We aim to ensure that the MTR systems are smoothly deployed via Autopilot in self-deploying mode and that Teams sets up automatically. Thank you for your support!Teams Room System Autopilot deployment does not work - Error Code: 6, 0x80180014
Teams Rooms Limitations
I set up 2 Teams Rooms for one of my clients and in learning how to set up and use a Teams Room and train the client, there seems to be a LOT left to be desired with Teams Room, especially for the price of the Teams Room Pro license! The Teams Room includes an Audio Conference license, but if you want to use it you have to send the invite AS the room. So users needing this would need to be a delegated admin of the room resource. And who wants to send out an invite from "Main Conference Room on behalf of Jane" to their customers? This means each user needs their own Audio Conference license* to send out their own invites and then add the Teams room. What is the point of the room having an audio conference license? If you add a Teams Room to your invite, the attendees are shown the location of the meeting as that conference room, the only clue it is an online/teams meeting is the Teams info in the invite's message body. Then when the attendee gets an Outlook reminder for the meeting it actually shows the location as the conference room NOT a Teams meeting. No minutes are included so you can't actually use the Teams Room as a conference phone unless you add minutes. I would think for the cost of Teams Room Pro it would include a Teams Phone with Calling Plan license. So if you just want to have a conference call you have to setup a whole Teams meeting and then just use the audio portion. This has been a very difficult journey. Explaining all of this to my client after convincing them to spend a good amount of money on a Teams Room setup (equipment cost, to be fair, is not a Microsoft problem) and then continually telling them the limitations and how they need to spend more money for additional licenses to get the features they want is not a good solution. For those looking to sell a Teams Room, do the research first and be warned it is NOT a cheap or easy solution! *Thankfully the Audio Conference license is now free, that's a big thank you out to Microsoft for that!
Town Hall forced producer view for Teams Room
Teams room accounts added as presenters to a Town Hall are joining the meeting in the co-organizer view, no matter what role was assigned. Prior to 03/10/25, Teams Room could join as presenter and had meeting view control. Some change seems to have taken place over the weekend, and now even room accounts scheduled as external presenters are joining in the co-organizer view. The in-meeting change view button is now blocked during a the Town Hall. Has anyone else seen this or know about the change?
Yealink HDMI ingest - lag and call failure
We have many Yealink MVC800ii and MVC840 MTR systems running in our meeting rooms. We're seeing real issues with HDMI ingest, particularly using the HDMI cable that connects to the MTouch II panel, and less so when using the WPP20 wireless dongle - but both are not working optimally. The usual pattern is that either presenting or sharing content (both scenarios are affected) works until around 50-60mins into a call/meeting then things start getting really laggy. Mouse moves or slide navigation are delayed and not seen on the front-of-room displays or by external participants for several seconds. The delay then starts to extend to 30+seconds, usually resulting in the call eventually dropping and the MTR needing to be restarted. This is happening in different rooms, to different users using different models of laptop and when sharing content stored locally on their devices as well as opened directly from M365 services such as SharePoint or OneDrive. All indications point towards a problem with the in-room kit, like a memory leak. All of our systems have fully up-to-date software and firmware and I've confirmed that they are restarting nightly via the 02:01 scheduled task. Other than Extron CTL100 workplace controllers installed in some of the affected rooms, there is no 3rd-party hardware involved in the MTR set-up, its all standard Yealink kit. We've swapped out components, cables, and even factory reset and rebuilt some systems. Call activity and system health shown in the TAC rarely show any issues. Sometimes there is a report of 'poor' audio quality in some (not all) of the affected meetings, but generally everything appears 'healthy' or 'good'. Has anyone experienced these symptoms (with Yealink or other manufacturers)? Or any ideas on what to try? It's now a real problem for us as we open more MTR equipped rooms.
