Reference intel amt ms01

Finn (MS-01, Proxmox host) has Intel vPro/AMT fully provisioned and Network Active via MEBx (confirmed in MEBx screenshots 2026-06-20).

Access path: MEBx is inside the regular InsydeH2O BIOS menu on the MS-01 -- NOT via Ctrl+P at POST (which is the generic Intel default). Navigate through BIOS Advanced to find the MEBx submenu.

Network config (static, in MEBx Network Setup): - DHCP Mode: Disabled - IPv4: 192.168.86.68 - Subnet: 255.255.255.0 - Gateway: 192.168.86.1 - DNS: 0.0.0.0 (unset; irrelevant for direct-IP KVM) - Network Access State: Network Active

Reach it from Vector (or any separate physical box on the LAN), NOT from Console.

https://192.168.86.68:16993   (AMT web UI / MeshCommander, digest auth)
http://192.168.86.68:16992    (plain HTTP, digest auth)

TLS port 16993 only opens if AMT was provisioned with a cert; standard admin-control-mode setups (this one) use plain 16992 only, so try 16992 first. Use MeshCommander on Vector rather than a raw browser for KVM redirection.

KEY GOTCHA (why probes from Console fail): Console is a VM running on Finn. AMT/ME shares the host physical NIC via a sideband channel, and a guest on the same hypervisor generally cannot reach its own host's out-of-band AMT, the traffic never properly loops back to the ME. Symptom from Console: .67 (host) pings fine but .68 (ME) shows INCOMPLETE ARP and ports 16992/16993 refused. This is expected, not an AMT fault, and is not evidence AMT is broken. Never probe or validate AMT reachability from Console; if AMT connectivity comes up, immediately check the test origin and redirect to Vector before diagnosing further. Always test AMT from Vector (or Sol).

Credential: AMT password stored in NordPass under "Finn MEBx".

Reference guides: - spaceterran.com: Step-by-Step Guide: Enabling Intel vPro on Your Minisforum MS-01 - virtualizationhowto.com: Intel vPro with AMT on MS-01 - YouTube: Setting up Mesh Commander with Minisforum MS-01

[merged 2026-07-09 from 3 duplicate auto-memory writes, all session 8a2756b9-b9d9-4142-ad8b-f96081ab5f26, confidence 0.85-0.88, mode direct]