Comments
-
Just to answer my question in this thread for others. SolarWinds Support told me that the old Nodes table is now referenced as a view - so these old custom sql alerts continue to work. I was confused because all my alerts were migrated successfully, but when I looked at them they all looked the same. I was expecting the…
-
One more question to better understand this ... I ran the upgrade on a development server and my custom SQL query alerts migrated successfully. But when I looked at them, expecting the table names to be different, they were unchanged. And looking at the SELECT statement - I checked and there is no longer a Nodes table. How…
-
Thank you for the confirmation, alterego.
-
actually it looks like the hotfix name has changed.to SolarWinds Orion Platform 2015.1.3 Hotfix 1
-
I am posting because I still see this marked as Not Answered ( I know I looked here before ) Quick and Dirty - There are 2 parts required: (WMI uses DCOM and RPC to communicate) On DMZ server - configure WMI to communicate only over port 24158. Now just 2 ports are required to be opened on the firewall, port 135 (RPC) and…
-
Running SAM 6.1.1 I am having the same problem with 2 VMware ESXi (5.5) Hosts I know its not a router, but the behavior is identical. and we have many ESXi's monitored successfully, including CPU and Memory. No CPU or Memory monitored. List resources and CPU /Memory box is unchecked. Check the box and submit. Still no CPU…
-
I am sharing what works for us to allow WMI monitoring on servers residing in the DMZ without having to configure any/any in the firewall rule to get it working. Quick and Dirty - There are 2 parts required: On DMZ server - configure WMI to communicate only over port 24158. Now just 2 ports are required to be opened on the…