XOAP PSADT Package Wizard is a Windows desktop application that guides you through creating PSAppDeployToolkit (PSADT) v4 deployment packages. Instead of manually editing PowerShell scripts, you use a step-by-step wizard to configure application metadata, write deployment logic, upload installer files, and export a ready-to-deploy .zip package.

What you get

Each exported package is a standard PSADT v4 folder containing:

• Invoke-AppDeployToolkit.ps1 — The main deployment script (generated by the wizard)
• Invoke-AppDeployToolkit.exe — PSADT executable stub
• PSAppDeployToolkit/ — The PSADT module
• Files/ — Your installer files (MSI, EXE, configuration files, etc.)
• Supporting folders (Config/, Strings/, SupportFiles/, Assets/)

These packages can be deployed with SCCM/MECM, Intune, or any deployment tool that runs PowerShell scripts.

The post Introduction appeared first on XOAP.

Installation

System requirements

• Windows 10 (version 1809+) or Windows 11
• x64 processor
• Internet connection (only for first-time .NET runtime download and optional PSADT download)

Install steps

1. Run PackageWizard-Setup-{version}.exe
2. If .NET 9 is not installed, the installer will automatically download and install the required runtimes from Microsoft (Microsoft.WindowsDesktop.App and Microsoft.AspNetCore.App). This may take a few minutes on first install.
3. Choose the installation folder (default: C:\Program Files\XOAP PSADT Package Wizard)
4. Optionally create a desktop shortcut
5. Click Install

Uninstall

Use Windows Settings → Apps → XOAP PSADT Package Wizard → Uninstall, or run the uninstaller from the Start Menu.

Your packages and settings in %AppData%\XOAP\PackageWizard\ are preserved after uninstall. Delete that folder manually if you want a completely clean removal.

First launch

Launch XOAP PSADT Package Wizard from the Start Menu or desktop shortcut.

On first launch, the application:

1. Starts a local backend server on a random free port (runs entirely on your machine)
2. Opens the wizard interface in an embedded browser window (WebView2)
3. If older data exists in %AppData%\PackageWizard\, it is migrated to %AppData%\XOAP\PackageWizard\ automatically

You will land on the Packages Workspace — your dashboard for all saved packages.

Recommended first-time setup

1. Open Settings (gear icon, bottom-left)
2. On the PSADT Toolkit tab, verify that an active toolkit is detected. Click Download Latest PSADT to fetch the newest release from GitHub if you want the latest version (this persists to %AppData%\XOAP\PackageWizard\Toolkit\{tag}\)
3. On the General tab, set your Default App Script Author (pre-fills new packages) and Default Output Folder (where exports are saved)
4. Use the Dark/Light theme toggle in the sidebar footer to pick your preferred theme

The post Installation & first launch appeared first on XOAP.

The main window

The main window has a left sidebar (navigation), a top header (breadcrumbs and the active wizard step bar when a package is open), and a main panel (the current view).

Sidebar: Top section

Sidebar: Wizard steps

Once a package is active, the sidebar shows the seven wizard steps. Steps you haven’t reached yet are enabled only if prerequisites are met; completed steps show a check mark.

1. Files
2. Session Config
3. Parameters
4. Install Phase
5. Uninstall Phase
6. Repair Phase
7. Preview

Sidebar: Bottom section

• Settings — application preferences, toolkit management, package configuration
• Tags — manage the color-coded tag library
• Dark/Light Mode toggle — persists across restarts
• About — version, platform info, license, xoap.io link

Wizard header strip

When a package is active, a strip below the breadcrumb shows:

• An “Active” badge with the package name
• Exit — returns to the dashboard
• Save — persists any unsaved in-memory changes (also auto-saves every 2 seconds)

Wizard footer

At the bottom of every wizard step: Back, Step N of 7, and Next / Finish. The Next button is disabled when the current step has validation errors; hover it to see the reason as a tooltip.

Packages workspace (dashboard)

The dashboard is your central workspace for managing packages.

Header

• Package Usage Widget — Shows {used} | {max} Packages used with a progress bar and percentage. The free edition is limited to 10 packages; the widget turns red and the Start New Package button becomes disabled at the cap.
• Start New Package — Creates a blank package and opens the first wizard step
• Import Local — Opens a drawer to drop/select one or more existing PSADT .zip packages to import into the workspace

Toolbar

• Tag filter (left) — Filter packages by assigned tag (or “All tags”)
• Search — Filter by package name
• Select All Packages — Batch checkbox
• Assign Tags — Opens a drawer to assign/remove tags on the selected packages
• Export (download icon) — Exports every selected package; in the desktop app each zip is written to the Default Output Folder (or Downloads fallback). In a browser the zips download one-by-one
• Delete (trash icon) — Deletes selected packages (with a confirmation prompt)

Package card

Each package card shows:

• Package name (auto-set from AppName once filled in)
• Application metadata (vendor, name, version, architecture)
• Assigned tags (color-coded badges; limit 5 tags per package)
• Creation date
• Per-card actions: Open (enter wizard), Export, Edit Tags, Delete

Multi-select

Click the card checkbox (or Select All) to queue packages for batch export / delete / tag assignment.

The post UI overview appeared first on XOAP.

Click Start New Package on the dashboard. The wizard guides you through seven steps. You can navigate freely between steps using the sidebar or the Previous/Next footer buttons. Every change is auto-saved to the active package roughly every 2 seconds, or immediately when you click Save in the header strip.

Step 1: Files manager

Upload the installer files that your deployment script will reference.

How to upload:

• Drag and drop files or folders onto the upload area, or
• Click the upload area to open the file browser

Features:

• Folder structure is preserved (useful for complex installers)
• Maximum upload size: 5 GB per request
• Automatic metadata detection: When you upload an MSI or EXE, the wizard reads its embedded ProductName, ProductVersion, and architecture and offers to pre-fill Session Configuration

File Tree:

• View all uploaded files in a tree structure
• Delete individual files or folders
• Clear all files for the active package

Uploaded files are stored per-package in %AppData%\XOAP\PackageWizard\workspace\Files\{packageId}\ and are bundled into Files/ inside the exported zip.

Step 2: Session configuration

Configure the application metadata that PSADT uses for logging, UI display, and detection. Every field here is written into the $adtSession = @{ ... } block of the generated script.

Application information

Script metadata

Deployment settings

Display settings

Step 3: Parameters

Add custom PowerShell parameters to your deployment script. These are appended to the param() block alongside the default PSADT parameters.

Default parameters (always present, read-only):

• DeploymentType — Install / Uninstall / Repair
• DeployMode — Auto / Interactive / NonInteractive / Silent
• SuppressRebootPassThru (switch)
• TerminalServerMode (switch)
• DisableLogging (switch)

For each custom parameter you can set:

Example use case: Add -Environment with ValidateSet = Dev,Staging,Production to control which configuration file a caller deploys.

Step 4: Install phase

Write the PowerShell code that runs when DeploymentType = Install. The phase is split into three Monaco code editors:

Editor features:

• Full PowerShell syntax highlighting (Monaco Editor)
• Cmdlet autocomplete — start typing any PSADT v4 cmdlet name and the editor suggests it, including a snippet with required parameters. Type - after a known cmdlet to get parameter suggestions with their types, required flag, description, and valid values.
• Function Builder button — opens a modal to pick a cmdlet, fill in its parameters via form fields (with a file picker populated from your uploaded files), and insert the generated code at the cursor. See Function Builder & Cmdlet Autocomplete.
• Maximize — each editor has a full-screen toggle
• Clear — wipe the section’s content

Example installation code:

## Install the MSI
Start-ADTMsiProcess -FilePath 'MyApp.msi' -Action Install

## Copy configuration file
Copy-ADTFile -Path "$($adtSession.DirFiles)\config.xml" -Destination "$envProgramFiles\MyApp\"

Step 5: Uninstall phase

Same three-section structure (Pre, Main, Post) as the Install Phase. Runs when DeploymentType = Uninstall.

Example:

## Remove the MSI
Uninstall-ADTApplication -Name 'MyApp' -FilterScript { $_.Publisher -eq 'Contoso' }

## Clean up leftover files
Remove-Item -Path "$envProgramFiles\MyApp\config.xml" -Force -ErrorAction SilentlyContinue

Step 6: Repair phase

Same three-section structure. Runs when DeploymentType = Repair. Many packages leave the repair phase empty — that’s fine; PSADT simply runs an empty function.

Step 7: Script preview & test run

Displays the complete generated script in a read-only Monaco editor with PowerShell highlighting. This is exactly what Invoke-AppDeployToolkit.ps1 will contain in your exported package.

Actions on this page:

Test Run uses the same PSADT module and Files/ directory that would ship in the exported zip. It has a 120-second timeout.

Export is available from the Packages Workspace toolbar (not from this page) — see below.

The post Creating a package appeared first on XOAP.

There are three ways to export:

1. Per-package export — from the dashboard, click Export on a package card
2. Batch export — select multiple packages and click the Export toolbar icon
3. HTTP download — when running in a browser (not the desktop app), exports download as {AppVendor}_{AppName}_{Version}_{Arch}.zip through the browser

In the desktop app, exports are written directly to the Default Output Folder set in Settings. If that path is empty or invalid, the app falls back to your Downloads folder.

The exported .zip contains everything needed to deploy:

Contoso_MyApp_1.0.0_x64.zip
  Invoke-AppDeployToolkit.ps1     <- Your generated script
  Invoke-AppDeployToolkit.exe     <- PSADT executable stub
  PSAppDeployToolkit/             <- PSADT module
  PSAppDeployToolkit.Extensions/  <- Extensions (if present in toolkit)
  Config/                         <- Configuration
  Strings/                        <- Localization
  SupportFiles/                   <- Support files
  Assets/                         <- Icons
  Files/                          <- Your uploaded files
    MyApp.msi
    config.xml

Free vs Paid: In the paid edition, enabling Include README.md on the Settings → General tab causes a README.md with package metadata, parameters, and phase documentation to be generated and added to the exported zip. The toggle is visible but locked in the free edition.

The post Exporting packages appeared first on XOAP.

You can import existing PSADT packages (v3 or v4) from .zip files.

1. From the dashboard, click Import Local
2. A drawer opens; drop one or more .zip files (or click to browse)
3. The wizard processes each zip and reports status

For each zip, the wizard will:

• Detect whether it’s a v3 (Deploy-Application.ps1) or v4 (Invoke-AppDeployToolkit.ps1) package
• Parse the script to extract session configuration values
• Extract phase content (pre/main/post for each deployment type)
• Extract any custom parameters
• Copy Files/* into the package’s workspace directory
• Add a new package to your workspace (respecting the 10-package cap)

For v3 packages, command names and variables are automatically translated to v4 syntax using the same translation service used by the /api/translate endpoint.

After import, you can review and edit each package through the normal wizard steps.

The post Importing existing packages appeared first on XOAP.

Installed apps

The Installed Apps page (/installed-apps) lets you browse applications installed on your Windows machine.

Controls

The registry is queried from:

• HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall\ (64-bit)
• HKLM\Software\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\ (32-bit)
• HKCU\Software\Microsoft\Windows\CurrentVersion\Uninstall\ (per-user)

Snapshot workflow

1. Click Take Snapshot before running your deployment
2. Run your PSADT package (via Test Run or a real deploy)
3. Click Compare to see which applications were installed, removed, or modified
4. Results show status for each app and can help you verify that your uninstall phase cleans up everything your install phase added

The post Installed apps appeared first on XOAP.

The Logs page (/logs) shows the API server’s log files.

• Session selector — each time the API starts it opens a new log file named api-{yyyy-MM-dd-HHmmss}.log. The dropdown lists all sessions still on disk (14-day retention).
• Monaco viewer — the selected log is rendered read-only in a code editor
• Search — filter lines in the current log
• Auto-refresh — the current session log refreshes every 5 seconds so you can watch requests stream in live

Files are stored in %AppData%\XOAP\PackageWizard\logs\. Each session’s log has a 10 MB size cap; files older than 14 days are cleaned up on startup. A parallel log for the desktop shell (desktop-{yyyy-MM-dd}.log) exists in the same folder but is not shown in this viewer.

The post Logs appeared first on XOAP.

Tags help you organize packages in the dashboard. Open Tags from the sidebar footer.

Managing Tags

• Create a tag with a name (max 40 characters), description (max 160), and color
• Available colors: cyan, pink, orange, green, purple, indigo
• Edit or Delete tags at any time. Deleting a tag removes it from all packages automatically.

Assigning Tags

• From the dashboard, click the tag icon on a package card, or
• Select multiple packages and click Assign Tags on the toolbar

Each package can have up to 5 tags in the free edition. Tags appear as colored badges on package cards and in the tag filter dropdown.

The post Tags appeared first on XOAP.

Open Settings from the sidebar footer. It is organized into three side-tabs.

General tab

Default package values

Documentation options — locked in free edition

Package storage — locked in free edition

The Save Settings button at the top of the page saves General tab values and any pending Package Configuration edits in one action.

PSADT toolkit tab

Active toolkit for export

Shows which toolkit will be used for script generation and export:

• Source label — Custom, Bundled, or No Toolkit Available
• Module Version — detected from PSAppDeployToolkit/PSAppDeployToolkit.psd1
• Custom Extensions included — badge shown if PSAppDeployToolkit.Extensions is present
• Refresh — re-queries the server

Below the status card:

• Auto-check for toolkit updates on startup — toggles GitHub version check at startup

Resolution order (top wins):

1. Custom toolkit path (if set and valid) — paid feature (see below)
2. Downloaded toolkit in %AppData%\XOAP\PackageWizard\Toolkit\{tag}\
3. Bundled template shipped with the installer

Download latest from GitHub

• Large Download Latest PSADT button — fetches the latest release from github.com/PSAppDeployToolkit/PSAppDeployToolkit, extracts it (zip-slip protected), and sets it as the active toolkit
• Displays the latest release tag and an “Update available” badge when applicable

Use custom toolkit — locked in free edition

Locked in free edition. Both the text input and the button are displayed but disabled.

Package configuration tab

Reads Config/config.psd1 from the active toolkit and renders each section as a card.

For each field the UI shows:

• The field key (e.g. MSI_LogPath)
• Any comment/description parsed out of the .psd1
• A form control appropriate for the type (text input, number input, or True/False toggle)

Editing a field and clicking Save Settings (top of page) writes the changes back to config.psd1 (with zipslip / path-traversal protection). The signature block, if present, is stripped on save.

The post Settings appeared first on XOAP.