Record Duplication When Booting To Automation Using External NICs

Products

• Deployment Solution

Issue/Introduction

Customer boots an unknown computer that doesn't have an internal NIC into automation using a docking station.(Surface Pro laptops etc).  The MAC address of the docking station is reported to the NS and the record is created.

The machine is then sent out to the employee's desk and needs to be imaged again.  At the employee's desk a USB dongle is used to connect the computer to the Notification server. The machine is booted into automation and because the USB dongle has a separate MAC address, a new record is created.

There is no error other than a separate record created.  See below.

Environment

DS 8.x

Cause

In automation the pectagent reports numerous unique values.  For example:

 

Creating hash..

MACAddress=00-50-56-05-FE-A9

[UUID+BoardSerialNumber+MAC] ComputerFingerprintHash=iBeHA277Jj91ixQdNAcCWA==

[Transmuted_UUID+BoardSerialNumber+MAC]

ComputerFingerprintHash=h7b5RwPRV8Os7+DhpVMDdg==

[UUID+BoardSerialNumber_Blank+MAC] ComputerFingerprintHash=sU2Fqag9oObWw7qDEEQVzw==

[Transmuted_UUID+BoardSerialNumber_Blank+MAC]

ComputerFingerprintHash=oVYnulvfsaas1cnUAA3QOg==

BiosSerialNumber and BoardSerialNumber both are different.

[UUID+BiosSerialNumber+MAC] ComputerFingerprintHash=vogWEmAVs92Cq00TceSn4A==

[Transmuted_UUID+BiosSerialNumber+MAC]

ComputerFingerprintHash=jYoQO4qh1dulLJr6jdaWBw==

[UUID+BiosSerialNumber_Blank+MAC] ComputerFingerprintHash=sU2Fqag9oObWw7qDEEQVzw==

ComputerFingerprintHash sU2Fqag9oObWw7qDEEQVzw== is already present 

[Transmuted_UUID+BiosSerialNumber_Blank+MAC]

ComputerFingerprintHash=oVYnulvfsaas1cnUAA3QOg==

ComputerFingerprintHash oVYnulvfsaas1cnUAA3QOg== is already present 

[Individual ID] BIOS SerialNumber = VMware-42 39 ee de 85 d1 ca 53-6f 53 11 e8

20 30 ee b7

[Individual ID] Board SerialNumber = None

[Individual ID] UUID = DEEE3942-D185-53CA-6F53-11E82030EEB7

[Individual ID] Transmuted UUID = 4239EEDE-85D1-CA53-6F53-11E82030EEB7

GetAdaptersInfo() returned a result of '111' when initialized.

[Individual ID] MACAddress= 00-50-56-05-FE-A9

 

 

 

SQL Server ResourceKey table:

42F4551C-B5EF-43C1-BDA5-82D014D62463 distinguishedname 

CN=CL-W7-X64-01,CN=COMPUTERS,DC=EPM,DC=LOCAL

42F4551C-B5EF-43C1-BDA5-82D014D62463 fqdn            CL-W7-X64-01.EPM.LOCAL

42F4551C-B5EF-43C1-BDA5-82D014D62463 name.domain    CL-W7-X64-01.EPM

42F4551C-B5EF-43C1-BDA5-82D014D62463 uniqueid    H7B5RWPRV8OS7+DHPVMDDG==

42F4551C-B5EF-43C1-BDA5-82D014D62463 uniqueid    IBEHA277JJ91IXQDNACCWA==

42F4551C-B5EF-43C1-BDA5-82D014D62463 uniqueid    JYOQO4QH1DULLJR6JDAWBW==

42F4551C-B5EF-43C1-BDA5-82D014D62463 uniqueid    OVYNULVFSAAS1CNUAA3QOG==

42F4551C-B5EF-43C1-BDA5-82D014D62463 uniqueid    SU2FQAG9OOBWW7QDEEQVZW==

42F4551C-B5EF-43C1-BDA5-82D014D62463 uniqueid VOGWEMAVS92CQ00TCESN4A==

 

These multiple unique values should be used to make a match regardless of different MAC addresses.  Matching by these other unique values is not currently taking place.

 

DSUniqueID in the registry was introduced in 8.5 RU2 to resolve the issue with shared USB ethernet devices.

Resolution

Solution: Symantec has resolved the issue in 8.5 RU2.