The Edventory Agent for unmanaged Windows PCs

Windows machines that live outside Active Directory and any MDM (front-office PCs, shop computers, donated laptops) can inventory themselves with the Edventory Agent: a small installable client that reports hardware facts at every boot and once a day.

Create the connector

Settings → Connectors → New data connector → choose Edventory Agent. You get an enrollment key and a ready-made install command. Need the key again later? Open the connector's setup panel and click Reveal key — enrolling more PCs never requires generating a new one.

Install on each PC

Download EdventoryAgent.msi from the connector's setup panel, double-click it on the PC, and paste the enrollment key when the installer asks. For mass rollout, install silently with the key baked in — msiexec /i EdventoryAgent.msi ENROLLKEY=evk_… /qn — from any deployment tool, a startup script, or your standard image.

Watch devices appear

Each PC checks in within a minute of install, then at every boot and once a day (at a randomized time). The device record shows an Agent check-in section: CPU, RAM, disk & free space, BitLocker status, last user, last boot, and OS build.

Question	Answer
What does it send?	Hardware facts only: hostname, make/model, serial, OS build, CPU, RAM, disk size/free, MAC addresses, BitLocker status, last logged-on user, last boot. No files, no browsing history, no screenshots.
Can Edventory control the PC?	No. The agent is read-only by design: it sends facts and receives nothing. There is no remote-command channel.
How do I audit it?	The collector is a plain PowerShell script installed at `C:\Program Files\Edventory Agent` — open it and read every line. Run it with `-DryRun` to print exactly what would be sent without sending it.
How do I remove it?	Settings → Apps → Edventory Agent → Uninstall (or `msiexec /x EdventoryAgent.msi /qn`). The scheduled task, files, and registry entries are all removed.
Duplicate serials?	Budget PCs sometimes ship placeholder BIOS serials ("To be filled by O.E.M."). The agent detects these and uses the Windows machine GUID instead, so those machines still get one record each.

ℹ️

A machine that stops checking in for 14+ days is flagged as stale in the connector panel and on its device record. That's the usual sign a PC was retired without telling anyone.

🛡️

The enrollment key can only write device records; it can't read any district data. Admins can reveal it from the connector panel at any time (each reveal is recorded in the activity log). If the key leaks, rotate it — installed agents keep the old key and stop reporting until reinstalled with the new one.