Changeing GUID number on systemboard

GUID is a Windows function not a motherboard Number. Its associated with digital rights management certificates and specific installs of software.

Short for Globally Unique Identifier, a unique 128-bit number that is produced by the Windows OS or by some Windows applications to identify a particular component, application, file, database entry, and/or user. A GUID is also used in a Windows registry to identify COM DLLs. Knowing where to look in the registry and having the correct GUID yields a lot information about a COM object (i.e., information in the type library, its physical location, etc.). Windows also identifies user accounts by a username (computer/domain and username) and assigns it a GUID. Some database administrators even will use GUIDs as primary key values in databases.

GUIDs can be created in a number of ways, but usually they are a combination of a few unique settings in internet explorer or windows media player based on specific point in time (e.g., an IP address, network MAC address, clock date/time, etc.).

There is no such thing as a motherboard GUID.

Im telling you, i´m 1000% sure.

Ther is a GUID number present in the hardware

When you try to boot with the networkadapter(pxe) the following numbers display

Mac adress

GUID number

Sorry

 

Speedstep,

 

Could it be that Dell ties the OEM Windows that they sell to the motherboards?

@pjdebusser wrote:

 Im telling you, i´m 1000% sure.

Ther is a GUID number present in the hardware

When you try to boot with the networkadapter(pxe) the following numbers display

Mac adress GUID number Sorry

---

 

PXE GUID 128-bit (32 hex digits) globally unique identifier
Located in PXE BIOS or dynamically created from Ethernet MAC address by adding 0’s to front or Ethernet address .

With dell this is sometimes called

SMBIOS GUID during the PXE boot process

This is still a WINDOWS RIS issue.

 

If the ADS PXE service responds to the device, it sends the device a DHCPOFFER message with the IP address of the ADS PXE service so that the device can request the Startnbs network boot program from the TFTPD service. On the device, Startnbs requests boot instructions from the ADS PXE service, which relays the request to the Controller. The Controller sends the PXE boot instructions to the ADS PXE service, which relays them to the device, only if the Controller can match the device's SMBIOS GUID or MAC address to an existing device record, or if the Controller is configured to add a new device record if the device is not listed in the Controller database.

http://www.microsoft.com/technet/prodtechnol/windowsserver2003/proddocs/ads/nbs_boot_policy_overview.asp