I've been tinkering with AMT lately and thinking about using it in our environment. I've made a little test environment just to try out host-based provisioning, but I'm having some weirdness and was hoping someone could explain this behavior.
One thing I can't figure out is how to get into the MEBx after I've provisioned the device. I can log into the WebUI remotely using the Digest admin username and new password, but the MEBx doesn't seem to use this password...? I thought it was the same thing, however I've tried it multiple times and can't seem to get back into MEBx. Any ideas?
Another weird issue I was having was that I could log into the WebUI only through Firefox and Chrome -- Internet Explorer (11) would prompt me for credentials but would not take them... similar to how MEBx seems to be responding. However, I managed to eventually get IE to do this right by using the FQDN in the address bar instead of the IP address.
The reason I'm trying to get back into MEBx is to see if the settings I imported into it from ACUConfig all took. Obviously some portion of them did because the WebUI is up, the ME service said it was provisioned, the ACUConfig log said it was successful, and so on.
The reason I'm wondering if something is not-right is because I can't seem to do any Remote Control (toggle power) with the machine in any state. The WebUI seems to send the command but nothing happens. I also tried Manageability Commander Tool ME and when I try sending it a power off or reset it returns me an "INTERNAL_ERROR" response.
So that's where I am so far. Let me know if you guys have any insight to the behavior I'm experiencing. Here's some of the information on my test machine:
Dell Latitude E6520
Intel AMT ver. 7.1
Intel SCS 184.108.40.206b