This is the second post about configuring Intel vPro with Linux, the first post was about Intel Setup and Configuration Service 7.2 that is a special version designed for Linux users, actually only supported on SUSE Linux Enterprise Desktop (SLED) 11 SP1, 64bits.
Now, I’ll describe how to configure a Linux machine using Intel SCS 7.2 for Host-based configuration. The very first step is to install the required drivers and services in order to allow the ACUConfig (i.e. a utility that is part of Intel SCS) to communicate with the Intel ME for locally provisioning the Linux machine.
Intel Management Engine Interface:
It’s a driver that must be installed that allows applications to access the Management Engine firmware via the host interface. Messages from the Intel MEI driver are sent to the systems log (i.e. /var/log/messages). Once the Intel MEI driver is running, an application can open a file to it, connect to an application on the firmware side, and send and receive messages to that application.
There isn’t a console output showing that installation succeeded.
Intel Local Manageability Service:
The Local Manageability Services (aka. LMS) allow applications, such as ACUconfig, to access the ME firmware via the Management Engine Interface. The LMs is dependent on the MEI driver, so the MEI driver should be installed prior to LMS installations. As the majority of Linux services, LMS runs as a daemon and messages from the service will be sent to syslog. Once the LMS is running, it listens for incoming connection requests on the following ports:
You should receive a message in the console about the status of installation and service.
Now that your Linux is ready for host-based configuration, you can test and check the status of your vPro machine using ACUConfig using syntax like this:
linux-8xff:/home/bruno/Downloads/IntelAMTSCS/Executables # ./ACUConfig -Output console Status Starting log 2011-12-27 19:23:42
: Retrieving machine status...
Intel(R) AMT version- 7.1.3
The system is unconfigured.
The system TLS setup is using PKI.
The system supports host-based configuration.
AMT state- Pre-Provision(0)
Exit with code 0 - The requested operation completed successfully.
Note in this output that the system is unconfigured and that supports host-based configuration.
In order to configure Intel® vPro™ it is required that we supply information about how the machine behaves such as: WebUI, IDE-R, KVM, security authentication and authorizations, network connectivity, etc. The way that we accomplish it with Linux is the same with Windows machines: you should use Intel SCS 7.1 console to create the profile and export to .xml file.
This process is fully documented in Intel SCS 7.1 documentation folder.
The provisioning process is very similar with Windows ACUConfig version as you can in this video:
At this point, we are able to manage an Intel vPro machine in User Control Mode.