What can we do when we don't trust UUID?
-
Using the uuid as a unique system ID has been proven to not be a reliable method of system identification. I saw this when working with dnsmasq trying to deliver a certain iPXE boot file based on the system requesting boot info. I ended up giving up on the task since the UUID field is defined in IEEE documentation, but the implementation of that 32 character field it up to the hardware manufacture to populate. There is no guidance from IEEE on the content of this field or even a requirement for the system manufacturer to populate this field.
In my testing I found that most enterprise system builders do this this field to uniquely identify their hardware, but not all do. So what can we do to create a uniquely identifiable ID for fog to use. Initially we were using the network adapter’s hardware mac address for system identification. This process worked great until computers began shipping without built in ethernet adapters. USB dongles where then required to image these machines with FOG. The issue here is that now we have many machines that used the same USB dongle (or dock) for imaging and they all have the same mac address inside fog.
So again I ask, what can we do?
One solution comes from the way I had to program and manage unique record keys in Lotus Notes back in the early 2000s. At that time we used several fields to create a unique composite key that specifically described that record for searching.
I feel we can use the same concept with FOG to create a new key that precisely describes a system registered in FOG. It may be required to create a new database field to contain this key for this discussion lets call the key
fluid
(Fog Logical Unit ID) [yes there is a double meaning here too].What I propose would be to use the following fields that FOG is already collecting when the system is registered. The
fluid
key might be comprised of the following fields: <mac_address>|<System Serial Number>|(alternate would be <Motherboard Serial Number> if <System Serial Number> was blank or contained non lower ascii characters)
<Motherboard Asset Tag><Chassis Asset>|<System Product> Or any other smbios key that is unique to the specific hardware.I did intentionally include the Motherboard asset tag and the chassis asset tag to allow the IT admin to have the ability to add uniqueness to the
fluid
if all other fields became equal.I did collect samples of a few systems I have at home to see if we could find uniqueness in what FOG is collecting.
Dell e6410
System Manufacturer Dell Inc. System Product Latitude E6410 System Version 0001 System Serial Number 5XXXxX1 System Type Type: Laptop BIOS Vendor Dell Inc. BIOS Version A16 BIOS Date 12/05/2013 Motherboard Manufacturer Dell Inc. Motherboard Product Name 04373Y Motherboard Version A03 Motherboard Serial Number /5XXXxX1/CN1XXXXXR03D5/ Motherboard Asset Tag CPU Manufacturer Intel CPU Version Intel(R) Core(TM) i7 CPU M 640 @ 2.80GH CPU Normal Speed Current Speed: 2799 MHz CPU Max Speed Max Speed: 4000 MHz Memory 3.65 GiB Hard Disk Model WDC WD2500BEKT-75PVMT0 Hard Disk Firmware 01.01A01 Hard Disk Serial Number WD-WXK1AXXXXX4 Chassis Manufacturer Dell Inc. Chassis Version Chassis Serial 5XXXxX1 Chassis Asset
Dell e6440
System Manufacturer Dell Inc. System Product Latitude E6440 System Version 00 System Serial Number 7XXXxX1 System Type Type: Laptop BIOS Vendor Dell Inc. BIOS Version A14 BIOS Date 12/01/2015 Motherboard Manufacturer Dell Inc. Motherboard Product Name Motherboard Version Motherboard Serial Number /7XXXxX1/ / Motherboard Asset Tag Not Specified CPU Manufacturer Intel CPU Version Intel(R) Core(TM) i5-4300M CPU @ 2.60GHz CPU Normal Speed Current Speed: 2600 MHz CPU Max Speed Max Speed: 2600 MHz Memory 3.75 GiB Hard Disk Model Crucial_CT275MX300SSD1 Hard Disk Firmware M0CR040 Hard Disk Serial Number 172XXXXX535 Chassis Manufacturer Dell Inc. Chassis Version Chassis Serial 7XXXxX1 Chassis Asset
VMWare virtual machine
System Manufacturer VMware, Inc. System Product VMware Virtual Platform System Version None System Serial Number VMware-42 2e a9 xx 9b xx 2c 15-xx af xx d9 xx xx xx a9 System Type Type: Other BIOS Vendor Phoenix Technologies LTD BIOS Version 6.00 BIOS Date 04/14/2014 Motherboard Manufacturer Intel Corporation Motherboard Product Name 440BX Desktop Reference Platform Motherboard Version None Motherboard Serial Number None Motherboard Asset Tag Not Specified CPU Manufacturer GenuineIntel 000000000000 000 CPU Version Intel(R) Xeon(R) CPU E5620 @ 2.40GHz CPU Normal Speed Current Speed: 2400 MHz CPU Max Speed Max Speed: 30000 MHz Memory 3.85 GiB Hard Disk Model Hard Disk Firmware Hard Disk Serial Number Chassis Manufacturer No Enclosure Chassis Version Chassis Serial None Chassis Asset No Asset Tag
Intel NUC
System Manufacturer ................................. System Product ................................. System Version ................................. System Serial Number ................................. System Type Type: Desktop BIOS Vendor Intel Corp. BIOS Version FYBYT10H.86A.0047.2014.1224.1147 BIOS Date 12/24/2014 Motherboard Manufacturer Intel Corporation Motherboard Product Name DN2820FYK Motherboard Version H24582-204 Motherboard Serial Number GEFYXXXXXXY Motherboard Asset Tag ................................. CPU Manufacturer Intel CPU Version Intel(R) Celeron(R) CPU N2830 @ 2.16GHz CPU Normal Speed Current Speed: 2160 MHz CPU Max Speed Max Speed: 2400 MHz Memory 3.68 GiB Hard Disk Model SanDisk SDSSDP128G Hard Disk Firmware 3.2.0 Hard Disk Serial Number 1510XXXXXXX89 Chassis Manufacturer ................................. Chassis Version Chassis Serial ................................. Chassis Asset
Lenovo X60
Lenovo System Manufacturer LENOVO System Product 17023LU System Version ThinkPad X60s System Serial Number LVXXXX6 System Type Type: Notebook BIOS Vendor LENOVO BIOS Version 7BETD5WW (2.16 ) BIOS Date 03/31/2008 Motherboard Manufacturer LENOVO Motherboard Product Name 17023LU Motherboard Version Not Available Motherboard Serial Number 1ZDXXXXX0S Motherboard Asset Tag CPU Manufacturer GenuineIntel CPU Version Intel(R) Core(TM) Duo CPU CPU Normal Speed Current Speed: 1667 MHz CPU Max Speed Max Speed: 1667 MHz Memory 1.46 GiB Hard Disk Model FUJITSU MHY2080BH Hard Disk Firmware 0084000D Hard Disk Serial Number K43XXXXXX62PA Chassis Manufacturer LENOVO Chassis Version Chassis Serial Not Available Chassis Asset
Virtualbox
System Manufacturer innotek GmbH System Product VirtualBox System Version 1.2 System Serial Number 0 System UUID ac7a7b42-e5d2-4bac-bcda-ef5ae35d4cf0 System Type Type: Other BIOS Vendor innotek GmbH BIOS Version VirtualBox BIOS Date 12/01/2006 Motherboard Manufacturer Oracle Corporation Motherboard Product Name VirtualBox Motherboard Version 1.2 Motherboard Serial Number 0 Motherboard Asset Tag Not Specified CPU Manufacturer CPU Version CPU Normal Speed CPU Max Speed Memory 724.69 MiB Hard Disk Model VBOX HARDDISK Hard Disk Firmware 1.0 Hard Disk Serial Number VBa44dd0ba-42d13f3b Chassis Manufacturer Oracle Corporation Chassis Version Chassis Serial Not Specified Chassis Asset Not Specified
-
@george1421 Thanks for opening this thread. I’ve been onto that and opened an issue on github to work on that already but it’s still a great idea to discuss this important issue here in the forums as not all of you are on github I suspect.
Good to start with collecting system information as you did. So we see what’s available before we actually get into deciding about what to use.
As described in the github issue I still think we should not add another field to the DB for that. For that all FOG users would have to go through some kind of process to fill this new field with proper information for each and every client they have. Though we could do all this with the fog-client and other means of updating the DB field when clients run tasks I don’t think we need to go there.
What I propose is adding a logic to the PHP code that kind of concatenates (though not in the sense of string concat…) all the information we already have in the DB to find that one unique host currently talking…
-
@sebastian-roth said in What can we do when we don't trust UUID?:
As described in the github issue I still think we should not add another field to the DB for that.
I’m not suggesting one way or the other here, but just opening the discussion.
Adding a new field would be possible especially if the
fluid
value can be calculated based on values already in the inventory database. This could be a simple (or complex) sql script delivered with a FOG update just like we do today. If the value can be calculated then it can be populated.You do raise an interesting point, what are the impacts to the FOG Client if we move away from mac address being the key identifier? The mac address will need to be involved somewhere still with booting since iPXE isn’t as smart as the FOG programmer’s PHP skills.
-
Looking through the specs you posted I get the impression that we should be able to reliably identify unique systems checking those five:
- MAC address
- System UUID
- System Serial Number
- Motherboard Serial Number
- Hard Disk Serial Number
Though this is where the problems start. We need iPXE to report those figures right on boot-up so we can identify each and every client properly. So we cannot wait for linux to come up and read DMI information I am afraid. We might need to add some code to iPXE to be able to make this work.
Check out this list: http://ipxe.org/cfg (serial, asset, … sounds good - and we should be able to add more in case we need)
-
@sebastian-roth I wonder if we should see if the testers can provide more examples of what I posted. We only have Dells at my work so what I found almost all dells are exactly the same in what they produce. It may be of some value to get the inventory of the MSI board that started this quest too. The more data we have to start with, the better the decision will be even before any code is crafted.
As for the ipxe that is going to be a difficult one.
These four look interesting:
manufacturer (string) Manufacturer product (string) Product name serial (string) Serial number asset (string) Asset tag
You can’t/shouldn’t use the hard drive serial number since that is the one device that may change more frequently than the other values. Hard drive crashes, is replaced and now we have a new identity.
-
@george1421 @Sebastian-Roth this is a very good conversation to be having. FOG 2.0 was looking at system uuids to identify computers, but for the reasons you stated, that wouldn’t work very well. Thinking out-loud here, maybe these points are worth considering:
- There is no 1 single we can rely on as you showed in your original post, and some derived value based on client information may be the best route to go.
- A static key derived from values may not be the best idea. Instead it should be a weighted component comprised of several fields. For example, one could think about it like so:
- UUID: .4
- Primary MAC: .2
- Motherboard asset #: .2
- Hard drive asset #: .1
- Ram/CPU information :.1
For each field that matches, a score gets increment by that amount; the host with the highest score, and above some threshold, gets selected/matched (essentially a fuzzy search). This provides some tolerance against machine’s hardware being upgraded, or portable network adapters being used. Obviously the fields I picked were completely arbitrary and some testing may need to go into it to pick the best identifiers.
-
Trying to keep this short but - I don’t think HDD serial numbers should be used because disks fail and get replaced. Also, a technician may trade HDDs in two boxes to see if a problem stays with the original box or moves to the new box.
I don’t think RAM information is a good one either, since RAM can be added. CPU would be better but still not great.
If the motherboard is changed out, that is effectively a new host - because it’ll come with a new MAC and new motherboard serial number.
-
This is just a discussion. Nothing here is set in stone, the idea is to come up with a better solution than relying on a single point.
-
@Wayne-Workman as I said,
Obviously the fields I picked were completely arbitrary and some testing may need to go into it to pick the best identifiers.
and as Tom said, this is just brainstorming how to best identify hosts; nothing is set in stone.
Also, for the reasons you stated, hdd and ram have a lower weight in the fuzzy search; but they are still important metrics.
As for the motherboard being changed out, that’s essentially saying you have a brand new computer, not much we can do about that. But even then, the fuzzy search would be able to suggest a couple hosts that are more likely than the rest. That would allow FOG to cooperate with fog admins; if a host has been changed greatly, FOG can prompt the user to select which host it is, and update its metrics. The point of a fuzzy search is to handle most changes in a host gracefully. There will always be extremes.
-
@joe-schmitt The issue is with fuzzy searches, iPXE must somehow identify the system or will it just pass the mac address to a FOG backend process and that backend process will reach out and identify the hardware. In at way the mac address will be a tickler to trigger fog to reach out and identify the hardware?
I do think you are on the right approach for a weighted average though.
I might suggest that we do try to use the fields iPXE can read and combine them into a passable string to the fog back end processes. iPXE has some crude string concatenation functions that we might use. I realize for FOG 2 we might not use iPXE (guess), so the process may be different.
manufacturer (string) Manufacturer product (string) Product name serial (string) Serial number asset (string) Asset tag
-
@george1421
Posiflex 3815System Manufacturer POSIFLEX System Product XT3815 System Version B1F2212311 System Serial Number XTHXXX26 System UUID 12345678-1234-5678-90ab-cddeefaabbcc System Type Type: Notebook BIOS Vendor INSYDE Corp. BIOS Version REV.H BIOS Date 02/10/2017 Motherboard Manufacturer POSIFLEX Motherboard Product Name XT3815 Motherboard Version B1 Motherboard Serial Number Type2 - Board Serial Number Motherboard Asset Tag Type2 - Board Asset Tag CPU Manufacturer Intel(R) Corporation CPU Version Intel(R) Celeron(R) CPU J1900 @ 1.99GHz CPU Normal Speed Current Speed: 2009 MHz CPU Max Speed Max Speed: 2416 MHz Memory 3.75 GiB Hard Disk Model Phison SSBP064GTMC0-S11 Hard Disk Firmware SBFM00.8 Hard Disk Serial Number 171XXXXXX126 Chassis Manufacturer Chassis Manufacturer Chassis Version Chassis Serial Chassis Serial Number Chassis Asset
-
@Joe-Schmitt understood. Just participating here.
@george1421 said in What can we do when we don't trust UUID?:
I might suggest that we do try to use the fields iPXE can read
That’s a great start. I don’t know what things iPXE can currently read, but we need to figure out all of those.
Of course, if the iPXE provided information is not enough to get a single result in a fuzzy search, then FOS can be loaded fully and it’s first task would be to retrieve the other system information that would allow the FOG Server to correctly identify the host in a fuzzy search.
-
I don’t know what things iPXE can currently read, but we need to figure out all of those.
See here: http://ipxe.org/cfg
Of course, if the iPXE provided information is not enough to get a single result in a fuzzy search, then FOS can be loaded fully and it’s first task would be to retrieve the other system information that would allow the FOG Server to correctly identify the host in a fuzzy search.
Don’t think it’s wise to spin up FOS for that. We’d simply add the stuff needed to iPXE. It’s coded in C and has full access to all the information FOS would have as well. No need to do this extra round trip!
@Joe-Schmitt said:
For each field that matches, a score gets increment by that amount; the host with the highest score, and above some threshold, gets selected/matched (essentially a fuzzy search).
Sounds like a nice idea. Though I definitely wouldn’t put UUID up that high. Essentially all information is kind of problematic and that’s what’s driving us to find a new solution.
- UUID is fffffff-… or 0000000-… in some cases - totally useless.
- MACs are shared amongst hosts via USB NICs, hard drives serials can change as of dying hardware or intended change
- RAM/CPU or any other static hardware information is nowhere unique in huge environments where lots of identical machines are bought in a batch
- Motherboard serial and motherboard asset tag should be the best bet but in reality are not unique - sometimes not even set at all! (see @FallingWax’s post
Type2 - Board Serial Number
)
That said I still like the idea of the fuzzy search but wouldn’t make much if a science out of it. Essentially we have many hosts out there not having proper inventory data in the DB anyway.
I will start by adding the needed information to the iPXE params and we’ll take it from there.
Edit: Ok, I just brought up the iPXE shell on an iMac that I have here for debugging and saw that iPXE already has this smbios information:
uuid
,asset
(not set on the iMac by the way),board-serial
(lookes good on the iMac),manufacturer
(don’t think we wanna use that),product
(no),serial
(probably being the system serial and looking pretty good on the iMac - different to the board-serial as well!) -
System Product OptiPlex 3020 System Version 00 System UUID 4c4c4544-004e-3510-8058-cac04f443532 System Type Type: Space-saving BIOS Vendor Dell Inc. BIOS Version A14 BIOS Date 11/01/2016 Motherboard Manufacturer Dell Inc. Motherboard Product Name 0WMJ54 Motherboard Version A01 Motherboard Serial Number CN7016351L0B2B Motherboard Asset Tag Not Specified CPU Manufacturer Intel CPU Version Intel(R) Core(TM) i3-4150 CPU @ 3.50GHz CPU Normal Speed Current Speed: 3500 MHz CPU Max Speed Max Speed: 3800 MHz Memory 3.77 GiB Hard Disk Model SAMSUNG SSD PM851 2.5 7mm 128GB Hard Disk Firmware EXT08D0Q Hard Disk Serial Number S1CTNSAFC25193 Chassis Manufacturer Dell Inc. Chassis Version Chassis Serial Chassis Asset
System Manufacturer Dell Inc. System Product OptiPlex 3040 System Version Not Specified System Serial Number System UUID 4c4c4544-0039-5210-8046-c3c04f584432 System Type Type: Desktop BIOS Vendor Dell Inc. BIOS Version 1.5.3 BIOS Date 04/18/2017 Motherboard Manufacturer Dell Inc. Motherboard Product Name 05XGC8 Motherboard Version A01 Motherboard Serial Number CN7220067Q00X2 Motherboard Asset Tag Not Specified CPU Manufacturer Intel(R) Corporation CPU Version Intel(R) Core(TM) i3-6100 CPU @ 3.70GHz CPU Normal Speed Current Speed: 3700 MHz CPU Max Speed Max Speed: 4200 MHz Memory 3.75 GiB Hard Disk Model SanDisk Z400s 2.5 7MM 128GB Hard Disk Firmware Z2329012 Hard Disk Serial Number 162905404356 Chassis Manufacturer Dell Inc. Chassis Version Chassis Serial Chassis Asset
System Manufacturer Dell Inc. System Product Vostro 15-3568 System Version Not Specified System Serial Number System UUID 4c4c4544-0033-4310-8032-b3c04f344632 System Type Type: Laptop Type: Docking Station BIOS Vendor Dell Inc. BIOS Version 01.09.00 BIOS Date 04/07/2017 Motherboard Manufacturer Dell Inc. Motherboard Product Name 0PF3V3 Motherboard Version A00 Motherboard Serial Number CNWSC0073P002Z Motherboard Asset Tag Not Specified CPU Manufacturer Intel(R) Corporation CPU Version Intel(R) Core(TM) i3-7100U CPU @ 2.40GHz CPU Normal Speed Current Speed: 2400 MHz CPU Max Speed Max Speed: 2400 MHz Memory 3.63 GiB Hard Disk Model LITEON CV3-CE128-11 SATA 128GB Hard Disk Firmware TC7110D Hard Disk Serial Number TW09K30XLOH0072D00NI Chassis Manufacturer Dell Inc. Dell Inc. Chassis Version Chassis Serial Chassis Asset
System Manufacturer Dell Inc. System Product Vostro 3558 System Version 01 System Serial Number System UUID System Type Type: Laptop BIOS Vendor Dell Inc. BIOS Version A01 BIOS Date 02/09/2015 Motherboard Manufacturer Dell Inc. Motherboard Product Name 0D13PT Motherboard Version A00 Motherboard Serial Number CN1296356I00CC Motherboard Asset Tag Not Specified CPU Manufacturer Intel(R) Corporation CPU Version Intel(R) Core(TM) i3-4005U CPU @ 1.70GHz CPU Normal Speed Current Speed: 1700 MHz CPU Max Speed Max Speed: 1700 MHz Memory 3.76 GiB Hard Disk Model WDC WD5000LPVX-75V0TT0 Hard Disk Firmware 01.01A01 Hard Disk Serial Number WXG1A35128LC Chassis Manufacturer Dell Inc. Chassis Version Chassis Serial Chassis Asset Not Specified
System Manufacturer Dell Inc. System Product Latitude 3350 System Version Not Specified System Serial Number System UUID 4c4c4544-0057-3310-804d-c3c04f564232 System Type Type: Laptop BIOS Vendor Dell Inc. BIOS Version A09 BIOS Date 11/24/2016 Motherboard Manufacturer Dell Inc. Motherboard Product Name 0KVTCC Motherboard Version A00 Motherboard Serial Number CN7620665L000W Motherboard Asset Tag Not Specified CPU Manufacturer Intel(R) Corporation CPU Version Intel(R) Core(TM) i3-5005U CPU @ 2.00GHz CPU Normal Speed Current Speed: 2000 MHz CPU Max Speed Max Speed: 2000 MHz Memory 3.48 GiB Hard Disk Model SAMSUNG SSD CM871 2.5 7mm 128GB Hard Disk Firmware FXT02D1Q Hard Disk Serial Number S26PNXAH333996 Chassis Manufacturer Dell Inc. Chassis Version Chassis Serial Chassis Asset
System Manufacturer LENOVO System Product 36641Y5 System Version ThinkCentre M72e System Serial Number System UUID c21e5f78-c7a0-11e2-ae45-d2b84f742100 System Type Type: Desktop BIOS Vendor LENOVO BIOS Version F1KT70AUS BIOS Date 06/12/2015 Motherboard Manufacturer LENOVO Motherboard Product Name Motherboard Version NO DPK Motherboard Serial Number Motherboard Asset Tag CPU Manufacturer Intel(R) Corporation CPU Version Intel(R) Core(TM) i5-3330 CPU @ 3.00GHz CPU Normal Speed Current Speed: 3000 MHz CPU Max Speed Max Speed: 3800 MHz Memory 7.60 GiB Hard Disk Model SAMSUNG MZ7PC128HAFU-000L5 Hard Disk Firmware CXM07L1Q Hard Disk Serial Number S11VNSAD408679 Chassis Manufacturer LENOVO Chassis Version Chassis Serial Chassis Asset
System Manufacturer LENOVO System Product 6885DKG System Version ThinkPad Edge E531 System Serial Number System UUID df5a9f01-53e7-11cb-9630-d2fdad1ea42e System Type Type: Notebook BIOS Vendor LENOVO BIOS Version HEET48WW (1.29 ) BIOS Date 03/13/2015 Motherboard Manufacturer LENOVO Motherboard Product Name 6885DKG Motherboard Version 0B98401 PRO Motherboard Serial Number 1ZSGS3CY12A Motherboard Asset Tag Not Available CPU Manufacturer Intel(R) Corporation CPU Version Intel(R) Core(TM) i3-3110M CPU @ 2.40GHz CPU Normal Speed Current Speed: 2400 MHz CPU Max Speed Max Speed: 2400 MHz Memory 3.43 GiB Hard Disk Model KINGSTON SVP200S360G Hard Disk Firmware 501ABBF0 Hard Disk Serial Number 50026B7226009BF5 Chassis Manufacturer LENOVO Chassis Version Chassis Serial Chassis Asset
System Manufacturer LENOVO System Product 80LT System Version Lenovo B50-80 System Serial Number System UUID 357e7bb2-5b76-11e5-90ab-1c394715e364 System Type Type: Notebook BIOS Vendor LENOVO BIOS Version A8CN54WW(V3.07) BIOS Date 09/02/2016 Motherboard Manufacturer LENOVO Motherboard Product Name Lenovo B50-80 Motherboard Version SDK0J40700 WIN Motherboard Serial Number Motherboard Asset Tag NO Asset Tag CPU Manufacturer Intel(R) Corporation CPU Version Intel(R) Core(TM) i3-4005U CPU @ 1.70GHz CPU Normal Speed Current Speed: 1700 MHz CPU Max Speed Max Speed: 1700 MHz Memory 3.77 GiB Hard Disk Model ST500LT012-1DG142 Hard Disk Firmware 0002LVM1 Hard Disk Serial Number W3PLYRC4 Chassis Manufacturer LENOVO Chassis Version Chassis Serial Chassis Asset
System Manufacturer Hewlett-Packard System Product HP x2 210 System Version Type1ProductConfigId System Serial Number System UUID System Type Type: Notebook BIOS Vendor Insyde BIOS Version F.02 BIOS Date 09/11/2015 Motherboard Manufacturer HP Motherboard Product Name 8173 Motherboard Version 35.0A Motherboard Serial Number PBKGK00WB9I08U Motherboard Asset Tag Type2 - Board Asset Tag CPU Manufacturer Intel(R) Corporation CPU Version Intel(R) Atom(TM) x5-Z8300 CPU @ 1.44GHz CPU Normal Speed Current Speed: 1440 MHz CPU Max Speed Max Speed: 1494 MHz Memory 3.78 GiB Hard Disk Model Hard Disk Firmware Hard Disk Serial Number Chassis Manufacturer HP Chassis Version Chassis Serial Chassis Serial Number Chassis Asset Chassis Asset Tag
ystem Manufacturer Hewlett-Packard System Product HP ProBook 4330s System Version A0001D02 System Serial Number System UUID 73c1971f-f974-11de-8224-4cc45f066085 System Type Type: Notebook BIOS Vendor Hewlett-Packard BIOS Version 68SRR Ver. F.63 BIOS Date 04/06/2017 Motherboard Manufacturer Hewlett-Packard Motherboard Product Name 167E Motherboard Version KBC Version 22.26 Motherboard Serial Number PCMED001Y2UAAU Motherboard Asset Tag Not Specified CPU Manufacturer Intel(R) Corporation CPU Version Intel(R) Core(TM) i3-2350M CPU @ 2.30GHz CPU Normal Speed Current Speed: 2300 MHz CPU Max Speed Max Speed: 2300 MHz Memory 3.78 GiB Hard Disk Model Hitachi HTS723232A7A364 Hard Disk Firmware EC2OA60W Hard Disk Serial Number E38345630AYM6N Chassis Manufacturer Hewlett-Packard Chassis Version Chassis Serial Chassis Asset
System Manufacturer TOSHIBA System Product Satellite Pro C660 System Version PSC0RE-01S00EFR System Serial Number System UUID 37ad4484-97b2-e011-9a99-b870f4c7b6c0 System Type Type: Laptop BIOS Vendor TOSHIBA BIOS Version 2.00 BIOS Date 05/09/12 Motherboard Manufacturer TOSHIBA Motherboard Product Name PWWAA Motherboard Version 1.00 Motherboard Serial Number 123456789AB Motherboard Asset Tag Base Board Asset Tag CPU Manufacturer Intel(R) Corporation CPU Version Intel(R) Core(TM) i3 CPU M 370 @ 2.40GHz CPU Normal Speed Current Speed: 2398 MHz CPU Max Speed Max Speed: 4000 MHz Memory 3.65 GiB Hard Disk Model KINGSTON SV300S37A60G Hard Disk Firmware 580ABBF0 Hard Disk Serial Number 50026B774900C327 Chassis Manufacturer TOSHIBA Chassis Version Chassis Serial None Chassis Asset
System Manufacturer TOSHIBA System Product SATELLITE PRO C850-10N System Version PSKC9E-00100SFR System Serial Number System UUID System Type Type: Notebook BIOS Vendor Insyde Corp. BIOS Version 6.80 BIOS Date 10/01/2013 Motherboard Manufacturer Type2 - Board Vendor Name1 Motherboard Product Name Type2 - Board Product Name1 Motherboard Version Type2 - Board Version Motherboard Serial Number Type2 - Board Serial Number Motherboard Asset Tag Type2 - Board Asset Tag CPU Manufacturer Intel(R) Corporation CPU Version Intel(R) Core(TM) i3-2350M CPU @ 2.30GHz CPU Normal Speed Current Speed: 2300 MHz CPU Max Speed Max Speed: 4000 MHz Memory 3.74 GiB Hard Disk Model KINGSTON SVP200S360G Hard Disk Firmware 501ABBF0 Hard Disk Serial Number 50026B722B033A8F Chassis Manufacturer OEM Chassis Manufacturer Chassis Version Chassis Serial OEM Chassis Serial Number Chassis Asset
System Manufacturer System Product System Version System Serial Number System UUID 7a76cd61-5e99-e111-8229-2c27d725b073 System Type Type: Desktop BIOS Vendor Intel Corp. BIOS Version BLH6710H.86A.0160.2012.1204.1156 BIOS Date 12/04/2012 Motherboard Manufacturer Intel Corporation Motherboard Product Name DH67CF Motherboard Version AAG10215-207 Motherboard Serial Number BTCF219009Q9 Motherboard Asset Tag To be filled by O.E.M. CPU Manufacturer Intel(R) Corp. CPU Version Intel(R) Core(TM) i3-2100 CPU @ 3.10GHz CPU Normal Speed Current Speed: 3100 MHz CPU Max Speed Max Speed: 3800 MHz Memory 3.75 GiB Hard Disk Model KINGSTON SVP200S360G Hard Disk Firmware 501ABBF0 Hard Disk Serial Number 50026B72250FA05F Chassis Manufacturer Chassis Version Chassis Serial Chassis Asset
-
@Matthieu-Jacquart Awesome, thanks! From your information it seems like asset tag is pretty useless but motherboard serial is looking great I reckon!
-
@matthieu-jacquart Very nice and detailed information. Thank you !!
-
To help this tread, HP Computer : ProBOOKG2 :
System Manufacturer HP System Product HP ProBook 640 G2 System Version System Serial Number xxxxxxxxxxxxxx System Type Type: Notebook BIOS Vendor HP BIOS Version N76 Ver. 01.07 BIOS Date 04/18/2017 Motherboard Manufacturer HP Motherboard Product Name 80FD Motherboard Version KBC Version 22.6E Motherboard Serial Number xxxxxxxxxxxxxxxxxx Motherboard Asset Tag CPU Manufacturer Intel(R) Corporation CPU Version Intel(R) Core(TM) i5-6200U CPU @ 2.30GHz CPU Normal Speed Current Speed: 2700 MHz CPU Max Speed Max Speed: 8300 MHz Memory 7.66 GiB Hard Disk Model WDC WD5000LPLX-60ZNTT1 Hard Disk Firmware 02.01A02 Hard Disk Serial Number WD-xxxxxxxxxxx Chassis Manufacturer HP Chassis Version Chassis Serial xxxxxxxxxxxxxxx Chassis Asset ```
-
@jonathan-cool said in What can we do when we don't trust UUID?:
Motherboard Serial Number xxxxxxxxxxxxxxxxxx
Is this just masked by hand or really
xxxxxxxxxxxxxxxxxxx
? -
@sebastian-roth Masked
-
@sebastian-roth said in What can we do when we don't trust UUID?:
Is this just masked by hand or really xxxxxxxxxxxxxxxxxxx?
If he actually posted the values, someone could use them to make fake warranty calls and get free replacement parts.