I am having issues provisioning a workstation with Windows 7 Pro x64 with vPro v9 via LabTech. I have tried uninstalling and re-installing MEI as well as installing the needed driver updates to the computer but none of these made any difference. I have attached the screen shot of the full error to this topic. Any help would be greatly appreciated. Thanks in advance.
I am using a Lenovo ThinkPad T420 and Windows 7 prof. x64 as my main workstation. Yesterday I did a reinstallation of Windows 7 (ISO image from MSDNAA and not the Lenovo DVD). After the OS and all drivers (using Lenovo System Update) were installed, I had a look at the device manager and recognized the "Intel management engine interface". Since I don't need this function I researched how this device can be disabled. First I had a look in the System BIOS which stated that AMT is disabled:
Thank you for your interest in the Intel® Active Management Technology (Intel® AMT) High-level API Technology.
Introduction to the High-level API Intel Management Library Technology
Intel® Active Management Technology (Intel® AMT) is a capability embedded in Intel-based platforms (in an Intel AMT device). Intel AMT enables remote access to platforms even when the operating system is not available or the platform is turned off. The only requirement is that the platform must be connected to a power supply and a network.
Thank you for your interest in the Intel® Active Management Technology (Intel® AMT) Software Development Kit. The Intel® AMT SDK (Software Development Kit) contains the building blocks and documentation material needed to develop software that interacts with Intel® AMT systems.
The TightVNC don't supports anymore Intel KVM for firmware version 9? I have a machine with fw version 7 and I can get remote access using Tight, but in version 9 I always face a timeout problem.
With Real VNC (only Intel KVM connection mode) works perfectly.
I am using Intel vPro solution manager its only copy the ISO image to that INTEL machine but unable to boot the system.
What could be the problem?
The following doc states the following in section 3.2.1.
"The ES runs asynchronously on a self-timed circuit and uses thermal noise within the silicon to output a random stream of bits at the rate of 3 GHz. "
- 第 1 页