- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Good morning,
we are having a really strange problem. We have a perfectly functioning EMA Server with 6 AMT Clients connected; CIRA OK.
From the same SERVER, with the same agent, we tried to deploy new clients, CIRA does not connects.
Analyzing the client side problem, we notice that the IP of the ema server in the CIRA section is wrong, unknown, never entered anywhere.
How is this possible? in the attached example "OK" = correct client settings --> "CIRA SERVER=ema-server"; example "KO" = client with fake IP in the "CIRA Server" filed.
Where does that IP come from? How is it possible that with the same agent, same network conditions, and the same procedure something like this happens?
The ip of ema-server is 10.222.16.165
The ip that is shown in the "KO" client for CIRA server field is 10.46.7.198 ? what is this ?
Thanks a lot
Marco
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Good morning and many thanks again for the support doned.
I' ve understood that in the air was floating bigger problems ...so i ve make from scrartch a brand new ema-server and reprovision all clients again ... all works ok.
Why a fake IP has taken the control of my ema server as a ghost .. probably no one knows ..
For now i thank you so much again and go ahed; you can close all my tickets.
BR
Marco dB
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello SIOSYS,
Good day.
Thank you for sharing the ECT logs from the two endpoints. Upon review, we observed that both systems are running Microsoft Windows Server 2019 Standard. However, as per the Intel® EMA prerequisites, supported operating systems for endpoints are Windows 10 and Windows 11.
You can refer to Section 1.2 – Supported Operating Systems on page 11 of the Intel EMA Installation Guide here:
To proceed, please share the following from both endpoints:
- A screenshot of the General tab
- A screenshot of the Hardware Manageability tab from the Intel EMA console
Once the endpoints meet the supported OS requirements, please perform the following actions:
- Update the BIOS: https://www.dell.com/support/home/en-in/drivers/driversdetails?driverid=mwyxy&oscode=w2021&productcode=optiplex-7060-desktop
- Update the Intel Management Engine (ME) Driver for Windows 10 & 11: https://www.intel.com/content/www/us/en/download/682431/intel-management-engine-drivers-for-windows-10-and-windows-11.html
- Update the Network Card Driver
After completing the above steps, please check the CIRA connection status. If the issue persists, kindly share the latest ECT logs from both endpoints for further analysis.
Note:
As a stand-alone application, the Intel® EMA Agent supports installation on:
- Microsoft Windows 10
- Microsoft Windows 11
The Intel® EMA Server supports:
- Microsoft Windows Server 2019
- Microsoft Windows Server 2022
Crypto for Intel ME 11 systems is disabled by default on Windows Server 2022.
Let us know if you need any assistance with these steps.
Regards,
Suneesh S
Intel Customer Support Technician
intel.com/vPro
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Good morning and thank you in advance for the fast answer.
"However, as per the Intel® EMA prerequisites, supported operating systems for endpoints are Windows 10 and Windows 11." --> We know it, but it seems to works correctly anyway. However, I think that our issue - in this case - is not related to OS.
Attached for both clients (sample of an OK client and sample fo an OK client).
- A screenshot of the General tab
- A screenshot of the Hardware Manageability tab from the Intel EMA console
"Once the endpoints meet the supported OS requirements, please perform the following actions" --> some clients are HP not DELL, on a DELL sample KO Client we had:
- updated BIOS
- updated ME
- update NET Drivers (MW10 Drivers Works on MWS2019)
Same issue. Attached new ECT Logs on that updated client.
For clarety, the issue is that: for some unkow reason on some unprovisioned client, when we install the EMAAgent, in the CIRA SERVER filed of the AMT is pushed (or from the installer or from the Server during the provisioning stage) an UNKOW IP (10.46.7.198) that we don't know it comes from. Address of the EMA-SERVER is 10.222.16.165. On the "OK" clients in that flied was correctly pushed the DNS name of the EMA-SERVER "ema-server" and CIRA works.
It is quite strange that in an UNKNOW IP is pushed in the AMT, instead before, the correct dns name of the ema server was pushed. Nothing is changed and dns resolution on KO clients correclty point to the right IP.
It is possibile to manually edit on the AMT of the KO clients the CIRA SERVER Filed (under cira information) to make it point to the right dns EMA-SERVER name and make CIRA works again?
EMAAgent.exe / .msh attached for inspection (7z)
Many thanks again
Marco dB
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Good morning and thank you in advance for the fast answer.
"However, as per the Intel® EMA prerequisites, supported operating systems for endpoints are Windows 10 and Windows 11." --> We know it, but it seems to works correctly anyway. However, I think that our issue - in this case - is not related to OS.
Attached for both clients (sample of an OK client and sample fo an OK client).
- A screenshot of the General tab
- A screenshot of the Hardware Manageability tab from the Intel EMA console
"Once the endpoints meet the supported OS requirements, please perform the following actions" --> some clients are HP not DELL; on a DELL sample KO Client we had:
- updated BIOS
- updated ME
- update NET Drivers (MW10 Drivers Works on MWS2019)
Same issue. Attached new ECT Logs on that updated client.
For clarety, the issue is that: for some unkow reason on some unprovisioned client, when we install the EMAAgent, in the CIRA SERVER filed of the AMT is pushed (or from the installer or from the Server during the provisioning stage) an UNKOW IP (10.46.7.198) that we don't know it comes from. Address of the EMA-SERVER is 10.222.16.165. On the "OK" clients in that flied was correctly pushed the DNS name of the EMA-SERVER "ema-server" and CIRA works.
It is quite strange that in an UNKNOW IP is pushed in the AMT, instead before, the correct dns name of the ema server was pushed. Nothing is changed and dns resolution on KO clients correclty point to the right IP.
It is possibile to manually edit on the AMT of the KO clients the CIRA SERVER Filed (under cira information) to make it point to the right dns EMA-SERVER name and make CIRA works again?
EMAAgent.exe / .msh attached for inspection (7z)
Many thanks again
Marco dB
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Good morning and thank you in advance for the fast answer.
"However, as per the Intel® EMA prerequisites, supported operating systems for endpoints are Windows 10 and Windows 11." --> We know it, but it seems to works correctly anyway. However, I think that our issue - in this case - is not related to OS.
Attached for both clients (sample of an OK client and sample fo an OK client).
- A screenshot of the General tab
- A screenshot of the Hardware Manageability tab from the Intel EMA console
"Once the endpoints meet the supported OS requirements, please perform the following actions" --> some clients are HP not DeLL, on a DELL sample KO Client we had:
- updated BIOS
- updated ME
- update NET Drivers (MW10 Drivers Works on MWS2019)
Same issue. Attached new ECT Logs on that updated client.
For clarety, the issue is that: for some unkow reason on some unprovisioned client, when we install the EMAAgent, in the CIRA SERVER filed of the AMT is pushed (or from the installer or from the Server during the provisioning stage) an UNKOW IP (10.46.7.198) that we don't know it comes from. Address of the EMA-SERVER is 10.222.16.165. On the "OK" clients in that flied was correctly pushed the DNS name of the EMA-SERVER "ema-server" and CIRA works.
It is quite strange that in an UNKNOW IP is pushed in the AMT, instead before, the correct dns name of the ema server was pushed. Nothing is changed and dns resolution on KO clients correclty point to the right IP.
It is possibile to manually edit on the AMT of the KO clients the CIRA SERVER Filed (under cira information) to make it point to the right dns EMA-SERVER name and make CIRA works again?
EMAAgent.exe / .msh attached for inspection (7z)
Many thanks again
Marco dB
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Good morning and thank you in advance for the fast answer.
"However, as per the Intel® EMA prerequisites, supported operating systems for endpoints are Windows 10 and Windows 11." --> We know it, but it seems to works correctly anyway. However, I think that our issue - in this case - is not related to OS.
Attached for both clients (sample of an OK client and sample fo an OK client).
- A screenshot of the General tab
- A screenshot of the Hardware Manageability tab from the Intel EMA console
"Once the endpoints meet the supported OS requirements, please perform the following actions" --> some clients are HP not DeLL, on a DELL sample KO Client we had:
- updated BIOS
- updated ME
- update NET Drivers (MW10 Drivers Works on MWS2019)
Same issue. Attached new ECT Logs on that updated client.
For clarety, the issue is that: for some unkow reason on some unprovisioned client, when we install the EMAAgent, in the CIRA SERVER filed of the AMT is pushed (or from the installer or from the Server during the provisioning stage) an UNKOW IP (10.46.7.198) that we don't know it comes from. Address of the EMA-SERVER is 10.222.16.165. On the "OK" clients in that flied was correctly pushed the DNS name of the EMA-SERVER "ema-server" and CIRA works.
It is quite strange that in an UNKNOW IP is pushed in the AMT, instead before, the correct dns name of the ema server was pushed. Nothing is changed and dns resolution on KO clients correclty point to the right IP.
It is possibile to manually edit on the AMT of the KO clients the CIRA SERVER Filed (under cira information) to make it point to the right dns EMA-SERVER name and make CIRA works again?
EMAAgent.exe / .msh attached for inspection (7z)
Many thanks again
Marco dB
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Good morning and thank you in advance for the fast answer.
"However, as per the Intel® EMA prerequisites, supported operating systems for endpoints are Windows 10 and Windows 11." --> We know it, but it seems to works correctly anyway. However, I think that our issue - in this case - is not related to OS.
Attached for both clients (sample of an OK client and sample fo an OK client).
- A screenshot of the General tab
- A screenshot of the Hardware Manageability tab from the Intel EMA console
"Once the endpoints meet the supported OS requirements, please perform the following actions" --> some clients are HP not DeLL, on a DELL sample KO Client we had:
- updated BIOS
- updated ME
- update NET Drivers (MW10 Drivers Works on MWS2019)
Same issue. Attached new ECT Logs on that updated client.
For clarety, the issue is that: for some unkow reason on some unprovisioned client, when we install the EMAAgent, in the CIRA SERVER filed of the AMT is pushed (or from the installer or from the Server during the provisioning stage) an UNKOW IP (10.46.7.198) that we don't know it comes from. Address of the EMA-SERVER is 10.222.16.165. On the "OK" clients in that flied was correctly pushed the DNS name of the EMA-SERVER "ema-server" and CIRA works.
It is quite strange that in an UNKNOW IP is pushed in the AMT, instead before, the correct dns name of the ema server was pushed. Nothing is changed and dns resolution on KO clients correclty point to the right IP.
It is possibile to manually edit on the AMT of the KO clients the CIRA SERVER Filed (under cira information) to make it point to the right dns EMA-SERVER name and make CIRA works again?
EMAAgent.exe / .msh attached for inspection (7z)
NOTE: FROM EMAServerLog-Manageability
2025-05-12 12:20:03.4524|INFO||3488|24|PerformRound2Provisioning - MeshManageabilityServer.CentralManageabilityServer, EMAManageabilityServer, Version=1.14.2.0, Culture=neutral, PublicKeyToken=57d11e903ea1ca2c - [1] - Adding remote access server (ema-server:8080, 3) : (mearvideo,B29CC8B2).
2025-06-30 10:57:02.3095|INFO||7068|59|PerformRound2Provisioning - MeshManageabilityServer.CentralManageabilityServer, EMAManageabilityServer, Version=1.14.2.0, Culture=neutral, PublicKeyToken=57d11e903ea1ca2c - [1] - Adding remote access server (10.46.7.198/ema-server:8080, 3) : (AGARVIDEO,79B30671).
On the Server Side we haven't touch nothing; just leave the VM active.
How is possibile this?
Many thanks again
Marco dB
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Good morning and thanks in advace for the fast answer.
"supported operating systems for endpoints are Windows 10 and Windows 11." --> We know it, usually it works good anyway.
I think that the kind of problme we are encountering is not realated to OS (6 clients are working well, new 5 clinets are not working with the same issue related to the "fake" IP of the cira server pushed in from we donw know where).
Attached for both sample client (OK and KO):
- A screenshot of the General tab
- A screenshot of the Hardware Manageability tab from the Intel EMA console
For "Update the BIOS" --> some clients are HP not DELL --> on a "KO" DELL Client we had:
- updated the BIOS
- updated ME
- updated the Net Driver (MW10 Drivers works on MWS2019)
Same issue. Attached new ECT Logs for an updated client.
For clarety, the issue - on 5 different clients - is that: when we run the EMAAgent.exe / .msh in the CIRA Server filed of the Clients (AMT) is pushed an IP (10.46.7.198) that we don' t know from where is taken (EMA Server is 10.222.16.165). From these client dns resolution of ema-server correct reach 10.222.16.165. In band monitoring correctly works. CIRA obviusly not.
With the same EMAAgent.exe / .msh - previously - on different 6 Client in that Filed of AMT (CIRA SERVER) was correctly pushed the name "ema-server".
Is there a way for manually modify that field in amt to get CIRA works ? the CIRA Server Filed on AMT needs to be corrected from 10.46.7.198 (unknow IP) to ema-server (correct dns name of the EMA SERVER that usually was pushed in the clients "before").
It is quite strage that an unknow IP is pushed from the installer or from the EMA server in the "provisiong operations" in the "CIRA Server Filed" (under *** CIRA Information ***) of an AMT ... in-band functionallity (from OS) correctly works.
Attached also EMAAgent.exe / .msh for inspection (7z)
Many thanks again
Marco dB
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello SIOSYS,
Thank you sharing the details.
We see that you have updated the ME driver as per our request, however the BIOS update has not been done which is a critical update and still is on the same version, according to the new ECT shared.
Intel recommends following the prerequisites and keep the firmware and the drivers to the latest as a best practice, which has been tested in our environment, else the setup might or might not work.
Hence kindly update the BIOS of the machine KO (AGRIM1), to the latest through the download link given below for test purpose and share us the new ECT log once done.
Note: Please notice that this is a critical update and the working endpoint OK (VAARVIDEO) is running upon the version 1.30.0. Whereas KO (AGRIM1) 1.2.17.
Additionally, could you please confirm which version of Intel® EMA you are currently using.
Once done, we can go ahead and check upon the change in IP address of the CIRA server.
We appreciate your cooperation and understanding.
Regards,
Suneesh S
Intel Customer Support Technician
intel.com/vPro
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello, thanks again form the support.
Test Client in KO is now up to date.
EMA Server is latest (Intel® EMA v1.14.2.0)
However the issue is not client side (also because AGRIM1 is one of 5 clients that have the same issue)
See this: https://community.intel.com/t5/Intel-vPro-Platform/Round2Provisioning-ISSUE-UNKNOW-IP/td-p/1700872
The issue is in the "Round2Provisioning" commited by the server to the client.
But, as said, on the server we have not touch anything from the successfully installation of the first 6 OK clients, just leave it powered on in idle. That UNKNOW ip on the server side do not exist anywhere, and the dns resolution works great from client to server and in reverse.
Many thanks again.
BR
Marco dB
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello SIOSYS,
Thank you for the update.
As per the ECT, we believe that there could be an existence of a second EMA instance, please let us know how many EMA servers and DNS has been used, it would be great if you can share us the network diagram of the Intel EMA environment.
We would suggest you gather the endpoint group and the AMT profile from working profile.
Then proceed with the following steps:
- Access the Intel® Endpoint Management Assistant (Intel® EMA) using your tenant credentials.
- From the left toolbar, select Endpoints.
- Click View next to the endpoint you wish to unprovision.
- Under Actions, select Stop managing the Endpoint.
- In the new window, choose Remove Provisioning (first option at the bottom).
- Access the endpoint, uninstall and delete the old agent files, and then restart the system.
- During the reboot, press Ctrl + P to enter MEBx, log in, and perform a full unprovision.
- Download the agent file from the working machine, reinstall it on the endpoint, and allow around 5 minutes for CIRA to connect.
Once done, kindly generate the latest ECT logs and also share the FQDN with us.
Regards,
Suneesh S
Intel Customer Support Technician
intel.com/vPro
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Good morning and many thanks again for the support doned.
I' ve understood that in the air was floating bigger problems ...so i ve make from scrartch a brand new ema-server and reprovision all clients again ... all works ok.
Why a fake IP has taken the control of my ema server as a ghost .. probably no one knows ..
For now i thank you so much again and go ahed; you can close all my tickets.
BR
Marco dB
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello SIOSYS,
Thank you for your response.
As requested, we will proceed to close this case. If you need any further assistance in the future, please don’t hesitate to reach out.
Best regards,
Suneesh S
Intel Customer Support Technician
intel.com/vPro
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page