Cira Not Connected on EMA 1.10.1

[YasserA]

Dear Sir/ Madam,

Around 61 of 394 machines seems to have a Cira Not Connected.

And therefore won't power up via powershell script.

Can you please help us troubleshoot?

Can you please email me an email address and what logs you need?

Kindest regards and many thanks!

Yasser

[MIGUEL_C_Intel]

Hello, Yasser,

Thank you for using Intel community support.

For troubleshooting, we encourage our customers to create an account and send us an email, web case, or chat. I am sending a private email asking for the logs and the EMA configuration.

Regards,

Miguel C.

Intel Customer Support Technician

[YasserA]

Dear Miguel,

Thank you for your patience - I was away.

I have emailed you the logs as requested.

Kindest regards

Yasser

[YasserA]

Dear Miguel,

This is not all due to migration

Initially we were not using Cira on some machines as we thought TLS would work – then we realised TLS won’t work if machines don’t have powered on machine on the subnet

All machines on that subnet will not turn on via script.

So we moved away from TLS and to CIRA

So the machines that are not currently working – are perhaps due to some experimentation to get them working – that failed.

So we need to reset them in some way?

I thought by deploying the emaagent with the parameter -FullInstall would be enough to do this

And initially they do work – and do turn on via powershell script…

But then after a while – they stop working.

The script is taken from the zipped up scripts on your website – with small modifications to make it simpler.

I hope this helps?

We need to know why the cira connection gets lost or corrupted? And how to permanently fix this.

Kindest regards

Yasser

[YasserA]

Dear Miguel,

We get the following error via our scripts on machines that don't have Cira Connected:

VERBOSE: REST Error Status: 409 Conflict
Invoke-WebRequest : {"Message":"{\"ExtendedCode\":2022,\"ExtendedMessage\":\"Endpoint is not ready to execute this
operation yet, please wait and retry\"}"}

What does Error Status 409 Conflict mean?

I was hoping this may help troubleshoot?

Kindest regards

Yasser

[YasserA]

Also might be useful - clients have this:

[2023-07-06 02:53:41.174 PM] \Agent\MeshManageability\agent\core\meshctrl.c:1143 Packet is not encrypted correctly or uses an old key. Last error: 0

[Eduardo_B_Intel]

Hello Yeser,

I wish you an excellent day, Sir.

Here are some responses to your current questions. 

1- This is still pending and will be answered soon. 

2- Records do get deleted. The ECT Tool removes the endpoint and configuration, but the endpoints stay within server and you'll have to stop managing them. 

3- No, the Suffix is not removed, if it was done manually in the Mebx, the tool should not deleted it. 

4- This one is also pending and still under review. 

5- This should not affect. Would it be possible for you to show us the settings being used and how this relates to the EMA profile. The AMT version should not affect here since the certificate is the one making

the connection. Where other tested newer versions shown different results?

As soon as you share those details in regards to the last question. I'll proceed to check back with my team to answer what is pending, Sir. 

[Eduardo_B_Intel]

Hello Yeser,

This is a follow up to check if you have been able to gather the requested information so the case moves forward.

[Eduardo_B_Intel]

Hello Yeser,

This is a follow up to check if you have been able to gather the requested information so the case moves forward. I will wait and follow up again within the next 3 business days, on 08/17/2023