Replies: 1 comment
-
Oh, I should also add that while I had a monitor and keyboard connected at one point, I was seeing a bluish "two computers" icon that would flash in the upper right of my monitor like every five seconds or so which I'm fairly certain I've never seen this particular monitor do. So I assume that was some AMT "activity indicator" essentially, which is all the more frustrating since it clearly seems to be hooked into the GPU at some level. I think I did have MeshCentral sitting on one of the three different remote access screens at the time. I don't think it was the Desktop tab, but rather one of the two SOL tabs. That's assuming the Terminal tab and the Intel AMT -> Serial-over-LAN tab are essentially exposing the same underlying functionality. It's also worth mentioning that those last two tabs also actually have a connect button (well, Terminal says "HW Connect" and the AMT one just says "Connect") which actually does switch between connected and disconnected whenever I click the button. This is why I assume the SOL stuff would actually work fine if I bothered to configure a tty for it. But again, the BIOS level access is what I was really hoping for, without needing to spend even more money on something like a PiKVM. |
Beta Was this translation helpful? Give feedback.
-
I've spent the better part of a day at this point trying to determine whether this is even possible. I recently purchased the ASRock Industrial NUC-125H to replace my fairly old PC Engines APU2 as my router. It supports Intel's AMT and the basic remote power control functionality and querying of information is all working via a MeshCentral instance running on a Linux machine in my local LAN.
However, the real functionality I was hoping to utilize was the remote KVM functionality to be able to access the device's BIOS as well as perform any sort of operating system related installation tasks. I wasted a whole bunch of time going down the OpenWSMAN rabbit hole only to find out these more recent AMT versions have disabled VNC functionality entirely apparently. I had basic wsman functionality working with commands like:
after grabbing that cert.pem from:
So pivoting over to MeshCentral was easy enough as I had the basic AMT stuff working from remote systems in my LAN. However, I then ran into the brick wall of MeshCentral not giving me anything useful under the Desktop tab of the device I added as an agentless, AMT only device. It simply says
Disconnected
under that screen with no other options to do anything else that might be useful, aside from changing the image encoding settings, etc. I assume I could probably get the terminal or serial over LAN stuff going by passing the right arguments to my kernel or running a dedicated terminal on the correct tty (I'm seeing both ttyS0 and ttyS1 in my kernel boot log). But this isn't really the level of functionality I'm hoping for here, as it still wouldn't allow me to say, access the BIOS or boot any random OS and control everything remotely.I'm running the latest release version under NixOS (which also took a little sleuthing to track down the --datapath argument):
without any initial server config.json being passed in. So maybe it's a simple matter of enabling a server option?
Anyway, I'd love to hear that this all works somehow. But I figured rather than continue banging my head against this brick wall, I'd simply go to the source and hopefully get some clarification on all of this.
Thanks for any information!
Beta Was this translation helpful? Give feedback.
All reactions