Hi there,
No apology necessary for the long post, we actually like a LOT of detail when reading through these so we can formulate the best response, so thank you for the detail. I believe in your post, you have two questions. Please let me know if I missed something and apologies for the delay in response:
First question:
I gather the status: "Check with OEM" means Intel cant confirm HPs Patch for ME is fixing the 00075. Neither does HP supply me with a probing tool that lets me know 00075 is fixed after Patch. Would anyone share their take on wether I can assume "Check with OEM" means Im ok as long as i Patched according to OEM?
Answer:
If applied HP Version: 8.1.71.3608 patch and firmware has been validated by OEM and then an unprovision/reprovision of your system (if provisioned previously) then your system is considered remediated.
Second, and more important (to me anyway) question:
I have not installed or started a service called "microLMS". I can not find it (or info about it) in the registry or in any documentation available to me (locally, from HP, here on intel site, or in google). I have found that one version of this "microLMS" is placed in the extraction-folder tor the Intel SA Discovery Tool, and I have found another, much larger file online from Mesh Commander / Intel Mesh / Mesh Central (MeshCentral ). Both are called "Mesh Agent Service", -one signed by "MasterRoot" and one signed "Intel". I quess the first of these is a Beta version Intel Mesh Central use for web UI, and the second one extracted by Discovery tool is some "full version" of this small LMS service. The one Mesh Central / Mesh Commander use is afaik (and according to Ylian @ intel / meshcentral) just a port forwarding tool for integration between AMT and Web UI / Meshes. What the Intel signed smaller one is, I have no idea.
Is there an actual service running on my computer called "microLMS"? Does the Discovery tool from Intel invoke it from its own directory upon start of Tool for some kind of auditing purpouse? Is it used to confirm port binding of some sort and thus the last line in the result from the Discovery tool stating "microLMS service state: Running", does not mean a LMS service is actually running on my system?
Answer:
The discovery tool utilizes MicroLMS, for example, if a system is not running LMS, the discovery tool will run MicroLMS included with the tool. MicroLMS is needed for a local application to talk down to the firmware.