Ylianst / MeshCommander

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.
Apache License 2.0
326 stars 71 forks source link

Question about Remote Desktop #89

Open ZENAdmin-Ops opened 1 year ago

ZENAdmin-Ops commented 1 year ago

Hello,

I have a question about using Remote Desktop when the computer has an external video card installed (i.e. not using the onboard display adapter).

I'm finding that with this configuration when I try to use Remote Control, the display remains blank.

I have tried attaching a video dongle to the onboard adapter, to try and show the on-board video as being "in use"; but this hasn't made any difference.

I was wondering if there might be any other work-arounds to try?

Thank you.

Close04 commented 1 year ago

AMT with dual GPU is a pain. I have the same on my Lenovo mini PC. The video output between the iGPU and the dGPU switches between when you boot up at BIOS stage and when you are in WIndows with drivers loaded. I even tested, only the video feed is missing, the mouse movement on the black remote desktop screen matched the mouse movement on a real screen.

What I did after preparing my Windows 11 with the full set of drivers was to fiddle in the BIOS with the GPU priority. Did the same in WIndows. Now when I boot up I can't see in the Remote Desktop the first part of the boot process (BIOS). I get video output only after the OS and drivers load. I think I had to fiddle with this for a few days before I got it running. But this makes full management a pain, I can't properly install from an ISO like this. It also means my Windows sees the virtual monitor attached to the iGPU by default.

Unfortunately this also means I can't check more right now because the computer is remote and I can't get eyes on the real video output in BIIOS on a monitor but I hope it points you in the right direction. Also what helped me was to use the MeshCommander FW instead of the application. The app routinely told me another connection is established (in use) for some reason.