Proviniong vPro fails on some pcs

[tiweyop382]

Hello,

we have some problems with configuring vPro on some devices.
We have installed Intel® EMA v1.12.2.0 to use a certificate (digicert) to configure vPro in Admin mode.
We have 450+ endpoints in the console and almost 250 of them are working as expected (Provisioning complete and CIRA Connected).

The other 200+ endpoints have some problems and the provisioning doesn't work.
The majority of the hardware is DELL and some LENOVO, we don't have a particular model that doesn't work.
Often we have the same model with the same BIOS version, that on some pcs the provisioning works fine and on some pcs don't...

The EmaAgent.log reports the same thing over and over:

[2024-07-02 01:32:53.305 AM] \Agent\MeshManageability\agent\microstack\ILibAsyncSocket.c:428 internalSocket ERROR: 10035. Last error: 10035

What does it mean?
Do you need some other logs? Questions?

Thanks for your help
Best regards

[Suneesh]

Hello tiweyop382,

Greetings of the day.

Kindly share us the ECT logs.

Intel® EMA Configuration Tool (ECT):

https://www.intel.com/content/www/us/en/download/19805/30485/intel-endpoint-management-assistant-configuration-tool-intel-ema-configuration-tool.html

Installation:

Download and unzip the tool.

Double-click the .msi file and follow the prompts.

Run:

a-Open a command prompt as administrator (alternatively, you can run the tool from Windows PowerShell*).

b-Navigate to the installation folder (default C:\Program Files (x86)\Intel\EMAConfigTool).

c-Run the command: EMAConfigTool.exe --verbose

Regards,

Suneesh

[tiweyop382]

Hello Suneesh,

no problem, see attachment.

[Suneesh]

Hello tiweyop382,

Greetings!

We are currently checking with our internal team on this matter and will provide an update as soon as possible.

Regards,

Suneesh

[Suneesh]

Hello tiweyop382,

I hope this email finds you well.

To assist in resolving the issue you're experiencing, could you please perform the following steps on a non-working system to manually fix the PKI DNS suffix?

1. **Check the PKI DNS Suffix Setting:

  - Go to the non-working machine.

  - Navigate to **Managed Endpoints** in the Intel EMA interface.

  - Capture a screenshot of how the PKI DNS suffix is set.

2. **Verify Inband Agent Functionality:

  - Open the terminal (Command Prompt).

  - Execute the following command:

    ```

    ema>agent -swarmserver

    ```

  - The expected response should include port 8080.

  - If the inband agent is working correctly, the issue is likely related to the PKI DNS suffix configuration.

Could you please provide us with the screenshot of the PKI DNS suffix setting from the EMA interface and confirm the terminal command output? This will help us better understand the situation and provide a more accurate solution.

Thank you for your cooperation. We look forward to your response.

Best regards,

Suneesh

[tiweyop382]

Hello Suneesh,

I don't understand the first question, where can I found the PKI DNS suffix? On the Intel EMA console I don't see it...

And if that it's the problem, how can we set the PKI DNS suffix from remote (without enter in the BIOS Intel MEBx) ?

For the second question you can see the attachment, the pc is able to contact the swarmserver on port 8080

Regards

[vij1]

Hello tiweyop382,

Greetings!

We are currently checking with our internal team on this matter and will provide an update as soon as possible.

Regards,