When 2003 came out, and for quite a while after that WMI and Perfmon had a
less than reliable connection, where if you changed the MOF file or
installed the drivers the first time, you had to try a number of procedures
to get the the WMI data to appear in Perfmon these were documented when
there was still a wmifilt sample in the DDK. In fact during that time, it
was recommended to me on this forum that the only sure way to get the data
into perfmon was to write an NT4 style DLL to read the WMI data and present
to Perfmon as we used to do.
I am now trying to get WMI and Perfmon to play nice on Windows Server 2008
and Windows 7, and am wondering if this was ever resolved, or should I be
looking at a DLL. Right now I am seeing problems that remind me of the bad
old days of WMI on 2003, so would like some guidance whether to look at my
MOF definitions and code more, or am I seeing the same old problem that
remained in Server 2003 through every revision I know of?
–
Don Burn (MVP, Windows DKD)
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
__________ Information from ESET NOD32 Antivirus, version of virus signature database 4282 (20090727) __________
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
Since I am getting no answers on the first question, can anyone say if old
DLL model of providing data to Perfmon still works on Server 2008 and
Windows 7?
–
Don Burn (MVP, Windows DKD)
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
“Don Burn” wrote in message news:xxxxx@ntdev…
> When 2003 came out, and for quite a while after that WMI and Perfmon had a
> less than reliable connection, where if you changed the MOF file or
> installed the drivers the first time, you had to try a number of
> procedures to get the the WMI data to appear in Perfmon these were
> documented when there was still a wmifilt sample in the DDK. In fact
> during that time, it was recommended to me on this forum that the only
> sure way to get the data into perfmon was to write an NT4 style DLL to
> read the WMI data and present to Perfmon as we used to do.
>
> I am now trying to get WMI and Perfmon to play nice on Windows Server 2008
> and Windows 7, and am wondering if this was ever resolved, or should I be
> looking at a DLL. Right now I am seeing problems that remind me of the
> bad old days of WMI on 2003, so would like some guidance whether to look
> at my MOF definitions and code more, or am I seeing the same old problem
> that remained in Server 2003 through every revision I know of?
>
>
> –
> Don Burn (MVP, Windows DKD)
> Windows Filesystem and Driver Consulting
> Website: http://www.windrvr.com
> Blog: http://msmvps.com/blogs/WinDrvr
>
>
>
> Information from ESET NOD32 Antivirus, version of virus
> signature database 4282 (20090727)
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>
>
>
Information from ESET NOD32 Antivirus, version of virus signature database 4282 (20090727)
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
Don,
I expose WMI perf counters to perfmon in WDM as well as ndis miniport driver for debugging purpose on nt5x and 6x. It’s kinda working in a way that’s not very predictable.
If the counters don’t show up, I would have to
- stop and restart some kind of msft “performance adapter” service,
- close and restart perfmon,
- expand and collapse the WMI object class a couple of times.
- combination of 1), 2) and 3)
Eventually, it would show up most of the time. I have never tried having a nt4 style DLL though.
Calvin Guan
Broadcom Corp.
Connecting Everything(r)
Yep, this is the procedure they documented for a while, as one customer of a
hardware firm who heard this said “What they don’t call for killing a goat a
midnight while giving a special chant”. Basically, it used to take anywhere
from 1 to 30 tries to get this functional. At present I am now over 30
with a KMDF driver on 2008, where the weird thing is that some of the WMI
classes show up, but others don’t.
–
Don Burn (MVP, Windows DKD)
Windows Filesystem and Driver Consulting
Website: http://www.windrvr.com
Blog: http://msmvps.com/blogs/WinDrvr
wrote in message news:xxxxx@ntdev…
> Don,
>
> I expose WMI perf counters to perfmon in WDM as well as ndis miniport
> driver for debugging purpose on nt5x and 6x. It’s kinda working in a way
> that’s not very predictable.
>
> If the counters don’t show up, I would have to
> 1) stop and restart some kind of msft “performance adapter” service,
> 2) close and restart perfmon,
> 3) expand and collapse the WMI object class a couple of times.
> 4) combination of 1), 2) and 3)
>
> Eventually, it would show up most of the time. I have never tried having a
> nt4 style DLL though.
>
> Calvin Guan
> Broadcom Corp.
> Connecting Everything(r)
>
>
> Information from ESET NOD32 Antivirus, version of virus
> signature database 4283 (20090727)
>
> The message was checked by ESET NOD32 Antivirus.
>
> http://www.eset.com
>
>
>
Information from ESET NOD32 Antivirus, version of virus signature database 4283 (20090727)
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
Yes, it’s very frustrating that the OS protocol perf counters always appear reliably but mine are by luck. I wasn’t aware of the documented procedure for this. I learned it the hard way.
At one point, I worked with msft through our channel but it got lost somewhere. I didn’t push hard enough since I don’t need them in production.
It will be nice if msft folks are listening and shed some lights on in public list if possible, or fix it so that we can have more confidence in using perf cnt for production purpose.
Btw, what is “Windows DKD” in your signature?
Calvin Guan
Broadcom Corp.
Connecting Everything(r)