Comments
-
You can create a Powershell script to run an SNMP query against the server OID, or poll WMI. Then compare the returned results to the drives monitored. You can even add them via the script if you decide to do it.
-
This will get you close. You'll have to look up the Base64Encode. Set xmlHTTP = CreateObject("MSXML2.XMLHTTP") With xmlhttp .Open "post", URL, False, User, Password .setRequestHeader "Authorization", "Basic " & Base64Encode(User & ":" & Password) .setRequestHeader "content-type", "text/xml; charset=utf-8" .setRequestHeader…
-
Create a Powershell monitor with the code and test it; $a = $psversiontable.psversion Write-Host "Statistic: 100" Write-Host "Message: " $a Output Result: Message.Statistic:5.1.14393.3053 Statistic.Statistic:100 Of course that is the version on the server running the monitor. You have to upgrade to the latest version.
-
Open a Powershell command prompt and enter Add-PSSnapin Microsoft.Exchange.Management.PowerShell.E2010 That should give you a bit more of an error message.
-
Here's a snippet from the script I run, let me know if it helps; If ($NodeType -eq 'SNMP') { $applicationId = (Invoke-SwisVerb $swis "Orion.APM.Application" "CreateApplication" @( $NodeID, TEMPLATE ID, CREDENTIAL, "true" )).InnerText If ($NodeType -eq 'WMI') { $applicationId = (Invoke-SwisVerb $swis "Orion.APM.Application"…
-
I ran into an issue recently where doing this fixed it - change $args[1] to [int]$args[1] It may be trying to compare it to a string vs. an integer.
-
You might try using the write-eventlog cmdlet to help debug your Powershell code. I often write things into the WIndows event log with debug information in it
-
You can use the Powershell command get-scheduledtaskinfo to get the LastRunTime and the result of that. It also shows the next time it's supposed to run so you could do some comparison.
-
Try this one [Q] Batch Editing Custom Properties w/ Powershell
-
Using the Exchange Powershell snapin you can use the Get-Queue cmdlet.