Autopilot Error (0x81036502) - Endpoint Manager
Dear community members, I am facing an issue with my Endpoint Manager's autopilot feature. It suddenly stopped working and I am receiving error code 0x81036502. I would greatly appreciate any help or advice on how to resolve this issue. According to my research, this error is related to either a timeout issue or with the Windows 10 version 22h2. I am running Windows 10 version 22h2 on my endpoint. I have tried several troubleshooting steps but to no avail. If anyone has any information or suggestions, please share them with me. Thank you for your time and assistance. Best regards, Rashad Bakirov
Why is "Activate device admin app" displaying when setting up Outlook on Android?
Hi Everyone, I'm not very experienced with the Intune product set and within my tenant I don't have admin access to manage any settings related to mobile access management. From the beginning of this week, I'm receiving reports from people installing the Outlook for Android app and connecting to our tenant that they are seeing an additional "Activate device admin app" screen that we were not expecting to see. The screen is that which is displayed at the following URL https://support.office.com/en-us/article/set-up-email-in-the-outlook-for-android-app-886db551-8dfa-4fd5-b835-f8e532091872 None of the admins have reported making any changes at tenant level. Are there any reasons why this message will have started appearing at this stage? Could Microsoft have made a change to the configuration settings? (perhaps one that has been announced already) Thanks everyone.
Autopilot Pre Provisioning Stuck at Device Setup
Hello Everyone, I was trying to use Autopilot Preprovisioning for Windows 10 devices that we would like to setup before we deliver it to our end user. We were getting correct Intune Autopilot profile Once we click on Pre provisioning Device Prepration completed in 2 minutes then Device setup never completed and stuck on Identifying for 60 minutes As my ESP setting is set to 60 minute. I am getting that red screen mentioning that provisioning can not be completed. however that device is visible in Endpoint portal with correct name template as per Autopilot profile Not sure why it is getting stuck at Device Setup Unable to identify Apps Configuration profile network Your advise on this issue would be really appreciable. I have tried it on OOBE device and existing device that met all the pre requisite.
Intune App Protection Policies (The apps on this device are already managed)
Hi One of our users got this error for some reason. The device is an iPhone, enrolled into Intune. When the user opens Microsoft Teams they get the following error. Remove Account The apps on this device are already managed. Only a single managed account is allowed on a device. Select the account you want to remove. This account and all associated data will be removed from all managed apps. Then it displays two identical work accounts for the user. (Example) user @ domain.com user @ domain.com No matter what we delete this just goes on and on for Teams, no other apps has this issue and no other user has this issue, and it just started happening today.
Company portal failing to install error 0x87D1041C
Hello Everyone, I have added company portal (offline version) from Microsoft store for Business and deployed it to 6 autopilot enrolled windows 10 laptops. All laptops are with same hardware & configurations. Out of all laptop, company portal application is getting failed in one windows 10 laptop. I have tried to uninstall and re-install it but it's showing same error every time in that particular laptop. However apps are getting published in company portal in that laptop. then why in Endpoint manager it's showing failed to install with error code 0x87D1041C.-2016281111 error Intune windows 10 update rings Using deadline settings
[Edited] Hello everyone, hoping you all are having a good day. I need some inputs on my current Windows 10 update rings policy. I set the deadline settings as shown below to multiple pilot devices. These devices are identical in all hardware but has different windows 10 builds (1909, 1709, 1903, 20H1, 21H2). Devices with Windows 10 1709 builds has been successful but I got this error "-2016281111 (Not applicable for this device)" on other versions. Policy Applied : User group User License : M365 Business premium and Windows 10 Enterprise E3
