Hardware Information Analisys - "Invalid" Result

Usage and Config
1

(imported topic written by MarlonRojas)

Guys

I am using this analisys to get information about the following fileds:

Identifying Number - Windows

Computer Model - Windows

We get a LOT of machine with INVALID data as value in this filed. How we can fix tihis problem to get the correct information?

Thanks!

2

(imported comment written by francesco.latino)

Hi,

I suspect WMI returned values might contain some unexpected values. (or not returning at all)

Can you send me a screenshot showing a sample of the INVALID data value returned by the analisys ?

If you use the QnA on a failing target, and run the “Model” question “concatenation “~|~” of (string values of…” which value did you get ?

(something like q: concatenation “~|~” of (string values of…)

Thanks

Francesco

3

(imported comment written by MarlonRojas)

Francesco Thank for reply.

Here is the attachment, I will do test on failed machine and send you the results.

Thanks

4

(imported comment written by MarlonRojas)

Francesco I create a vbs script that query the Win32_ComputerSystem table and get

Model = “INVALID”

Of course Tivoli read y show this value. Now exists a way to fix it at WMI lvl?

Thanks!

5

(imported comment written by francesco.latino)

Hi,

I see 3 possible ways (just thinking and giving you some suggestions from our experience)

1- hook WMI query with a custom C code. But this is complex, may be dangerous - probably not supported by Microsoft - and not the best way. The problem is not on the WMI dll I guess. I think problem is in the machine’s BIOS the WMI code is looking at. So I would not change WMI logic.

2- Contact IBM HW or Lenovo HW and discuss about this problem: I assume the WMI is reading BIOS memory at a given offsset (as we do during PXEboot) and this location has that invalid value.

You may PXEboot this target in TPMfOSd BareMetal, and check in TPMfOSd WebUI -> Target Monitor the model field: I know we read this information from a given BIOS location: if it contains INVALID, then problem is in the BIOS itself. If TPMfOSd reads it correctly, then WMI is reading something else.

3- any other WMI query/column showing a meaningful value ? maybe the model is somewhere else ?

Thanks

Francesco