Skip to content
MDO Documentation

Custom apps

Use Custom App under Apps in the sidebar to deploy an installer that isn’t in the Winget catalog.

Supported files

Section titled “Supported files”

You can upload .msi, .exe, .msix and .ps1 files up to 500 MB. The installer type is either MSI or EXE. An MSIX file is handled as an EXE; MDO has no MSIX-specific handling.

When you upload an MSI, MDO reads its product name, version, product code and manufacturer and fills them in for you.

Fields

Section titled “Fields”
  • Display name (required): the name shown in Intune.
  • Version, Publisher and Description.
  • Installer type: MSI or EXE.
  • Installer arguments: passed to the installer as written. For an MSI, /qn /norestart is typical. For an EXE, use the vendor’s silent switch, for example /S (NSIS), /VERYSILENT /SUPPRESSMSGBOXES (Inno Setup) or /s /v"/qn" (InstallShield).
  • Wrap with PSADT: wraps the installer in PSADT with your tenant’s branding, as in Deploying apps.
  • Pre and post scripts and Remove desktop shortcuts the install creates, as in the deploy wizard.

Test silent arguments on one machine before deploying widely.

Uninstall

Section titled “Uninstall”

An MSI is uninstalled by its product code. For an EXE, MDO can only build a real uninstall when the detection rule is a registry rule on the app’s Uninstall key, which holds the uninstall command. Otherwise tick Deploy without uninstall to deploy anyway.

Detection rules

Section titled “Detection rules”

Intune uses the detection rule to decide whether the app is installed:

  • MSI product code: selected automatically for MSI uploads, using the product code MDO read from the file.
  • File: a Windows path, with an optional file version.
  • Registry: a key path, with an optional value name.

Next steps

Section titled “Next steps”