- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-14-2019 01:43 PM
OOB Discovery populates each discovered computer serial number field with the baseboard serial number. We are looking to replace that with the bios serial number, which matches our Asset Tags. I have tried by deactivating some o the WMI fields in the Windows-Hardware probe with no luck.
Perhaps I am looking in the wrong place, but that's why I am looking for help. Thanks!
Solved! Go to Solution.
- Labels:
-
Discovery
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-13-2020 09:14 AM
ServiceNow has created an out of the box solution to choose the BIOS Serial Number instead of the Baseboard Serial Number for the Windows OS - Servers pattern. The update is being released in Paris per KB KB0786378:
New mid server property introduced "mid.win.baseboard.or.bios.insertion" , based on the property value (true / false) pattern will insert BaseBoard or Bios Serial number.
If false - BaseBoard number will be populated
If true - BIOS serial number will be inserted
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-14-2019 04:55 PM
That might be tough with probes/sensors since alot of that processing is done behind the scenes. I might suggest that a BR that does a lookup on the serial number table grabs the one you want then set the base class serial number with the same after insert/update. However, when you migrate over to patterns something like this will be much easier!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-20-2020 11:29 PM
Hi!
Probably you already found it, but just in case, ServiceNow has a workaround for this. Honestly, I don't like it very much, but it worked for me (I tried the 1st option, copying the steps in different order and then removing the original ones):
https://hi.service-now.com/kb_view.do?sys_kb_id=5a902894dbeaf7402be0a851ca9619d8
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-21-2020 04:06 AM
I agree with Doug regarding going to patterns. We had the problem with HP Superdomes that the baseboard serial number was being used, but that baseboard number was shared among the OS instances running on the individual cards. Fixing that by tweaking the "Linux - Hardware Information" Shared Library is a relatively simple fix.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
01-21-2020 05:02 AM
As Cesar has done, I have also implemented Option #1 from KB KB0749739 How to make 'Windows OS - Servers' Pattern return Bios Serial number instead of Baseboard Serial num.... I tested option 2 and option 3 and was not able to get these options to work. Since steps 3.10 and 3.12 are part of a shared library it affects 2 Patterns: Windows OS - Desktops and Windows OS - Servers. The text shows swapping steps 3.10 and 3.12:
FROM: 3.10 Add Win32_BIOS.SerialNumber to temporary table
3.12 Add Win32_BaseBoard.SerialNumber to temporary table
TO: 3.10 Add Win32_BaseBoard.SerialNumber to temporary table
3.12 Add Win32_BIOS.SerialNumber to temporary table
Note: the graphic in the KB article KB0749739 is incorrect for Option #1 (shows swapping options 3.10 and 3.13).
I wanted to add that Probe-based discovery (for Windows hosts) chooses the BIOS serial number on the Serial Number field on the form and Pattern-based discovery is now choosing the Baseboard Serial number. The BIOS serial number is the industry standard way to identify a computer. The Baseboard serial number is the industry standard way to identify the motherboard. For some reason this has changed in Pattern-based discovery.
This issue has been discussed in other community articles:
After upgrading to London, Discovery is picking baseboard serial number as CI serial number
discovery workstation scans - incorrect serial number