Resources to help you solve app deployment problems in Microsoft Intune
Updated: April 24, 2015
Applies To: Microsoft Intune
This topic provides resources to help you solve app deployment problems with Microsoft Intune.
If you can’t log in to the Microsoft Intune company portal
Check to see if your account exists in the Microsoft Intune account portal or if it is disabled.
Make sure that you are provisioned on this account in the Microsoft Intune account portal.
In the Microsoft Intune account portal, make sure that you are using the right user name and password to log in to Intune and that it is in the format: firstname.lastname@example.org.
If the Contact IT information is missing in the company portal
In the Microsoft Intune administrator console, click Admin > Company Portal.
Set the Contact IT details.
If you can’t see specific apps in the list
Make sure you are checking the list of apps for a user or device to which the app was deployed.
Make sure that the device meets the necessary device requirements.
If you receive an error while downloading an app
Make sure there are not too many concurrent downloads per user. Each user can download one app at a time.
Make sure there are not too many concurrent downloads per account. Wait a few minutes and then try again.
If you receive an iOS native message that you can't install, that the installation is canceled or that you need to retry, it might be due to momentary high traffic. Wait a few minutes and then try again.
If the iOS app download progress bar is complete but the app installation fails, something might be wrong with the app files that you provided.
If clicking a link to an iOS app takes you to a previous location in the iTunes App Store
The current iTunes App Store session is opening to the previous app page.
Close the iTunes App Store on the device and retry the link.
If you receive an error while launching an iOS app
The expiration date of the app might not be valid.
If your app is stuck “in progress” while uploading
When uploading an app, first the metadata is added, followed by the app package. After the metadata has been uploaded, the app will appear in progress. If you see that your app is in the in progress state for an unusually long time, delete the app and then upload it again.
Make sure not to manage the deployment of the app while it is in the “in progress” state.
If you encounter a failure when installing an iOS app
Make sure that your organization’s firewall allows access to the Apple provisioning and certification web sites.
For more information, view the Apple developer documentation.
If managed apps are not reporting installation status
Installation status was not collected for managed app installations prior to the Microsoft Intune service update in November 2014. For devices that installed managed apps prior to this service update, update each associated app deployment with the appropriate deployment action (for example, Available install). Each device will update the app during the automatic check for available apps. For more information, see Update apps.
The following table lists common errors that may occur during Intune app deployment, the likely causes, and possible solutions to help you troubleshoot them.
0x80CF201C (client error)
To install this app, you must have a sideloading-enabled system.
Make sure that the app package is signed with a trusted signature and installed on a domain-joined device that has the AllowAllTrustedApps policy enabled, or a device that has a Windows Sideloading license with the AllowAllTrustedApps policy enabled (applied when a Windows RT device is enrolled).
The package could not be opened.
Check the AppxPackagingOM event log for more information.
The package failed update, dependency, or conflict validation
Check the AppXDeployment-Server event log for more information.
The provided package is already installed, and reinstallation of the package is blocked
You might receive this error if you are installing a package that is not identical to the package that is already installed. Confirm the digital signature is also part of the package. When a package is rebuilt or re-signed, that package is no longer bitwise identical to the previously installed package. Two possible options to fix this error are as follows: