Export (0) Print
Expand All

Resources to help you solve software deployment problems in Microsoft Intune

Updated: February 18, 2015

Applies To: Microsoft Intune

This topic provides resources to help you solve software deployment problems with Microsoft Intune.

  1. Check to see if your account exists in the Microsoft Intune account portal or if it is disabled.

  2. Make sure that you are provisioned on this account in the Microsoft Intune account portal.

  3. 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: joe@domain.com.

  1. In the Microsoft Intune administrator console, click Admin > Company Portal.

  2. Set the Contact IT details.

  1. Make sure you are checking the list of software for a user or device to which the software was deployed.

  2. Make sure that the device meets the necessary device requirements.

  1. Make sure there are not too many concurrent downloads per user. Each user can download one application at a time.

  2. Make sure there are not too many concurrent downloads per account. Wait a few minutes and then try again.

  3. 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.

  4. If the iOS application download progress bar is complete but the application installation fails, something might be wrong with the application files that you provided.

  5. If you successfully download an Android application and the Android user is not able to install it, go to Application Settings and make sure that the Unknown Sources checkbox is selected.

  1. The current iTunes App Store session is opening to the previous application page.

  2. Close the iTunes App Store on the device and retry the link.

  1. The expiration date of the application might not be valid.

  2. Make sure that the .ipa package and .plist file match and have the same bundler ID.

  1. A manifest file is required to enable wireless distribution of iOS application. For more information and to see a sample manifest file, view Apple developer documentation and follow iOS developer guidelines to create a valid manifest file.

  2. Make sure that the .ipa package and .plist file match and have the same bundler ID.

    The .plist manifest file is a separate file, and not one of the files included in the .ipa package.

  1. When uploading an application, first the metadata is added, followed by the application package. After the metadata has been uploaded, the application will appear in progress. If you see that your application is in the in progress state for an unusually long time, delete the application and then upload it again.

  2. Make sure not to manage the deployment of the application while it is in the “in progress” state.

  1. Make sure that your organization’s firewall allows access to the Apple provisioning and certification web sites.

  2. For more information, view the Apple developer documentation.

  • 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 software. For more information, see Update software.

The following table lists common errors that may occur during Intune software deployment, the likely causes, and possible solutions to help you troubleshoot them.


Error code Possible problem Suggested resolution


0x80CF201C (client error)

To install this app, you must have a sideloading-enabled system.

Make sure that the software package is signed with a trusted signature and installed on a domain-joined computer that has the AllowAllTrustedApps policy enabled, or a computer 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.

Possible causes:

  • The package is unsigned.

  • The publisher name does not match the signing certificate subject.

Check the AppxPackagingOM event log for more information.


The package failed update, dependency, or conflict validation

Possible causes:

  • The incoming package conflicts with an installed package.

  • A specified package dependency is not found.

  • The package does not support the correct processor architecture.

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:

  • Increment the version number of the app, then rebuild and re-sign the package.

  • Remove the old package for every user on the system before you install the new package.

See Also

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
© 2015 Microsoft