This permanently removes the pharmacy and all its data from the Fleet API. The Supervisor on the store VM will receive 410 Gone on its next heartbeat and switch to announce mode — run the script below on the VM to fully uninstall it.
Run in elevated PowerShell on the store VM:
Run in elevated PowerShell on the store VM. The machine will appear in Pending Approval — approve it from the dashboard to complete enrolment.
No token required — machine self-registers on install:
twc-{store number} (e.g. twc-341). For posx-harness this is also used as the site code automatically.One VM per Pharmacy ID. Each Pharmacy ID supports one enrolled machine. For pharmacies with multiple VMs, give each a unique ID — see Multi-VM pharmacies below.
Most pharmacies have a single VM — no special setup needed. If a store has two or more VMs (e.g. a POS terminal and a dedicated server), each VM needs its own Pharmacy ID and a role so you can control which agents each one runs.
twc-341) — it becomes the Pharmacy ID. For each additional VM, enter the same store code and select Add as new VM; Fleet auto-assigns a numeric suffix (twc-341-2, twc-341-3, …).PUT /pharmacies/twc-341/roles {"roles":["server"]}
PUT /pharmacies/twc-341-2/roles {"roles":["pos"]}
targetRoles on the agent to limit which VMs receive it:
POST /admin/agents/fleet-push
{ "agent": { "name": "posx-harness", "mode": "Deployment", "targetRoles": ["pos"] } }
Agents with no targetRoles (the default) are pushed to all VMs regardless of role — so existing single-VM pharmacies are unaffected.
API URLs and other installer settings can be stored once per environment in ⚙ Admin → Environment Profiles. When adding an agent to a pharmacy, pick the environment and settings fill in automatically — only the pharmacy-specific API key needs to be entered.
Brands are referenced by every pharmacy. Deleting a brand while pharmacies use it will fail — reassign them first.
| Order | Code | Name |
|---|
Set the API URL and other install settings once per environment. When you add an agent to a pharmacy, pick the environment and these fill in automatically.
| Agent | Environment | Params | Updated | |
|---|---|---|---|---|
| Loading… | ||||
Per-agent, per-channel artifact configuration. The supervisor picks the row matching the agent's channel, falling back to stable. Floating = no version set; supervisor always downloads the latest from the URL.
| Agent | Channel | Version | Updated | |
|---|---|---|---|---|
| Loading… | ||||
Enter your email to receive a login link.
A login link has been sent. It expires in 10 minutes.