: Include images, XML configs, or helper executables.

: Select all files inside the folder, right-click, and select Send to > Compressed (zipped) folder . Name it ws1.zip .

: In the Workspace ONE Console , go to Apps & Books > Native > Internal and upload your ZIP.

: Make your custom tools look professional in the Intelligent Hub . Step-by-Step: Creating Your ws1.zip Package

: Use registry keys or file paths to verify if the "app" (your script) actually finished.

: Place your main PowerShell script (e.g., DeployConfig.ps1 ) and any supporting files in a single folder.

A common pitfall when extracting ZIPs in the background via PowerShell's Expand-Archive is that the command may try to show a progress bar. Since WS1 runs in a hidden system context, this can cause the script to hang. As noted by users on Reddit , always add -ErrorAction SilentlyContinue to your expansion commands to ensure smooth, silent execution. How can I help further? If you'd like, I can:

If you’ve ever tried to deploy a standalone PowerShell script through , you might have run into the "one-file limit" for basic script resources. But what if your script needs a configuration XML, a custom icon, or a secondary installer?