Install the OpenFrame Agent on Windows
Phase 2 — Device Deployment · OpenFrame Onboarding
Guide maintenance · Owner: Conrad Lunderstedt · Last full review: 23 Sep 2026
Each section below carries its own Last verified date. When the installer or the Add Device screen changes, update that section and its date only.
The OpenFrame agent installs on Windows with a single PowerShell command. It downloads the client, unpacks it, and registers the PC to the customer you chose. Do one by hand first, the way this guide walks through it, so you know what "working" looks like before you push it fleet-wide.
Everything you need is in one place: Devices → Add Device.
What you'll do
Last verified: 23 Sep 2026
| Step | Where | Takes |
|---|---|---|
| Check you have the right access | OpenFrame and the PC | 1 min |
| Copy the install command | OpenFrame → Devices → Add Device | 1 min |
| Add antivirus exclusions | The PC's AV console | 2 min, third-party AV only |
| Run the command | An elevated PowerShell on the PC | 2 min |
| Confirm it's online | OpenFrame → Devices | 1 min |
Work through them in this order. The AV step is the one people skip and then regret.
Before you start
Last verified: 23 Sep 2026
You'll need:
- The Admin role in OpenFrame.
- Local administrator rights on the PC, so you can open an elevated PowerShell (Run as administrator).
- The right customer picked out. Every customer has its own install command, and whatever you copy decides where the PC lands.
Tip: Choose the customer carefully. Moving a device to a different customer or group after install currently means uninstalling and reinstalling the agent. Ten seconds of checking here saves a reinstall later.
Get the install command
Last verified: 23 Sep 2026
- In OpenFrame, go to Devices → Add Device.
- Under Select Customer, choose the client this PC belongs to.
- Under Select Platform, choose Windows.
- Optionally add a Device Tag; it's applied when the device is created.
- The command appears under OpenFrame Installation Script. Click Copy Install Command.
The command downloads and extracts openframe-client.exe. It always pulls the latest release, so there's nothing to version-pin.
Tip: Copy it fresh for each customer. A command copied last week for a different client will put this PC in the wrong place.
Add antivirus exclusions
Last verified: 23 Sep 2026
Some antivirus products flag the installer or the remote-control component on first run. It's a false positive, and it's easiest to head off before you run anything. Defender usually lets it through; if the PC runs third-party AV (Avast, AVG, Bitdefender, Webroot and similar), add these folder exclusions first.
C:\Program Files\OpenFrameC:\ProgramData\OpenFrameC:\ProgramData\OpenFrameInstallC:\Program Files\OrbitC:\Program Files\Mesh Agent
The Mesh Agent folder is the remote-control component and the one third-party AV most often flags after install, so don't leave it out.
If you skipped this and the install was blocked, add the exclusions, restore anything quarantined, and run the command again. It's safe to re-run.
Tip: Rolling out to a whole customer? Push these exclusions through the AV console as a policy before you deploy, rather than per machine.
Run the command
Last verified: 23 Sep 2026
- On the Windows machine, open PowerShell as administrator (right-click → Run as administrator).
- Paste the command you copied and press Enter.
- Wait for it to finish. You'll see the download and extraction progress, then a completion message. Don't close the window early.
That's it for the machine. Everything else happens in OpenFrame.
Tip: If PowerShell refuses with "running scripts is disabled", start a session with
powershell -ExecutionPolicy Bypassand paste the command there.
Confirm it's online
Last verified: 23 Sep 2026
Back in OpenFrame, open Devices. The PC should appear under the customer you chose and show Online within a minute or two. Full verification and first checks are in Confirm Your First Device Is Connected.
Troubleshooting
Last verified: 23 Sep 2026
"Running scripts is disabled on this system."
Execution policy is blocking it. From an admin PowerShell, start a bypass session with powershell -ExecutionPolicy Bypass and paste the command there, or set a policy that fits your org's standards.
Permission or access-denied errors.
You're not elevated. Close the window and reopen PowerShell with Run as administrator.
Download fails or hangs.
Check outbound internet on the PC, and confirm a proxy or web filter isn't blocking GitHub release downloads; that's where the client is hosted.
Antivirus quarantined it.
Add the exclusions above, restore anything quarantined, and re-run the command.
Installed but shows Offline.
Give it a couple of minutes. If it stays offline, follow Confirm Your First Device Is Connected, then Troubleshooting a Disconnected Device (Phase 10).
Device not appearing, or stuck pending.
TODO before publishing: insert the doctor command and what its output looks like.
Landed in the wrong customer or group.
There's no move option yet. Uninstall the agent, copy the install command from the correct customer, and run it again.
Quick checklist
Before you move on to the next device, confirm you've:
- Selected the correct customer (moving later means a reinstall)
- Chosen Windows and, optionally, added a tag
- Added AV exclusions if the PC runs third-party AV
- Run the command in an elevated PowerShell and let it finish
- Confirmed the PC shows Online under Devices
What's next
One device in, and you know what a good install looks like. Install the OpenFrame Agent on macOS covers the Mac side; Confirm Your First Device Is Connected is where you check the agent is reporting properly before you scale up.
