
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
06-07-2018 08:23 AM
We are in the process of congiuring discovery and CI's and have come across an issue. When the discovery runs and creates or updates a CI it is entering the baseboard serial number into the serial number field.
I am looking for how to change this entry to update the field with the BIOS or Chassis serial number. We use Dell hardware so the 7 digit servic tag is all we need in the record.
thanks.
Solved! Go to Solution.
- Labels:
-
Enterprise Asset Management

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-23-2018 12:37 AM
The Dell BIOS Serial numbers tend to be the same as their seven digit service tag, at least on some OptiPlex devices that I've tested here, such as the 3010 and 3020 models.
In Windows, entering wmic bios get serialnumber should return that correctly (and that'll do it for any device)
I'd check the discovery probe for Windows - Hardware Information as a WMI Probe. The WMI Fields in that probe should show Win32_BIOS.SerialNumber
That serial number should return the same as the WMI query above. The post-processor script should also refer to that accordingly - another thing to check. Both of the above are normally out of the box configs so should work.
This probe should be included in the Windows - Identity discovery probe as well and is in the Windows - Identity sensor. That sensor should be active.
I suspect what's actually happening is that the WMI query being run is actually Win32_baseboard.serialnumber as above which would return the field as you mentioned. You can verify this by:
wmic baseboard get serialnumber
You can of course in the WMI fields above set the active to false, as long as the post-processor script doesn't need to reference it. That way it should always return the BIOS serial number.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-07-2019 05:45 AM
I'm also not seeing the expected results so I suspect it's using Patterns rather than Probes to discover the Serial Number.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-19-2019 08:16 AM
I also did the same thing as you, thinking that it would corect the issue, but I am still getting the Baseboard Serial Number as my cmdb_ci_serialnumber. Have you found any other solutions to correct this problem?

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-19-2019 02:30 PM
Tate,
Did you resynchronize with the MID Servers? (Related Links --> Synchronize with MID Servers) This pushes the new code out to the MID Servers.
Are you using Probes rather than patterns?
Also, the bad serial numbers should just be overwritten on the next discovery run so if your CI's are on the schedule, you should see them just automagically get fixed.
Nate
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-07-2021 04:28 PM
Other community articles that may be helpful on this topic:
After upgrading to London, Discovery is picking baseboard serial number as CI serial number
Computer Discovery. How to replace baseboard serial number with bios