Install a sensor on Windows
A Windows installer that registers the sensor as a Windows service, for estates where a Linux host is the awkward thing to provide.
This deployment path is planned but not delivered. A Windows host cannot run a sensor today — deploy on a Linux host with Docker and give it a route to whatever you need reached.
What it will change
As with the Linux package, the platform-facing behaviour is unchanged: the same deployment token, the same enrolment exchange, the same outbound-only polling, the same requirements and placement rules.
| Same as Docker | Different |
|---|---|
| The deployment token and enrolment flow | Packaging: a Windows installer rather than an image |
| The sensor's configuration settings | Where configuration and data live on disk |
| Outbound-only communication with the console | Service lifecycle: a Windows service, with a service account behind it |
| What integrations it can run, once placed | Capture and raw-socket prerequisites, which differ from Linux |
Document the installer, the service account and privileges it requires, the on-disk paths for configuration and data, how the deployment token is supplied at install time, and any additional prerequisites for active scanning and passive capture from a Windows host.
See also
- Upgrade a sensor on Windows
- Install a sensor on Linux (Docker) — the supported path today
- Sensors — what a sensor does, requirements and placement