tfoster2501

It's strange. Shortly after I ran the WMI test, the application monitors that utilize WMI began to work, and I was seeing data. But when I checked this morning, they are in unknown status with the 'Server Unavailable' error once more.

I performed the WMI test, and got results back as the test indicates I should.

That was indeed the issue I was having. Thank you very much for your assistance!

I get the following error: Server unavailable using WMI. Unable to connect to <IP Address> for WMI access. Unable to connect to server <IP Address> as user <Domain\MonitorAccount>.

So if I understand this correctly, because the property I would want to alert on is two levels down from Group (Node->monitorproperty), the Advanced Alert logic doesn't support it? If that is the case, then let me ask, is there a way to set up the logic so that I can alert on a node property (application status) for a…

Is the value for the alert, memory used, is that in kilobytes/megabytes?

So if I understand correctly, it will monitor the server without issue, but it will add those audit entries to the security log?

No, I do have Node Management, and all my servers are being managed with SNMP/WMI. But that one feature is missing. This is what mine looks like: So I need to get it added in to Node Management somehow.

That worked. I was able to MMC, Add Snap-In, select Computer Management, specify the name of the server I want to monitor, and have Computer Management successfully load for the target server.

I'm attempting to add the node. I could ostensibly add the node - I'm using SNMP, and the other monitors come back just fine. It's any service-based monitors I'm trying to add.

This would be the SQL Server Monitor. I assigned the account to the device during creation, and I want to add monitors to it that will need the credentials.