One agent, nothing new to install
- Run by the agent on the server. Active Directory, Exchange, SQL Server, Storage / iSCSI, Failover Cluster, DHCP and IIS are read by the daily check that every Windows computer runs once a day, at its own time, through the existing command queue. It only reads — WMI, the registry, the event logs, SELECT queries on SQL Server, Get and Test cmdlets on Exchange — and changes nothing.
- Servers found by themselves. The check recognises a domain controller, an Exchange server, a SQL Server instance, a storage server, a cluster node, a DHCP server or an IIS server on its own. Each computer has a monitoring setting per module — Automatic detection, Always monitor or Never monitor — and + Mark adds a server the detection missed.
- Check now, then Ask the AI. Check now runs a server's check again after a fix, at most once every 5 minutes per computer; an offline computer is checked as soon as it is back. On Active Directory (per domain), Exchange, SQL Server, Storage / iSCSI, Failover Cluster, DHCP and IIS, Ask the AI sends the AI assistant what the last check found, with the open alerts, and asks for the cause and the fix — read-only commands first, nothing changed without your confirmation.
- History and the client report. Each server keeps the history of its last checks, and the client report has a section for each module: Active Directory, Exchange, SQL Server, Storage and iSCSI, Failover clusters, DHCP, IIS and Hyper-V.
Infrastructure overview
- Everything on one page. Infrastructure → Overview, also opened by clicking the Infrastructure group in the sidebar, starts with four totals: Critical alerts, Warnings, Modules OK and Modules with problems.
- A card per module — Hyper-V, Active Directory, Exchange, SQL Server, Storage / iSCSI, Failover Cluster, DHCP, IIS, Backups, Third-party backups, Syslog, Network configs, Printers and Lifecycle — each with what it watches, a health bar (OK, Warning, Error, Unknown), its open alerts, two figures that matter for it, such as DCs failing or Fullest scope (%), the last check and its top three problems. Click a card or a problem to open the module.
- Most urgent open alerts — the ten most urgent open infrastructure alerts, critical first, with the module, the client and the computer.
- It only reads. Opening or refreshing the page never asks an agent anything, and it refreshes itself every 2 minutes while you look at it. Modules your plan does not include are shown dimmed.
Hyper-V
- Hosts managed from the browser. Add any Windows computer with the agent as a Hyper-V host: its virtual machines, virtual switches and Hyper-V settings are read and changed by the agent on the host itself, as the system account — no remote management port to open, no host password stored.
- Virtual machines, end to end. State, CPU, memory, disks, IP addresses, checkpoints and replication health of each VM; start, shut down, restart, save, pause or turn it off; create a VM, change its processors, memory, disks, network adapters and DVD, take and apply checkpoints, move or live-migrate it, export and import it.
- Hyper-V Replica. Enable replication to another host from the VM's Replication tab, then suspend, resume or resynchronize it, run a test failover, fail over and reverse the replication.
- Replication alerts. A virtual machine whose replication health is Critical or Warning raises an alert of the same severity — one per virtual machine, even when its primary, its replica and the nodes of its cluster are all in the module. Only hosts that are online and were read recently count: an offline host never opens or closes anything. The alert closes by itself when the replication is healthy again or removed; when several open at once, each administrator gets one summary email.
- Kept current on its own. Every online host sends a new inventory every half hour without anyone opening it; these automatic inventories stay out of the Operations tab and are deleted after 3 days.
- Changes are for administrators. Technicians with the module see the hosts, the virtual machines and the history; only administrators change anything, and every change is written to the audit log.
Active Directory
- Every domain controller, every day — dcdiag, replication, the AD services, SYSVOL and NETLOGON, the clock against the PDC emulator, the FSMO roles, account hygiene and the members of the privileged groups. The details are on Active Directory & third-party backups.
- Alerts — dcdiag failures, replication failing for more than 24 hours, a stopped AD service, a clock more than 5 minutes off, SYSVOL or NETLOGON not shared, and a new member of a privileged group.
Exchange
- On-premises Exchange 2013, 2016, 2019 and Subscription Edition — version and build, services, mailbox databases and their DAG copies, transport queues, certificates and the IIS bindings on ports 443 and 444, server components (maintenance mode), disk space and health sets.
- Alerts — a service stopped, a database dismounted or a copy failed, queues building up (warning from 100 messages, critical from 500), a certificate expiring within 30 days, a missing IIS certificate, an inactive component, low disk space and a check failing three times in a row.
SQL Server
- Every instance, SQL Server 2008 to 2025 — up to 16 per computer, read with Windows authentication as the computer's SYSTEM account and SELECT queries only: services, version and end of support, databases, transaction log use, the last full, differential and log backups, SQL Server Agent jobs, the volumes of the database files and, on Express, the 10 GB limit.
- Missing read access, explained. When the SYSTEM account may not read something, the server window shows the T-SQL script that grants the read access; SLApp never runs it and never changes permissions.
- Alerts — a service stopped, a database not online, a transaction log more than 90% used, no full backup in 7 days, no log backup in 24 hours, a failed SQL Server Agent job, low disk space, an Express database near its limit and a check failing.
Storage / iSCSI
- SAN and server storage, through WMI only — iSCSI sessions and targets, disks, Multipath I/O (MPIO) paths, Storage Spaces pools with their virtual and physical disks, and the free space of the storage volumes and Cluster Shared Volumes. SLApp never brings a disk online, reconnects a session or changes MPIO.
- Alerts — an iSCSI target not connected, a disk offline, read-only or unhealthy, an MPIO path lost, a pool or a virtual disk degraded, a physical disk failing and low space on a storage volume.
Failover Cluster
- The whole cluster, from its nodes — the quorum and its witness, the nodes, roles, resources, Cluster Shared Volumes and cluster networks. Read-only: SLApp never moves a role, drains a node or changes the quorum.
- Alerts raised once per cluster — a node down or paused, a role failed or offline, a resource or a CSV failed, low space on a CSV, a cluster network down and a witness problem; a stopped Cluster Service is raised per node.
DHCP
- Windows DHCP servers — the DHCP Server service, the server's authorization in Active Directory, the use of every IPv4 scope, the IPv6 scopes, the failover relationships and the server statistics.
- Alerts — the service stopped, the server not authorized, a scope 85% full (critical from 95%), and a failover relationship that is not Normal, raised once per relationship.
IIS
- Every IIS web server — the W3SVC and WAS services, every site with its bindings and applications, the application pools, the HTTPS certificates and the HTTP 5xx errors of the last 24 hours.
- Alerts — a service, site or application pool stopped, an HTTPS binding without a certificate, a certificate expiring or not covering the site's name, and a site returning too many server errors.
Alerts under your control
- Where you already look. Infrastructure alerts appear in Alerts, on the Dashboard, in the client's Alerts tab, in the footer ticker and on the Overview, and become a ticket in one click. Most close by themselves once the problem is fixed; only an administrator can close one by hand.
- Generate alerts, module by module. An administrator can turn a module's alerts off with the Generate alerts checkbox at the top of its page — next to the list of hosts for Hyper-V — or all together in Settings → General → Alerts. Its open alerts are resolved at once and nothing new opens or is emailed, while the page keeps showing the state of every server, with the checkbox in orange so a quiet page is not taken for a healthy one. Ticked again, the alerts return at the next check, and those that were open come back without a second email. For Hyper-V it also stops the half-hourly inventories.
- Emails for the people who look after the module. An alert is emailed to your administrators when it opens, and again when a Warning becomes Critical. A technician who turned on Critical alerts in My profile also gets the critical ones — but only for the modules they have access to, or with the Alerts module: someone who only looks after websites gets no Hyper-V, SQL Server or Active Directory email.
- No flood on day one. The first check of a newly monitored server opens its warnings without an email; on IIS and Hyper-V the first look sends no email at all.
How it works
- 01
Nothing to set up
The daily check starts by itself on every Windows computer with the agent and finds the servers; add your Hyper-V hosts with + Add Hyper-V host.
- 02
Start from the Overview
Infrastructure → Overview shows which modules need attention; click a card to open the module and its servers.
- 03
Fix and check again
Open a server, fix what it shows — or Ask the AI first — then press Check now.
- 04
Choose who hears about it
Leave Generate alerts on for what you look after, and give each group of technicians the modules it works on: their alert emails follow.
What it needs
- The agent on the servers — nothing new to install. The daily check needs Windows PowerShell 3.0 or later (Windows Server 2012 and later); the Exchange part needs 64-bit PowerShell.
- The Complete plan: on Essential these modules, and their sections of the client report, are not available.
- It is a daily check, not live monitoring: a problem shows up at the next daily check or after Check now. Hyper-V hosts are read every half hour.
- Technicians with a module mark servers, change how a computer is monitored and run a check; closing an alert by hand, turning a module's alerts off and every change in Hyper-V are for administrators.
Infrastructure
Hyper-V, Active Directory, Exchange, SQL Server, storage, failover clusters, DHCP and IIS of every client on one overview — with alerts you switch on or off per module.