Quantcast
Channel: Intel® Active Management Technology
Viewing all articles
Browse latest Browse all 162

AMT could not connect to machine after Windows boot error displayed

$
0
0

Hi,

A customer has a Lenovo M93p with AMT 9.1.0. I have set it up for remote KVM and it works fine.

Last week, I restored this system from a Windows backup. While the restore was running, I left the customer site and returned to my office. When I got back to my office, I was able to connect to the machine using the Intel Manageability Commander Tool, start the remote VNC Viewer, watch the restore complete, and click OK to initiate the required reboot. So far so good.

However, after the reboot, the machine did not start properly; it needed a startup repair. I saw error 0xc00000e as white text on a black background. I believe it was at this point that I tried to use Take Control to reboot the machine. Soon I was no longer able to connect remotely to the machine using the Commander Tool. The machine was not even responding to ping. It was like AMT it was no longer pulling an IP address for the machine. I had to drive back on site to complete the startup repair.

Once I completed the startup repair, AMT remote KVM started working again.

Obviously this is the exact situation where you want out-of-band manageability, and the reason to pay a premium for advanced AMT machines. But it failed.

Is there a known issue with controlling a machine that is displaying a boot error? Is there something I could have done to restore connectivity while off-site?

Thanks,

Mark Berry
MCB Systems

 


Viewing all articles
Browse latest Browse all 162

Trending Articles