PackMyApp Documentation

Deployment Wizard: Full Flow

Walk through the 7-step deployment wizard from tenant choice to deploy execution.

Workspace And Deployment Audience: Customer Access: Tier dependent

Deployment Wizard: Full Flow

The deploy experience is a stepped wizard: one step at a time, a progress stepper on top, and a plain-language review before anything touches Intune.

Deployment wizard with progress stepper, starting at the Workspace step

Prerequisites

  • Tenant connection is healthy.
  • You are in the correct customer context.
  • Target app is selected from the catalog (or via Discovery → Deploy managed copy).

Click Path

  1. Open App and switch to the Catalog tab (or start from Discovery).
  2. Select an app and click Deploy.
  3. Follow the stepper — completed steps show a green check, and you can click any completed step to go back:
  4. Workspace — pick the tenant that should receive the deployment.
  5. Platform — Windows (Win32 · Intune) or macOS (PKG/DMG).
  6. Version — latest is recommended; the chosen version shows a green Chosen state.
  7. Settings — how the install behaves (see below).
  8. Assign — who gets the app, including extra targets.
  9. Updates — whether PackMyApp keeps the app up to date automatically.
  10. Review — a one-sentence summary of exactly what will happen, then Deploy.
  11. Monitor the deploy activity log until completion.

Step 4: Settings

Every option lives on one screen — title on the left, control on the right, sensible defaults filled in. Most teams only pick Install for and click Next.

Settings step: install-for, device requirements, restart, conflict handling, exit codes, Company Portal, app details

  • Install for — Per-Machine (recommended, default) or Per-User.
  • Only install on devices that meet… — minimum Windows version, memory, CPU, processors. Devices that don't qualify are skipped, not failed.
  • Restart after install — what happens if the installer asks for a reboot.
  • If the app is open when it installs — ask the person to close it (retry later), close it automatically, or wait and retry. Enforced by the generated install wrapper.

Conflict handling row: action dropdown plus process names

  • Self-service uninstall — let people remove the app themselves from Company Portal.
  • Exit codes — the standard Windows codes are mapped for you; add custom codes only for unusual installers.
  • Templates — save the current settings under a name and apply them to any future deployment in one click.

Templates bar: choose a saved template, apply, or save the current settings

Step 5: Assign

Pick the primary Entra group (or create one with +). Under More targets you can add extra groups (include or exclude), All devices, or All users — each with its own intent: install, available in Company Portal, or uninstall.

Assign step with an extra multi-target row

Step 7: Review

Before deploying you see, in plain language, exactly what will happen — app, target, platform, version, and whether auto-updates are on — plus a compact recap of the settings you changed.

Review step: one-sentence summary plus settings recap above the Deploy button

Expected Result

  • The deploy pipeline runs with the intended tenant, version, settings, and assignments.
  • The activity log confirms completion or shows a clear failure stage.

If It Fails

  1. Re-check Workspace and Platform first.
  2. Re-check the Assign selection or skip-assignment intent.
  3. Gating messages (for example a missing install scope) now appear on the step itself.
  4. Use Settings > Activity Logs to identify the failing stage.

Next Articles