Migrate Script-based Apps

Applies to: Patch My PC Cloud

Important This documentation is for a pre-release feature still under development and, therefore, incomplete. As a result, both functionality and documentation are subject to change. Once this feature is released, it will be announced and this banner removed. Patch My PC (PMPC) Cloud evaluates ConfigMgr applications using an initial full scan when the environment.

When applications are inventoried from ConfigMgr, PMPC Cloud analyses the application metadata to understand how the application is installed and how it should be migrated. As part of this process, the installation command line is evaluated and the primary installer file is identified from the application’s content source folder.

Identifying a Script-based App

ConfigMgr does not explicitly label an application as Script-based. In most cases, the easiest way to confirm that an application is Script-based is to select the application from the Migration dashboard and review the Installation Program field.

If the Installation Program contains a .ps1, .cmd, .bat or .vbs file reference, the application can be considered Script-based.

During the migration deployment flow, the File tab also indicates when an application is being treated as Script-based and the script content is displayed.

If the application is identified as Script-based, as much of the existing metadata as possible is captured to support migration. This includes any supporting content to ensure the application behaves the same way after it is migrated to Intune.

Migration Behavior of Script-based Apps

Script-based apps can only be migrated as PMPC Custom Apps.

When the application is migrated, PatchMyPC-ScriptRunner.exe becomes the new primary installer and invokes the original script defined in the installation command line. This approach preserves the original installation behaviour while allowing the deployment to take advantage of additional Patch My PC customisations that would not be available with a "lift and shift" migration.

In the example shown, a PowerShell-based Windows Update script is being migrated. The installation script content is displayed inline within the migration flow, allowing it to be reviewed or edited before proceeding. The script is currently not code-signed, which is indicated by the warning shown below the editor. The script can be exported for signing and then re-imported, or migrated as-is depending on your organisation’s script-signing requirements.

Note

If the script is code-signed, any modification on the File tab will invalidate the existing signature. For this reason, editing should only be performed on unsigned scripts. Signed scripts should be exported, re-signed after any changes, and then re-imported before completing the migration.

Preserved Properties of Script-based Apps

The following information indicates the properties that are carried forward from the ConfigMgr application to the migration deployment flow when the application is migrated as a PMPC Custom App.

• Source Files

• DisplayName

• Vendor

• Description

• Version

• Return Codes

• Information URL

• Privacy URL

• Detection Rules