Install the OpenFrame Agent on Windows

Same idea as the Mac, different shell. The OpenFrame agent installs on Windows with a single PowerShell command that downloads the client, unpacks it, and registers the PC to the customer you pick. Here's how to do one by hand before you roll it out fleet-wide.

Before you start

• You need an Admin role in OpenFrame.
• You need local administrator rights on the Windows machine, and you'll run the command in an elevated PowerShell (Run as administrator).
• Know which customer this PC belongs to — set it at install time so the device lands under the right client.
• Expect a possible antivirus block on first install. It's a false positive; handle it with the exclusions below.

Get the install command

1. Left nav → Devices → Add Device.
2. Under Select Customer, pick the client this PC belongs to.
3. Under Select Platform, choose Windows.
4. (Optional but recommended) Click Add Device Tag to attach tags now — e.g. Type: desktop or Purpose: server. It saves sorting later (see Organize Devices with Device Tags).
5. The command appears under Device Add Command. Click Copy Command.

It looks like this (your key and org ID are embedded — keep them private):

powershell
Set-Location ~; `
Remove-Item -Path 'openframe-client.zip','openframe-client.exe' -Force -ErrorAction SilentlyContinue; `
Invoke-WebRequest -Uri '<openframe release URL>/openframe-client_windows.zip' -OutFile 'openframe-client.zip'; `
Expand-Archive -Path 'openframe-client.zip' -DestinationPath '.' -Force; `
& '.\openframe-client.exe' install --serverUrl <your-tenant>.openframe.ai --initialKey <YOUR_KEY> --orgId <YOUR_ORG_ID>

In plain terms: it downloads the Windows client zip, extracts it, and runs openframe-client.exe install pointed at your tenant with an enrollment key and the customer's org ID.

The --initialKey is a live enrollment token. Treat the copied command like a credential — don't drop it in a public channel or a client-visible ticket.

Run it on the PC

1. On the target machine, open PowerShell as administrator (right-click → Run as administrator).
2. Paste the command and press Enter.
3. Let it download, install, and register. No reboot required.

Shortcut for the machine you're on: the Add Device screen has a Run on Current Machine button if you're enrolling the PC you're sitting at. For remote machines you'll use the copied command (and Deploy at Scale for many at once).

Confirm it worked

Go to Devices — the PC should show Online within a minute or two. Full verification and fixes are in Confirm Your First Device Is Connected.

Troubleshooting

Antivirus blocked the install. Very common on Windows and it's a false positive — the client just hasn't built reputation with security vendors yet. If it gets quarantined, add these folders to your AV exclusions:

• C:\Program Files\OpenFrame
• C:\Program Files\TacticalAgent
• C:\ProgramData\OpenFrame
• C:\ProgramData\OpenFrameInstall
• C:\ProgramData\TacticalRMM
• C:\Program Files\Orbit

Or temporarily disable protection for the install, then turn it back on. For managed AV, push these exclusions via policy before a mass rollout so you're not chasing blocks machine by machine.

"Running scripts is disabled on this system." Execution policy is blocking it. Run PowerShell as admin and either run the command in a session started with powershell -ExecutionPolicy Bypass, or set an appropriate policy per your org's standards.

Not elevated. If you see permission/access errors, you're not in an admin PowerShell. Close it and reopen with Run as administrator.

Download fails. Check outbound internet and that a proxy or web filter isn't blocking GitHub release downloads.

Installed but Offline. Wait a couple of minutes; if it sticks, see Confirm Your First Device Is Connected and Troubleshooting a Disconnected Device (Phase 10).

Quick checklist

• Selected the correct customer
• Chose Windows and (optionally) added tags
• Ran the command in an elevated PowerShell
• Added AV exclusions if the install was blocked
• Confirmed the PC shows Online under Devices

What's next

With a Mac and a PC both reporting in, verify them properly in Confirm Your First Device Is Connected — then, when you're ready to do this at volume, Deploy at Scale via RMM / GPO / MDM.

Based on OpenFrame v0.9.19. The install command and client version come straight from your console's Add Device screen — always copy the current one rather than reusing an old command.