I want to do the following for our Server Racked HP z2 Workstations.
During WINPE, Provision AMT via Intel EMA so our engineers can connect to them and troubleshoot build errors.
I can do the following successfully:
- Meshcmd ACMAMTDeactivate (De-provision old Client Control mode)
- Meshcmd AMTInfo
- PNPUtil /Add-Drivers /install /subdirs (IME drivers)
- EMAAgent -fullinstall
However the ACUConfig logs shows the following error:
\Agent\MeshManageabilty\agent\core\wincrypto.cpp:250 Failed trying to get Windows Cryptographic context. Last error: -2146885628.
I checked and EMAAgent and Cryptsvc are both started within WINPE. Do you know how I can fix the above error.
Running "MeshCMD.exe microlms" moves me past wincrypto.cpp error. However ACUConfig it then moves onto a different error:
- \Agent\MeshManageability\agent\microstack\ILibAsyncSocket.c:505 internalsocket ERROR: 10035. Last error 10035.
Going to raise another forum ticket asking if anyone has successfully provisioned within AMT, seems like the odds are stacked against you