Deploy JFrog Boost with Workplace ONE (WS1) MDM
Deploy JFrog Boost on managed Windows devices using Workspace ONE UEM scripts.
IT administrators can use Workspace ONE (WS1) to install JFrog Boost on managed Windows devices and configure agent integrations in one step. For company-wide deployment context, see Company-wide Boost Installation.
Note
For more information about individual developer setup, see JFrog Boost Quickstart.
This topic includes the following rollout tasks:
Add the Script in WS1
A single line performs both parts of the installation. The Windows installer puts the Boost binary on the user's PATH, and then boost init installs the Claude Code and Cursor hooks and accepts the preview terms non-interactively.
irm https://boost.jfrog.com/install.ps1 | iex; boost init --claude --cursor --accept-termsTo add the Boost install script in Workspace ONE UEM:
- In Workspace ONE UEM, go to Resources > Scripts.
- Click Add.
- Select Windows.
- In the Details tab, paste the Boost one-liner from the code block in this section into the Code field.
Set the Execution Context
Configure how Workspace ONE UEM runs the script on each device.
The following table lists the recommended execution settings.
| Setting | Value |
|---|---|
| Language | PowerShell |
| Execution context & privileges | User context with Admin privileges |
| End-user interaction | None |
| Execution architecture | Auto |
| Timeout | 30 |
To set the execution context:
- In the script configuration, open the execution settings for the Boost install script.
- Set each value to match the table in this section.
- Save the script.
Assign to a Smart Group
Assign the script to the smart group of Windows devices that should receive Boost. Rerunning the script is safe. It refreshes the binary and re-applies the selected integrations.
To assign the script to a smart group:
- In Workspace ONE UEM, open the Boost install script.
- Assign the script to the target smart group of Windows devices.
- Save the assignment.
Choosing Integrations
Change the boost init flags to match the agents your fleet uses. --accept-terms is required because the script runs without end-user interaction.
irm https://boost.jfrog.com/install.ps1 | iex; boost init --cursor --accept-terms
irm https://boost.jfrog.com/install.ps1 | iex; boost init --claude --cursor --codex --accept-termsOperational Notes for WS1 Deployments
- The one-liner is idempotent. Rerunning it upgrades Boost in place and re-applies the selected integrations.
- Instruct developers to restart their AI agent after the script runs to pick up the new hooks.
- The 30-second timeout covers the download on a normal connection. Raise it if your egress proxy is slow.
- Verify a device by running
boost versionandboost reportas the logged-in user.
Frequently Asked Questions
This section provides answers to frequently asked questions about deploying JFrog Boost with Workspace ONE UEM.
FAQs
Q: Which agent integrations does the default WS1 script enable?
A: The default one-liner runs boost init --claude --cursor --accept-terms, which installs Claude Code and Cursor hooks. For other agent combinations, see Choosing Integrations.
Q: What execution context should I use in Workspace ONE UEM?
A: Use PowerShell with user context and admin privileges, no end-user interaction, and a 30-second timeout. For more information, see Set the Execution Context.
Q: How do I verify Boost installed on a Windows device?
A: Run boost version and boost report as the logged-in user. Developers must restart Cursor or Claude Code after the script runs to pick up the new hooks.
Related Topics
Updated about 3 hours ago