DumbMonit

IntegrationsServers and machines

Windows (WinRM, no agent)

A Windows server or PC without installing anything, through WinRM and WMI queries: CPU, memory, disks, services (the chosen ones and every automatic service that is stopped), uptime and recent event log errors.

Documentation

Product descriptions are in English, as in the product. The page labels follow your language.

What DumbMonit watches

A Windows server or PC monitored without installing anything, through WinRM (WS-Management) and read-only WMI queries: CPU, memory, disks, services (the chosen ones and every automatic service that is stopped), uptime and recent event log errors. DumbMonit only sends fixed SELECT queries (WQL Enumerate). It never runs a command or a script on the server, and it can go through a relay agent to reach a network the server cannot.

Typical use. Windows server without an agent: CPU, memory, disks, services (including stopped automatic ones), uptime, event log errors

Examples

  • Windows Server 2019
  • Windows Server 2022
  • Windows 11 workstation

How it connects

What you need

  • Windows accountA local or domain account in the Remote Management Users group, as dumbmonit, DOMAIN\dumbmonit or dumbmonit@domain.

Network ports to open

  • 5986/TCPWinRM over HTTPS (default)
  • 5985/TCPOnly with the Allow unencrypted traffic option
Setup steps: Give DumbMonit a WinRM account on the Windows server
  1. On the server, in an elevated PowerShell, enable WinRM.

    Enable-PSRemoting -SkipNetworkProfileCheck -Force
  2. Create the HTTPS listener with a certificate named after the server (use your own certificate instead of this self-signed one if you have one), then open its port.

    $cert = New-SelfSignedCertificate -DnsName "srv01.corp.example.com" -CertStoreLocation Cert:\LocalMachine\My
    New-Item -Path WSMan:\LocalHost\Listener -Transport HTTPS -Address * -CertificateThumbPrint $cert.Thumbprint -Force
    New-NetFirewallRule -DisplayName "WinRM HTTPS" -Direction Inbound -Protocol TCP -LocalPort 5986 -Action Allow
  3. Create the account with a long random password, then add it to the groups listed below.

    net user dumbmonit * /add
    net localgroup "Remote Management Users" dumbmonit /add
    net localgroup "Performance Monitor Users" dumbmonit /add
    net localgroup "Event Log Readers" dumbmonit /add
  4. Give the account access to the WMI namespace: wmimgmt.msc → right-click WMI Control → Properties → Security → Root → CIMV2 → Security, add it and tick Enable Account and Remote Enable.

  5. In DumbMonit, enter the server name as its certificate names it (srv01.corp.example.com) and log in as dumbmonit, or DOMAIN\dumbmonit for a domain account.

Heads-up. The account runs no command on the server, it only reads WMI. NTLM and Basic (HTTPS only) are supported, Kerberos is not. Pending Windows updates cannot be read this way. A self-signed certificate needs the option Accept an unverifiable certificate.