KVM & Intel AMT
Hello,
I've been working to get Intel AMT up and running on a PC in my environment.
I've now got everything setup and working but I'm unable to "Remote Desktop" into the PC via AMT's "KVM Remote Desktop" feature.
I've tried using MeshCommander (version 0.7.7) as well as Intel's Manageability Commander (Version 2.0.345) to connect via Remote Desktop.
When I hit "Connect" in MeshCommander's Remote Desktop connection screen it goes to "Setup..." for about a second then to "Disconnected."
I get a similar result in Intel's Manageability Commander.
I'm not sure what else I need to do here to get it to connect. I have followed the video instruction on Intel's site to get everything to this point:
https://www.intel.com/content/www/us/en/support/articles/000026592/technologies.html
Everything else with ATM seems to be functioning with the exception of the Remote Desktop KVM feature. I can even connect via serial over LAN.
Any help is appreciated.
All Comments (7)
Hello,
Have you tried RealVNC Viewer Plus?
Regards
David Hervieux
I've tried with the non plus version which also did not work.
A questiin on the VNC method though. Do ports need to be specified when using VNC and if so which ports ?
I've tried to enable 5900 in AMT via MeshCommander and the Intel utility and that fails when I attempt to provide a password for the port.
Update :VNC Viewer Plus provides the following error:
"Error: 0x80862001: Unsupported or inactive display adapter."
Which is due to having an add on display adapter in the PC. Any way to work around that without pulling the add on card?
Hi Kevin,
Would it be possible for you to post a screenshot of Mesh Commander's system status page?
Also, have you tried connecting from RDM with a ATM or VNC session?
The port used will vary depending on how your server is configured.
A server configured for encrypted port redirection will use port 16995.
A server configured for unencrypted port redirection will use port 16994.
A server configured without port redirection will use port 5900.
Port redirection, encrypted or not, is the preferred method if I'm not mistaken.
Jonathan Lafontaine
I can work to get that however I think this may be the issue:
https://support.lenovo.com/us/en/solutions/ht062228
I'm not seeing the onboard graphic controller in device manager on the PC so I'll have to enable that in BIOS.
Let me know the outcome.
Jonathan Lafontaine
Enabling the onboard graphic adapter per the steps in the link above from the Lenovo site is what it needed.
Remote Desktop/KVM is now functioning in MeshCommander and the Intel Utility.
There is a catch however, due to the dual adapters if you do not have the onboard graphics set as your "primary" in windows you will only see what would be displayed on the second monitor (due to the extend desktop setting in windows).
In a pre-boot environment the onboard graphics will take over as the primary so that should be good enough for me as I use RDP to access the PC in windows if it is up and running.
I'm going to try an plug in a smaller monitor into the onboard graphics and choose "duplicate" displays to see if that has a better result.
Thanks for the replies.