Ylianst/MeshCentral
1
0
Fork 0
mirror of https://github.com/Ylianst/MeshCentral.git synced 2024-11-22 22:17:31 +03:00
Code Issues Packages Projects Releases Wiki Activity

Baremetal AMT https://github.com/Ylianst/MeshCentral/discussions/4518

Browse Source
This commit is contained in:
silversword411 2022-11-10 08:39:58 -05:00
parent 6620a5773f
commit 27e44ec08b
No known key found for this signature in database
GPG Key ID: 6F4BD176F56B50CA
2 changed files with 8 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

BIN
docs/docs/intelamt/images/amtprovisioningserver.png Normal file
View File

Binary file not shown.
Side by Side

After

Width:  |  Height:  |  Size: 200 KiB

8
docs/docs/intelamt/index.md
View File

@ -49,6 +49,14 @@ Intel® AMT
If you are looking into managing remote computers that would be difficult to physically get access to for remote support or maintenance, one should probably look at getting a PC with Intel AMT.
## Bare-Metal Activation Server
The `AmtProvisioningServer` section in the `settings` section of the config.json will enable this feature. MeshCentral will then listen for activation requests, match against your ACM activation certificates and if everything goes well, will activate and add the device to a Intel AMT only device group. No agent or MeshCMD is involved.
This bare-metal activation server is not enabled by default and only makes sense when activating devices on the local network.
![baremetal](images/amtprovisioningserver.png)
## MeshCentral Group Types
Once MeshCentral is installed, a user will typically create a new device group. Here is the first hint that MeshCentral supports Intel AMT. Device groups come in two types. You can manage using a software agent, or using Intel AMT only.