XOAP Package Wizard is a Windows desktop application for creating software deployment packages without hand-writing scripts. A step-by-step wizard guides you through the application details, the deployment logic and the installer files. You then build a ready-to-deploy package or send it straight to your deployment platform.

Package types

The wizard supports four package types:

PSADT packages are available in both editions. MSIX, App Attach and IntuneWin packages need the Pro edition.

What a PSADT package contains

Each exported PSADT package is a standard PSADT v4 folder:

• Invoke-AppDeployToolkit.ps1: the deployment script, generated by the wizard
• Invoke-AppDeployToolkit.exe: the PSADT launcher
• PSAppDeployToolkit/: the PSADT module (and PSAppDeployToolkit.Extensions/ when present)
• Fichiers/: your installer files (MSI, EXE, configuration files, and so on)
• Supporting folders: Config/, Des cordes/, SupportFiles/, Actifs/
• README.md (optional, Pro): package documentation

Beyond building packages

Besides the four package wizards, the application includes:

• App Catalog. Browse about 14,600 applications from Evergreen and the winget community repository, and create a pre-filled PSADT package with one click. The app tells you when a newer version is available.
• Conversion Assistant. Converts a package from one type to another, and can repackage installers into MSIX.
• Testing. Run a package on your own machine, or on a clean, disposable Windows Sandbox.
• Connections. Upload or deploy directly to Microsoft Intune, Azure Storage and Microsoft Configuration Manager (MECM).
• FSLogix App Masking rules. Build rule sets for Azure Virtual Desktop.
• PSADT Templates. Keep your company’s own PSADT customizations, and keep them across toolkit updates.
• Shared Package Storage. Lets a team of packagers work in the same package workspace.

The post Introduction appeared first on XOAP.

Règles de fonctionnement

• Windows 10 version 1809 or later, or Windows 11
• x64 processor. Windows on ARM is supported through x64 emulation.
• .NET 9 Desktop Runtime and ASP.NET Core Runtime. The installer downloads them if they are missing.
• Microsoft Edge WebView2 Runtime (included in current Windows versions)
• An internet connection for:
  • the first-time .NET download (only if the runtimes are missing)
  • the App Catalog
  • downloading PSADT updates
  • uploads to Intune or Azure Storage

Some features have extra requirements:

Editions and installers

There are two installers. Both editions can be installed side by side.

Both installers are digitally signed by the publisher.

Étape à suivre pour installer

1. Run the installer.
2. If .NET 9 is not installed, the installer downloads and installs the required runtimes from Microsoft. This can take a few minutes.
3. Choose the installation folder. Keep the default unless you have a reason to change it.
4. Optionally create a desktop shortcut.
5. Cliquez sur Installer.

Updating

Run the installer of the newer version. It upgrades the existing installation in place. Your packages and settings are kept, because they are stored in your user profile and not in the program folder.

Désinstaller

Utilisation Windows Settings → Apps → XOAP Package Wizard → Uninstall, or the uninstall shortcut in the Start menu.

Vos paquets et vos paramètres dans %AppData%\XOAP\PackageWizard\ are kept after you uninstall. Delete that folder yourself if you want to remove everything.

Premier lancement

Démarrage Assistant de package XOAP from the Start menu or the desktop shortcut. On first launch the application does the following:

1. It starts its own local service. This service runs only on your machine and is not reachable from the network.
2. It opens the user interface in the application window.
3. If it finds data from an older version in %AppData% PackageWizard\, it moves that data to %AppData%\XOAP\PackageWizard\ automatically.

The application opens on the Packs de travail.

Configuration recommandée pour une première utilisation

1. Ouvrir Paramètres (bottom of the sidebar).
2. Sur le site Toolkit PSADT tab, check that an active toolkit is shown. To get the newest PSADT release, click Téléchargez la dernière version de PSADT.
3. Sur le site Général tab, fill in the following and click Sauvegarder les réglages:
   • Auteur par défaut du script d'application: pre-filled in every new package
   • Folder de sortie par défaut: where built packages are saved
4. Pro only:
   • Set up a signing certificate (Settings → General → Signing Certificates). You can skip this; a test certificate is created automatically on the first MSIX build.
   • Create your connections (Connexions).
5. Choose light or dark mode with the theme switch in the sidebar.

The post Installation & first launch appeared first on XOAP.

The window has three parts:

• les sidebar on the left
• les header at the top, with the breadcrumb, the help menu and the package bar when a package is open
• les main area

Sidebar: top section

Sidebar: Wizard Steps

When a package is open, the sidebar shows Wizard Steps with the package type and its steps:

• Completed steps show a check mark.
• A step stays disabled until the steps before it are valid.
• Click any available step to jump to it.

The steps depend on the package type:

Sidebar: bottom section

• Paramètres: application settings, toolkit, PSADT templates and package configuration
• Tags: manage your tag library
• Connexions: Intune, Azure Storage and MECM connections (Pro; shows a lock in Free)
• Upgrade card (Free edition only): links to the full version and to the plans
• Dark Mode / Light Mode switch. Your choice is remembered.
• À propos: version, platform, license (EULA) and website

But de tête

• Le breadcrumb shows where you are. Long package names that are cut off are shown in full when you hover over them.
• Le help menu (question-mark icon) has two entries:
  • Documentation opens this documentation.
  • Report a Bug opens an e-mail to XOAP support.

Package bar

While a package is open, a bar under the header shows:

• Actif, followed by the package name
• Sortir: closes the package and returns to the Packages Workspace
• Économiser: saves your changes now. Changes are also saved automatically.

Fouetture de l'assistant magicien

At the bottom of each wizard step you find:

• Retour
• Step N of M
• Next Step: <name>. This button is disabled while the current step has errors.
• Finition, on the last step. For PSADT, MSIX and IntuneWin packages, Finish saves the package, builds it, stores the result in the workspace and returns to the Packages Workspace (see Exporting and building packages).

Packages Workspace (dashboard)

Package type tabs

At the top of the workspace are four tabs: PSADT Packages, MSIX Packages, App Attach Packages et IntuneWin Packages.

• Each tab shows how many packages of that type you have.
• In the Free edition, the MSIX, App Attach and IntuneWin tabs show a lock.

But de tête

• Start New <Type> Package creates a package of the type of the selected tab and opens its first wizard step.
• Importer Local imports existing PSADT .zip paquets.
• Package usage (Free edition) shows how many of your 10 packages you have used. A banner appears when you are close to the limit.

Barre d'outils

Cartes de paquets

Each card shows:

• the package name, with the full name on hover
• ACTIVE when the package is currently open
• an amber UPDATE badge when the App Catalog has a newer version
• vendor and version
• a status line, which depends on the type:
  • PSADT: number of parameters
  • App Attach: image format and size
  • IntuneWin: number of detection rules
• the assigned tags

The action buttons on the card are:

To select several packages, use the checkbox on each card. You can then export, upload, tag or delete them all at once.

The post UI overview appeared first on XOAP.

1. Sur le site Packs de travail, select the tab for the package type you want (PSADT, MSIX, App Attach or IntuneWin).
2. Cliquez sur Start New <Type> Package.
3. Work through the wizard steps. Use Next Step, Retour or the step list in the sidebar.
4. On the last step, click Finition to build the package (App Attach images are built with the Build App Attach Image button on the last step).

Things to know:

• Auto-save. Every change is saved automatically after about two seconds. Click Économiser in the package bar to save immediately.
• Free edition limit. You can keep up to 10 packages. At the limit, Démarrer Nouveau Paquet is disabled until you delete a package.
• Other ways to create a package:
  • from the App Catalog
  • by importing an existing PSADT zip
  • by duplicating or converting an existing package

Adding files (all package types)

The first step of every wizard uses the same file manager (Package Content ou Source Files):

• Drag and drop files or folders onto the Local Source card, or use Add Files / Add Folder.
• The folder structure is kept, which helps with complex installers. Uploads can be up to 5 GB per upload.
• Le Structure tree shows all uploaded files. Use the trash icon to delete a file or folder.

Files are stored per package and included in the package when it is built.

The post Creating a package appeared first on XOAP.

The PSADT wizard has seven steps.

Step 1: Files

Upload the installer files that your deployment script uses. They end up in the Fichiers/ folder of the exported package.

Step 2: Session Config

Here you enter the application details that PSADT uses for logging, for the dialogs shown to users, and for detection. All values are written into the $adtSession bloc du script généré.

PSADT Template

At the top of the step, choose a PSADT Template for this package, or choose None (stock toolkit). New packages automatically use your default template.

Auto-Detect from Installer

If the package contains an MSI or EXE installer, the wizard reads the product name, vendor, version and architecture from it:

• With exactly one installer, detection runs automatically.
• It only fills fields that are still empty.
• The values it found are shown under Detected Properties.

Informations concernant la demande

Script settings

All Application Information and Script Settings fields are required before you can continue.

Configurations de déploiement

Paramètres d’affichage

Étape 3 : Paramètres

Add your own script parameters. They are added to the script next to the standard PSADT parameters.

The standard parameters are always present and cannot be changed:

• TypeDeDéploiement: Install / Uninstall / Repair
• ModeDéploiement: Auto / Interactive / NonInteractive / Silent
• Supprimer le mode de démarrage « RebootPassThru », TerminalServerMode, Désactiver le log (switches)

Pour chaque paramètre personnalisé que vous pouvez définir :

Steps 4–6: Install, Uninstall and Repair phases

Each phase has three code editors:

The editors offer:

• PowerShell syntax highlighting and cmdlet autocomplete
• Detect Command (Main editor). Pick an installer file and click Detect Command. The wizard recognises the installer type and inserts the ready-made PSADT command:
  • MSI and MSP packages get Start-ADTMsiProcess with silent switches.
  • EXE installers get Start-ADTProcess with the right silent switches. The wizard recognises Inno Setup, InstallShield, WiX Burn, Squirrel and NSIS installers.
  • The uninstall phase gets a registry-based Désinstaller-ADTApplication.
  • If the silent switches cannot be determined, a message says so and nothing is inserted. Write the command yourself in that case.
• Insert Function: opens the Function Builder.
• Maximize Editor / Restore: full-screen editing.

Leaving the Repair phase empty is fine.

Example of an install phase:

Start-ADTMsiProcess -FilePath 'MyApp.msi' -Action Install
Copy-ADTFile -Path "$($adtSession.DirFiles)\config.xml" -Destination "$envProgramFiles\MyApp\"

Step 7: Preview

This step shows the complete generated Invoke-AppDeployToolkit.ps1 in a read-only editor. What you see here is exactly what goes into the package.

Cliquez sur Finition to build the package and store the ZIP in the workspace.

The post Creating PSADT package appeared first on XOAP.

Pro edition. An MSIX package contains the installé application files (not an installer), together with a manifest that describes the app to Windows.

If you only have an installer (setup.exe or .msi), create a PSADT package with it and convert it to MSIX. The Conversion Assistant can repackage the installer for you.

Step 1: Source Files

Upload the application files, for example the folder with the application’s EXE and DLL files.

Step 2: Package Identity

The step also shows the resulting Package Family Name.

Step 3: Dependencies (Dependencies & Capabilities)

• Capabilities. Pick from the standard values or type your own. runFullTrust is required for classic Win32 applications.
• Framework dependencies. For example the Visual C++ runtime (VCLibs), WinUI or the Windows App Runtime. Pick a preset or enter Nom ou Name|MinVersion.

Step 4: Applications

Choisissez l'option Primary executable from your uploaded .exe files. This is the program that the Start menu entry launches.

Step 5: Signing

Windows only installs signed MSIX packages.

If no certificate exists, a long-lived self-signed certificate is created automatically on the first build. Its public certificate (.cer) is saved next to the package so you can trust it on target machines.

Step 6: Preview & Build

• Shows the validation results and the generated AppxManifest.
• When the status reads All checks passed — ready to build, cliquer Finition to build, sign and save the .msix.

Result: {name}.msix et {name}.cer.

The post Creating an MSIX package appeared first on XOAP.

Pro edition. App Attach delivers an MSIX app to Azure Virtual Desktop or Windows 365 session hosts by mounting it from a disk image instead of installing it.

Step 1: MSIX Source

Upload one of the following:

• a ready-made .msix ou .msixbundle, ou
• the application files. The wizard then builds and signs the MSIX for you.

Step 2: Image Format

About CIM images:

• A CIM image consists of several files: {name}.cim plus objectid_* et region_* files. Always copy all of them together.
• The generated scripts need the CimDiskImage PowerShell module on the session host. AVD’s built-in App Attach mounts CIM images without this module.
• Use VHDX for Windows Server 2019 and 2022 hosts.

A ready-made .msix that you upload is checked before it is used:

• Unsigned packages are rejected.
• Packages whose publisher does not match their signature are rejected.
• If the signer is not trusted on this machine, you get a warning.

Step 3: Signing

This step offers the same certificate and timestamp settings as the MSIX wizard. It applies when the wizard builds the MSIX itself. The public certificate (.cer) is saved next to the image, and the Stage script trusts it automatically on the session host.

Step 4: Lifecycle Scripts

App Attach uses four scripts:

Working default scripts are generated for you. To change one, click Customize:

• You can use Insert snippet… for logging or error handling.
• Reset to generated default undoes your changes.

For AVD host pools, Microsoft recommends the built-in App Attach feature in the Azure portal. In that case you only need the image.

Step 5: Metadata

Tapez le code ci-dessous Display name (required) and the Version.

Step 6: Preview & Build

The step shows the validation results and the image plan, and checks this machine:

• If the msixmgr tool is missing, the build is blocked and the reason is explained.
• Creating a disk image needs administrator rights. If the app is not running as administrator, the Request admin rights (UAC) switch appears (on by default). Windows shows an administrator prompt when the build starts. Choose Oui in that prompt.

Cliquez sur Build App Attach Image.

Result:

• the image (.vhdx, .vhd, or the .cim file set)
• the four lifecycle scripts
• {name}.cer

App Attach images are built to disk and cannot be uploaded from the app. Copy them to your file share yourself.

The post Creating an App Attach package appeared first on XOAP.

Pro edition. Creates a Microsoft Intune Win32 app package.

Step 1: Source Files

Upload the setup files, for example the MSI, EXE, scripts and configuration files.

Step 2: App Information

Enter Nom (required), Publisher, Version et Description. These are shown in the Intune admin center.

Step 3: Program

For MSI installers, the product information and a product-code detection rule are filled in automatically.

Step 4: Detection Rules

Intune uses detection rules to find out whether the app is installed.

• Add as many rules as you need with + Add detection rule. All rules must match.
• Rule types:
  • msi: the MSI product code
  • fichier: the full path of a file
  • Registre: a registry key, for example HKLM\SOFTWARE\…
  • scénario: a detection PowerShell script
• At least one rule is required to publish the app in Intune.

Step 5: Requirements

Step 6: Preview & Build

Review the build plan and click Finition.

Result:

• {name}.intunewin: the encrypted package
• {name}.intune.json: all app details, commands and detection rules, ready for automated publishing

To deliver a PSADT package through Intune, you don’t need an IntuneWin package. Upload the PSADT package to Intune directly (see Connections & uploads). It is wrapped as .intunewin automatically.

The post Creating an IntuneWin package appeared first on XOAP.

Test Run (PSADT)

Sur le site Aperçu step of a PSADT package:

1. Choisissez Type de déploiement (Install / Uninstall / Repair) and Mode de déploiement.
2. Optionally turn on Exécuter en tant qu'administrateur. Most installations need it, and Windows shows a UAC prompt.
3. Cliquez sur Test Run.

The script runs on this computer with exactly the files, toolkit and template that the exported package would contain. Its output appears in the PowerShell Output panel. A test run stops after 120 seconds.

Test Run installs software on your own machine. To keep your machine clean, use Test in Sandbox.

Test in Sandbox (PSADT)

Test in Sandbox runs the package on a clean, disposable Windows machine (Windows Sandbox), without leaving the app. It shows you how the package behaves on a fresh client.

1. Enable Windows Sandbox once: Settings → General → Windows Sandbox → Enable Windows Sandbox. Windows shows an administrator prompt, and a restart is needed afterwards. Windows Sandbox is not available on Windows Home editions.
2. Sur le site Aperçu step, choose Deployment Type and Deploy Mode:
   • Silencieux ou Non interactif for a fully automatic test
   • Interactif if you want to click through the PSADT dialogs in the sandbox window yourself
3. Cliquez sur Test in Sandbox.

A progress panel follows the run. When it finishes, it shows:

• the result based on the exit code
• les PSADT deployment log

Further notes:

• Annuler stops the test and closes the sandbox.
• Close Sandbox closes the sandbox window after the test.
• Only one sandbox can run at a time.
• Everything inside the sandbox is discarded when it closes.

Verifying with Installed Apps snapshots

Use the snapshot feature on the Installed Apps page to check what a package really installed and whether the uninstall removed it again.

The post Testing packages appeared first on XOAP.

Paquets PSADT

There are three ways to export a PSADT package:

• Single package: click Download ZIP on the package card.
• Several packages: select them and click Download ZIP in the toolbar.
• Finish: clicking Finition in the wizard builds the ZIP and stores it in the workspace. The card then offers the stored build for download.

The file is named {Vendor}_{AppName}_{Version}_{Arch}.zip. It is saved to the Folder de sortie par défaut (Settings → General), or to your Downloads folder if no output folder is set.

Contents of the ZIP:

Contoso_MyApp_1.0.0_x64.zip
  Invoke-AppDeployToolkit.ps1     generated deployment script
  Invoke-AppDeployToolkit.exe     PSADT launcher
  PSAppDeployToolkit/             PSADT module
  PSAppDeployToolkit.Extensions/  extensions (incl. your template code)
  Config/  Strings/  SupportFiles/  Assets/
  Files/                          your installer files
  README.md                       optional (Pro)

README.md (Pro): turn on Settings → General → Include README.md in exported packages to add documentation (package details, parameters and phases) to every ZIP.

MSIX, App Attach and IntuneWin packages

Every package is checked before it is built:

• Errors stop the build and are listed so you can fix them.
• Warnings are informational.

Built packages are stored in the workspace. The card then shows Download <type> instead of Construire.

The post Exporting packages appeared first on XOAP.