Windows
banshee/windows-collection/windows/snmp/
users
The number of users logged on to a Windows, by SNMP
par banshee1 installation2 versions
Users logged on to a Windows, by SNMP
Returns the number of users logged on to a Windows. One watch is proposed, unchecked: what is normal depends on the server, a jump host or a server without sessions.
How it works
The collector reads hrSystemNumUsers (1.3.6.1.2.1.25.1.5.0, HOST-RESOURCES-MIB): the number of sessions open on the system, at the console as well as remote.
- Nothing is skipped at the first run.
Nothing is written to the Windows: SNMP reads only.
Prerequisites
- The SNMP service of Windows, installed and started: - on Windows Server, the feature "SNMP Service" (Server Manager, Add Roles and Features; or
Install-WindowsFeature SNMP-Servicein PowerShell); - on Windows 10 and 11, the optional feature "Simple Network Management Protocol (SNMP)" (Settings, Optional features; orAdd-WindowsCapability -Online -Name SNMP.Client~~~~0.0.1.0in PowerShell). - In the properties of the service "SNMP Service", tab Security: - a community with the right READ ONLY, which banshee reads in
protocol:snmp:v2c:community; - under "Accept SNMP packets from these hosts", the address of the poller. - SNMPv3: the SNMP agent of Windows does not offer it;
protocol:snmp:versionstaysv2c. The community then travels in clear text: keep it read-only and accepted from the poller alone. - The Windows firewall open to the poller on UDP 161 (the rule "SNMP Service (UDP In)").
Outputs
| Name | Label | Unit | Per instance |
|---|---|---|---|
users | Users logged on | — | no |
Watches
| Name | Title | Kind | Defaults | Checked by default |
|---|---|---|---|---|
too-many | Too many users logged on | above a threshold, on users | no threshold: to set on the probe | no |
Limits
- Only the number is served: neither the names of the users nor the kind of their sessions.
- Not yet checked on a real Windows: which sessions the agent counts, a disconnected remote session among them.