hardware not showing up properly in hardware report

[john99]

I've noticed some systems don't report properly, i.e some don't report back the motherboard manufacturer or model number and some
other systems report the wrong CPU type, i.e. PIII 450 comes up as PII 348...

Will a bios update fix some of these issues or is this a generic problem with system hound?

Thanks

[john99]

I also tried the smbios=0 as stated in the previous thread. It doesn't seem to make a difference!

Unless I didn't add it right, here is how I added it.

HKEY_LOCAL_MACHINE\SOFTWARE\systemhound\pbplugin

And under there I added SMBIOS dword 0

There are mostly Asus motherboards, some say To Be Filled By O.E.M. and others say unknown.

I'm running 4.0.5.0 currently.

Thanks

[Dee]

The string "To Be Filled By O.E.M" would be read directly from the BIOS. Many BIOS manufacturers do this as a place holder for the PC manafacturer to put in the correct asset id.

systemhound can be configured to ignore these strings when collecting BIOS data (it already has a set of more common entries)....

On the client machine:
Create the file pbplugin.dat in the same directory as pbplugin.dll and using notepad enter the following entry within it

[IGNOREDSTRINGS]
To Be Filled By O.E.M=1

Note:The dat file follows the same format as a traditional INI file so you can enter several strings which should be ignored.

Then run shrefresh.exe on the client machine to collect and resend the audit details to the server. If the changes work then you could make the same changes on the Central server under the Release folder (there will be a separate copy of pbplugin.dll for each Operating system). By making this change on the Central Server you ensure the change will be deployed all the systemhound clients. Note: once you've created the file on the central server it will always overwrite the file on the client...so the server copy effectively becomes the master.

[Dee]

Try to set SMBIOS to 0 on just the problem machines. By setting this value to 0 you are telling systemhound to use WMI to query the PC BIOS rather than interfacing directly to it. To check you've set the setting correctly have a look at the systemhound log file hwinfo.log and you should see the entry "SMBIOS disabled" whenever the plugin pbplugin runs.  Generally speaking systemhound does a better job interrogating the BIOS than WMI.

If you are missing key data and want to see if the asset data you want is actually within the BIOS open the file sb.raw (on the client) within notepad (found under systemhound\logs) and search for the string. This file is a raw dump of the BIOS memory. If you can see the entry systemhound is not reporting within it then email the raw file (+hwinfo.log) to support together with details of the entry and we'll take a look at it.

Dee