Atamido

It appears the page for KB2734608 has been pulled. I think I'll hold off for a couple of days in case they need to update the package.

Is there any intention to update this list? I just got an email that new FoE 6.7.0 supports Server 2012 and I'm curious about the other couple of products that we use that don't list support yet. Does SAM 5.5 officially support it? Will UDT 3.0 support it?

Has this been resolved yet in NPM 11.5.0 so that you can poll node properties via the 64-bit process, or is FB275825 still an open issue?

We have a relatively large installation with ~30 different alerts that text people's phones. Creating a report for each of those would be cumbersome and it wouldn't allow one to acknowledge other alerts at the same time (such as if 10 devices alerted at once) by just hitting Select All and Acknowledge. On the topic of…

Be aware that if running the script in the above KB article, you are likely to encounter an error due to a malformed performance counter definition file. I encountered it a year ago and MS still hasn't fixed it. You can edit the file to get it to import correctly. Details on one of the bottom posts here.

In case anyone else is wondering, when trying to change the primary poller to another server, it adds an additional entry to the "engines" table in the database, resulting in two entries marked as "primary". This causes a number of random issues as services see the original primary poller first and try to talk to it. Even…

I may not have been clear. The linked template also has you to specify an NTP server as the source of comparison. The difference is that it doesn't require the remote management be configured on the Windows server. 

I managed to work around this problem by reworking how I solved the problem. It's not nearly as efficient, and there still couldn't be a WHERE in the upper section, but it does work with account limitations. WITH LastResponse (NodeId, MaxDate, PercentLoss) AS ( SELECT ResponseTime.NodeID, MAX(DateTime) MaxDate,…

I can confirm that if I remove the WHERE from within the SELECT that is inside of the JOIN, then it stops throwing the error. It appears that Solarwinds chokes on a WHERE statement inside of the select statement. I also tried inverting the statement so that the Nodes table was selected on the inner SELECT, and the…

If I receive an email for "Alert me when a node goes down", then I'd like to click a link and see how many alerts are active for "Alert me when a node goes down". Right now, all I can do is go to http://servername/Orion/NetPerfMon/Alerts.aspx and hit the Alert Name drop down box, scroll through and find the right alert,…

Is it possible to configure advanced alerts to run on an additional poller? I would be interested in this to that if our core engine experiences a problem, then we will still be able to send out alerts on the nodes that are still being polled.

Right, but if I could just specify a host name instead of an IP address, then I could completely avoid this nonsense.

I'm in a similar boat. I created a report to show the most recently downed nodes. But if there are any limitations applied (either to the account or the page) then I get the above error. The only thing that I'm doing differently than I've done in the past is having another SELECT statement inside of a JOIN. SELECT TOP 10…

Here is the report that I made that tells me when I last saw the nodes that are down. It queries the ResponseTime table for the response times, and then gets the periods that had less than 100% packet loss, and returns that. You might be able to get all of the PercentLoss with associated DateTime for a given node in a give…

I created a report once that polled the database table that stores the response time for pings, to create a list of the nodes that most recently went down, and when they last responded. I don't have it in front of me at the moment, but you could do something similar if it were really essential. It would be quite a bit more…

I reworked the SQL statement to consolidate all of the logic to one area, and fixed some bugs as well as increasing the accuracy. The reported uptime now takes into account the time that the node was polled for uptime, so you will see the numbers increment each time you refresh the page. It will work just fine without any…

I created a partial workaround for creating a report that can be displayed in Orion, here:

I created a partial workaround for creating a report that can be displayed in Orion, here:

If you just want the skew, and it's a Windows server, I made this template which will run the PowerShell locally on the poller and get the time from an NTP server and WMI query against the remote Windows server. It then provide the time difference in seconds.