How Advanced Installer Architect Complements PSADT in Application Packaging

PSADT Versions and Structure

Currently, there are two versions of PSADT:

• PSADT V3: It has been used for a long time, being robust and reliable. It lacks the visual elements and modern features. However, v3 has been deprecated, and it’s no longer developed or maintained.
• PSADT v4: The current stable PSADT version. A v4.1 is already in development, promising extra improvements.

PSADT v4 allows you to use it as a template, modifying the needed parts for each application individually. This structure offers a cleaner and more scalable structure, better suited for modern packaging workflows.

Let's get the most important files and folders that matter the most to a packager:

• Invoke-AppDeployToolkit.ps1: This is your main entry point. It's the script you call to run the deployment. Internally, it loads the configuration and handles lifecycle events such as Install or Uninstall.
• Invoke-AppDeployToolkit.ex: The wrapper executable that launches the script in a PowerShell host. This is what it’s being called alongside the install, uninstall, or repair parameter in configuration tools like Intune or SCCM. The exe interprets the PS1 script, which will eventually execute the setup files' configuration instructions.
• ServiceUI.exe: Useful when running installations in the SYSTEM context and you want to show UI to the logged-in user.
• Files: This is where you place your original setup installer file(s).
• SupportFiles: Any custom scripts, dependencies, or helper files needed before, during, or after the install. You can also put all your files in the previous “File” folder and point to them in your script. It improves organization but has no functional impact on behaviour.
• Assets: Any icons or logos used by the toolkit when displaying the interface. These can be replaced with the custom company ones. Just ensure you respect the format; otherwise, it will look odd.

Now, why is PSADT widely used?

• It’s free and open-source.
• It plays well with enterprise deployment tools like Microsoft Intune, MECM (SCCM), and even third-party solutions.
• Its folder structure makes it easy to wrap inside an IntuneWin package using Microsoft’s prep tool (IntuneWinAppUtil.exe) and push directly to the cloud.

PacKit, powered by Advanced Installer, offers a centralized workspace for managing all your application packages. It comes with a built-in PSADT integration.
With a push of a button, your "setup.exe" is wrapped automatically inside PSADT, and information is extracted and preconfigured inside the script.
You can later edit the script in your preferred editor. After that, with a simple click of a button, you can convert the PSADT script into an .intunewin file, ready to integrate and deploy to Intune.
You can learn more about PacKit’s capabilities here: https://www.getpackit.com/features

Now, let's see a few command examples that can be used in the installation and uninstallation sections, as well as pre- and post-installation:

# Remove a previous MSI-based version by name
Uninstall-ADTApplication -Name "Adobe Acrobat"
# Install Adobe
Start-ADTMsiProcess -Action "Install" -FilePath "$($adtSession.DirFiles)\AcroPro.msi" -Transforms "$($adtSession.DirFiles)\$transform" -Patches "$($adtSession.DirFiles)\AcrobatDCx64Upd2500120577.msp" -AdditionalArgumentList "EULA_ACCEPT=YES IGNOREVCRT64=1"
Remove-ADTFile -Path "$envCommonDesktop\Adobe Acrobat DC.lnk"
## Configure settings for Adobe Acrobat Reader DC
# Disable#Disable EULA
Set-ADTRegistryKey -Key "HKLM:\SOFTWARE\Adobe\Adobe Acrobat\DC\AdobeViewer" -Name "EULA" -Value "1" -Type "DWord"

Sometimes you need to make some configurations, but you don’t know:

• Which files need to be configured
• What registry keys need to be modified

Additionally, you may want to build an installer from scratch, relying on an easy-to-use UI with predefined functions. This is where Advanced Installer Architect comes in.

Use Cases Where Advanced Installer Complements PSADT

Generating MSTs (Transforms)

Advanced Installer can create a response transform of your MSI installer or a scratch transform that will alter it.

GUI installer builder

Advanced Installer Architect provides a rich, user-friendly GUI that lets you build installers step-by-step. You can:

• Easily configure files, registry keys, shortcuts, prerequisites, custom actions, and more.
• You can also design visually appealing installers with customizable themes, branding, logos, and dialogs—far beyond what PSADT’s basic UI notifications offer.

Repackaging and snapshotting

It can create MSI or EXE installers by capturing existing installations, helping you generate installers from legacy setups that you might otherwise struggle to script manually. These are the cases where you have setups that do not accept silent installs. Even if you put those installed wrapped inside PSADT, it will simply not install automatically. It will require repackaging, the process being the same as in the case of a customization configuration package.

Advanced features

The Architect edition supports auto-updates, digital signing, rollback scenarios, installation repair, and patching—all integrated into the packaging process.

Seamless integration

You can use Advanced Installer to build the base MSI or EXE installer. You can then wrap it with PSADT to leverage its powerful scripting capabilities for post-installation configuration or complex deployment scenarios.

Powerful troubleshooting and logging

Although PSADT generates its installer log located in c:/windows/logs/software, it does not offer the actual setup installer logging unless specified. Advanced Installer includes detailed logging and diagnostics features that can help you troubleshoot any installation issues during development or deployment.