Shortcut Menu

Skip

Main Navigation

Choose your language

You are here:

ActiveXperts.com > Administration > Scripts > WMI > VBScript > Win32_PingStatus

ActiveXperts Network Monitor ships with a large collection of WMI based PowerShell scripts and VBScript scripts to monitor and manage a network.

Use ActiveXperts Netork Monitor to monitor your virtualization servers, domains, computers and devices. It runs on a single Windows server, without agents required on the monitored systems. It has many built-in checks and also allows administrators to create custom checks using PowerShell, VBScript, WMI and SSH.


Win32_PingStatus - WMI sample in VBScript

The foundations for Manageability in Windows 7/2008/Vista/XP/2000 and Millennium Edition/'98 are Windows Management Instrumentation (WMI; formerly WBEM) and WMI extensions for Windows Driver Model (WDM).

ActiveXperts Network Monitor provides the ability to build monitor check routines based on WMI. ActiveXperts has collected more than a hundred WMI samples. You can use these samples as a base for new check routines you can write yourself.

On this site, you can find many WMI samples.

The Win32_PingStatus WMI class can be used in ActiveXperts Network Monitor to monitor your servers.


Win32_PingStatus

Description

ActiveXperts Network Monitor ships with a large collection of WMI based PowerShell scripts and VBScript scripts to monitor and manage a network.

Use ActiveXperts Netork Monitor to monitor your virtualization servers, domains, computers and devices. It runs on a single Windows server, without agents required on the monitored systems. It has many built-in checks and also allows administrators to create custom checks using PowerShell, VBScript, WMI and SSH.

Example(s)

On Error Resume Next
strComputer = "."
Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\cimv2")
Set colItems = objWMIService.ExecQuery("Select * from Win32_PingStatus",,48)
For Each objItem in colItems
    Wscript.Echo "Address: " & objItem.Address
    Wscript.Echo "BufferSize: " & objItem.BufferSize
    Wscript.Echo "NoFragmentation: " & objItem.NoFragmentation
    Wscript.Echo "PrimaryAddressResolutionStatus: " & objItem.PrimaryAddressResolutionStatus
    Wscript.Echo "ProtocolAddress: " & objItem.ProtocolAddress
    Wscript.Echo "ProtocolAddressResolved: " & objItem.ProtocolAddressResolved
    Wscript.Echo "RecordRoute: " & objItem.RecordRoute
    Wscript.Echo "ReplyInconsistency: " & objItem.ReplyInconsistency
    Wscript.Echo "ReplySize: " & objItem.ReplySize
    Wscript.Echo "ResolveAddressNames: " & objItem.ResolveAddressNames
    Wscript.Echo "ResponseTime: " & objItem.ResponseTime
    Wscript.Echo "ResponseTimeToLive: " & objItem.ResponseTimeToLive
    Wscript.Echo "RouteRecord: " & objItem.RouteRecord
    Wscript.Echo "RouteRecordResolved: " & objItem.RouteRecordResolved
    Wscript.Echo "SourceRoute: " & objItem.SourceRoute
    Wscript.Echo "SourceRouteType: " & objItem.SourceRouteType
    Wscript.Echo "StatusCode: " & objItem.StatusCode
    Wscript.Echo "Timeout: " & objItem.Timeout
    Wscript.Echo "TimeStampRecord: " & objItem.TimeStampRecord
    Wscript.Echo "TimeStampRecordAddress: " & objItem.TimeStampRecordAddress
    Wscript.Echo "TimeStampRecordAddressResolved: " & objItem.TimeStampRecordAddressResolved
    Wscript.Echo "TimestampRoute: " & objItem.TimestampRoute
    Wscript.Echo "TimeToLive: " & objItem.TimeToLive
    Wscript.Echo "TypeofService: " & objItem.TypeofService
Next