SerialNumber Field (manual entry)

[opekta]

I recently noticed that the SerialNumber field (in dbo_tblBIOS) for one of our computers was empty. So, I went ahead and entered it manually. I actually performed this "data entry" using an Access (ADP) "front end." But, I also opened the table in SQL Server Management Studio and verified that the field was, in fact, populated with the value I entered.

However, when I view the Action Screen for this computer, Lansweeper still does not display any "Tag" information. I even restarted the Lansweeper Service and performed a Trigger Scan, just to try and cover all the bases.

Is there some other table within the Lanswpeer database that also needs to be modified in order for this value to display?

NOTE: We have other identical models to this particular computer that are displaying the "Tag" information correctly.

Thanks,

Terry

[opekta]

I'm guessing you're refering to the IdentifyingNumber field in dbo_tblComputerSystemProduct (not dbo_tblComputersystem).

I see what you mean about the value "disappearing" after a subsequent scan.

I'll double-check the BIOS to verify the Asset (Service) Tag is actually showing up there. There must be something odd about this particular PC that's causing this WMI quey to fail. One scenario I can imagine would be the motherboard being replaced and the Service Tag not being set and the field technician before leaving.

Thanks again!

🙂

Terry

[Hemoco]

opekta wrote:
I'm guessing you're refering to the IdentifyingNumber field in dbo_tblComputerSystemProduct (not dbo_tblComputersystem).

Yes indeed, sorry.

I've seen the problem sometimes in outdated Dell bios versions where the TAG was set but didn't get scanned.

[Hemoco]

You need to update the table tblcomputersystem.
Unfortunately during the next scan the field will be blank again.

Best is to go into the bios and change the asset tag there.