• 08/10/2019
  • Public Content

Integrating Intel® AMT Discovery into a Management Console

Software developers sometimes struggle with how to integrate Intel® Active Management Technology (Intel® AMT) APIs into their management consoles, since most managed environments will have a mix of Intel AMT and non-Intel AMT clients. The first step is to identify the Intel AMT devices and their current configuration state by performing a discovery process.

Discovery Process

The discovery process starts out with using one or more discovery applications to gather information about the devices on the network. This process can be a combination of remote discovery and local discovery.
Exactly how to integrate the discovery will depend on the management console in question. Typically an Intel® Setup and Configuration Software (Intel® SCS) discovery tool is used as the basis for discovery, but custom solutions can be created as well, depending on the needs of the developer. See article on basic Discovery for more information.

Determining the Feature Set of the Device

Once you have the data from your systems, the question is how to use that information. At a minimum, you will need to filter on the following physical characteristics and tags.  
For example, let us assume the use of the Intel SCS configurator tool called
acuconfig.exe: When we call this from the command line we will use the “”systemdiscovery” switch to create an XML file that contains the feature set of the Intel AMT device.
Key characteristics:
  1. CPU (not provided by acuconfig.exe): Filter for only the Intel® Core™ i3 processor, Intel® Core™ i5 processor, Intel® Core™ i7 processor, Intel® Core™ M processor, and the Intel® Xeon® processor family.
  2. LMS.exe service: This is the Intel® WMI provider that lets the discovery tools communicate with the Intel AMT firmware. This service may not be installed if a custom OS is used. The missing files can be obtained by downloading the Intel® Management Engine Interface (Intel® MEI) driver package from the OEM website. Tip: generally classified as a "chipset driver" by OEMs.
    1. To determine if the LMS.exe is running, look for the service, or by parsing the verbose output log of acuconfig.exe.
  3. Values found in the discovery XML:
    1. <IsMEIEnabled> - Set by the system manufacturer, value must be true for Intel AMT to be enabled. Value is not dependent on LMS.exe.
    2. <IsAMTEnabledInBIOS> - Must be set to true. Some OEMs allow Intel AMT to be disabled in the BIOS, requiring it be enabled in the BIOS to activate Intel AMT. Tag value is dependent on LMS.exe
    3. <AMTSKU> - Which can be Intel® Standard Manageability or Intel AMT Full (Intel® vPro™ technology) or Intel® Small Business Advantage (Intel® SBA). This value declares the feature set; tag is dependent on LMS.exe.
 
*No product or component can be absolutely secure.

Product and Performance Information

1

Intel's compilers may or may not optimize to the same degree for non-Intel microprocessors for optimizations that are not unique to Intel microprocessors. These optimizations include SSE2, SSE3, and SSSE3 instruction sets and other optimizations. Intel does not guarantee the availability, functionality, or effectiveness of any optimization on microprocessors not manufactured by Intel. Microprocessor-dependent optimizations in this product are intended for use with Intel microprocessors. Certain optimizations not specific to Intel microarchitecture are reserved for Intel microprocessors. Please refer to the applicable product User and Reference Guides for more information regarding the specific instruction sets covered by this notice.

Notice revision #20110804