MeshCommander is a Intel(R) Active Management Technology (Intel(R) AMT) remote management tool. It's feature rich and includes a built-in remote desktop viewer for Hardware-KVM, a Serial-over-LAN terminal, IDER-Redirection support and much more. MeshCommander is built on web technologies and runs on many plaforms. In addition to being available as a stand-alone tool, MeshCommander was built to be very space efficient to that it can be uploaded into Intel AMT flash space to have it served diretly from the Intel AMT web serve.
I've only inserted the .iso file with a debian live.
When I tried to boot it, it worked up until the point where linux tried to find the rootfs, which failed with some odd errors about usb 1-16: reset high-speed USB device number 3 using xhci_hcd:
It turns out that I also have to specify a floppy .img file in the Storage Redirection window.
Can MeshCommander be changed to only redirect the devices that have an image? Or automatically insert an empty ephemeral floppy disk when we only specify an .iso file? Or warn the user about this? Or refuse to work until we supply both images?
While at the prompt:
I've only inserted the
.isofile with a debian live.When I tried to boot it, it worked up until the point where linux tried to find the rootfs, which failed with some odd errors about
usb 1-16: reset high-speed USB device number 3 using xhci_hcd:It turns out that I also have to specify a floppy
.imgfile in the Storage Redirection window.Can MeshCommander be changed to only redirect the devices that have an image? Or automatically insert an empty ephemeral floppy disk when we only specify an
.isofile? Or warn the user about this? Or refuse to work until we supply both images?