Hi guys

I have put together a script that will take use QAD-Computer to retrieve a list of server that are in AD and then ping them.  This works well and the error that I recieve if the server isn't pingable is fine. After pinging the list of servers I query them for using WMI.  Although this works I would like to know if there is a nice way to tidy up the WMI error messaes for servers that don't respond to WMI.  Ideally I would like to have a similar (but not the same) error as to the ping failure for WMI failures.  Also is there a way to make the WMI timeouts any quicker?

Here's my script.

# This script looks for all servers in AD, pings them and then queries the responding servers.
cls
#This function gets the WMI info
function Get-Info{
gwmi win32_operatingsystem -comp $_.name | select CSName,SerialNumber
trap {
write-Warning "RPC is not responding on $computer"
continue}
}
#This queries AD for Servers
$AD_Servers = get-qadcomputer -osname '*server*' -sizelimit 0

#This function pings each server in AD
function Ping-Host {
Begin { $Ping = new-object System.Net.NetworkInformation.Ping }
Process {
$computer = $_.name
trap {
write-warning "$computer is not pingable"
continue}
if ($Ping.Send($_.name)) { Get-Info }
}}

$AD_Servers | Ping-Host


Thanks for any advice.

Regards

Lee

Nice script.

For cleaning up the WMI errors one way would be to use the -ErrorAction parameter which almost all cmdlets support. For example

gwmi win32_operatingsystem -comp $_.name -ErrorAction SilentlyContinue| select CSName,SerialNumber

That should remove any error messages you see from your output.

As for WMI timeouts check this article I found: http://blog.usepowershell.com/2009/...-timeouts/

Seems pretty decent, makes use of the returnimmediately flag, I haven't used it with powershell but I have with vbscript. Cheers.

Also, your trap statement should come before the gwmi line if you want trap to catch any terminating errors created by that statement.

Ayth is right, as far as I remember RPC errors are not trapable, they are not terminating errors so the TRAP block won't invoke.
You should also follow tojo's suggestion, put all code after the trap call (in case the error is terminating error)