Intel AMT has two types of interfaces: network interfaces (Intel AMT Releases 2.5, 2.6, 4.0, and 6.0 and later releases support a wireless, along with a wired, network interface) and a local interface. Network interfaces send and receive traffic via a LAN or wireless network connection. The Intel AMT firmware functionality can be configured only via a network interface so that a local user or application is prevented from changing critical settings. Starting in Release 6.1, local applications can perform most configuration operations.
There are three methods that a network application uses to communicate with Intel AMT:
“Web services for management” is an emerging DMTF standard that uses an object–oriented approach to managing devices across a network. The standard is based on the Common Information Model (CIM) as extended by Intel to support all Intel AMT features. Release 3.0 and later releases support full management using CIM objects and custom AMT objects. With Release 3.2, Intel AMT implements the DASH 1.0 preliminary specification. Release 5.1 complies with the DASH 1.0 specification.
Proprietary Redirection Protocol
Using Intel AMT functions, an ISV application can configure the platform to send console text to a remote destination and to receive keystrokes from a remote source. This is referred to as the Serial over LAN capability. The platform can also be configured to read from or write to a remote floppy disk or CD by redirecting the data storage commands. Both of these features use a proprietary protocol. The Redirection Library, included in the SDK, implements this protocol.
The Intel AMT SDK includes extensive sample code that shows the use of the remote interface functionality.
Copyright © 2006-2022, Intel Corporation. All rights reserved.