Migration Not Supported Reasons

Applies to: Patch My PC Cloud

triangle-exclamation

This reference lists the reasons a ConfigMgr application may be marked as Not Supported in the MIgration Dashboard. These typically relate to unsupported application types, missing or inaccessible installer content, permission issues, or errors encountered while parsing installer metadata such as command lines or PSADT scripts.

Code
Reason

AmbiguousInstallers

Several possible installer files were found

ApplicationMarkedAsNotMigratable

The application is marked as not migratable

CmdScriptedApp

Command Line scripted application

DeploymentTypeInstallerCommandLineIsNull

The installation command line is not configured

DeploymentTypeInstallerIsNull

The deployment type exists but has no installer defined

ErrorProcessingPsadtScript

Unable to process PSADT script for deployment type

FailedToGetFeatureEnabledForCustomer

Failed to get feature enablement for customer

FailedToUploadAdditionalFileFromPublisherDueConnection

Failed to upload additional file from Publisher due to connection issue

FileAccessDenied

Access to file denied

FileMissing

Required file is missing

FileTypeNotDetectedForInstallCommand

Unable to detect the file type from the installation command provided

FileTypeNotSupported

The file type is not supported in the installation command line

FileTypeScriptRunnerNotSupported

The file type ScriptRunner is not supported in the installation command line

HashMismatch

File hash mismatch

InstallationContextNotDetected

Installation context not detected

InstallerContainsProhibitedFiles

Patch My PC helper files were found in the source directory

InstallerContentEmptyFileArray

Files are missing from the content folder

InstallerContentNotFound

No installation files were found

InvalidInstallerContentFilesSize

The total size of the installer files exceeds the Intune allowed limit

InvalidProductCode

Invalid product code

MissingContent

No content was found for the deployment type

MissingInstaller

The installer file is missing from the content folder

MultipleProductsMatched

Multiple products matched with the same file hash

NoFileAccessAccessGranted

The system cannot access the required files in the content source folder

NoMatchingInstallerFiles

Files referenced in the command line were not found in the content folder

NoReferencedFiles

No exe or msi files specified in the installer command line were found

OtherAppBucketType

Scripted application with not defined extension

PowershellScriptedApp

Powershell scripted application

PrimaryFileNotDetectedForMultiFiles

Unable to determine the primary installer

ProductIdRequired

The deployment type ID is missing

ProductIdRetrievalFailed

The deployment type ID is invalid or does not map to a known product

ProductMatchByHashFailed

API Error - Unable to evaluate the product hash

PSADTNoReferencedFiles

No files are referenced in the PSADT script

PsadtFeatureIsDisabled

PSADT App Migration feature is disabled for the current customer

PsadtFilesFoundInCommandLineOnly

Installer referenced in the PSADT script was not found in the content folder

Last updated

Was this helpful?