PECTAgent unable to register in automation

Products

• Deployment Solution

Issue/Introduction

After booting to preboot OS configured in Deployment Solution, some devices are unable to register with the SMP or receive tasks. A machine record is created in the console showing the correct IP address but no further information. Computer name shows as 'PECTAgent'.

The following are observed in SMP and Pectagent automation logs gathered from the client:

Operation 'Direct: Check URL' completed successfully. 
Operation 'Direct: Connect' completed successfully. 
Operation 'Direct: Head' completed successfully.

Operation 'Direct: Post' failed.
Error code: HTTP status 301: The requested resource was assigned to a new permanent Uniform Resource Identifier (URI), and any future references to this resource should use one of the returned URIs (0x8FA1012D)

Error code: HTTP status 401: The request requires user authentication (0x8FA10191) 
Error note: Authentication failed, server refused to authenticate with the provided credentials or the user account is locked

Environment

DS 8.x

Cause

Computer in automation is sending template values for machine serial number/UUID causing an internal merge or misidentification of the machine.

Pectagent logs showed these generic default template values were being sent for every make/model of the same computer:

    <key name="snboard" value="To be filled by O.E.M."/>
    <key name="uuid" value="00000000-0000-0000-0000-000000000000"/>
    <key name="uuidtrans" value="00000000-0000-0000-0000-000000000000"/>

NOTE: These values are defaults set by the manufacturer for some chipsets. UUID and UUIDTRANS values may vary but are shared on multiple machines when this issue occurs.

Resolution

Since the unique values of each machine are not unique, the Notification Server is unable to properly register the device. There are 3rd party tools that allow setting unique values for 'snboard', 'uuid', 'serial number'. Generally these values are set by the OEM (Original Equipment Manufacturer) and issues with these values should be addressed by the specific vendor.