AMT Activator Packaging
Activation of vPro systems that have not completed the provisioning/activation process prior to being placed in the field can be a daunting task in a large enterprise environment. Especially in the common situation where vPro systems have been deployed before the backend infrastructure is in place, and widely dispersed throughout the organization.
Challenges associated with activating dormant vPro devices are as follows:
The "hello packet" process must be restarted if more than 24 hours has passed and the system is still un-provisioned since the system was plugged into power. There several different ways to accomplish this:
Completely removing power from the system (including the battery for laptops), then plugging it back in.
Package and deploy the Activator Utility (formerly known as the Remote Configuration Tool (RCT)) to the local system.
Once the "hello packet" process is restarted, the system should contact the provision server, be identified by its fully qualified domain name (FQDN), receive its provisioning profile and complete the provisioning/activation process.
Intel HECI, LMS and UNS Drivers must be updated to current versions supported by your OEM, in order to successfully use Activator within the Windows environment.
It is also recommended to update the Intel® AMT firmware or system BIOS to the most current version depending on the specific hardware platform (i.e. AMT 2.x, 2.5, or 3.x.)
Using the Activator Package
In this guide we will use the Activator Package approach. In order to streamline deployment to multiple remote PCs, the Intel Activator Utility has been pre-packaged using a VB script with all of the command line syntax, and associated DLLs that the activator.exe requires to run in the background with no end-user intervention or prompts. The single executable is named iamt_activator.exe.
At launch, the Activator package (iamt_activator.exe) creates a directory on the end-users hard-drive, e.g. c:\activator_provisioning.
It temporarily extracts the activator.exe , libeay32.dll, msvcr71.dll, ssleay32.dll, StatusStrings.dll and iamt_activator.vbs
It launches the VB script that provides the activator syntax to perform the requested function and runs activator in the background, and creates a file Activatorlog_<NETBIOS name>.txt.
Once activator completes the results are captured in the Activatorlog_<NETBIOS name>.txt file and the activator.exe, VB script and associated DLLs are removed from the previously created folder. The text file remains in order to review the results, if needed.
The Intel activator utility does have requirements that will need to be considered in order to successfully activate dormant machines. It is highly recommended that you review the current to assist in planning your deployment. Additional information can be found here: http://software.intel.com/en-us/articles/intel-vpro-technology-activator-utility
The proper Intel HECI, LMS, and UNS drivers for the target OS need to be installed on the system prior to activation.
The current BIOS firmware loaded on the platform.
The permissions properly configured (below is an excerpt from the Intel Activator 126.96.36.199 User's Guide regarding permissions)
a. It is recommended to run the utility from the Local System account to retrieve platform information and to communicate with Intel AMT via the Management Interface driver. However, as it is possible to run it as domain user as well, the user running the tool should have the Client Configuration role in SCS and administrative permissions on the AMT system.
+b.+ The platform must have a Client Configuration role to enable the utility to perform its regular tasks. If the utility will be used for changing the Intel AMT platform's FQDN in the SCS repository, it will also need the Operator role. See Adding a User in the chapter Configuring Users and Groups in the Intel AMT Setup and Configuration Service Installation and User Manual. A straightforward way to do this is to define a Group for all platforms with Intel AMT that need setup and configuration, grant the group the Client Configuration role, and add platforms to this group when they are added to the domain or when it is time to configure the Intel AMT capability. Note that the default Domain Computers Group cannot be granted the Client Configuration role.
Example of an Activator Package http://communities.intel.com/openport/docs/DOC-2122