SSDs serial No in BIOS.

snip....
Somehow managed to get the format wrong. This should be easier to read.


.................................................. .......

Gary,

Your script shows serial numbers that are showing ~42 digits for both a
Kinston and a Samsung SSD drive.

I have a GPT drive with 4 partitions which is a 4TB drive and your script
also shows 42 digits and both the SSD's and the 4TB drive should have 15
digits if the WDC is included otherwise 12 digit serial number. Also,
nothing in the serial numbers match in any combination like at least the
next one does..

On a WDC 1.0TB drive your script shows W -DCWTAR7R412227 and Speccy shows
the serial number as WD-WCATR7142272. Do you see how your script appears to
be reversing the bytes on that?

So while you think it's providing correct serial numbers - its not. Easy
enough to verify. Either pull the drive, check the box it came in if you
have it or use another program.

So re-reading the post doesn't fix a broken script now does it. Great that
you took the time to pound out a script for this but it should have been
verified that it actually does work.

Your welcome,
--

snip....
Somehow managed to get the format wrong. This should be easier to read.


.................................................. ......

Gary,

Your script shows serial numbers that are showing ~42 digits for both a
Kinston and a Samsung SSD drive.

I have a GPT drive with 4 partitions which is a 4TB drive and your script
also shows 42 digits and both the SSD's and the 4TB drive should have 15
digits if the WDC is included otherwise 12 digit serial number. Also,
nothing in the serial numbers match in any combination like at least the
next one does..

On a WDC 1.0TB drive your script shows W -DCWTAR7R412227 and Speccy shows
the serial number as WD-WCATR7142272. Do you see how your script appears to
be reversing the bytes on that?

So while you think it's providing correct serial numbers - its not. Easy
enough to verify. Either pull the drive, check the box it came in if you
have it or use another program.

Speccy on my system returns EXACTLY the same serial info as do the scripts on
my system, for both volume and hardware serials! Not sure why yours is behaving
differently. Perhaps you shouldn't judge things by how your system behaves (or
misbehaves)!!

So re-reading the post doesn't fix a broken script now does it. Great that
you took the time to pound out a script for this but it should have been
verified that it actually does work.

The scripts aren't broken, and I didn't "pound them out"; -they were create in
WMI Code Creator!

Your welcome,

--
Garry

Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
comp.lang.basic.visual.misc
microsoft.public.vb.general.discussion

"GS" wrote in message news

snip....
Somehow managed to get the format wrong. This should be easier to read.


.................................................. ......

Gary,

Your script shows serial numbers that are showing ~42 digits for both a
Kinston and a Samsung SSD drive.

I have a GPT drive with 4 partitions which is a 4TB drive and your script
also shows 42 digits and both the SSD's and the 4TB drive should have 15
digits if the WDC is included otherwise 12 digit serial number. Also,
nothing in the serial numbers match in any combination like at least the
next one does..

On a WDC 1.0TB drive your script shows W -DCWTAR7R412227 and Speccy shows
the serial number as WD-WCATR7142272. Do you see how your script appears
to
be reversing the bytes on that?

So while you think it's providing correct serial numbers - its not. Easy
enough to verify. Either pull the drive, check the box it came in if you
have it or use another program.

Speccy on my system returns EXACTLY the same serial info as do the scripts
on my system, for both volume and hardware serials! Not sure why yours is
behaving differently. Perhaps you shouldn't judge things by how your system
behaves (or misbehaves)!!

So re-reading the post doesn't fix a broken script now does it. Great
that
you took the time to pound out a script for this but it should have been
verified that it actually does work.

The scripts aren't broken, and I didn't "pound them out"; -they were create
in WMI Code Creator!

Your welcome,


Gary,

I just used WMI Code Creator and got the same results I posted saying they
showed 42 characters for the GPT drive and the two SSD drives.

One WDC drive has the bytes out of order - same as I said

Another WDC drive that is on an eSATA port shows correctly.

I then used WD Lifeguard Diag tool to verify serial numbers against Speccy
and the WMI script.

The WMI script does not produce correct results for all the drives. So I
Goggled this anomaly and sure enough WMI and PowerShell results show that
WMI does reverse some bytes. It's also suspected that some manufacturers
enter serial numbers as hexadecimal strings and that’s what the WMI script
returns. And that sure looks like what I'm seeing for the two SSD's and one
GPT drive.

Reference:
https://social.technet.microsoft.com...ber?forum=ITCG

Only one WD drive shows a correct serial number in the WMI script. I have 5
physical drives on this system.

So it's possible your drives show correctly but out of 5 here, only one
shows correctly.

Here's the WMI generated code that I executed directly from the code
generator tool:

........................................code...... ..............
strComputer = "."
Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\CIMV2")
Set colItems = objWMIService.ExecQuery( _
"SELECT * FROM Win32_DiskDrive",,48)
For Each objItem in colItems
Wscript.Echo "-----------------------------------"
Wscript.Echo "Win32_DiskDrive instance"
Wscript.Echo "-----------------------------------"
Wscript.Echo "SerialNumber: " & objItem.SerialNumber
Next
.................................................. ..................

Namespace: root\CIMV2
Classes: Win32_DiskDrive
Property Selected: SerialNumber

The scripting tool isn't aware of how different manufactures enter their
serial numbers. I used two other tools to confirm my serial numbers against
the WMI script. The other tools obviously know how to handle the entry's
and present them correctly - hence my remark about the script being broke.

Have someone else test and verify and see what they get for results.

--


Bob S.

Gary,

I just used WMI Code Creator and got the same results I posted saying they
showed 42 characters for the GPT drive and the two SSD drives.

One WDC drive has the bytes out of order - same as I said

Another WDC drive that is on an eSATA port shows correctly.

I then used WD Lifeguard Diag tool to verify serial numbers against Speccy
and the WMI script.

The WMI script does not produce correct results for all the drives. So I
Goggled this anomaly and sure enough WMI and PowerShell results show that WMI
does reverse some bytes. It's also suspected that some manufacturers enter
serial numbers as hexadecimal strings and that’s what the WMI script returns.
And that sure looks like what I'm seeing for the two SSD's and one GPT
drive.

Reference:
https://social.technet.microsoft.com...ber?forum=ITCG

Only one WD drive shows a correct serial number in the WMI script. I have 5
physical drives on this system.

So it's possible your drives show correctly but out of 5 here, only one shows
correctly.

Here's the WMI generated code that I executed directly from the code
generator tool:

.......................................code....... .............
strComputer = "."
Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\CIMV2")
Set colItems = objWMIService.ExecQuery( _
"SELECT * FROM Win32_DiskDrive",,48)
For Each objItem in colItems
Wscript.Echo "-----------------------------------"
Wscript.Echo "Win32_DiskDrive instance"
Wscript.Echo "-----------------------------------"
Wscript.Echo "SerialNumber: " & objItem.SerialNumber
Next
.................................................. .................

Namespace: root\CIMV2
Classes: Win32_DiskDrive
Property Selected: SerialNumber

The scripting tool isn't aware of how different manufactures enter their
serial numbers. I used two other tools to confirm my serial numbers against
the WMI script. The other tools obviously know how to handle the entry's and
present them correctly - hence my remark about the script being broke.

Have someone else test and verify and see what they get for results.

Bob,
Thanks, I appreciate your efforts! I believe WMI can't handle hex data
correctly, but I have no idea why on earth an OEM would use that for a serial#!

I only have a Liteon CV3 256GB SSD on this machine and a WD 'MyPassport' 1TB
external drive for storage, so would be good if someone else runs the scripts
to confirm because AFAIC there's no way to know unless it breaks here.

--
Garry

Free usenet access at http://www.eternal-september.org
Classic VB Users Regroup!
comp.lang.basic.visual.misc
microsoft.public.vb.general.discussion