From 490834f369bb382e7adfbffe80c2845a8d23214a Mon Sep 17 00:00:00 2001 From: silversword411 Date: Thu, 10 Nov 2022 08:49:00 -0500 Subject: [PATCH] amt tweaking working from blog data --- docs/docs/intelamt/index.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/docs/intelamt/index.md b/docs/docs/intelamt/index.md index e5148d2a..3ebbf7c6 100644 --- a/docs/docs/intelamt/index.md +++ b/docs/docs/intelamt/index.md @@ -55,6 +55,8 @@ The `AmtProvisioningServer` section in the `settings` section of the config.json This bare-metal activation server is not enabled by default and only makes sense when activating devices on the local network. +Once enabled, Intel AMT can send “hello” data to the MeshCentral provisioning server on port 9971 and MeshCentral will respond by connecting back, authenticating, and activating Intel AMT. MeshCentral will then log the event, add the device to a pre-defined agent-less device group and complete any remaining configuration. A trusted CA certificate is required to perform this operation fully automatically. + ![baremetal](images/amtprovisioningserver.png) ## MeshCentral Group Types