Let us talk about HECI and LMS

Host Embedded Controller Interface (HECI ) driver is a software interface that is used to communicate to the AMT subsystem (Management Engine) to access AMT capabilities. Communication between the local host operating system (OS) and the ME is accomplished by means of the HECI driver. HECI is bi-directional, as either the host OS or Intel AMT firmware can initiate transactions.

Local Manageability Service (LMS) is a service that runs locally (in the user space) in the host operating system.LMS exposes AMT functionality through standard interfaces (For Example: general-info interface, firmware update interface, local agent-presence interface, etc.). LMS listens for the request directed to the AMT local host and when a application sends SOAP/HTTP message addressed to the local host then LMS intercepts the request and routes the request to the Management Engine Interface via the HECI driver.

 

 

 

When you have to access any AMT capabilities on the local machine you have to go through the HECI driver to access the Management Engine. LMS is an abstraction that sits on top of the HECI driver (and the ME) that interacts with the ME using standard interfaces.

 

Let us say you want to read/write data to the third party data store (3PDS) then your application uses the storage library API to accomplish the task. The storage library talks to the LMS interface and that in turn talks to the HECI driver to access the 3PDS. As far as your client application is concerned it typically talks to the LMS or Storage Library (AMT SDK) and eventually the message gets to the ME via the HECI driver.

 

 

 

Please note that currently the HECI driver is available for Windows*  and it will be made available on Linux*  in a future release .

 

 

 

Bottom line:

 

 

 

The HECI driver and LMS are needed whenever you may need to do anything locally on the AMT machine (such as storage, agent presence, and general info).

 

 

 

For additional information:

 

 

 

Intel AMT Architecture Guide, Intel AMT SDK Start Here Guide, Storage Design Guide

 

For more complete information about compiler optimizations, see our Optimization Notice.

20 comments

Top
anonymous's picture

I am curious if there is drivers for Windows 7 64 bit now. I have an HP DC7700 Ultr-slim desktop that I loaded Windows 7 64 bit on. However it can not find drivers for the PCI Simple Communications Controller. HP said there is a need for the HECI drivers, but they only have it for Windows 7 32 bit.

Any ideas other than installing the 32 bit version of the OS?

anonymous's picture

Is there a way to setup the heci driver as an administrator so that it cannot be disabled? If I want to be running custom applications that will use AMT for security, then I don't want to be allowing my users to just circumvent security by disabling the heci driver which will mean that any security application running on the system that uses heci to talk to AMT will be hosed.

anonymous's picture

Hi Linda

we too have the same issue you raised and can be very annoying.

We have a Dell estate and this problem only seems to have started from the 755's, (just testing 780's) I thought it was a conflict between Windows/Dell video driver settings but could this HECI driver be the source?

Might have to read up a bit more into this. I'll post back if i can fix. Please let me know if any one else has this problem.

Thanks Stuart

anonymous's picture

Does HECI driver interfere with any USB/Serial communication at all? Another way to ask this question is - Does HECI tries to "manage" comm port communication on a given PC?

Thanks.

anonymous's picture

I have a system that has been receiving HECI error EVENT ID 3 that leads to an E1EXPRESS error EVENT ID 24 for the Intel Network Adpater. What can I do to resolve this issue? The OS is a XP Embedded OS and the current drivers I have are:

Intel PRO Network Connections Software (Version 11.2 Driver 9.6.31.0)
Intel Management Engine Interface (Version 2.1.22.1033)Intel Active Management Technology Components (Version: 2.1.2.1031)
Local Manageability Service (Version 2.1.2.1019)
Serial Over LAN (Version 5.2.0.1019)
Intel AMT Status (Version 2.0.0.5)

Thanks in Advance

anonymous's picture

Hi Ajay,

Perhaps you can help. We have had an issue where the bios ME was registering in DNS as hpsystem.mydomain. The solutions we've found have been to disable this in the bios.

Now with these PC's, what are the potential impacts of disabling this? Is this just another layer that can be safely ignored?

What is it, in plain terms that this AMT system is providing?

Thanks

Jassen

anonymous's picture

I was doing some research and came across this page/blog. From some of the comments you made and others, looks like the HECI and/or SOL/LMS drivers might be causing my problem. We recently bought 2000 GX755 machines and I have refreshed our hardware independent image to accommodate the new machine. Drivers are all loading fine (including HECI and SOL/LMS along with the Intel Driver). Problem I am having is keeping the resolution at 1024x768 on the GX755. This resolution is needed for several in-house apps that we have. On our other models (gx620, gx280, HP dc5700, etc) this is no problem (even with the new monitor connected). I set the resolution inside the sysprep file. Any ideas on why it will not hold on the gx755? It will always go to the native resolution of the monitor attached. Our new PCs come with the Dell E198WFP monitor which has NR of 1440x900. Thank you.

Ajay Mungara (Intel)'s picture

Hi David,
Thanks for your comment.

I posted your question to our manageability discussion forum (http://software.intel.com/en-us/forums/manageability-software-development/) so that our Intel AMT experts can respond. Please check the forum thread for a response to your question.

anonymous's picture

Ajay,
How to install SOL/LMS and HECI silently via a batch program? I need to do this for our new Dell Opliplex 755. Following is part of my code. It seems to run but exit in a couple seconds. The first one - chipset software installation utility seems working. Please help!

:IntelAMT
Echo Install Intel AMT Chipset Software
Echo Install Intel AMT Chipset Software >>%systemroot%\setuplog1.log

Echo Installing Utility Driver.
c:
CD \Drivers\Dell\GX755\Chipset\Chipset1
start /wait setup.exe -s -sms
Echo Utility Driver Installed, rc=%ERRORLEVEL% >>%systemroot%\setuplog1.log;

Echo Installing Intel AMT SOL/ LMS Driver
c:
CD \Drivers\Dell\GX755\Chipset\Chipset2
start /wait setup.exe -s -sms
Echo Intel AMT SOL/ LMS Driver installed, rc=%ERRORLEVEL% >>%systemroot%\setuplog1.log

Echo Installing Intel AMT HECI Driver
c:
CD \Drivers\Dell\GX755\Chipset\Chipset3
start /wait setup.exe -s -sms
Echo Intel AMT HECI Driver installed, rc=%ERRORLEVEL% >>%systemroot%\setuplog1.log

Ajith Illendula (Intel)'s picture

Hi Rachael,
Did you receive the driver from your OEM? Each version of AMT firmware for a platform come with a version of HECI driver. Please make sure that they are in sync.
What AMT features are you using currently? If you are not using any of the features that needs HECI driver, you can try uninstalling it and monitor your system for blue screens. You can certainly run your system without HECI driver, but some of the AMT features might not be available by doing so. Also before unintalling the driver, please make sure that you can get the drivers from your OEM for re-installation.

Pages

Add a Comment

Have a technical question? Visit our forums. Have site or software product issues? Contact support.