Windows WMI setup
Agentless Windows monitoring using a Domain Admin monitoring account.
The monitoring account must be a Domain Admin account. The only Windows configuration required is to allow remote WMI from the Watchnode.
What this provides
| Monitoring area | Capability | Status |
|---|---|---|
| Server health | CPU, memory, disk space, network traffic and uptime through WMI | Included |
| Windows services | Monitor whether selected Windows services are running or stopped | Included |
| Windows event logs | Read available Application, System and Security event logs | Included |
| Active Directory | Directory, DNS, LDAP and replication health on domain controllers | Included |
| Windows Firewall | Allow remote WMI/DCOM from the approved monitoring source | Required |
Required configuration
Configure the Windows Firewall through a computer-targeted Group Policy Object (GPO) for the servers being monitored.
Note
- If the Windows Domain Firewall profile is disabled on the monitored servers, you can skip the Windows Firewall configuration in this section. The required WMI/DCOM traffic must still be permitted by any network firewall or other security controls between the monitoring system and the servers.
- Apply these firewall settings centrally through Group Policy. There is no need to configure each server individually.
- In Group Policy Management, create or edit the computer-targeted GPO used for the monitored servers.
- Go to Computer Configuration → Policies → Windows Settings → Security Settings → Windows Defender Firewall with Advanced Security → Inbound Rules.
- Enable the predefined Windows Management Instrumentation (WMI) inbound rules required for remote WMI/DCOM access, including WMI-In and DCOM-In.
- If availability is checked with ping, enable the File and Printer Sharing rule for Echo Request - ICMPv4-In.
- For each monitoring rule, open Scope → Remote IP address and restrict access to the approved monitoring server or monitoring network.
Windows service monitoring
Service monitoring is available with the administrative credential and can be used to report whether selected Windows services are running or stopped. No additional Service Control Manager permission configuration is required for this setup.
Windows event-log monitoring
You can monitor Windows event logs using the administrative credential. If you need Windows to generate specific audited security events, configure the required audit policies using the separate Windows Event logs by WMI guide.
Validation
- The firewall GPO has been applied to the in-scope servers.
- Remote WMI connectivity succeeds from the approved monitoring source.
- CPU, memory, disk, network, and uptime data can be queried.
- Windows service status can be queried when service monitoring is required.
- Windows event logs can be read when event-log monitoring is required.
Related links
For assistance, please contact the Netwatch support team.