Question about WMI connection and concurrent use

Hi All,

[Even I posted this sometimes ago via "managed newsgroups" {I am universal
msdn abonnement and pay for support}, I could not get an answer or any
notifications. This is my third attempt. If my question is not to understand
- bear with me for my english - but I could give additional
information/explanations. On the other hand, I cannot image, that this is
really unclear and not to understand/to explain by the experts].

I'll use one wmi connection by several concurrently running threads to one
server. I've already made a lot of outgoing calls from different threads [I
am using the .Net framework],
but that's another scenario.
Only my management server is allowed to connect network devices via snmp. So
I'll use this server as a proxy to ask network devices. In this case, my
local workstation will open a wmi connection to the system management server
and advise it to contact box x1, box x2, and so on [useing additional
WBemObjectSet objects]. I know all this to handle, but:How many threads can
this handle, or do I need
multiple connections?? Are the calls internally serialized or handled by
multiple threads?

I made already a similar thing, using this management servers WMI Ping
Provider, and found this extremly slow, but could not find the reason.

I could not find anaything in the SDK, wether scripting nor COM API. I am
using the .Net Framework to build my tool, not scripts.

Any help would be really very welcomed!

Best regards,
Manfred Braun

[Hopefully I get it managed this time to post it as a top-level entry;I am
afraid, only this level is watched for "managed newsgroups" ??]

.

Relevant Pages