I have a SuperMicro X9SAE mobo (7-series C216 chipset socket 1155), with latest BIOS 2.3 which comes with latest AMT version 8.1.72.3002 and MEBx 8.0.0.72. The management engine works well except after unplugging the system from AC mains, while off, and plugging it back in. If I do that I can log onto the AMT web UI at port 16992 but when I issue a remote control command to turn on the system, the counter counts, nothing happens and at the end of the countdown I even get kicked out of the web UI, having to log back in.

On the other hand, if I boot the system manually, shutdown the system to OFF while leaving the AC power connected, I can log onto the AMT Web UI and issue a power on remote control command and the system boots fine.

I have tried everything: reset BIOS NVRAM, take out battery, AMT reset jumper JPME1 which unprovisions everything. It is driving me crazy as I would like to be able to remotely turn on my system even after AC power interruption. The OS installed on this machine is Windows Server 2016. The CPU is a Xeon E3-1245V2, ECC RAM. I have tried different power supply and removing all pheripherals too. Thanks for any pointers.

Thanks, I will try this tonight.

I tried it and went into MEBX to activate the network interface. Then I briefly unplugged the system and was able to turn on the system via the web interface. So I thought the problem was resolved.

After this I booted Windows Server 2016, I shut it down and unplugged it for a long time. At that point I was no longer able to turn on the system via the AMT web interface. Now I am wondering whether there is something about the MEI driver in the system. Or it could be some hardware problem. Or it could be that latest AMT version 8.1.72.3002 has bugs in it and I need to downgrade.