Home Neural Network Unable to hook up with a Swarm Server – Failed PKI provisioning

Unable to hook up with a Swarm Server – Failed PKI provisioning

0
Unable to hook up with a Swarm Server – Failed PKI provisioning

[ad_1]

Hello,

Undecided the place to go from right here as I am at a little bit of a useless finish having tried nearly every thing I might consider. I am certain I had PKI provisioning (with CIRA) working at one level, however in the meanwhile none of my shoppers are in a position to provision.

The 2 notable entries within the EMALog-ManageabilityServer.txt log are “Error:Unable to hook up with a Swarm Server” and “Failed PKI provisioning”. I went down the rabbit gap of assuming it was a PKI difficulty, however now I am pondering there’s some difficulty associated to not having the ability to connect with the Swarm Server which is inflicting PKI provisioning to fail.

Be aware, within the log entries under, the home windows area has been subsituted with `.native` and the general public area has be substitured with `my.area.native`. Intel EMA server and Intel vPro suitable certificates is utilizing area `intelema.my.area.com`, and PKI DNS suffix has been configured within the BIOS of all computer systems as `my.area.com` 

Related log extract follows:

 

 

2024-01-30 12:18:36.8294|INFO||4728|23|AttemptPhase1_Pki - MeshManageabilityServer.CentralManageabilityServer, EMAManageabilityServer, Model=1.12.1.0, Tradition=impartial, PublicKeyToken=57d11e903ea1ca2c - [1] - Trying section 1 PKI provisioning : (M104,6FA481CF). 
2024-01-30 12:18:36.8294|INFO||4728|23|PerformPkiSetup - MeshManageabilityServer.CentralManageabilityServer, EMAManageabilityServer, Model=1.12.1.0, Tradition=impartial, PublicKeyToken=57d11e903ea1ca2c - [1] - Get Mesh data (Tenant) : (M104,6FA481CF). 
2024-01-30 12:18:36.8294|INFO||4728|23|PerformPkiSetup - MeshManageabilityServer.CentralManageabilityServer, EMAManageabilityServer, Model=1.12.1.0, Tradition=impartial, PublicKeyToken=57d11e903ea1ca2c - [1] - Message:Beginning PKI Setup course of for endpoint: (M104,6FA481CF) ComputerName: M104.native 
2024-01-30 12:18:36.9075|INFO||4728|23|PerformPkiSetup - MeshManageabilityServer.CentralManageabilityServer, EMAManageabilityServer, Model=1.12.1.0, Tradition=impartial, PublicKeyToken=57d11e903ea1ca2c - [1] - Message:Setup laptop title M104.native : (M104,6FA481CF). 
2024-01-30 12:18:36.9075|INFO||4728|23|RequestHostBasedProvisioningEx - MeshManageabilityServer.CentralManageabilityServer, EMAManageabilityServer, Model=1.12.1.0, Tradition=impartial, PublicKeyToken=57d11e903ea1ca2c - [1] - Message:Setup laptop title M104.native : (M104,6FA481CF). 
2024-01-30 12:18:36.9075|INFO||4728|23|RequestHostBasedProvisioningEx - MeshManageabilityServer.CentralManageabilityServer, EMAManageabilityServer, Model=1.12.1.0, Tradition=impartial, PublicKeyToken=57d11e903ea1ca2c - [1] - Message:Sending Agent Cease Distant Configuration Message : (M104,6FA481CF). 
2024-01-30 12:18:36.9075|INFO||4728|23|RequestHostBasedProvisioningEx - MeshManageabilityServer.CentralManageabilityServer, EMAManageabilityServer, Model=1.12.1.0, Tradition=impartial, PublicKeyToken=57d11e903ea1ca2c - [1] - Message:Connecting to Swarm Server : (M104,6FA481CF). 
2024-01-30 12:18:36.9232|WARN||4728|40|MessageManager_ReceivedMessageEx - MeshManageabilityServer.CentralManageabilityServer, EMAManageabilityServer, Model=1.12.1.0, Tradition=impartial, PublicKeyToken=57d11e903ea1ca2c - [0] - Warning:Acquired cease distant configuration standing from: 6FA481CF, standing: INVALID_PT_MODE (3) 
2024-01-30 12:18:37.0326|ERROR||4728|23|RequestHostBasedProvisioningEx - MeshManageabilityServer.CentralManageabilityServer, EMAManageabilityServer, Model=1.12.1.0, Tradition=impartial, PublicKeyToken=57d11e903ea1ca2c - [1] - Error:Unable to hook up with a Swarm Server, consumer=SYSTEM : (M104,6FA481CF). 
2024-01-30 12:18:37.0326|WARN||4728|23|PerformPkiSetup - MeshManageabilityServer.CentralManageabilityServer, EMAManageabilityServer, Model=1.12.1.0, Tradition=impartial, PublicKeyToken=57d11e903ea1ca2c - [1] - Warning: Failed Intel AMT SetupAdmin activation : (M104,6FA481CF). 
2024-01-30 12:18:37.0326|WARN||4728|23|AttemptPhase1 - MeshManageabilityServer.CentralManageabilityServer, EMAManageabilityServer, Model=1.12.1.0, Tradition=impartial, PublicKeyToken=57d11e903ea1ca2c - [1] - Failed PKI provisioning : (M104,6FA481CF). 

 

 

 SwamServer log exhibits the next:

 

 

2024-01-30 12:18:32.9700|INFO||9076|26|ProcessCommand - MeshServer.MeshAgent, EMASwarmServer, Model=1.12.1.0, Tradition=impartial, PublicKeyToken=57d11e903ea1ca2c - Message:Received 0 provisioning hash(s) from M104. Match discovered! DNS Suffix: my.area.com 
2024-01-30 12:18:33.0169|INFO||9076|54|ProcessCommand - MeshServer.MeshAgent, EMASwarmServer, Model=1.12.1.0, Tradition=impartial, PublicKeyToken=57d11e903ea1ca2c - Message:Intel AMT OTP confirmed. 

 

 

Working `emaagent.exe -swarmserver` on one of many shoppers yields the count on results of:

 

 

Intel(R) EMA Swarm server handle and port are intelema.my.area.native:8080

 

 

Checking netstat and Useful resource Monitor on the server, there’s a longtime connection between the shopper and the swarm server. See screenshot under. So undecided why it is saying it is unable connect with sawrm server except that is a purple herring?

TomW_0-1706589132240.png

If any individual might help, that’d be very a lot appreciated.

[ad_2]