Hi,

thanks for the hint about WMI queries and the KB - that's exactly what I wanted to know about.

We are suffering from this "issue" addressed in the KB as well, because SCCM reports either none or incorrect CPU names, which is especially anoying in management reports and dashboards - it ruins all the nice statistics ... :-)

Btw, there's a second KB related to that:
http://support.microsoft.com/kb/946554
This one fixes Celeron issues, while the other one fixes Core2Duo.

The sad thing is: Even with both patches installed (and the WMI query returning the correct value), KIX @CPU still reports "Intel Pentium III" ... so the question remains: Where does KIX dig up that ? It doesn't seem to use WMI queries, because it even returns a result when WMI is not running or damaged (see below).

And: Theoretically, yes, of course, the "easiest" would be to replace @CPU with the WMI query for Win32_Processor and .Name - but this just replaces something bad with something worse. IMHO, WMI is a nightmare in itself, because it can become damaged or inconsistent to any extent. That's the next thing I am having a big pain with: Damaged WMI (and I am not talking about 10 computers ...) - hot to detect and auto-repair.

So, my intention was to try to do as less as possible with WMI, and that was the reason for using @CPU and asking where from and how it gets it's result.

Andreas

Edited by AndreasBucher (2010-07-13 10:24 AM)
_________________________

King regards,

Andreas