- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Good Morning,
related to https://community.intel.com/t5/Intel-vPro-Platform/INTEL-EMA-CIRA-IP-FAKE-ADDRESS/m-p/1700645#M13031 i ve notice that FROM EMAServerLog-Manageability:
Client OK:
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).
CLIENT KO:
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).
For clarety, the issue is that: for some unknow reasons on all the new unprovisioned clients, when we install the EMAAgent, in the CIRA SERVER filed of the AMT is pushed an UNKNOW IP (10.46.7.198) --> see "Adding remote access server"
Previously was pushed the right dns name of ema-server "EMA-SERVER" ; so on all the new provisioned clients CIRA dont works.
NOTE that the only one IP that the EMA-SERVER has is: 10.222.16.165 and provisioning metod selected in the installation process of the ema server was FQDN only
It is quite strange that an UNKNOW IP is pushed in the AMT as remote access server, instead before, the right dns name of the ema server was pushed in.
Nothing is changed on the Server by our hands. Just leaved it powered on in Idle. EMA-Server OS is MWS2019.
Where can we correct or fix this wrong field for a right client provisioning ?
Many Thanks
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello SIOSYS,
As confirmed the issue is resolved in below mentioned thread after setting up a new EMA server and reprovisioning the clients resolved the issue. We will proceed to close this thread.
Solved: INTEL EMA - CIRA IP FAKE ADDRESS - Intel Community
Regards,
Suneesh S
Intel Customer Support Technician

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