EMA CIRA connect fail

[evenlin1]

I’ve set up a local EMA server and trying to connect a DUT to it for AMT testing. According to the documentation, I was able to provision the DUT successfully via EMA, but it fails to connect to CIRA.

Using the EMAConfigTool, I found that the AMT IP address was not assigned—it's also showing as 0.0.0.0 in the AMT Web UI.

However, if I manually provision the DUT by MEBX not EMA, the AMT IP will get assigned correctly and can access DUT via the AMT Web UI. Despite this, the CIRA connection still fails in EMA.

Could you help me figure out what’s causing the issue? Thank you!

[evenlin1]

Update EMAconfigtool logs

[vij1]

Hello evenlin1,

Thank you for reaching out to Intel.

To assist you effectively with your Intel® Endpoint Management Assistant (EMA) setup, we kindly request the following information:

1.     Operating System version of the server

2.     SQL Server version

3.     Deployment type of both the EMA server and SQL server (Physical or Virtual)

4.     Will the EMA and SQL servers be hosted on the same machine?

5.     Authentication mode to be used: Local, Azure AD, or Windows AD

6.     Intel® EMA software version you plan to use

7.     Number of endpoints to be provisioned

8.     Location of endpoints: Local or Remote

9.     Endpoint brand name and model

10.  Intel® AMT (ME) version

11.  BIOS version

Additionally, as you mentioned manually provisioning the endpoint via MEBx:

If provisioning was previously done using MEBx or another method, there may be stale or conflicting provisioning records or PKI DNS suffixes. We recommend unprovisioning the endpoint from MEBx and then reprovisioning the machine to ensure a clean setup.

Please provide the above details at your earliest convenience so we can proceed further.

Best regards,

Vijay N

Intel Customer Support

[evenlin1]

1.     Operating System version of the server

- windows 11 22621 

2.     SQL Server version

- SQL server 2022

3.     Deployment type of both the EMA server and SQL server (Physical or Virtual)

- Physical 

4.     Will the EMA and SQL servers be hosted on the same machine?

- yes

5.     Authentication mode to be used: Local, Azure AD, or Windows AD

- Local 

6.     Intel® EMA software version you plan to use

 - 1.14.3

7.     Number of endpoints to be provisioned

- 1

8.     Location of endpoints: Local or Remote

- in the same network

9.     Endpoint brand name and model

- ARL H

10.  Intel® AMT (ME) version

- 18.1.18.2616

11.  BIOS version

- Intel Reference Code : 0D.00.E4.40

If provisioning was previously done using MEBx or another method, there may be stale or conflicting provisioning records or PKI DNS suffixes. We recommend unprovisioning the endpoint from MEBx and then reprovisioning the machine to ensure a clean setup.

- Yes, i know nedd to unprovision target for EMA remote provision process. As first post picture, you can saw the targer can be provisioned via ema but cannot connect to CIRA.  Seems AMT IP didn't be deployed via ema from emaconfigure tool logs.

[vij1]

Hello Evenlin,

Greetings!

Thank you for sharing the requested details. Your environment setup looks mostly fine. However, we noticed that CIRA is not connected.

We observed that your server's operating system is Windows 11. Please note that Windows 11 has not been tested in our environment, and therefore, it may not be fully compatible with Intel® EMA.

As per the prerequisites outlined in the Intel® EMA Server Installation Guide (Section 1.2), we recommend installing one of the following supported operating systems:

·       Microsoft Windows Server 2019

·       Microsoft Windows Server 2022

·       Microsoft Windows Server 2025

You can refer to the official installation guide here:

https://www.intel.com/content/www/us/en/content-details/841803/intel-endpoint-management-assistant-intel-ema-server-installation-and-maintenance-guide.html

Note:

·       The getPFX API requires the Intel® EMA server to be installed on Windows Server 2019 or later.

·       Crypto for Intel ME 11 systems is disabled by default on Windows Server 2022.

Please consider updating your server OS to one of the supported versions to ensure full compatibility and functionality.

Best regards,

Vijay N

Intel Customer Support

[evenlin1]

Hi,

I install a new EMA server to windows server 2019 but still cannot connect CIRA. 

[vij1]

Hello Evenlin1,

Thank you for your response. We appreciate your efforts in installing Windows Server 2019 and for providing the endpoint details.

To help mitigate the issue, we kindly request you to follow the plan of action below and share the results with us:

Step-by-Step Instructions

1.     Unmanage the Endpoint from EMA Console

·       Log in to the Intel® EMA web console as Tenant Admin.

·       Navigate to Endpoints.

·       Locate the endpoint PTOP-JNNNI4TK and click View.

·       Click on Actions > Stop Managing Endpoint > Take Action.

2.     Uninstall the EMA Agent from the Endpoint

·       Log in to the endpoint.

·       Right-click on the EMA agent installer and select Run as Administrator.

·       Choose to Uninstall the agent.

·       After uninstallation, delete the agent files from the system.

3.     Unprovision the Endpoint from MEBx

·       Reboot the endpoint.

·       During boot, press Ctrl + P to enter MEBx.

·       Perform a Full Unprovision of the endpoint.

4.     Create a New Endpoint Group and AMT Profile

·       In the EMA console, create a new Endpoint Group and a new Intel® AMT Profile.

·       Configure the AMT Profile with the following settings:

·       General: Select Always use Intel AMT CIRA

·       Power States: Select Any time system is connected to power

·       Management Interfaces: Enable KVM, Web-Based UI, Serial Over LAN

·       FQDN Source: Select Shared with Host OS

·       IP Address: Select From the DHCP Server

·       Wi-Fi:

·       Enable Synchronize with host platform Wi-Fi profiles

·       Enable Wi-Fi connection in all system states (S1–S5)

·       Save the profile.

5.     Apply the Profile and Reinstall the Agent

·       Go to the Endpoint Group > Actions > View Configuration > Intel® AMT Auto Setup.

·       Select the new AMT profile, then Save.

·       Generate and download the new EMA agent files.

·       Install the agent on the endpoint.

6.     Verify and Share Status

·       Wait a few minutes after installation.

·       Check the endpoint status in EMA.

·       If CIRA is connected, it should appear in green or yellow.

·       Please share a screenshot of the status with us.

Best regards,

Vijay N

Intel Customer Support

[evenlin1]

Hi 

I follow your step but not work... CIRA still no connect...

attached emaconfig log

[vij1]

Hello Evenlin1,

Greetings!

Thank you for your response.

We kindly request you to update the Intel® Management Engine (ME) drivers to the latest version and then check whether CIRA is showing as connected.

You can download the latest ME drivers from the link below:

https://www.intel.com/content/www/us/en/download/682431/intel-management-engine-drivers-for-windows-10-and-windows-11.html

Additionally, please share the Intel® System Support Utility (SSU) logs with us. These logs provide valuable system information including OS, memory, processor, system type, display adapter(s), board information, network adapters (wired and wireless), and storage details.

For instructions on how to generate SSU logs, please refer to the guide below:

https://www.intel.com/content/www/us/en/support/articles/000057926/memory-and-storage.html

Looking forward to your update.

Best regards,

Vijay N

Intel Customer Support

[Suneesh]

Hello Evenlin1,

We are following up on this case.

If further assistance is necessary, please do not hesitate to reply.

Regards,

Suneesh S

Intel Customer Support Technician

intel.com/vpro

[vij1]

Hello Evenlin1,

If further assistance is necessary, please do not hesitate to reply.

Regards,

Vijay N

Intel Customer Support Technician

intel.com/vpro

[evenlin1]

Hi,

Sorry for the late reply! I found that when the target device receives its IP address through the router’s DHCP, it fails to connect to CIRA. However, when I configure both DHCP and DNS on the Windows Server (instead of using the router), CIRA connects successfully.

[vij1]

Hi evenlin1,

Thank you for your response and for sharing your findings.

It’s great to hear that configuring DHCP and DNS on the Windows Server resolved the CIRA connectivity issue. If further assistance is necessary, please do not hesitate to reply — we’re here to help!

Best regards,

Vijay N

Intel Customer Support