Skip to main content
This page is for the IT admin who deploys Bridge to Windows 11 devices. It uses Microsoft Intune; any MDM that can install an MSI as SYSTEM and run a PowerShell script as SYSTEM on a schedule can do the same. For Macs, see Install on macOS. The install has five steps, all assigned to a pilot device group first:
  1. Render the policy scripts from Barndoor’s MDM kit.
  2. Install the app as a Win32 app.
  3. Add the Remediations that apply Barndoor’s settings and the Codex policy.
  4. Deploy the clients people will use.
  5. Verify a device, then widen the group.
On Windows, Bridge runs from the system tray and launches Claude Desktop, Codex Desktop, and the Claude Code, Codex, and Kilo CLIs. Kilo Desktop, Kilo in VS Code, and provider lockdown aren’t available on Windows.

Before you start

  • Windows 11 Pro, Enterprise, or Education devices, Entra joined and enrolled in Intune, with an Intune licence for every user and device (Microsoft 365 Business Premium, E3 or E5, or Intune Plan 1; Business Standard doesn’t include it).
  • Windows Enterprise E3 or E5 for Remediations (part of Microsoft 365 E3 or E5). Without it, see Without Remediations.
  • A Mac or Linux machine to render the policy scripts. The MDM kit’s render.sh is a bash script.
  • Two values from your Barndoor admin: your organization slug and the backend URL. See Values IT needs.

1. Render the policy scripts

Unpack the MDM kit and render the Windows files:
Use --dns-control-source external_swg instead if a secure web gateway already blocks the LLM provider APIs. The scripts land in rendered/windows/. They carry no IDs, so unlike the macOS profiles, re-rendering after a change is harmless.

2. Install the app as a Win32 app

Download the MSI for the current stable version, for x64 (amd64) or Arm (arm64): https://downloads.barndoor.ai/barndoor-gui/<version>/Barndoor-<version>-windows-<amd64|arm64>.msi, for example Barndoor-v0.1.246-windows-amd64.msi. index.json gives the current stable version (latest) and each version’s SHA-256. Deploy it as a Windows app (Win32), not as a line-of-business app, which doesn’t install reliably:
  1. On a Windows machine, wrap the MSI with Microsoft’s Win32 Content Prep Tool:
  2. In Intune, Apps → Windows → Add → Windows app (Win32), and upload the .intunewin file. Intune reads the install and uninstall commands and the detection rule from the MSI.
  3. Assign it as Required to the device group.
Intune installs the app shortly after the device’s next check-in. Add/Remove Programs then shows Barndoor, published by Barndoor AI, Inc.
The MSI is a per-machine installer, code-signed by Barndoor AI, Inc. It installs C:\Program Files\Barndoor\barndoor.exe (the barndoor command) and barndoor-gui.exe (the tray app), puts that folder on the machine PATH, and starts the tray at every sign-in.

3. Add the Remediations

Create a Remediation for each pair of rendered scripts (Devices → Scripts and remediations → Remediations → Create): For both, run as SYSTEM (Run this script using the logged-on credentials: No), in 64-bit PowerShell, hourly, assigned to the device group. Leave Enforce script signature check off unless you sign the rendered scripts with your own certificate. The Codex Remediation reports compliant until Bridge is installed, so expect the Codex policy up to an hour after the app.
Without Windows Enterprise E3 or E5, upload Set-BarndoorPolicy.ps1 as a platform script (Devices → Scripts and remediations → Platform scripts) with the same settings. A platform script runs once, so upload it again after any change.

4. Deploy the clients

Bridge launches these clients but doesn’t install them:
  • Claude Desktop: the MSIX build, from https://claude.ai/api/desktop/win32/x64/msix/latest/redirect, as an MSIX line-of-business app or through your usual MSIX channel. Bridge refuses the build winget install Anthropic.Claude installs, with install the MSIX build of Claude Desktop.
  • Codex Desktop: the Microsoft Store package (OpenAI.Codex). In Intune, add it as a Microsoft Store app (new).
  • Claude Code, only when your Claude routes bill people’s Claude subscriptions: Claude Desktop gets the subscription sign-in from Claude Code. It installs per user (irm https://claude.ai/install.ps1 | iex). Bridge offers to install it at launch if it’s missing, but deploying it with Bridge saves people the wait. The first time someone clicks Launch Claude Desktop, the tray signs them in to Claude.
Keep HKLM\SOFTWARE\Policies\Claude clear on devices that use Bridge. If your Claude Desktop registry policy sets anything beyond app-behaviour settings (disableAutoUpdates, autoUpdaterEnforcementHours, updateViaUpdatesHost, relaunchEnforcementHours, configRecheckIntervalMinutes, egressProxyUrl, egressProxyPacUrl), Claude Desktop ignores the configuration Bridge gives it and runs ungoverned, with no error. barndoor doctor warns when this is the case.

5. Verify a device

In the signed-in user’s PowerShell (not over SSH, where Windows Credential Manager isn’t available), run barndoor doctor. Among its sections, expect:
Then sign in from the tray icon (it may be under the ^ overflow), click Launch Claude Desktop, and ask for something that needs one of your organization’s tools. Once the pilot looks right, widen the group. Bridge’s log is in %LOCALAPPDATA%\Barndoor\Logs.

Codex policy on Windows

The Codex policy works as it does on macOS. With it on a device:
  • Launch Codex Desktop appears in the tray once Codex Desktop is installed for the user.
  • The codex CLI, and Codex Desktop opened directly, work only through Barndoor. Codex Desktop opened directly stops at ChatGPT configuration could not be loaded … undefined profile barndoor-active; people launch it from Bridge instead.
  • It replaces any Codex requirements file of your own, so a fleet that ships its own Codex requirements shouldn’t deploy the Codex Remediation.
Bridge launches only Codex Desktop builds it has reviewed; barndoor codex-desktop-policy builds says whether the installed one is supported.

Updates

There’s no Windows updater script, and barndoor update refuses on managed devices. For each new stable release, add the new MSI as a new Win32 app that supersedes the previous one. Each MSI upgrades the one before it in place and never downgrades.

Uninstall

Change the app’s assignment to Uninstall; Bridge is removed at the next check-in. The Barndoor policy and the Codex policy stay, and without Bridge the Codex policy stops Codex Desktop from opening.
Before you uninstall:
  1. Unassign both Remediations.
  2. As SYSTEM, run barndoor.exe codex-desktop-policy remove. It deletes only Barndoor’s file.
  3. As SYSTEM, run reg delete HKLM\SOFTWARE\Policies\Barndoor /f.
Reassigning an uninstalled app as Required doesn’t reinstall it right away: Intune waits up to 24 hours before it re-evaluates the app on that device.

Local MCP servers on Windows

If your organization publishes its own local MCP servers, pin the publisher key in the publisher_keys registry value instead of a macOS profile: fill in the commented publisher_keys line in both Detect-BarndoorPolicy.ps1 and Set-BarndoorPolicy.ps1. Set-BarndoorPolicy.ps1 deletes any value it doesn’t list, so a key added another way is gone after the next hourly run. See Pin the key with MDM and Windows builds.