Community
cancel
Showing results for 
Search instead for 
Did you mean: 
GRile
New Contributor I
3,367 Views

How to tell if my PC supports AMT?

I have a Lenovo http://pcsupport.lenovo.com/gb/en/products/Desktops-and-all-in-ones/ThinkCentre-M-Series-desktops/Th... M73 ThinkCentre and the CPU is Core™ http://ark.intel.com/products/80815/Intel-Core-i5-4590-Processor-6M-Cache-up-to-3_70-GHz i5-4590. When I try to run the ACUWizard I receive the attached error message. I am running the ACUWizard with a local admin account. The ME firmware is 9.1.1.1000. I have installed Intel Management Engine Components 11.6.0.1047.

2017-02-22 13:29:59: Thread:8092(DETAIL) : ACU.dll, Category: SetCompatibilityMode Source: ACUDll.cpp : SetCompatibilityMode Line: 220: Set compatibility mode to 10.0.

2017-02-22 13:29:59: Thread:8092(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : CheckAMT Line: 85: Entering

2017-02-22 13:29:59: Thread:8092(DETAIL) : ACU Configurator , Category: -HECI- Source: HECIWin.cpp : HECIWin::Init Line: 191: Connected to the Intel(R) Management Engine Interface driver, version 11.6.0.1042

2017-02-22 13:29:59: Thread:8092(ERROR) : ACU Configurator , Category: -HECI- Source: HECIWin.cpp : HECIWin::_doIoctl Line: 410: Intel(R) Management Engine Interface error- I/O control command The handle is invalid. (6)

2017-02-22 13:29:59: Thread:8092(ERROR) : ACU Configurator , Category: -HECI- Source: HECIWin.cpp : HECIWin::Init Line: 200: Intel(R) Management Engine Interface error- Failed to connect to the Intel(R) Management Engine Interface PTHI client.

2017-02-22 13:30:14: Thread:8092(DETAIL) : ACU Configurator , Category: -HECI- Source: HECIWin.cpp : HECIWin::Init Line: 191: Connected to the Intel(R) Management Engine Interface driver, version 11.6.0.1042

2017-02-22 13:30:14: Thread:8092(ERROR) : ACU Configurator , Category: -HECI- Source: HECIWin.cpp : HECIWin::_doIoctl Line: 410: Intel(R) Management Engine Interface error- I/O control command The handle is invalid. (6)

2017-02-22 13:30:14: Thread:8092(ERROR) : ACU Configurator , Category: -HECI- Source: HECIWin.cpp : HECIWin::Init Line: 200: Intel(R) Management Engine Interface error- Failed to connect to the Intel(R) Management Engine Interface PTHI client.

2017-02-22 13:30:29: Thread:8092(DETAIL) : ACU Configurator , Category: -HECI- Source: HECIWin.cpp : HECIWin::Init Line: 191: Connected to the Intel(R) Management Engine Interface driver, version 11.6.0.1042

2017-02-22 13:30:29: Thread:8092(ERROR) : ACU Configurator , Category: -HECI- Source: HECIWin.cpp : HECIWin::_doIoctl Line: 410: Intel(R) Management Engine Interface error- I/O control command The handle is invalid. (6)

2017-02-22 13:30:29: Thread:8092(ERROR) : ACU Configurator , Category: -HECI- Source: HECIWin.cpp : HECIWin::Init Line: 200: Intel(R) Management Engine Interface error- Failed to connect to the Intel(R) Management Engine Interface PTHI client.

2017-02-22 13:30:44: Thread:8092(DETAIL) : ACU Configurator , Category: -HECI- Source: HECIWin.cpp : HECIWin::Init Line: 191: Connected to the Intel(R) Management Engine Interface driver, version 11.6.0.1042

2017-02-22 13:30:44: Thread:8092(ERROR) : ACU Configurator , Category: -HECI- Source: HECIWin.cpp : HECIWin::_doIoctl Line: 410: Intel(R) Management Engine Interface error- I/O control command The handle is invalid. (6)

2017-02-22 13:30:44: Thread:8092(ERROR) : ACU Configurator , Category: -HECI- Source: HECIWin.cpp : HECIWin::Init Line: 200: Intel(R) Management Engine Interface error- Failed to connect to the Intel(R) Management Engine Interface PTHI client.

2017-02-22 13:30:59: Thread:8092(DETAIL) : ACU Configurator , Category: -HECI- Source: HECIWin.cpp : HECIWin::Init Line: 191: Connected to the Intel(R) Management Engine Interface driver, version 11.6.0.1042

2017-02-22 13:30:59: Thread:8092(ERROR) : ACU Configurator , Category: -HECI- Source: HECIWin.cpp : HECIWin::_doIoctl Line: 410: Intel(R) Management Engine Interface error- I/O control command The handle is invalid. (6)

2017-02-22 13:30:59: Thread:8092(ERROR) : ACU Configurator , Category: -HECI- Source: HECIWin.cpp : HECIWin::Init Line: 200: Intel(R) Management Engine Interface error- Failed to connect to the Intel(R) Management Engine Interface PTHI client.

2017-02-22 13:31:14: Thread:8092(DETAIL) : ACU Configurator , Category: -HECI- Source: HECIWin.cpp : HECIWin::Init Line: 191: Connected to the Intel(R) Management Engine Interface driver, version 11.6.0.1042

2017-02-22 13:31:14: Thread:8092(ERROR) : ACU Configurator , Category: -HECI- Source: HECIWin.cpp : HECIWin::_doIoctl Line: 410: Intel(R) Management Engine Interface error- I/O control command The handle is invalid. (6)

2017-02-22 13:31:14: Thread:8092(ERROR) : ACU Configurator , Category: -HECI- Source: HECIWin.cpp : HECIWin::Init Line: 200: Intel(R) Management Engine Interface error- Failed to connect to the Intel(R) Management Engine Interface PTHI client.

2017-02-22 13:31:29: Thread:8092(DETAIL) : ACU Configurator , Category: -HECI- Source: HECIWin.cpp : HECIWin::Init Line: 191: Connected to the Intel(R) Management Engine Interface driver, version 11.6.0.1042

2017-02-22 13:31:29: Thread:8092(ERROR) : ACU Configurator , Category: -HECI- Source: HECIWin.cpp : HECIWin::_doIoctl Line: 410: Intel(R) Management Engine Interface error- I/O control command The handle is invalid. (6)

2017-02-22 13:31:29: Thread:8092(ERROR) : ACU Configurator , Category: -HECI- Source: HECIWin.cpp : HECIWin::Init Line: 200: Intel(R) Management Engine Interface error- Failed to connect to the Intel(R) Management Engine Interface PTHI client.

2017-02-22 13:31:44: Thread:8092(DETAIL) : ACU Configurator , Category: Status message Source: HECIDiscovery.cpp : CheckAMT Line: 154: AMT Status code - An internal error has occurred in the Intel(R) AMT device. This might indicate an interface error, or an application error. (0xc0004269)

2017-02-22 13:31:44: Thread:8092(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : IsChangeToAMTAllowed Line: 1100: Entering

2017-02-22 13:31:44: Thread:8092(DETAIL) : ACU Configurator , Category: -HECI- Source: HECIWin.cpp : HECIWin::Init Line: 191: Connected to the Intel(R) Management Engine Interface driver, version 11.6.0.1042

2017-02-22 13:31:44: Thread:8092(ERROR) : ACU Configurator , Category: -HECI- Source: HECIWin.cpp : HECIWin::_doIoctl Line: 410: Intel(R) Management Engine Interface error- I/O control command The handle is invalid. (6)

2017-02-22 13:31:44: Thread:8092(ERROR) : ACU Configurator , Category: -HECI- Source: HECIWin.cpp : HECIWin::Init Line: 200: Intel(R) Management Engine Interface error- Failed to connect to the Intel(R) Management Engine Interface PTHI client.

2017-02-22 13:31:44: Thread:8092(ERROR) : ACU Configurator , Category: Error message Source: HECIDiscovery.cpp : IsChangeToAMTAllowed Line: 1108: Failed to connect to the WD client of the Intel(R) Management Engine Interface. (0xc0000056)

2017-02-22 13:31:44: Thread:8092(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : CheckAMT Line: 170: Exiting

2017-02-22 13:31:44: Thread:8092(DETAIL) : ACU Configurator , Category: AMT Status Source: ACUDll.cpp : GetHostAndMEInfo Line: 4296: This system does not have Intel(R) AMT (or it is disabled in the Intel MEBX, or the correct drivers are not installed or enabled, or the current user does not have permissions to the drivers). (0xc0000063)

2017-02-22 13:31:44: Thread:8092(DETAIL) : ACU Configurator , Category: Returned data Source: ACUDll.cpp : GetHostAndMEInfo Line: 4474: GetHostAndMEInfo output data: IsAMT:False, isEnterpriseMode:False, configurationMode:0, isRemoteConfigEnabled:False, AMTversion:, isMobile:False, provisioningTlsMode:0, uuid:7D4BA014-10EF-11E5-973A-90014CA31500, isClientConfigEnabled:False, hostBasedSupport:False, configurationState:2032405000, FQDN:RILEY.domain.co.uk, embeddedConfigurationAllowed:False. isLANLessPlatform:False. PKIDNSSuffix: Empty.

0 Kudos
6 Replies
MichaelA_Intel
Moderator
1,108 Views

grahamriley

Hi Graham,

I can confirm that you're processor is vPro enabled. For future reference, you can go to http://ark.intel.com/ http://ark.intel.com to check for this type of information. Yours is here: http://ark.intel.com/products/80815/Intel-Core-i5-4590-Processor-6M-Cache-up-to-3_70-GHz http://ark.intel.com/products/80815/Intel-Core-i5-4590-Processor-6M-Cache-up-to-3_70-GHz

Saw this in the log:

2017-02-22 13:31:44: Thread:8092(DETAIL) : ACU Configurator , Category: AMT Status Source: ACUDll.cpp : GetHostAndMEInfo Line: 4296: This system does not have Intel(R) AMT (or it is disabled in the Intel MEBX, or the correct drivers are not installed or enabled, or the current user does not have permissions to the drivers). (0xc0000063)

On power up, hit CTRL-P to enter MebX to enable it and try it again.

Michael

GRile
New Contributor I
1,107 Views

Hi Michael,

Thanks for your reply. I know that my CPU is vPro enabled however I was wondering how I can tell if it supports AMT? If I got into BIOS I do not see MEBX options, only Smart Connect. I am guessing therefore that it does not support AMT.

Graham

MichaelA_Intel
Moderator
1,107 Views

grahamriley

Hi Graham,

MEBx options are not in BIOS but are accessed at startup by doing the key combination of CTRL-P You should see this option as your system is coming up. Let me know if you do not see this option.

Michael

GRile
New Contributor I
1,107 Views

Thanks, yes, you are correct but usually you see some reference to MEBx within the BIOS lie I do on some of the other Lenovo ThinkCentre machines we have but on this one we see no sign of it. See attached pic. I'll still try pressing CTRL-P at startup though and see what happens! I'll try upgrading the ME firmware.

Cheers,

Graham

GRile
New Contributor I
1,107 Views

OK, ME Firmware has been updating to 9.1.37.1002 but still I see no sign of MEBx / AMT. Also Ctrl+P does nothing. I wonder if the restriction is within the CPU or if it is Lenovo which have not enabled in within the BIOS. The problem is that going forwards we will be looking to purchase many more corporate systems and we need a way to find out if these contain AMT / MEBx. I guess we'll just have to ask the vendor and hope that they know!

Graham

MichaelA_Intel
Moderator
1,107 Views

grahamriley

Hi Graham,

I dug into this a little further and while the processor supports vPro, it looks like Lenovo did not enable AMT in BIOS. If the M73 is supposed to have the AMT capability, you can contact Lenovo for the BIOS update. I know this is not what you were looking for but hopefully they will be able to help.

Regards,

Michael

Reply