The baseboard serial number is populated on the serial number record instead of the BIOS serial number for Windows servers/desktops patterns for discoveryDescriptionFurther after the fix for the same issue PRB1436659/KB0861828, the baseboard serial number is populated on the serial number record instead of the BIOS serial number.Steps to Reproduce Run Discovery on Windows server using patterns. The main CI's serial number field will have the baseboard serial used, instead of BIOS serial number for Windows servers/desktops patterns for discovery, which is incompatible with what other plugins that populate the CMDB, such as SCCM.Workaround1- Use the attached scripts as follows: - For instance version prior to Paris Patch 3, upload all three files to the instance: OSs - Pre Sensor script, Windows OS - Desktops pattern, Windows Identity - Hardware Information shared library. - For instance version Paris Patch 3 and above, upload only the two files: OSs - Pre Sensor script, Windows OS - Desktops pattern. sa_pattern_prepost_script_59e84c5b9f2322001d753758442e70f3.xml - OSs - Pre Sensor script sa_pattern_bfaf65f7db75a200868a7c841f96199d.xml - Windows OS - Desktops pattern sa_pattern_2ba886d6dbc12200c06776231f96194b.xml - Windows Identity - Hardware Information shared library How to upload the XML files to the instance 2) Add a mid server property (introduced in the earlier fix, valid for this workaround as well), as documented in KB0786378 - BaesBoard Serial number is populated on the serial number record instead of the BIOS Serial number for windows servers: The workaround uses mid server property "mid.win.baseboard.or.bios.insertion", based on the property value (true / false) the pattern will use BaseBoard or Bios Serial number. If false - BaseBoard number will be used (default value)If true - BIOS serial number will be used 3) Sync pattern to MID ServerRelated Problem: PRB1453911