Re: Multiple WMI Connections

Hi,

I've run a similar system too, but I wrote my own ping provider because we use Win2k. You are talking "synchronous" here as opposed to "async", that's fine, mine is synchronous too.

I wrote a WMI script to connect to iterate through a list of 2,000
workstations and:

1. ping each one using win32_pingstatus
2. if online connect with WMI with an array of passwords
3. get the version of a specific file and write it to a CSV file

OK, this is pretty easy. I do this all the time to test for patch compliance.

What I discovered was that even with the initial PING the list took too
long to process.

Define too long? I don't understand the problem here. Did you test it carefully to find out which part was taking "too long".

As a possible solution I took the list of 2000 and broke it down into 4
lists of 500.

Yes, I do that sometimes, but not if I just want a file version.

The report generated showed the incorrect results and I am concerned I
am missing something.

Define "incorrect".

What needs to be changed in a script if multiple instances are running?

But you said you "iterate" them, so there are not multiple instances?? Iterate means you are connecting to each one and then disconnecting, then releasing handles to objects, then moving to the next one?

Would the variables each script creates need to be uniquely named?

Don't understand, surely there's only one script here?? The whole point of WMI is that the calling script is remoting to each machine - that the beauty of it.

If you're using async it's a whole different ball game. None of the above applies.

--
Gerry Hickman (London UK)
.

Loading