Teams - Camera and screen share issue
Hi, Since yesterday we have been having firm wide issues with camera usage and screen share in Teams calls. When user 1 calls user 2, user 1 can see user 2s camera and screen share. User 2 cannot see user 1s camera or screen share. It seems to be that the recipient cannot see camera feed or screen share, but the original caller can see incoming camera feeds and screen shares. We have tried fully reinstalling and nuking local cache, but no luck. Before we start looking a bit deeper, has any others had this at all. Many thanks guys
HELP! I teach kindergarten..
Hi! Teams newbie here! We will be using Teams this upcoming school year for when we have a weather related day. The biggest thing that scares me is that they have access on the bottom part of their iPads it has the section where - video, mute/unmute/, speaker icons. Is there a way to remove the speaker icon for attendees, so students cant mute the presenter? Is there a way to change in the settings or somewhere to turn off access for attendee's to not have access to change their background effect? Thank you for any help! signed a Very Nervous Teacher
Teams with Third Party device
Hi. Is it possible to leverage teams as a "SIP Trunk" provider, or use a single user account with a third party desk phone? The reason for this would be to provide a couple SIP trunks to an onsite phone system which has SIP capabilities (Yeastar P series). I keep looking at provisioning phones, but it requires codes to be generated and entered, and I was hoping there would just be some standard SIP credentials available, such as the SIP domain name, username and password. This is all that is required to register a SIP Trunk usually. Is this possible at all? There are already many teams phone accounts in operation on the tenant, but one site has an existing phone system which is able to make internal extension calls just fine, but currently has no external calling available due to SIP trunks being cancelled by the owner. They had hoped to use Teams for the trunks. Thanks.Please help, i cannot login into any of my microsoft teams accounts on the app.
So i randomly wasnt able to login into any of my microsoft teams accounts on the app. it would load for a little and end up showing: sorry, we werent able to log you in your account, please try again later. i think that the app might be the problem, because it works on the web and any other device. I am on a samsung tablet by the way. I have been desperatly trying everything for clear data app, cash, uninstall and reinstall, turn on and off my device. i am in desperate need of the solution to my problem.
delete Teams Members from Azure Admin not sync on Teams App
Hello All, i have deleted bulk of Teams members for group of Teams that we have from our Azure Admin three days ago, and all done successfully. but tell now, i a can see the member in some of our Teams still there in Teams App, but empty in Azure !!! any clue plzNative 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, EZTeams 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
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.
