mrxinu

It might be time for some pizza and a late-night maintenance window. Are you database savvy by chance? You could poke around in the alert definitions table and see if there is extra stuff in there that shouldn't be there.

Tricky. What about this? * Run a PowerShell script via scheduled task daily at the desired time. * Have your PowerShell script update a node custom property (i.e., PowerShellTaskResults). * Have your SAM PowerShell component examine the custom property for this node every 30 minutes. That way you'll be able to get your…

Hey , could you post a snippet of the code you're having problems with? It's possible the method is supported but you're trying to access it from the wrong object.

After seeing your alert definition, there's definitely something afoot. Try re-running the configuration wizard, rerunning your tests, and if that doesn't sort it out, open a ticket.

I agree completely with jamison.jennings​ on the fresh database. You could delete all the nodes which would take the interfaces with it but it wouldn't truly be a clean slate if you're concerned about cruft hanging around from previous upgrades. If you just want an empty inventory though, that'll do the trick. -- Steven W.…

Not sure how I did it, but your solution worked. I reran SP4 when done just in case. Thank you, my friend! Debbi My pleasure! Thanks for coming back and verifying the solution worked. =)

You had the right idea - master/slave replication is what I needed to know. So you're using 'show master status', 'show slave status', and the like to determine its health, right? I'd write a small script that does the following: * Connect to the master database. * Run the 'show' commands. * Determine its health based on…

I assume your Support_EndDate custom property will only have a date if the node has a support end date? If so, the WHERE clause in the query won't return those nodes and the containing group won't trigger an alert.

Done!

In that case, change the user that runs the Alerting Engine to a user with privilege to restart the service and then use 'Execute an external VB script' to restart the service. That way you don't have to rely on the ${ComponentID} or the state of the service. So, in order: * Change the running user of the Alerting Engine…

Can you show us the latest revision of your code?

Yeah, every time I'm onsite with a customer - though usually we're looking for things to go down, not up. If you're around, shoot me an email and we can fire up a gotomeeting or something tonight. sklassen at sigmasolinc dot com

Boom, I wouldn't have thought of those reasons.

Oh wow, I stand corrected. It looks like we're both correct! There's a new predicate for the WHERE clause called CONTAINS that's available in SQL Server 2014 and later: The important bit is probably the warning at the top of the blog post you linked above: Before we begin, you have to understand that the CONTAINS SQL…

So we were close - the filter was: VolumeType = 'Fixed Disk' AND Volumes.Caption LIKE 'C:\%' AND VolumeSpaceAvailable < 2147483648. We had to prepend the 'caption' with the table name to avoid ambiguity with the nodes table.

Leave it to me to miss the fact that the library costs hundreds of dollars. Let's see what we can do with calling out to the TFTP binary. I've set up a server locally to play with; be right back.

Hi Ben, I'll give it some thought and get back to you tomorrow afternoon (today is pretty well packed). It's definitely doable with some PowerShell.

Huh, odd. Do you have time for a gotomeeting session in about a half hour?

Dove-tailing with Andy's reply - you could create a group of the devices that are connected to that particular switch and use that to make the report more targeted.

Hey Casper, no worries - it's my pleasure. Here are the two scripts in Powershell. You'll have to fix the path and remove the -WhatIf option from the Remove-Item cmdlet in order to actually go through with the deletion in both scripts. Let me know if you run into any problems or if I missed something. Edit: I was missing…

I used a Disconnect cmdlet where I could find one, but I see what you mean. Now that I'm reading this article it looks like maybe there could be a cleanup step added at the end to clean things up even without a Disconnect equivalent.

What query produced what you've got there? -- Steven W. Klassen Programmer Analyst @ Loop1 Systems http://www.loop1systems.com/ http://www.linkedin.com/in/mrxinu

We still need to work out the thresholds, but here we go. It works against all drives on the system. It assumes they're local systems at the moment, so we'd have to tweak it to hit remote systems. Let me know about the questions above and we'll get it nailed down. # # program: find-and-check-logdir-size.ps1 # # max…

Okay, let me hack up something that will get the sizes of those directories (wherever they may be hiding) and then we can figure out how to handle the thresholds. There's an option in SAM that will let you treat statistics as differences, but that would only tell you if the consumption went up very quickly, not that it had…

Psst, whatcha talkin' about?

Ah, fair enough. Then we're back to the situation I ran into - no matter what worked from the command line, it didn't work from the alerting engine. I also tried having the alerting engine run under a user I knew would have no problems running psexec locally. No dice.

Here you go... -- Steven W. Klassen Programmer Analyst @ Loop1 Systems http://www.loop1systems.com/ http://www.linkedin.com/in/mrxinu

It looks like maybe that's a typo in the manual - the variable should be ${Interface.Caption} or ${Caption} (if you're using an Interface alert). I always prefer to use the former so that my meaning is explicit. Try the insert variable button at the bottom and look through the variables for the interface. If you're looking…

Ah well, I don't know about all that; I like the new layout of the board. But it looks like you're trying to get the answer with your own thread and maybe tacking on to a couple others (below). Let's stick to your thread. http://thwack.solarwinds.com/thread/40657 http://thwack.solarwinds.com/thread/35298

Hi Ade, The lines you quoted that set the hostname, username, and password need to be updated with your information. Once you've done that, the line you mentioned that sets the client.BaseAddress needs no further modification - it uses the hostname value you specified at the top of the file. The methods in the class are a…