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
Native Teams Phone - Background Image
Hello all, Recently Our org. have purchased a few Native Teams Desk phone Poly CCX600 & Conference Trio C60. It appears the default Teams background image, which looks almost blank, after signing in the phone. I followed up the background image document provided by the vendor Poly without luck. Is anyway to modify the background image on these native Teams phones? Your information and support are highly appreciated. Best regards, EZ
Poly devices and the transition to Android Open Source Project (AOSP)
Today we had a handful of our Poly Teams meeting devices sign out and then refused to re-enroll afterwards. Our devices included Poly Studio X30, X50, X70 and TC8 touch panels. on the screens that were attached to the equipment, upon failure of sign-in and re-enrollment we saw a message on the screen saying "Signing out... This device isn't enrolled in device administrator. Contact your admin". The devices were still available in the Teams admin center so I was able to retrieve diagnostics from the devices. Within the CompanyPortalEventsLog* file in the root of the zip file containing the diagnostic data there was the following line TIMESTAMP CompanyPortalReasonCode: WORK_PLACE_JOINED CompanyPortalStatus: UNKNOWN FailureReason: ENROLLMENT_RESTRICTIONS After further investigation, the devices also had updates applied to them during the early morning hours. After some searching and reading through this article Moving Teams Android Devices to AOSP Device Management | Microsoft Community Hub - even though my devices weren't supposed to be available until February, I followed Step 1 to create an enrollment profile for Android Open Source Project (AOSP) with the settings outlined. However, in my tenant, "For Microsoft Teams Devices" was still being marked as preview. Once this profile/policy was in place I was successful in logging our devices in with their resource accounts. Lucky us that it happened on Friday and not one of our core work days. So, watch out for your Android Teams Room devices with this change/transition happening. Try to work ahead of it to prevent Teams Meeting Room Android devices and Android phones from experiencing downtime in your offices and set the policy up as soon as you can. There's a secondary step to make sure to have a Compliance policy in place for AOSP devices as well, be sure to have that set up so that your devices are still flagged as Compliant in your tenant. https://learn.microsoft.com/en-us/mem/intune/protect/compliance-policy-create-android-aosp If anyone else sees any other symptoms of this issue post them to this thread to help others troubleshoot.
User getting not informed in ACTIVITY when SharePoint library is updated
Hello After a couple of weeks user are not getting informed in Teams ACTIVITY when a new or updated document in the library is created. It is a bit weird as some are getting updates others are not. But the ones not getting updates, getting updates from others. If we are looking inside the settings of the client, everything is ok. They will get notifications in their ACTIVITY in Teams. How can we fix that problem? Thanks in advance. Kind regards Michael DamaschkeHow to Access Participants’ Camera and Mic Device Names in a Teams Plugin
Hello, I’m currently developing an integration for Microsoft Teams focused on enhancing meeting security. One of the features I’m looking to implement involves gathering information about other participants’ camera and microphone device names during or after a meeting. Could anyone point me to the appropriate Microsoft Graph API endpoints, SDKs, or supported methods that allow access to this type of device information for meeting participants? Any guidance on how to implement this functionality correctly and in compliance with Microsoft’s policies would be greatly appreciated. Thank you!Teams SIP Gateway connected phones and voicemails
We have a strange issue. A Teams user got a new SIP device that is successfully integrated via SIP Gateway. If a caller leaves a message, it will appear as a voicemail in Outlook, all Teams apps and devices. The SIP device also shows that there is a new voicemail, but if we want to listen to the voicemail and press 1, we get told that there are no voicemails. Do we need to change or add anything in the configuration? Regards, MatthiasSoft Focus is (Suddenly) Unavailable for Some Users
Some users are suddenly getting this when attempting to use soft focus, though they were able to use it in the past. We (IT) haven't made any specific changes that I know of that would affect this. Does anyone know what has changed within Teams and why it's mentioning network connection? (Users are of course able to join their meeting with video, just not soft focus.)
Microphone not working mid call
I use teams with my bluetooth headset. But all of a sudden few weeks ago my problem starts. Micrphone is unmuted, but nobody can hear me. When i go to audio settings switch to notebook mic and back to headset, it works. Then i mute mic and again unmute and again nobody can hear me. I didnt change anything. I dont know if its so hard for M$ engineers to make simple IM app where the basics work without issue. Really hate this app and somebody from M$ should be fired for this piece of sh*t.
