- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We now have 333 machines where CIRA connection is YELLOW.
Can you send me the troubleshooting steps for this.
to remediate I run "ACUConfig deprovision, then restart EMAAgent service" but why does this CIRA corruption keep happening???
Intel EMA seems very flakey!
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello Jools86,
Greetings!
Kindly share the below details:
OS version of the Server:
SQL version:
Location of both; (physical, virtual):
Will they be on the same server machine?
Intel® EMA software version:
FQDN:
Could you please confirm are using CCM/ ACM?
Regards,
Vijay N.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Vijay
Windows Server 2019
SQL Server 2016: 13.0.6419.1
Virtual (in a Datacenter)
1.11.0
ACM
FQDN - confidential
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello Jools86,
Greetings!
Thank you for providing the details. We are currently reviewing the information and we will reach out to you as soon as possible. We request your patience during this time.
Regards,
Vijay N.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello Julian,
I hope this message finds you well.
Following up on our previous discussion, I would like to gather more information to assist you better and provide some additional troubleshooting steps.
- Confirmation of CIRA Connection:
- Could you please confirm if Client Initiated Remote Access (CIRA) was working correctly before the issue started? You mentioned that the issue was resolved after reprovisioning the endpoints while the EMA software on the server side remained unchanged.
- BIOS or Management Engine Driver Update:
- Were there any updates made to the BIOS or the Management Engine driver before this issue began? Knowing this can help us understand if any recent changes might have triggered the problem.
- ECT Logs for Troubleshooting:
For a thorough investigation, could you please provide the ECT logs from an endpoint experiencing issues and from an endpoint that has been fixed?
- Intel® EMA Configuration Tool (ECT)
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,
Vijay N.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Vijay I have run the command: EmaConfigTool.exe" --writexml --filepath "C:\Temp" --verbose
but cannot send results to a public platform. Can you email me so I can end back to you.
As an FYI:
To fix:
- ACuconfig.exe Unconfigure /Full /Adminpassword
- Restart-Service EMAAgent
No recent BIOS update.
CIRA had worked, machines just decided to go YELLOW and we end up finding them in a report.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello Julian,
Greetings!
Thank you for your response. As we are dealing with sensitive data, we will proceed with a web portal case and continue working on the new case. Please share the ECT logs over there in the new case.
Thank you for your cooperation.
Regards,
Vijay N.

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page