| Last Modified On : | December 1, 2008 9:35 AM PST |
Rate |
|
FAQs
Intel® AMT/ME is setup correctly, but my password is always rejected when trying to connect through the WebUI or the Manageability DTK tools. What is wrong?
The problem could be with your keyboard mapping. MEBx thinks that you are typing on a QWERTY keyboard and if you are using an operating system that has a different keyboard mapping, the password will not match.
Is there something in Intel® AMT that blocks remote desktop traffic? After installing the chipset drivers (Intel® AMT HECI, Intel® AMT SOL and Intel Chipset Software) I am no longer able to remote desktop to or from this system. I have a Dell© Optiplex 755 system.
There aren’t any settings in Intel® AMT that could block the remote desktop traffic. The problem could be due to the wrong Video Driver. The Dell Driver CD comes with RADEON® HD 2400 PRO and RADEON HD 2400 XT, you have to make sure that you install the correct one. Device Manager does not show any issues with the wrong driver. So, go to your Event Viewer and see if you have any errors with RDPDD.dll. If so, try installing the correct driver from the CD or support.dell.com.
Is it possible to have a null or invalid GUID on an Intel® AMT system?
The GUIDs are initialized, stored and handled by the BIOS. So it is possible that an Intel® AMT device gets a null or invalid GUID, but Intel® AMT will detect it as invalid and won't use it.
Can malware detection in Intel® AMT replace antivirus applications?
No, you want to have both at the same time. One big benefit of Intel® AMT is that it is tamperproof. When you put policies in Intel® for malware detection, they cannot be circumvented in anyway from the host. The drawback is that Intel® AMT is located underneath the host operating system and doesn't have all the information that a host application would have. So really a combination of the two is ideal.
Is there a way to install an operating system on 20 computers at the same time with Intel® AMT?
The answer is yes. Intel® AMT provides the ability to boot a disk remotely on the computer. The first step is to mount a CD-ROM drive onto the remote computer and then boot off of the remote CD-ROM drive. The rest of it is up to the administrator like building an ISO image that performs all the operations the administrator wants to perform.
What if the DHCP server is not working? There is no way to connect to the machine, right?
When Intel® AMT is configured for DHCP mode, if the DHCP server is not working, Intel® AMT will never be able to obtain a valid IP address and you will not be able to connect to it remotely. If Intel® AMT is configured in static IP mode you can connect to it using the static IP address.
I am getting an error message about communication to the Intel Manageability Engine. I have an Intel DQ35MP motherboard and an Intel® Core™2 Quad. I had previously updated to the latest BIOS and it was working fine. I have re-flashed the BIOS but the problem remained the same?
You should do a CMOS reset. For this, disconnect the power cord and LAN cable. Remove the CMOS battery for 15 seconds and insert it back in. When you power on, the Manageability Engine settings will revert to their factory defaults. The default user name and password is admin/admin. Please remember to change it to a strong password before configuring the ME further.
The system is unresponsive and won't boot. How can this be resolved?
- Unplug power cord, wait 20 seconds and try to boot the system again.
- DIMM 0 must be populated with memory for AMT to work. AMT firmware is uncompressed and run in DIMM 0.
Difficulties with building the Sample Code in the AMT SDK.
Please refer to the Intel AMT SDK User’s Guide in the DOCS folder of the SDK for prerequisites and setup information. Also take a look at this video: http://software.intel.com/en-us/videos/how-to-compile-intel-amt-sdk-sample-code
The Intel® AMT system will not boot on USB key.
- The USB boot partition needs to be 256MB or smaller.
- Need to format USB key to be DOS bootable.
After a few successful writes to the Intel® AMT Storage, write errors occurred for all subsequent writes. Re-flashing the AMT memory did not help, but leaving the system on overnight did help. Why is this?
Flash write limits may have been exceeded. Optimize writes to see if this resolves the problem. Flash wear out protection is enforced by AMT to avoid permanent damage to flash by malware. Once the limit is exceeded, there is a time limit (40 minutes) that must be satisfied in order to write again.
Hello packets are sent only when OS is on.
This is probably because the Intel® AMT has been configured to only be active in S0 state. Try changing the Intel® AMT communicate when the system is in Sx state (when the OS is not up). Look for the configuration setting in the MEBx.
When working in DHCP and setting a block-all policy in System Defense, after a certain amount of time AMT will be inaccessible.
When in DHCP mode, the AMT system relies on the host operating system (OS) to respond to IP network traffic requests (ARP requests). These requests are cached, so the OS will continue to respond to the ones from the cache even after the filter has started to block new ones coming in.
Workaround: When defining a block-all policy, make sure to define 2 extra filters.
1. Pass Tx filter on Ethernet header for 0x806 (ARP)
2. Pass Rx filter on Ethernet header for 0x806 (ARP)
3. Make sure these filters are part of the policy.
This will make sure that the host will answer ARP requests.
What are the possible reasons for the Intel SCS Exception: Cannot contact back AMT with IP:xxx.xxx.xxx.xxx?
Check the following:
- The current password of the security key entered to the MEBx doesn’t match the MEBx password (most common reason).
- Duplicate DNS registration (two host names bind the same IP) .
- The SCS profile TLS PSK is configured to be plain text; the AMT machine doesn’t support this.
- Is there a security program running on the AMT system that might be blocking communication? Also check the Firewall.
What happens if the flash image update crashes in mid-update?
There isn't an issue re-flashing the device if there is a flash write error. There is no dependency between corrupt data and the ability to re-flash the device with a good image.
How can I make sense out of the AMT Event Log messages?
There is a conversion in the IPMI (Intelligent Platform Management Interface) Specification that takes the event data number and turns it into text. You can get the IPMI Specifications at the following link: http://www.intel.com/design/servers/ipmi/spec.htm
How do I turn on the error logs for the Intel SCS application?
You can do this by going into the registry as follows:
Enter a string value V in the following:
HKEY_LOCAL_MACHINE->SOTWARE->Intel->AMTConfServer->LOG then LogLevel
How do you reset the password for the Intel Management Engine BIOS if you have forgotten the password?
In order to reset the password of ME BIOS, disconnect the power cord and LAN cable. Remove the CMOS battery for 15 second and insert it back in. This time when you power on, ME settings will revert to factory defaults. The default user name and password is admin/admin. Please remember to change it to a strong password before configuring the ME further.
My SCS server is not receiving “Hello” messages even though I have entered a PID/PPS key pair and changed the password on the Intel® AMT device.
Make sure that Intel® AMT can connect to your SCS by providing the correct IP address of the SCS in the MEBx or by adding a DNS entry called “PROVISIONSERVER” that maps to the machine the SCS is running on. Intel® AMT can automatically locate the SCS if it can find a DNS for an entry called “ProvisionServer.<your.domain.com>.
When I try to log onto the SCS Console and I have entered the FQDN and the virtual directory, I get the following error message: Login Failed. Reason: The underlying connection was closed. An unexpected error occurred on a send.
Check to make sure the AMT Config service is running. Sometimes the service fails to start or unexpectedly stops after the install.
Where is the SCS getting it’s time from? Windows time is set correctly but the SCS’s time is different.
The SCS gets the time from the OS (displays as UTC.) The AMT Clock can be synchronized from within the SCS User Interface. Make sure the AMT clock check box in the Maintenance Policies portion has been selected. It is also documented on page 85 of the “Intel® AMT SCS Installation and User Manual”
Building AMT ConsoleSln.sln project
I am having trouble compiling the SCS Source code. What version of MS VS is required?
Take a look at the readme with your version of the SCS to see the version of Visual Studio and other prerequisites. When the project is build for the first time, there will be a warning that it could not connect to revision control and asks if you want to temporarily connect without revision control or permanently remove revision control. Choose the “Permanently Remove” option.
