%3CLINGO-SUB%20id%3D%22lingo-sub-1365322%22%20slang%3D%22en-US%22%3ESupport%20Tip%3A%20Intune%20Co-Managed%20Windows%2010%20Device%20Apps%20in%20Pending%20State%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1365322%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSTRONG%3EBy%20Lee%20Yan%20%7C%20Sr.%20Service%20Engineer%20%7C%20Intune%20Support%20as%20a%20Feature%3C%2FSTRONG%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EWe%20have%20received%20a%20few%20support%20cases%20recently%20where%20customers%20using%20co-management%20-%20when%20a%20Windows%2010%20device%20has%20the%20Configuration%20Manager%20client%20and%20is%20enrolled%20to%20Intune%20-%20reported%20that%20apps%20are%20unexpectedly%20shown%20as%20pending%20in%20the%20Intune%20admin%20console%20or%20download%20pending%20in%20the%20Company%20Portal%20app%20after%20the%20user%20has%20clicked%20on%20install.%20Below%20we%20share%20two%20of%20the%20most%20frequent%20reasons%20apps%20are%20in%20the%20%E2%80%9CPending%E2%80%9D%20state.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20first%20scenario%20involves%20Configuration%20Manager%20and%20Intune%20co-managed%20Windows%2010%20devices%20and%20MSI%20and%20Win32%20apps.%20When%20a%20device%20is%20co-managed%2C%20the%20admin%20needs%20to%20decide%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fmem%2Fconfigmgr%2Fcomanage%2Fhow-to-switch-workloads%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ewhich%20of%20the%20workloads%3C%2FA%3E%20are%20managed%20by%20Configuration%20Manager%20and%20which%20of%20the%20workloads%20are%20managed%20by%20Intune.%20If%20you%20want%20apps%20to%20be%20deployed%20through%20Intune%2C%20then%20you%E2%80%99ll%20move%20the%20slider%20for%20Client%20apps%20workload%20to%20%E2%80%9CPilot%20Intune%E2%80%9D%20for%20devices%20in%20the%20pilot%20collection%20or%20%E2%80%9CIntune%E2%80%9D%20for%20all%20Windows%2010%20devices%20enrolled%20in%20co-management.%20Otherwise%2C%20if%20the%20MSI%20or%20Win32%20apps%20are%20deployed%20as%20required%20you%20may%20see%20status%20of%20Pending%20or%20no%20status.%20If%20the%20apps%20are%20deployed%20as%20Available%20and%20the%20users%20have%20selected%20install%20from%20the%20Company%20Portal%2C%20the%20user%20would%20see%20Download%20pending%20in%20the%20Company%20Portal.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThe%20second%20scenario%20is%20when%20your%20Windows%2010%20device%20is%20enrolled%20through%20Azure%20AD%20join%20with%20%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fmem%2Fintune%2Fenrollment%2Fquickstart-setup-auto-enrollment%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Eauto-enrollment%3C%2FA%3E.%20When%20the%20user%20logs%20onto%20the%20device%20using%20a%20local%20account%2C%20the%20apps%20targeted%20to%20the%20user%20as%20required%20will%20also%20be%20shown%20as%20Pending%20or%20if%20the%20apps%20are%20deployed%20as%20Available%20and%20the%20users%20have%20selected%20install%20from%20the%20app%20in%20the%20Company%20Portal.%20For%20this%20scenario%2C%20all%20types%20of%20apps%20are%20impacted%2C%20not%20just%20MSI%20and%20Win32%20apps.%20Simply%20asking%20the%20user%20to%20logon%20to%20the%20device%20using%20the%20Azure%20AD%20account%20to%20which%20the%20apps%20have%20been%20targeted%20will%20resolve%20this%20issue.%20This%20scenario%20only%20affects%20Azure%20AD%20joined%20MDM-managed%20Windows%2010%20devices%20and%20does%20not%20affect%20bring%20your%20own%20devices%20(BYOD).%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EHope%20this%20helps%20you%20have%20successful%20Windows%2010%20device%20app%20deployments!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-1365322%22%20slang%3D%22en-US%22%3E%3CP%3EAre%20you%20using%20co-management%20-%20when%20a%20Windows%2010%20device%20has%20the%20Configuration%20Manager%20client%20and%20is%20enrolled%20to%20Intune%20-%20and%20noticed%20apps%20unexpectedly%20shown%20as%20pending%3F%20Read%20this%20post%20for%20two%20frequent%20configurations%20and%20how%20to%20solve%20them.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1365322%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EConfiguration%20Manager%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EIntune%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESupport%20Tip%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Ewindows%2010%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1369024%22%20slang%3D%22en-US%22%3ERe%3A%20Support%20Tip%3A%20Intune%20Co-Managed%20Windows%2010%20Device%20Apps%20in%20Pending%20State%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1369024%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20for%20the%20post.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20also%20saw%20some%20issues%20with%20%22Pending%22%20download%20on%20Co-Managed%20devices%20-%20the%20cause%20was%20slightly%20different%20to%20the%20information%20posted%20here%20and%20I%20wrote%20a%20brief%20blog%20that%20may%20help%20others%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20title%3D%22Co-Management%20Client%20Apps%20Proxy%20Issue%22%20href%3D%22https%3A%2F%2Fcarlbarrett.uk%2Fco-management-client-apps-workload-and-system-account-proxy-configuration%22%20target%3D%22_blank%22%20rel%3D%22noopener%20nofollow%20noopener%20noreferrer%20noopener%20noreferrer%22%3ELink%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CFONT%3EThanks%2C%3C%2FFONT%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CFONT%3ECarl%3C%2FFONT%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E

By Lee Yan | Sr. Service Engineer | Intune Support as a Feature

 

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. Below we share two of the most frequent reasons apps are in the “Pending” state.

 

The first scenario involves Configuration Manager and Intune co-managed Windows 10 devices and MSI and Win32 apps. 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. 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. Otherwise, if the MSI or Win32 apps are deployed as required you may see status of Pending or no status. 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.

 

The second scenario is when your Windows 10 device is enrolled through Azure AD join with auto-enrollment. When the user logs onto the device using a local account, the apps targeted to the user as required will also be shown as Pending or if the apps are deployed as Available and the users have selected install from the app in the Company Portal. For this scenario, all types of apps are impacted, not just MSI and Win32 apps. Simply asking the user to logon to the device using the Azure AD account to which the apps have been targeted will resolve this issue. This scenario only affects Azure AD joined MDM-managed Windows 10 devices and does not affect bring your own devices (BYOD).

 

 

Hope this helps you have successful Windows 10 device app deployments!

1 Comment
Regular Visitor

Thanks for the post.

 

We also saw some issues with "Pending" download on Co-Managed devices - the cause was slightly different to the information posted here and I wrote a brief blog that may help others:

 

Link 

 

Thanks,

 

Carl