Converting packages

Use the Conversion Assistant to turn a package into another type, for example PSADT → MSIX, MSIX → App Attach, or PSADT → IntuneWin.

1. On the Packages Workspace, click Convert… on a package card.
2. The assistant analyses the package and shows a card for each target type.

Each target card shows:

• Readiness: Ready to build, N details needed, or Not possible from this payload
• Carries over automatically: values taken from the source, such as name, version, publisher, install and uninstall commands, and silent switches
• Needs your input: only the fields the assistant cannot derive, with pickers for your uploaded files
• Checks: a preview of the build validation
• This machine: notes about your computer, for example that App Attach needs administrator rights

Conversion always creates a new package. The original is not changed. Name, version, publisher, architecture, uploaded files and tags are carried over. The analysis is available in both editions; creating MSIX, App Attach or IntuneWin packages needs Pro.

When the package contains an installer #

MSIX and App Attach need the installed application, not its setup program. If the source package contains an installer, the assistant offers three options:

• Repackage the installer (recommended). The wizard unpacks the installer without running it on your machine:
  • MSI: an administrative extraction rebuilds files, registry and shortcuts.
  • Inno Setup, NSIS and self-extracting archives: unpacked with an extraction tool when one is available.
  • Other installers (WiX Burn, InstallShield, unknown): are passed to Install & capture, with the reason shown.
  Repackaging runs in the background with progress and Cancel. Afterwards a pre-filled package opens in the wizard, and a report shows what was rebuilt and what was skipped.
• Install & capture. The installer runs silently and the wizard records what changed in the file system and registry. Things to know:
  • The app must run as administrator.
  • Use a disposable virtual machine for this.
  • Your own user profile data is never captured.
• Keep as-is. Builds a package that contains the raw installer. You get a warning that the result will probably not work as expected.

Viability check #

Before any work is done, the assistant checks whether the app can work as MSIX or App Attach at all:

• Blockers (not possible): kernel drivers, credential providers, in-process shell extensions (for example Explorer context menus), and hardware license dongles. The evidence is named.
• Conditional: Windows services work with MSIX but not with App Attach.
• Warnings: writes to the install folder, scheduled tasks, machine environment variables.

Other conversions #

• PSADT → IntuneWin offers two options:
  • Deploy this PSADT package via Intune: the whole PSADT package is wrapped.
  • Repackage the raw installer: install and uninstall commands are derived from the installer.
• Conversions to PSADT create real install and uninstall code from the source:
  • An .msi becomes Start-ADTMsiProcess.
  • An MSIX is built, signed and provisioned machine-wide, and its certificate is trusted.