Surfaces servers short on disk, long overdue for a reboot or running with stopped critical services, plus domain controllers, SQL Server instances and the cloud versus on-prem split.
The Server Health Monitor skill uses Lansweeper inventory data joined to Windows service data to assess the server fleet. It reports uptime, disk pressure, domain controllers, SQL Server inventory by version, cloud versus on-prem distribution and auto-start services that are not running. It is also the entry point for cloud-estate questions across Azure, AWS and GCP, and gives infrastructure teams a triage list before problems turn into incidents.
Why the Server Health Monitor Matters Here
IT perspective
“Which servers need attention before they cause an incident?”
Low-disk and long-uptime servers become an ordered triage list.
Stopped auto-start services are named per server so they can be restarted.
Security perspective
“Which critical servers are unhealthy or unaccounted for?”
Domain controllers and SQL Server instances are listed with their state, so none go unwatched.
The cloud versus on-prem split shows where the server estate actually lives.
Beta
Lens Workbench
Ask your asset data a question. Get a straight answer.
Lens Workbench is a dedicated space where you can ask questions about your asset data and get straight answers, build live reports that stay current, connect your existing tools through MCP connectors, and take action directly, like adding or retiring an asset.