PackMyApp Forge Desktop Guide

Prerequisites

• Windows environment with Forge installed.
• PackMyApp account on Tier 1, MVP, Tier 2, or Tier 3 (Forge is not available on Tier 0).
• Active linked tenant context in PackMyApp.

What Is Forge?

PackMyApp Forge is a Windows desktop application that converts a traditional Win32 installer (.exe, .msi) into an Intune-ready package. It generates the install command, uninstall command, and detection rules automatically, then hands the package off to PackMyApp for deployment.

Automatic Recognition (Forge 0.4.0+)

Forge reads the installer binary itself — no filename guessing — to work out which application it is and how to install it silently:

• Product identity comes from the installer's own metadata (VersionInfo for .exe, the Property table for .msi): product name, version, and publisher. Forge shows this as, for example, Recognized Cursor 3.7.21 (Anysphere).
• Installer framework is detected from byte signatures inside the binary: Inno Setup, NSIS, InstallShield, WiX Burn, Squirrel, InstallAware, Advanced Installer, install4j, and Wise. Each framework gets its documented silent switches automatically (Inno Setup → /VERYSILENT /NORESTART /SUPPRESSMSGBOXES, NSIS → /S, InstallShield → /s /v"/qn /norestart", WiX Burn → /quiet /norestart, and so on).
• MSI packages additionally get the extracted ProductCode for exact msiexec /x {ProductCode} uninstalls and ProductCode-based detection (95% confidence).
• Detection rules are generated from the recognized identity (registry uninstall entry: DisplayName + minimum version) instead of placeholders.
• Confidence is honest: 95% (MSI with ProductCode), 90% (framework + identity), 82% (framework only), 68% (identity only). Below that, Forge tells you to verify the silent switch instead of pretending.

The catalog match also uses the recognized product name, so a file called setup_v3_final(2).exe still matches the right catalog app.

Click Path

1. Launch Forge desktop app.
2. Click SIGN IN and complete browser authentication with your PackMyApp-linked Microsoft account.
3. Wait for Forge to confirm session validation before continuing.
4. Click Select source folder and navigate to the folder containing your installer file.
5. Select the installer file (.exe or .msi).
6. Review the auto-generated profile fields: - Install command: the command Intune will run to install the app silently. - Uninstall command: the command Intune will run to remove the app. - Detection rule: the registry key or file path Forge uses to confirm successful installation.
7. Edit any of the three fields if the auto-detection is not accurate for your installer.
8. Click Run validation to verify the detection rule and commands, or choose Skip validation if you have already tested manually.
9. Review the validation output.
10. Click Build package to generate the Intune .intunewin package.
11. After package build, continue to deploy handoff from the PackMyApp web interface.

Expected Result

• Forge session is valid and tied to the correct tenant context.
• Package build completes with a valid .intunewin output.
• Deploy handoff is ready in PackMyApp without manual repackaging.

Field Reference

If It Fails

1. If sign-in fails, verify PackMyApp session in browser and retry.
2. If tier check fails, confirm your PackMyApp plan includes Forge access.
3. If detection rule validation fails, edit the rule manually and re-run validation.
4. If build fails, verify installer file is intact and not locked by another process.
5. If tenant handoff fails after build, verify linked tenant in Settings > Tenant Connection.

Next Articles

• Forge: Step-By-Step Operator Flow
• Connect A Tenant
• Troubleshooting: Deploy And Update Issues