Notifications

191 views

Description

By default, OOB 'Windows OS - Servers' Pattern return Baseboard Serial number, but in some cases, the customer might want to use the Bios Serial number for the CI instead.

Steps to Reproduce

Run Discovery on windows server using patterns

Trigger Windows -Hardware information shared library

Observe that BaseBoard Serial number is populated on the serial number record field.

Workaround

This problem has been fixed. If you are able to upgrade, review the Fixed In or Intended Fix Version fields to determine whether any versions have a planned or permanent fix.

The default behaviour remains the same after the fix, returning the Baseboard Serial number. 

The fix introduces a new mid server property "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 (default value)
  • If true - BIOS serial number will be inserted

Note: This may not have been completely fixed in Paris for Windows Servers and Desktops. See:
PRB1436659 KB0861828 The baseboard serial number is populated on the serial number record instead of the BIOS serial number for Windows servers when using the Windows - OS Servers pattern for discovery


Related Problem: PRB1371559

Seen In

SR - IRM - Audit Management - New York 2019 Q3
SR - IRM - Audit Management PA Content - Madrid 2019 Q1
SR - IRM - GRC Profiles - Madrid 2019 Q2
SR - IRM - PA Premium Integration - New York 2019 Q3
SR - IRM - Policy and Compliance - Madrid 2019 Q2
SR - IRM - Policy and Compliance PA Content - Madrid 2019 Q1
SR - IRM - Risk Management - New York 2019 Q3
SR - IRM - Risk Management PA Content - Madrid 2019 Q1
SR - IRM - SIG Assessment Legacy - Madrid 2019 Q1
SR - IRM - Vendor Risk Management - Madrid 2019 Q1
SR - ITOM - CMDB CI Class Models - 201907
SR - ITOM - CMDB CI Class Models - 201908
SR - ITOM - CMDB CI Class Models - 201909
SR - ITOM - Discovery and Service Mapping - 201908
SR - ITOM - Discovery and Service Mapping - v1.0.35
SR - ITOM - Fundamentals Istanbul Jakarta Kingston r1 - v5.99.6
SR - PAR - Performance Analytics Content Pack for Service Portal - v1.0
SR - Security - Integration Framework - Madrid 2019 Q2
SR - Security - Support Common - Madrid 2019 Q2
SR - Security - Support Orchestration - Madrid 2019 Q2
SR - SIR - Check Point Integration - New York 2019 Q3
SR - SIR - ElasticSearch Integration - Madrid 2019 Q1
SR - SIR - Exchange Online Integration - New York 2019 Q3 2
SR - SIR - ReverseWhoIs Integration - Madrid 2019 Q2
SR - SIR - Security Incident Response - Madrid 2019 Q2
SR - SIR - Security Incident Response Flow Designer Content - Madrid 2019 Q2
SR - SIR - Security Incident Response PA Content - New York 2019 Q3
SR - SIR - Security Incident Response UI Patch - London 2019 Q2 v.6.2.3
SR - SIR - Splunk Sighting Search Integration - Madrid 2019 Q1
SR - SIR - Store SecOps Setup Assistant - Madrid 2019 Q2
SR - SIR - Store Threat Core - Madrid 2019 Q2
SR - SIR - Store Trusted Security Circles Client - New York 2019 Q3
SR - SIR - Threat intelligence - New York 2019 Q3
SR - SIR - WHOIS Integration - New York 2019 Q3
SR - VR - Configuration Compliance - New York 2019 Q3
SR - VR - Qualys - New York 2019 Q3
SR - VR - Shodan Exploit - New York 2019 Q3
SR - VR - Solution Management Madrid Q2
SR - VR - Vulnerability Response - New York 2019 Q3
SR - VR - Vulnerability Response PA Content - Madrid 2019 Q2

Fixed In

Paris

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2020-10-19 00:20:53
Published:2020-10-15