Primary Lookup Key And Virtual Connect
Article: 189
Applies to: Release 3.80 or greater
In previous releases, to determine if a computer existed in the database:
| • |
The PXE Server used the MAC Address retrieved by the PXE bootstrap code.
|
| • |
The Deployment Engine used the user-defined Primary Lookup Key, either MAC Address,
Serial Number, UUID, or Asset Tag. The latter three fields are retrieved by the agent from SMBIOS.
|
In 3.80, Altiris has made the following improvements:
| • |
The PXE bootstrap code now retrieves all four fields.
|
| • |
The PXE Server uses the same matching algorithm as the Deployment Engine.
|
| • |
The Primary Lookup Key can now be a combination of the four fields, e.g. Serial Number + MAC Address.
|
For RDP customers, MAC Address must be one of the Primary Lookup Key fields for the following reasons:
| • |
Integrity servers don't have SMBIOS.
|
| • |
For RDP releases 3.81 and earlier, in newer ProLiant servers the SMBIOS has been located higher in memory where the 16-bit PXE bootstrap code can't access it.
|
When using Virtual Connect virtual identifiers,
| • |
Blade rip-and-replace functionality will not work. Virtual identifiers are designed to enable server movement as opposed to in-place server replacement.
|
| • |
HP strongly recommends virtualizing all of the identifiers, not just some. Doing so will eliminate duplicate server entries in the console and database.
|
|
Printable version
