Supported pilot scope
The Windows pilot targets Windows 11 x64. The native service and tray require no separate Python, Git or .NET installation. Selected Windows service monitoring begins with release 0.11.0; current downloads can include newer development releases. Disposable Windows Server tests provide lifecycle evidence; they do not establish support for every Windows Server version.
The installer is an unsigned development release. Authenticode signing, publisher reputation and broader platform acceptance remain production work. Do not turn off Windows security controls to work around an installation error.
Install and confirm
Installation is available only through your existing private deployment administrator. Public downloads and enrollment are closed.
- Open
/downloads/windows/on the configured application. - Use its current verified PowerShell installation command on the Windows device. Review the source and checksum before the administrator prompt.
- Add a Windows machine in the portal and open Fleet Monitor (the current installed app name) from Start.
- Choose Setup / enroll, approve the local administrator prompt and paste the one-time code into the hidden prompt.
- Confirm Connected, the installed version, a recent portal check-in and inventory. Allow a second sample for CPU.
The background service runs under a restricted service identity. The tray runs as the desktop user. Closing the status window or quitting the tray leaves monitoring running. A sleeping device cannot check in.
Local diagnostics
This command reads the Windows service status; it does not start or stop it:
Get-Service -Name FleetMonitorAgent
The service being Running does not prove a successful server response. Compare it with the companion's confirmed status and the portal's last received check-in. For startup errors, an administrator can inspect the application event log:
Get-WinEvent -FilterHashtable @{LogName='Application';ProviderName='FleetMonitorAgent'} -MaxEvents 10 | Select-Object TimeCreated,Message
Inspect locally and redact machine-specific information before sharing logs. A missing event provider can mean installation never completed.
Agent updates from the application
Development releases from 0.12.0 add a separate SYSTEM scheduled updater for agent-update requests from the signed-in application. The ordinary collector keeps its restricted account. Local helper setup and actual application-requested installation have recorded acceptance on the tested platform. Helper startup after reboot and broader lifecycle checks remain separate; this is lab evidence, not production readiness. See agent-update setup and progress.
Stopping the collector does not disable the separate updater. Use the local disable controls if that helper should not poll. It accepts only the configured server's agent-release requests; it does not install OS patches or run arbitrary scripts. Follow the current download page rather than treating an older documented capability version as the latest package.
Update and startup
Choose Check for updates → Update agent in the tray when a newer release is available. The protected updater rechecks the release, asks for administrator approval and preserves enrollment. Quit and reopen the tray afterward to load its updated interface. The monitoring service and per-user tray login preference are separate.
Initial installation, a real tray upgrade and reboot were accepted on the pilot device. Explicit icon-only quiet login remains an outstanding acceptance check. Application-requested agent updates have separately passed on the tested Windows 11 device.
Optional update scanner
If the restricted collector cannot query Windows Update, the report stays unavailable. A separate, off-by-default SYSTEM scheduled scanner can supply a read-only report. Enabling it is an explicit administrator action using the application's instructions. Service monitoring itself does not need this helper. The scanner does not install OS patches or reboot the device.
Upstream: Get-Service, Windows service access rights.
Remove or retire a device
Follow the platform-specific uninstall guide. Ordinary removal retains enrollment for reinstallation; revoke the device separately in the application when retiring it.