Erd Commander For Windows 10 Usb Boot
Keena Wiegert
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.
However your description left me wondering exactly how were you connecting? If you where using only the Commander tool, then you were actually using Serial-Over-Lan (SOL). AMT Commander does not have KVM technology integrated by default. That would explain the lack of visible connection as the device was possibly at gui based windows(KVM) vs command line (SOL).
The initial connection is always via Remote Commander Tool. I have installed self-signed certificates on all managed machines, so I use Remote Commander to initiate the SSL connection, then click Launch Viewer to do KVM using UltraVNC. (Blogged all this here.)
When I say it couldn't connect, I mean that when I clicked on Remote Commander's "Connect" button, it tried for a while ("Abort Connect") then gave up (went back to "Connect'). The button never changed to "Connected" so both the "Take Control" and "Launch Viewer" buttons stayed grayed out. In other words, I never got as far as Serial-over-LAN.
I realize troubleshooting an issue that is no longer occurring is almost impossible. Just thought I would check if there is a known issue (so I don't drive home next time before I finish!). It occurs to me I should have checked Help > Debug Information while the error was occurring and;/or done some packet sniffing. Probably not worth it to me to try to recreate the issue at this point.
Your usage model according to the blog looks just fine and as far as I can tell things should have worked as expected. Sounds like we might not figure this one out, if you encounter it again let us know.
Thanks Joe. So what triggers the "handoff"? It seems like AMT maybe handed off network control to the "OS" but it wasn't really an OS, just a boot error, so it didn't load a network driver. Is there a flowchart somewhere that explains how the control flow works?
The handoff of the LAN connection is the activation or deactivation of the Network driver within the OS. An easy way to see this is to setup a non terminating ping (ping -t) to the vPro client and then disable the network interface within the OS. This will provide a temporary stop to returns (2) of the ping packet and then a restart with a different TTL value.
If I had to conjecture, it was probably a BIOS issue of some sort and how it handled the handoff. During POST, the BIOS which temporarily "owns" the NIC failed to release control, as there was a corrupt MBR. If you continue to see this, I would recommend filing a bug report to the OEM to root cause the issue
The odd thing is that I saw the boot error in the KVM window the first time (I know because I wrote it down after seeing it). I'm pretty sure it was after I attempted to reboot remotely from the Commander Tool that I lost the KVM and further connections failed. It's like the error screen was displayed while the BIOS was still in control but then it did the handoff--to nothing. I.e. the BIOS failed to _retain_ control since there was no network driver in the bootloader OS.
I'm running into a similar problem with an Asus Q170M-C-CSM motherboard. If Windows 10 crashes during boot (which it has been on a consistant basis, usually during automated reboot due to updates being installed), the remote power controls don't work even when I've been connected from commander from boot.
If you are connected via wired connection and watching the boot process and the KVM fails when the OS crashes. It sounds like it is a OS and Board interaction causing a disconnect. I would put a ticket in with ASUS for them to resolve the Win 10 issue
Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.
I booted my computer today and found the Grub rescue command prompt. I have been given this computer and it has Linux and windows 7 on it, but I have only ever used the windows section. I have no idea about Linux at all, and was startled by this "Grub" thing.
It won't let me do anything in the command prompt, and i can't boot windows. I have a netbook, so there's no CD drive on the computer. I need a way to get into windows 7 from this command prompt. With a little bit of searching (on my phone) I found a couple things to enter that are supposed to let me into windows. I tried this:
That was the first sequence of things that didn't give me an error. But when I got to typing "boot" it told me the Bootmgr cannot be found...? I have no idea what this means. All I want to do is to be able to boot windows again, I don't care how, I just want access. Like I said, my computer doesn't have a CD drive, so I can't use a disk. Is there a way to fix this through the Grub command prompt? Any answers would be appreciated.
d3342ee215