![]() ![]() ![]() ![]() The second scenario is when your Windows 10 device is enrolled through Azure AD join with auto-enrollment. ![]() If the apps are deployed as Available and the users have selected install from the Company Portal, the user would see Download pending in the Company Portal. Otherwise, if the MSI or Win32 apps are deployed as required you may see status of Pending or no status. If you want apps to be deployed through Intune, then you’ll move the slider for Client apps workload to “Pilot Intune” for devices in the pilot collection or “Intune” for all Windows 10 devices enrolled in co-management. When a device is co-managed, the admin needs to decide which of the workloads are managed by Configuration Manager and which of the workloads are managed by Intune. The first scenario involves Configuration Manager and Intune co-managed Windows 10 devices and MSI and Win32 apps. Below we share two of the most frequent reasons apps are in the “Pending” state. We have received a few support cases recently where customers using co-management - when a Windows 10 device has the Configuration Manager client and is enrolled to Intune - reported that apps are unexpectedly shown as pending in the Intune admin console or download pending in the Company Portal app after the user has clicked on install. Service Engineer | Intune Support as a Feature ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |