1 of 1 people found this helpful
So you could send SOAP/HTTP request thru the local OS (e.g. browser) and it would excute the ME comands in FW. For example excuting on local browser WebUI.
I believe that if you attempt to communicate via the loopback address (127.0.0.1 or 'localhost'), then the packets are handled at the software driver level and do not actually progress to the hardware devices -- e.g., the NIC or, as in this scenario, the Intel(R) Management Engine (Intel(R) ME). Therefore, the LMS is utilized to forward your local Intel(R) AMT / Intel(R) ME communication to the HECI driver which then forwards the requests to the Intel(R) ME for processing.
If you are reviewing the latest Intel(R) AMT SDK documentation, there is a page titled "Local Access" that details how local communication works for Intel(R) AMT. [<Intel_AMT_SDK>\DOCS\Implementation and Reference Guide\default.htm --> About Intel AMT > Local Access].
Thanks guys, that clears that up. So LMS is not used on a full-time basis, only for loop back scenarios.