SG-SCCM Invalid serial numbers
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-20-2022 12:54 AM
Hi all,
"SCCM 2016" plugin use "SncSerialNumber" function so the condition to determine if a serial number is "valid = false" are:
1) Serial number is empty.
2) Serial number is composed of the same repeating character.
3) Serial number meets any of the conditions listed under dscy_invalid_serial.
Reference: KB0744965
Question:
1) Does SG-SCCM plugin use the above to determine if a serial number is valid?
2) If yes, have I to add custom entries on "dscy_invalid_serial" table?
3) If no, which logic is used and where I could setup custom values?
Thanks for the help.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-20-2022 05:50 AM
All Service Graph connectors go through the Cleanse Serial Number operation. This operation has a list of invalid serial numbers. You can modify that list to account for your invalid serial numbers.
Please see this post for further details.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-21-2022 12:40 AM
Hi jgates,
thanks for the response, could you please clarify the below:
- the Cleanse Serial Number operation script first check the validity of the input via the function:
- var valid = new global.SerialNumberManager().isValid(input)
- then loop throught the invalidStrings array and check the related validity:
- for (j = 0; j < invalidStrings.length; j++) {
if (inputLowercase.includes(invalidStrings[j])) {
output[i] = '';
break;
}
}
- for (j = 0; j < invalidStrings.length; j++) {
- I seen that global.SerialNumberManager isValid function uses the SncSerialNumber(), so check the entries against dscy_invalid_serial table
- So I doesn't understand why are performed two checks for input validity (since some of the entries on invalidStrings are already into dscy_invalid_serial table)
Thanks for the help.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-15-2025 10:22 AM
Did anyone resolve this? After Yokohama upgrade my 'SCCM Computer Identity' job is showing a handful of serial_number errors. Just an annoyance.
Example error: