Troubleshooting PC's that won't provision

[CSVHolyWar]

I'm running host based provisioning with Intel EMA server.  I have about 140 pc's that are vpro-cable.  I mass-provisioned them with some deployment software and about 30 of them did not successfully provision.  Most of them are sitting as 'pending activation'.  I've tried clearing the record and reprovisioning and no success.

I took a look at the logs from the Manageability server for one of our pcs (518p).  It seems it will automatically keep trying to provision the pc.  Looking thru this log here I found an error - Invalid_pt_mode.  I don't know what this means.  I tried searching Google and intel documents and can't find anything regarding this error message.

Any help would be appreciated.  Thank you

This is the log from the manageability server from today (9-9-22):

PublicKeyToken=57d11e903ea1ca2c - [1] - Message:-- Attempting phase 1 host based provisioning : (518P,2A52D3DA).
2022-09-09 00:02:00.3580|INFO||4572|8|RequestHostBasedProvisioningEx - MeshManageabilityServer.CentralManageabilityServer, EMAManageabilityServer, Version=1.7.1.0, Culture=neutral, PublicKeyToken=57d11e903ea1ca2c - [1] - Message:Sending Agent Stop Remote Configuration Message : (518P,2A52D3DA).
2022-09-09 00:02:00.3580|INFO||4572|8|RequestHostBasedProvisioningEx - MeshManageabilityServer.CentralManageabilityServer, EMAManageabilityServer, Version=1.7.1.0, Culture=neutral, PublicKeyToken=57d11e903ea1ca2c - [1] - Message:Connecting to Swarm Server : (518P,2A52D3DA).
2022-09-09 00:02:00.3893|WARN||4572|55|MessageManager_ReceivedMessageEx - MeshManageabilityServer.CentralManageabilityServer, EMAManageabilityServer, Version=1.7.1.0, Culture=neutral, PublicKeyToken=57d11e903ea1ca2c - [0] - Warning:Received stop remote configuration status from: 2A52D3DA, status: INVALID_PT_MODE (3)
2022-09-09 00:02:00.4831|INFO||4572|8|RequestHostBasedProvisioningEx - MeshManageabilityServer.CentralManageabilityServer, EMAManageabilityServer, Version=1.7.1.0, Culture=neutral, PublicKeyToken=57d11e903ea1ca2c - [1] - Message:Requesting ME administrator account : (518P,2A52D3DA).
2022-09-09 00:02:00.9963|INFO||4572|8|RequestHostBasedProvisioningEx - MeshManageabilityServer.CentralManageabilityServer, EMAManageabilityServer, Version=1.7.1.0, Culture=neutral, PublicKeyToken=57d11e903ea1ca2c - [1] - Message:Disconnecting Swarm Server : (518P,2A52D3DA).
2022-09-09 00:02:00.9963|INFO||4572|8|HostBasedSetup - MeshManageabilityServer.CentralManageabilityServer, EMAManageabilityServer, Version=1.7.1.0, Culture=neutral, PublicKeyToken=57d11e903ea1ca2c - [1] - Message:Attempting host based provisioning : (518P,2A52D3DA).
2022-09-09 00:02:00.9963|INFO||4572|8|StartRouter - MeshManageabilityServer.CentralManageabilityServer, EMAManageabilityServer, Version=1.7.1.0, Culture=neutral, PublicKeyToken=57d11e903ea1ca2c - [1] - Message:Starting Mesh Router 52938 -> 2A52D3DA:16992, user@email.com
2022-09-09 00:02:01.2163|INFO||4572|8|HostBasedSetup - MeshManageabilityServer.CentralManageabilityServer, EMAManageabilityServer, Version=1.7.1.0, Culture=neutral, PublicKeyToken=57d11e903ea1ca2c - [1] - Message:Creating DotNetWSManClient object : (518P,2A52D3DA).
2022-09-09 00:02:03.4368|WARN||4572|8|HostBasedSetup - MeshManageabilityServer.CentralManageabilityServer, EMAManageabilityServer, Version=1.7.1.0, Culture=neutral, PublicKeyToken=57d11e903ea1ca2c - [1] - Warning:Error (2) - Intel.Manageability.WSManagement.WSManException: The underlying connection was closed: The connection was closed unexpectedly. ---> System.Net.WebException: The underlying connection was closed: The connection was closed unexpectedly.
at Intel.Manageability.WSManagement.DotNetWSManClient.HttpSendReceive(MemoryStream postData, XmlDocument& resp)
at Intel.Manageability.WSManagement.DotNetWSManClient.WSManSendReceive(Header header, XmlElement[] bodyIn, XmlElement[]& bodyOut)
--- End of inner exception stack trace ---
at Intel.Manageability.WSManagement.DotNetWSManClient.WSManSendReceive(Header header, XmlElement[] bodyIn, XmlElement[]& bodyOut)
at Intel.Manageability.WSManagement.DotNetWSManClient.Get(Uri resourceUri, IEnumerable`1 selectors)
at Intel.Manageability.Cim.Untyped.CimObject.Get(CimKeys keys)
at MeshManageabilityServer.CentralManageabilityServer.HostBasedSetup(Int32 slot, String adminuser, String adminpass, X509Certificate2 rootCertificate, String strEndpointString, AmtSetupRecord amtSetupRecord) : (518P,2A52D3DA).
2022-09-09 00:02:03.4368|WARN||4572|8|RequestHostBasedProvisioningEx - MeshManageabilityServer.CentralManageabilityServer, EMAManageabilityServer, Version=1.7.1.0, Culture=neutral, PublicKeyToken=57d11e903ea1ca2c - [1] - Warning:Host Based Setup (1st try) - INTERNAL_ERROR : (518P,2A52D3DA).
2022-09-09 00:02:03.4368|INFO||4572|8|HostBasedSetup - MeshManageabilityServer.CentralManageabilityServer, EMAManageabilityServer, Version=1.7.1.0, Culture=neutral, PublicKeyToken=57d11e903ea1ca2c - [1] - Message:Attempting host based provisioning : (518P,2A52D3DA).
2022-09-09 00:02:03.4524|INFO||4572|8|StartRouter - MeshManageabilityServer.CentralManageabilityServer, EMAManageabilityServer, Version=1.7.1.0, Culture=neutral, PublicKeyToken=57d11e903ea1ca2c - [1] - Message:Starting Mesh Router 52941 -> 2A52D3DA:16992, user@email.com
2022-09-09 00:02:03.6555|INFO||4572|8|HostBasedSetup - MeshManageabilityServer.CentralManageabilityServer, EMAManageabilityServer, Version=1.7.1.0, Culture=neutral, PublicKeyToken=57d11e903ea1ca2c - [1] - Message:Creating DotNetWSManClient object : (518P,2A52D3DA).
2022-09-09 00:02:05.8728|WARN||4572|8|HostBasedSetup - MeshManageabilityServer.CentralManageabilityServer, EMAManageabilityServer, Version=1.7.1.0, Culture=neutral, PublicKeyToken=57d11e903ea1ca2c - [1] - Warning:Error (2) - Intel.Manageability.WSManagement.WSManException: The underlying connection was closed: The connection was closed unexpectedly. ---> System.Net.WebException: The underlying connection was closed: The connection was closed unexpectedly.
at Intel.Manageability.WSManagement.DotNetWSManClient.HttpSendReceive(MemoryStream postData, XmlDocument& resp)
at Intel.Manageability.WSManagement.DotNetWSManClient.WSManSendReceive(Header header, XmlElement[] bodyIn, XmlElement[]& bodyOut)
--- End of inner exception stack trace ---
at Intel.Manageability.WSManagement.DotNetWSManClient.WSManSendReceive(Header header, XmlElement[] bodyIn, XmlElement[]& bodyOut)
at Intel.Manageability.WSManagement.DotNetWSManClient.Get(Uri resourceUri, IEnumerable`1 selectors)
at Intel.Manageability.Cim.Untyped.CimObject.Get(CimKeys keys)
at MeshManageabilityServer.CentralManageabilityServer.HostBasedSetup(Int32 slot, String adminuser, String adminpass, X509Certificate2 rootCertificate, String strEndpointString, AmtSetupRecord amtSetupRecord) : (518P,2A52D3DA).
2022-09-09 00:02:05.8728|WARN||4572|8|RequestHostBasedProvisioningEx - MeshManageabilityServer.CentralManageabilityServer, EMAManageabilityServer, Version=1.7.1.0, Culture=neutral, PublicKeyToken=57d11e903ea1ca2c - [1] - Warning:Host Based Setup (2nd try) - INTERNAL_ERROR : (518P,2A52D3DA).
2022-09-09 00:02:05.8728|INFO||4572|8|HostBasedSetup - MeshManageabilityServer.CentralManageabilityServer, EMAManageabilityServer, Version=1.7.1.0, Culture=neutral, PublicKeyToken=57d11e903ea1ca2c - [1] - Message:Attempting host based provisioning : (518P,2A52D3DA).
2022-09-09 00:02:05.8883|INFO||4572|8|StartRouter - MeshManageabilityServer.CentralManageabilityServer, EMAManageabilityServer, Version=1.7.1.0, Culture=neutral, PublicKeyToken=57d11e903ea1ca2c - [1] - Message:Starting Mesh Router 52944 -> 2A52D3DA:16992, user@email.com
2022-09-09 00:02:06.1072|INFO||4572|8|HostBasedSetup - MeshManageabilityServer.CentralManageabilityServer, EMAManageabilityServer, Version=1.7.1.0, Culture=neutral, PublicKeyToken=57d11e903ea1ca2c - [1] - Message:Creating DotNetWSManClient object : (518P,2A52D3DA).
2022-09-09 00:02:08.2933|WARN||4572|8|HostBasedSetup - MeshManageabilityServer.CentralManageabilityServer, EMAManageabilityServer, Version=1.7.1.0, Culture=neutral, PublicKeyToken=57d11e903ea1ca2c - [1] - Warning:Error (2) - Intel.Manageability.WSManagement.WSManException: The underlying connection was closed: The connection was closed unexpectedly. ---> System.Net.WebException: The underlying connection was closed: The connection was closed unexpectedly.
at Intel.Manageability.WSManagement.DotNetWSManClient.HttpSendReceive(MemoryStream postData, XmlDocument& resp)
at Intel.Manageability.WSManagement.DotNetWSManClient.WSManSendReceive(Header header, XmlElement[] bodyIn, XmlElement[]& bodyOut)
--- End of inner exception stack trace ---
at Intel.Manageability.WSManagement.DotNetWSManClient.WSManSendReceive(Header header, XmlElement[] bodyIn, XmlElement[]& bodyOut)
at Intel.Manageability.WSManagement.DotNetWSManClient.Get(Uri resourceUri, IEnumerable`1 selectors)
at Intel.Manageability.Cim.Untyped.CimObject.Get(CimKeys keys)
at MeshManageabilityServer.CentralManageabilityServer.HostBasedSetup(Int32 slot, String adminuser, String adminpass, X509Certificate2 rootCertificate, String strEndpointString, AmtSetupRecord amtSetupRecord) : (518P,2A52D3DA).
2022-09-09 00:02:08.2933|WARN||4572|8|RequestHostBasedProvisioningEx - MeshManageabilityServer.CentralManageabilityServer, EMAManageabilityServer, Version=1.7.1.0, Culture=neutral, PublicKeyToken=57d11e903ea1ca2c - [1] - Warning:Host Based Setup (3rd try) - INTERNAL_ERROR : (518P,2A52D3DA).
2022-09-09 00:02:08.2933|WARN||4572|8|PerformAction - MeshManageabilityServer.CentralManageabilityServer, EMAManageabilityServer, Version=1.7.1.0, Culture=neutral, PublicKeyToken=57d11e903ea1ca2c - [1] - Warning:-- Failed host based provisioning : (518P,2A52D3DA).

[JoseH_Intel]

Hello CSVHolyWar,

Thank you for joining the Intel community

I can see you are using EMA version 1.7.1. There is an updated version 1.8.1 which it would be worth to try Intel® Endpoint Management Assistant (Intel® EMA)

Let me know if this helps

Regards

Jose A.

Intel Customer Support Technician

[CSVHolyWar]

I updated to the latest version per your suggestion but it didn't appear to fix anything.  Also the web interface seems a little faster.

[Jimmy_Wai_Intel]

What version of AMT version do you have on the PCs that cannot be provisioned? If you don't know the AMT version, what are the CPU's on those?

Regards,

Jimmy Wai

Intel Technical Sales Specialist

[CSVHolyWar]

CPU0: Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz (2 cores)	11.8.92
CPU0: Intel(R) Core(TM) i7-8665U CPU @ 1.90GHz (4 cores)	12.0.90
CPU0: Intel(R) Core(TM) i7-4785T CPU @ 2.20GHz (4 cores)	9.1.45
CPU0: Intel(R) Core(TM) i7-6700T CPU @ 2.80GHz (4 cores)	11.8.92
CPU0: Intel(R) Core(TM) i7-8700T CPU @ 2.40GHz (6 cores)	12.0.90
CPU0: Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz (6 cores)	12.0.90

[Jimmy_Wai_Intel]

Hi CSVHolyWar,

Based on the info provided, 3 of the system are not supported. Thus, provisioning is failing on those. Please see my comments below.

CPU0: Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz (2 cores)	11.8.92	Not a vPro capable CPU. AMT not available
CPU0: Intel(R) Core(TM) i7-8665U CPU @ 1.90GHz (4 cores)	12.0.90	This should work if it is a vPro system. Do you see vPro sticker on it?
CPU0: Intel(R) Core(TM) i7-4785T CPU @ 2.20GHz (4 cores)	9.1.45	This is too old to be supported.
CPU0: Intel(R) Core(TM) i7-6700T CPU @ 2.80GHz (4 cores)	11.8.92	From EMA version 1.8, the minimum supported AMT version is 12. However, 11.x should still work technically. Thus, this should work if it is a vPro system. Do you see vPro sticker on it?
CPU0: Intel(R) Core(TM) i7-8700T CPU @ 2.40GHz (6 cores)	12.0.90	This should work if it is a vPro system. Do you see vPro sticker on it?
CPU0: Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz (6 cores)	12.0.90	Not a vPro capable CPU. AMT not available

[CSVHolyWar]

Ok, that is helpful.  The 9.1.45 one can still be provisioned using older software such as the SCS ACU Wizard though, correct?  I will have to check vpro stickers on the other machines

[Jimmy_Wai_Intel]

SCS should still be able to provision the PC with FW version 9.1.45 if it is a vPro PC, but Intel EMA may not be able to adopt and manage it with AMT even after it was provisioned.

[JoseH_Intel]

Hello CSVHolyWar,

In such case you want to take a look and follow the instructions depicted in this article:

How to Troubleshoot a Client Initiated Remote Access (CIRA)... (intel.com)

Let me know if this helps

Regards

Jose A.

Intel Customer Support Technician