clstrickland/Package for Intune Win32 Deployment
Packages an application source folder and specified scripts into an .intunewin file and creates output bundles, processing a INSTRUCTIONS template.
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Maintainedlast commit Apr 14, 2025
- License
- None
Pinned Snippet
uses: clstrickland/intune-win32-packager@3a35d43280f9e4df089156a4ef4b17113e14215b # v0.6tags can be moved; commit SHAs can't. why a SHA?
Inputs
| name | description | required | default |
|---|---|---|---|
| app_source_folder_path | Path to the FOLDER containing the main application installer and any dependencies (relative to the workspace root). | yes | — |
| install_script_path | Path to the PowerShell install script (e.g., Install.ps1) relative to the workspace root. This script MUST handle running the actual installer from the "../App" directory relative to itself. | yes | — |
| uninstall_script_path | Path to the PowerShell uninstall script (e.g., Uninstall.ps1) relative to the workspace root. | yes | — |
| detection_script_path | Optional: Path to the PowerShell detection script (e.g., Detect.ps1) relative to the workspace root. | no | — |
| output_bundle_name | Name for the output folder (created in workspace root) containing the .intunewin, scripts, and INSTRUCTIONS.md. | yes | IntunePackage |
| source_bundle_name | Name for the output folder (created in workspace root) containing the source files used for packaging (App and DeploymentScripts folders). | yes | IntunePackage_Source |
| app_name | The application name to use for the .intunewin file and instructions. | yes | — |
Outputs
| name | description |
|---|---|
| output_bundle_path | The workspace-relative path to the generated output bundle folder. |
| source_bundle_path | The workspace-relative path to the generated source bundle folder. |