Intel AMT is basically a hardware/firmware solution where everything happens on the insides of the computer, in hardware and embedded software. The main interface is the network card - you control Intel AMT remotely.
However, many utilities are available for controlling or receiving data from a local interface - on the computer in which Intel AMT is enabled.
This local functionality is a very important part of the manageability system. Applications (administrative tools, anti-virus apps...) can stock essential data in the storage interface or set agents for software availability assessment. IT managers can perform a system update from this interface, or set user notification options.
For all this magic to happen in the computer, a special set of software is needed. Part of my work in Intel relates to this software functionality, and in the next posts we'll focus on each software in the package and explain what it does, how it does it and what are the methods (and consequences) of removing it. A great place to that expands on this subject is the Intel AMT overview (scroll to the Local Access section).
If you have an Intel AMT machine, the software that you have available is (your mileage may vary, depending on system manufacturer and Intel AMT generation):
- Intel MEI (or Intel HECI), a device driver
- Local Management Service (LMS), which allows network communication from local host
- User Notification Service (UNS), used in order to inform (via Windows' Event Viewer) about manageability operations taking place on the computer
- Intel® AMT System Status Service (AtChkSrv), a service that monitors the Intel AMT status
- Intel® AMT System Status (AtChk), a GUI for the service above (implemented as a notification area icon)
We'll see more details on these, in future posts. For best results, please write in the comments any and all questions you may have on the matter!
To be continued… :)
Articles in the Intel® AMT software series: