1) Enabling kvm is a very important step that's easy to miss. Meshcentral doesn't give you any helpful hints if you forget it.
2) When the remote graphical console is in use, the _physical_ display will have an alternating yellow/red border and will periodically go blank. Impossible to miss and highly annoying (if you're OK with the remote access). I suspect there's a way to disable this when connecting with one of the expensive/"secure" tools, as otherwise the poor person being helped would start bleeding from the eyes.
3) On the device I've used it with, a monitor must be plugged in or the remote graphical console won't work.
4) When the OS initializes NICs, it may cause AMT to lose connectivity. I tried to give my ME its own hostname in the BIOS config (which should fix this), but got incomprehensible errors when I tried to change the option. On multi-NIC systems, one solution is to prevent the OS from using the NIC shared with AMT.
Power management, mobile and firmware developer on Linux. Security developer at Aurora. Ex-biologist. mjg59 on Twitter. Content here should not be interpreted as the opinion of my employer. Also on Mastodon.
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
Re: graphical console in linux
Date: 2017-05-03 03:47 pm (UTC)1) Enabling kvm is a very important step that's easy to miss. Meshcentral doesn't give you any helpful hints if you forget it.
2) When the remote graphical console is in use, the _physical_ display will have an alternating yellow/red border and will periodically go blank. Impossible to miss and highly annoying (if you're OK with the remote access). I suspect there's a way to disable this when connecting with one of the expensive/"secure" tools, as otherwise the poor person being helped would start bleeding from the eyes.
3) On the device I've used it with, a monitor must be plugged in or the remote graphical console won't work.
4) When the OS initializes NICs, it may cause AMT to lose connectivity. I tried to give my ME its own hostname in the BIOS config (which should fix this), but got incomprehensible errors when I tried to change the option. On multi-NIC systems, one solution is to prevent the OS from using the NIC shared with AMT.