"Richard Mueller [MVP]" <rlmueller-nospam@xxxxxx> wrote in
> <nightstar@xxxxxx> wrote in message
>> This kind of helps, and what I am currently doing. But if I get to an
>> item, like a switch or printer (that does ping), I then try to connect
>> to that IP to retreive info (using WMI) because it pings and these
>> delay for a horrible amount of time. Is there a way around this,
>> without having to create a list of 900+ items that are scattered
>> throughout the network that do ping but are not WMI units.
> I don't know of a solution. The same thing happens if a computer does not
> have WMI installed, or does not support the WMI class I am using. There is
> no way to control the long timeout.
> However, you could use ADO to retrieve the NetBIOS names of all computers
> in the domain (or in one or more OU's). Then at least you would know that
> all devices are computers. The Inventory.vbs program I linked earlier
> actually does this. There are also ways to retrieve only DC's:
> or, only servers:
> For more on using ADO in VBScript programs see this link:
There is one method I know of that might be of help to the OP, but it might
be less convenient to use if the target domain systems must be identified by
their IP, subnet by subnet.
The command 'net view' will create a list of all computers in the domain
that are currently known to the browse master. This will include all
computer that have been operational and connected within the last 10 or 15
minutes (I think). This will include machines recently turned off, and will
exclude machines recently turned on. It will also exclude non-computer
devices occupying IP address space.
I find I get a very high hit rate out of this if I avoid times when machines
are more likely to be getting turned on or off, such as the end of shifts,
meal breaks, and etc. I don't even bother pinging each candidate to see if
it is still there, as that generates a second or two extra per system, which
can be significant in a large network.