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.
Cloud Storage not visible on managed Android
Hi, We have about 20 fully managed Android phones running Teams. We've added to a channel a cloud storage link to SharePoint. Up until yesterday (3rd of January 2023) this worked perfectly. However, now these aren't visible anymore. Logging in with the same user on the web, non MDM (intune) managed smartphone (but still managed with MAM) do show the cloud storage folder. Access rights (read) in SharePoint are ok, I can navigate to the location in Sharepoint via the URL. I've also excluded a device of all policies (MDM and MAM) but nothing changes. Anyone else who has this issue?Teams Android Devices Endpoint Manager Corporate Identifiers
Hello! I get various Teams Devices (Panels, Phones, MTRoA) enrolling to EndpointManager/Intune without any problem. Works perfectly. The enroll, they are checked against policies, etc.. all good. HOWEVER, I totally fail with them showing up on the corporate iIdentifiers page. I tried adding them with both a) their serial number as reported in the TAC or the device properties as well as b) their MAC address as suggested by some blogs. No difference. They do not report on the corporate identifiers page ("never contacted )and therefore do not move automatically from being personal devices to corporate owned devices. Is there any trick I miss? Thanks for any pointers.
Office 365 ProPlus - Teams Client missing / different O365 versions
Hello everyone, i'm experiencing the following two problems while deploying office 365 ProPlus within intune: 1. When deploying my default O365 AppSuite the client is receiving this just as expected, but the teams client is missing after installation. Of course i ticked the checkbox "Teams" in the blade "Configure App Suite" ;-) The Installation state is succesful. 2. I try to differntiat between some Office 365 ProPlus Installations: First: A basic package "O365 ProPlus Semi-Annual Channel" - Access, Excel, OneDrive Desktop, OneNote 2016, Outlook, PPT, S4b, Word, Teams Second: A basic package "O365 ProPlus Monthly Channel" - Access, Excel, OneDrive Desktop, OneNote 2016, Outlook, PPT, S4b, Word, Teams Third: "Publisher Semi-Annual" - only MS Publisher Fourth: "Visio Semi-Annual" - only MS Visio The Installation of the default package (first one) via required is working. When i try to publish the third and fourth package, either as available or required, this is not working. 1. Availability set to "available": it is'nt appearing in the company portal. (the first one shows up correctly) 2. Availability set to "required": Error Code (0x87D1041E) Regarding to the 2nd error i found this forum entry. Do you guys have any experiences with this? How do you deploy office via intune? My thought at this was: Every user is getting the default programs via "required" setting. If a user needs publisher or visio he can download it via company portal ("available" setting for the belonging app package) Thank you in advance. :-)
