sotasolutions

There have been lots of "Did he really just say that" moments in my IT career, but my favourite one is still an elderly, retired ex local authority representative phoning for support for a problem with MS Word. After describing the problem I asked her to click Tools and Options. Her: "Click? How do I do that?" Me: "Move…

It's now working. A combination of getting WinRM correctly configured on the target machine, credential impersonation on the monitor and also ensuring the script was looking at the services "Status" rather than its "State". Under Get-Service, it's running status is "Status". If you use Get-WMIobject win32_service, it's…

Ok.. that's all fine 'n' dandy, but how do these codes affect miscalculation of the lines in the script? I can see that the If Then Else command is defaulting to the "Else" situation, giving both variables a value of 1, because the string of the status is something other than "Stopped" (presumably due to WinRM shenanigans…

The credential we use for monitoring is attached to the service account which is a Domain Administrator. I did try the "specify account" setting, but I got the same result. I did find through Google'age that the access denied error being shown in the logs is due to a WinRM issue, so how would I go about utilising WinRM in…

Thanks. Platform is definitely set to x64 for PS. Will look at using a SAM agent.

No. There is no exit code on any of our other PS scripts, and they work fine. Oddly, when we were looking at creating monitors via PowerShell initially, obviously the requirement was there to include the exit, but they only seemed to work properly when we removed it.

Ok.. things are starting to come together now. I'm getting "Get-Service : Cannot open Service Control Manager on computer 'Server1'. This operation might require other privileges."

I had tried that initially, but couldn't find the logs. Now I've found them, there are some logs that are showing "Access is Denied" errors when I was trying using "get-wmiobject win32_service" instead of get-service (although obviously the syntax is slightly different). Don't see any for the "get-service" version though.…

Thanks for the suggestion Ray. When I posted this query, I figured that as there didn't appear to be a way to do this natively, I'd have to revert to a UDP. You're right that the Watchguard OIDs appear to have a fair number of pollers regarding BoVPNs in terms of the traffic going over them and static info like the remote…

Thanks..I tried that, and it made no difference at all.. I haven't even got as far as reporting whether or not the status is up or not - just clicking "Get Script Output" gives me an incorrect answer. In addition, I have written a couple of other scripts without that final line and had no problems?

Managed to fix it. All I did was set the polling IP of the switch to the interconnect IP rather than the management IP, and then did a "List Resources" in the node management screen. All reporting back properly now!

Solved: Problem was I wasn't running the Advanced Alert Manager as Administrator (despite logging in with a domain admin account) and as such a whole slew of Trigger Conditions weren't showing, and now are. Don't you just hate those "wood / trees" situations?

After some jiggery pokery, and fiddling around with different things, it looks as if the problem is the fact that for whatever reason, Powershell is not recognising the text of $stat1 and $stat2 and reverting to what ever is set in the "Else" section of the If function. I tried reversing the logic, so that it checks to see…