
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-24-2019 08:01 AM
hi all,
discovery horizontal pattern for workstations are pulling serial number from win32_baseboard as 'L1XXXXXXXXXX'
instead, they are expecting the serial number pulled from Win32_SystemEnclosure which is 'PCXXXXXXXXX'. this is the same number we get from the SCCM imports. not sure whats going on here...
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-13-2020 09:26 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
01-07-2021 02:35 PM
Martin,
The new solution does not appear to be fixed in Paris yet. KB article KB0786378 (BaesBoard Serial number is populated on the serial number record instead of the BIOS Serial number f...) has been updated with the following:
"Note: This may not have been completely fixed in Paris for Windows Servers and Desktops."
Also, KB article KB0861828 (The baseboard serial number is populated on the serial number record instead of the BIOS serial numb...) has the following update:
"This problem is currently under review."
Also, KB article KB0860250 (BaseBoard Serial number is populated on the serial number record instead of the BIOS Serial number f...) also contains the following update:
"Note: This may not have been completely fixed in Paris for Windows Servers and Desktops."
Our team opened a ticket with ServiceNow to get clarification on the new information in KB articles (KB0786378, KB0861828, and KB0860250).