If you are using a Mac but need to prepare a Windows EXE for Intune deployment, you can use the command-line version of the Microsoft Win32 Content Prep Tool via Terminal.
pkgbuild --component /Path/To/YourApp.app --install-location /Applications /Path/To/Output/YourApp.pkg Use code with caution.
pkgbuild --component /Path/To/Your/WineskinApp.app --install-location /Applications /Path/To/Output/OutputPackage.pkg Use code with caution.
Instead, you must choose one of the following solutions based on your specific goal: convert exe to pkg
./IntuneAppUtil -c -o Use code with caution.
Repackaging MSI inside PKG (if EXE contains MSI)
By choosing the correct workflow for your specific use case, you can bypass the architectural barriers between Windows and macOS to distribute your software smoothly. If you are using a Mac but need
: Defines the destination path and name of your new PKG file.
Ensure your translation layers match the target hardware. Modern Macs utilize Apple Silicon (M1/M2/M3 chips), which requires translation via Rosetta 2 if the underlying Wine engine or application uses x86_64 architecture. Verify that your compiled .pkg works seamlessly across both Intel and Apple Silicon hardware before pushing it to production fleets.
You must possess an active Apple Developer Account to sign the package using the productsign utility. Instead, you must choose one of the following
Set up a clean Windows Virtual Machine on macOS using Parallels Desktop.
pkgbuild --root /path/to/payload --identifier com.user.app output.pkg Sign the Package:
