Draupnir

Section 1

Upload & Configure

Installer intake

Upload an installer, capture the packaging metadata, and send it straight into the Azure DevOps flow behind Draupnir.

Vendor instructions shipped with this payload Read these

Quoted verbatim. Draupnir can tell this payload needs more than one step, but only you can turn these words into steps — it will not guess them.

Drop an installer here

Supported formats: .exe, .msi, .msix

or select from storage

No file selected yet.

Select application folder

Choose the folder containing the application and its main .exe entry point

No folder selected yet.

Main EXE filename The primary executable inside the folder (entry point for the MSI wrapper) Custom Install Folder Name Optional Overrides the folder name inside C:\Program Files\Publisher\. Leave blank to use the app name. Use to deploy production and test instances side-by-side without conflicts.

No shortcut icon selected

Optional. Overrides the icon on the Desktop and Start Menu shortcuts. Leave blank and the shortcuts use the icon embedded in the main EXE. Must be a real Windows .ico — a renamed .png produces a blank shortcut icon on the endpoint. This is separate from the Company Portal app icon.

Complete, pre-tested PSADT package source (e.g. trading app launchers). The pipeline packages it as-is into a .intunewin without install verification — detection rules below are mandatory.

Select package source folder

The PSADT source root (Invoke-AppDeployToolkit.ps1 / Deploy-Application.ps1, Files/, SupportFiles/…)

No source selected yet.

or upload the source as a .zip

No zip selected

Install Command Optional Defaults to the PSADT convention, e.g. Deploy-Application.exe -DeploymentType Install -DeployMode Silent (v3) or Invoke-AppDeployToolkit.exe … (v4). Only fill this for custom parameters. Uninstall Command Optional Defaults to the install command with Install replaced by Uninstall Description Optional

No icon selected

How Intune knows the app is installed (e.g. the deployed Start Menu shortcut or a marker file). File/registry rules are compiled into a detection script; alternatively supply your own detection .ps1.

If users already have an older version installed, pick the existing Intune app this package replaces.

Upload a vendor's unattended-install payload (installers plus a fragile batch/cmd entry). Draupnir analyzes it, reports what is risky, and compiles a hardened entry script from the chain you review below.

Select vendor payload folder

The unattended-install folder root (batch/cmd entry, MSIs/EXEs, optional post-install scripts)

No payload selected yet.

Entry Script Multiple candidate entry scripts were found in the payload — pick the one the vendor actually launches, then re-analysis runs against it.

Architecture Re-targets every {arch}/ step below at the selected architecture folder.

The chain compiled from the payload. Reorder, edit, or add steps before packaging.

Conditions checked before the first step runs — block the install if a conflicting product, registry key, or file is present.

How Intune knows the app is installed. File/registry rules are compiled into a detection script; alternatively supply your own detection .ps1.

Pre-install Script Optional

Pick a previously uploaded script or upload a new one.

or upload a new script

No script selected

Publisher Product Name Version Language Architecture Silent Switches e.g. /S /silent /qn

Select installers from the inbox that must be installed before the main package.

Loading packages…

Installer Folder Optional

For multi-file installers: select a local folder whose contents will be uploaded alongside the main .exe. The folder name must match the package name.

No folder selected

Jira Ticket Optional

Link a Jira ticket to notify the reporter and add them to the assignment group after packaging.

Pipeline Branch Optional

Branch to run the pipeline on. Defaults to main.

Upload a new file or pick one from storage, then the pipeline triggers automatically.

Section 2

Pipeline Execution

Awaiting run Open pipeline

A simplified packaging timeline that mirrors the Azure DevOps run behind the scenes.

Build ID —

Overall status Queued

Last refresh Waiting for first poll

Section 3

Post-Packaging Actions

Next step

Create the assignment group right away using the same metadata you used for packaging.

Assignment intent

Group preview

Naming convention:

CL-AZ-DWP-APP-Available-Publisher_Product_Version_EN_x64

Smoke Test Pending

The smoke test group has been assigned. Once the tester confirms the app works on a laptop, click below to finalize — this removes the smoke test group and notifies the requester via Jira.

Supersedence Optional

If this package replaces an app that users already have installed, configure supersedence so existing installations receive the new version.