Initial

tools/README.md

@@ -0,0 +1,30 @@
+# Tools
+
+Drop external tools used by POSHManager here.
+
+## IntuneWinAppUtil.exe (Microsoft Win32 Content Prep Tool)
+
+Place `IntuneWinAppUtil.exe` in this directory to enable in-app `.intunewin`
+packaging (the **Build** action on an Intune deployment). POSHManager runs:
+
+```
+IntuneWinAppUtil.exe -c <sourceFolder> -s <setupFile> -o <outputDir> -q
+```
+
+and ingests the resulting `.intunewin` into the Asset Library, linking it to the
+deployment for content upload.
+
+Download it from the official repository:
+<https://github.com/microsoft/Microsoft-Win32-Content-Prep-Tool>
+
+### Requirements / configuration
+
+- The tool is a Windows executable; the **Build** action requires the API host
+  to run on Windows. POSHManager auto-detects this and disables Build otherwise.
+- Override the tool location with `INTUNEWIN_UTIL_PATH=/path/to/IntuneWinAppUtil.exe`.
+- To use a cross-platform packager instead, set `INTUNEWIN_BUILD_COMMAND` to a
+  command template using the placeholders `{source}`, `{setup}`, and `{output}`,
+  e.g. `INTUNEWIN_BUILD_COMMAND="my-packager --src {source} --setup {setup} --out {output}"`.
+  The command must produce `<setupFileBaseName>.intunewin` in `{output}`.
+
+`IntuneWinAppUtil.exe` and the `_build/` working directory are git-ignored.