PackMyApp Documentation

Forge: Step-By-Step Operator Flow

Follow the guided 5-step Forge wizard from sign-in through deploy completion.

Forge Desktop Audience: Customer Access: Tier dependent

Forge: Step-By-Step Operator Flow

Prerequisites

  • Windows device with Forge installed.
  • PackMyApp account on Tier 1, MVP, Tier 2, or Tier 3.
  • Active linked tenant state in PackMyApp.
  • Installer file ready (.exe or .msi) in a dedicated source folder.

Full Operator Flow

Step 1 — Sign In

  1. Open Forge and click SIGN IN.
  2. Browser opens Microsoft authentication. Sign in with your PackMyApp-linked work account.
  3. Wait for Forge to show session validation success. Do not continue until you see confirmation.

Step 2 — Select Installer

  1. Click Select source folder and choose the folder containing your installer.
  2. Select the installer file. Forge parses the file and populates the install/uninstall/detection fields automatically.

Step 3 — Review And Edit Profile Fields

  1. Review the three generated fields: - Install command: check that the silent flag (/S, /quiet, /qn, etc.) is correct for this installer. - Uninstall command: check that the removal command uses the same product code or path the installer registered. - Detection rule: check that the registry key or file path will be present after a successful install.
  2. Edit any field that is not accurate. Use your installer documentation or a test machine to verify.

Step 4 — Validate

  1. Click Run validation to test commands and detection rule.
  2. Review the validation output. Fix any flagged issues before continuing.
  3. If you have tested the installer manually on a reference machine, you can click Skip validation instead.

Step 5 — Build Package

  1. Click Build package.
  2. Wait for Forge to generate the .intunewin package. Build time depends on installer size.

Step 6 — Assign Group And Deploy

  1. After build, continue to PackMyApp web interface for deploy handoff.
  2. In the deploy wizard, at step 5. Choose Group, search for or create the target Entra security group.
  3. Select assignment intent (Required or Available for enrolled devices).
  4. Complete 6. Auto-Update Options if you want to configure automatic version updates.
  5. Click Deploy and monitor the activity log until completion.

Expected Result

  • Forge build completes without errors.
  • PackMyApp deploy wizard runs with the packaged app in the correct tenant and group context.
  • Activity log confirms successful deployment or shows a clear failure stage for remediation.

If It Fails

  1. If session validation fails, re-check tenant link in Settings > Tenant Connection and retry sign-in.
  2. If installer profile fields are wrong, edit them manually and re-run validation before building.
  3. If group creation fails during deploy, retry with a unique group name.
  4. If deploy fails at a specific step, use Settings > Activity Logs to identify the stage.
  5. Always test with one app in a controlled group before larger rollouts.

Next Articles