EXE, MSI, DSM: what PilotDeploy handles — and what it does not

The most common wrong expectation about a packaging tool is that it replaces install testing. It does not. What PilotDeploy does is narrower and more useful: it reads the source, makes the decisions visible and writes a PSADT package with a fixed structure.

This page lists which sources are handled, what comes out and where the limits are — before you invest time in a package.

Three source types, three starting points

EXE. An EXE is a black box with parameters that are sometimes documented and sometimes guessed. PilotDeploy detects file type, architecture and signature and suggests silent parameters. Whether the call really runs silently only the test shows. More: finding silent switches without guessing.

MSI. An MSI brings an installer database with properties and documented return codes. The most forgiving case: fewer riddles, more traceable settings.

DSM. DSM is an older package format with its own script logic (script.inc) and payload. PilotDeploy reads the scripts, maps commands and keeps unknown logic as a review item. For existing packages, migration is often faster than rebuilding.

In all three cases the file is read in the browser; it is not uploaded to a server for analysis.

What ends up in the package

The export is a ZIP with a fixed structure:

• launcher (Deploy-Application.exe) and Deploy-Application.ps1
• sources under Files/Source
• reports and metadata under PackageInfo, including manifest.json

Plus the details you confirm in review: install command, uninstall command, detection and return codes. The documentation describes this output contract.

What PilotDeploy does not do

• No install test. Whether a package works shows on a clean Windows machine, not in the builder.
• No deployment. No connection to your Intune tenant, no agent.
• No automatic updates. A new package exists only when you build one.
• No finished .intunewin file. The export contains the PSADT ZIP and the Intune helpers; the .intunewin file is built locally with IntuneWinAppUtil.exe.
• No detection guarantee. The rule is suggested and checked, the decision stays with you.

These are not weaknesses, they mark the line between packaging and operations. See PilotDeploy and Robopack.

Sources that are not listed

The website names EXE, MSI and DSM as sources. MSIX, App-V and Winget packages are not part of that set. No export is documented for those formats; clarify the need before signing up.

The same goes for very large sources: no size limit is published on the website. Check it in the app before planning a multi-gigabyte package.

Why detection is the critical part

A package that installs but is not detected counts as not installed in Intune and gets deployed again. The most common failure is a version check that is not updated with the next release. That is why detection is its own checkpoint in PilotDeploy, not a footnote.

How the three paths — registry, file, script — work is covered in detection rules that survive an update.

What has to happen before rollout

1. Install on a clean machine, no test leftovers.
2. Check uninstall: does anything stay behind?
3. Install again. Only then is the package repeatable.
4. Deploy to a small test group and read the Intune feedback.

Skip these four and you are testing in production.

FAQ

Can I package a folder instead of a file? Yes, the app also offers folder selection. A ZIP is not accepted as a single source; unpack it first.

Are my installers uploaded? Not for analysis. Analysis runs in the browser. If you store the finished ZIP in the personal package catalogue, it can contain installers and payload and leaves the device encrypted; that is optional and switchable.

Does PilotDeploy know whether an EXE installs silently? It suggests parameters and flags them as a checkpoint. Proof comes from the test, not the analysis.

Do I get a ready-made Intune app? You get a PSADT ZIP plus the install, uninstall and detection details. Uploading and assigning happens in Intune.

Catalogue and scope

PilotDeploy currently shows nine reviewed templates in the catalogue. That is not a 30,000-app catalogue: the focus is building your own package from EXE, MSI, DSM and folders.

Next step

If you want to check a source: the builder starts without a credit card, the first 20 exports are free. The product page shows the flow.