I've recently implemented OOB in my office and I'm having difficulties getting VNC to connect to the clients. When I try to connect to a client using VNC Viewer Plus I get the following error, "KVM tunnel TLS failure. Check TLS configuration and certificates." Everything else is working. I can connect to the client from IE using HTTPS. Powershell commands are also connecting to the client using TLS with no issues. I've pretty much ran out of ideas on how to get this working. Any help would be appriciated.
I use Ubuntu 13.10 (kernel 3.11.0 amd64) server running on dq67sw.
I'm trying to enable HTTPS on my VPRO enabled server.
HTTP (on port 16992) runs without problems but I think it is not a good idea holding a port always open on my router (directly connected to internet) and sending password on an unsecured connection.
Basically this is my actual configuration (host side):
- a router/firewall directly connected to WAN/Internet with port-forwarding enabled on port 16992 (this port is always open)
- AMT enabled / TLS disabled on host computer (this computer is directly connected to the router)
Hello to all,
I have a question that I hope you all can help me address. We are in the process of provisioning our workstations in my environment so that we can use the Intel KVM functionality. With that being said, we have several Dell workstations each running a different version of AMT firmware. The firmware on our workstations ranges from 7.1.2, 7.1.4, 8.0.4 and 8.1.0.
In AMT 9.5 SDK(IntelAMT184.108.40.206Gold) there is note related to img/iso file redirection for Linux
When working in Linux, Redirection is supported with physical disks only. There is no Linux Redirection support for iso or img files.
But when I checked the Redirection sample program available in AMT 9.5 SDK(ntelamt220.127.116.11gold\IntelAMT18.104.22.168Gold\Linux\Intel_AMT\Samples\Redirection\RedirectionSample), it shows like iso/img can be redirected. README have following details
I recently deployed a Lenovo M93p desktop that has AMT 9.0.2-build 1345. I set up vPro from MEBx, changing the password as required when I first went in to MEBx. That's the password I'm still using to access the web UI.
The web UI event log is reporting thousands of authentication failures (see screen shot).Since the vPro ports are only open inside the LAN and across a private VPN, it's unlikely that it's a real attack.
I found a 2009 reference on this:
I am using HLAPI that came with the AMT 8.1.4198 SDK. I am trying to use HLAPI Redirection with TLS to remotely install another OS using a web interface. I was able to sucessfully change the HLAPIVariables.TempFilesDirectory so that temporary files are created in a directory the site has write access to. This is essential since the application running the actual code is IIS. This works fine and the MC.ini file created by the RedirectionImpl class is created in the temporary directory I created. However the imrsdk dll also creates some temporary files, a log file and a client.db file.
I found this forum from the Open Manageability Developer Tool Kit (MDTK) page.
I'm setting up a new Lenovo M93p running AMT 9.0.2-build 1345. This is for a small business, so it's all manual provisioning. I've turned on SOL, IDER, and KVM. I've set user consent to NONE.
I can access the machine via a web browser (port 16992) for power control, log viewing, etc. However when I try to Connect from MDTK 1.26, the connection times out. Same thing if I try to connect from UltraVNC.
Hi. We're trying to use iAMT on some boards that are being developed for us, but having one issue:
We setup a MEBx password on the board, and everything works great. We have Admin level access and can KVM/etc as needed. However, once line power is removed and the CMOS battery is missing/dead, the MEBx account resets and we lose our iAMT config. After that, we obviously can't KVM/etc to fix the machine.
I have two "SUN Microsystems" workstations identical but one is not able to access the Management Engine BIOS Extension (MEBx).
There's no point in which, during boot, it tells 'Press <Ctrl-P> to enter MEBx Setup', I have tried serveral reboots pressing every solitary second 'Ctrl+P' but still absolutely no way to access. I have also tried to update the BIOS version several times but still nothing.
The other identical machine works fine instead and it is showing the Ctrl-P message.