MeshCentral: Intel AMT not detected by agent, but meshcmd detects it

I have a Lenovo Thinkpad W540 that I’m trying to set up with Intel AMT in WAN-only mode. The AMT policy on the group is Fully Automatic. I have booted the laptop off a USB with the setup.bin provided by MeshCentral, and it is fully activated in ACM mode.

From agent console:

> amt
Intel AMT not detected.

From OS terminal:

[root@alpha meshagent]# meshcmd amtinfo
DHCP error, timeout
Intel AMT v9.1.45, activated in Admin Control Mode (ACM).
Wired Enabled, DHCP, 54:EE:75:49:B2:19, 192.168.1.42
Wireless Enabled, DHCP, CC:3D:82:7D:21:70
Trusted DNS suffix: meshcentral.k7dxs.net
Connection Status: Direct, CIRA: Disconnected.
[root@alpha meshagent]#

Environment information:

Agent OS: Arch Linux (64 bit)
Intel ME: v9.1.45 activated in Admin Control Mode (ACM)

About this issue

Original URL
State: open
Created 2 years ago
Comments: 17 (4 by maintainers)

Most upvoted comments

I’m going to try to write something in the JS to see if it can verify amt absence when smbios says it’s absent. If it works, I can probably use it to force that smbios value to true so it gets reported correctly. I’ll ping you again when I have that ready to see if you can test on your Lenovo system.

krayon007 on Jun 15, 2022