I am trying to get Intel vPro AMT configured on my new Windows 10 machine (named COLORADO) which I'll call "the server"
The problem is that I cannot connect to it remotely from a different machine (the client).
I have posted several screenshots/photos in the following gallery:
These are photos of the web interface run on the server, at:
and the MEBX (BIOS extension) accessed with Ctrl-P on boot.
and one of the network configuration in the ACUWizard application.
The web interface, running on the local machine COLORADO in Internet Explorer, is reporting the local IP address as: 0.0.0.0
I don't think this is right?
On a remote machine (even if I turn off the firewall on both computers), I get a web page not found if I try to go to the same URL as above.
Yet on that remote machine, if I run (in a command prompt window):
telnet COLORADO 16992
it does connect, though does not prompt for anything. So there IS something running on port 16992 accessible across the network.
If I run:
I get a response from 192.168.1.67
So there is network connectivity to the OS across the network.
VNC client on the client machine cannot connect to the server.
, and the Intel "Manageability Commander Tool" run on the client also tries to connect for a few seconds, then stops trying with no error message.
Both AMT and the local operating system on COLORADO are configured with static IP address: 192.168.1.67
with default gateway and DNS server set to my router: 192.168.1.254
I had tried setting them both to DHCP, with the DHCP server set to 192.168.1.67 as a fixed IP address, but no difference.
The machine is home-built (June 2017) with a SuperMicro X11SSV-Q motherboard (which supports vPro).
It is in a workgroup (not a member of a windows domain).
It is on a wired network (Ethernet) connected to a home broadband router, and I am currently using a Windows 7 client on wireless on the same local network.
The MEBX version is: Intel(R) Management Engine BIOS Extension v11.0.0.0008/Intel(R) ME v126.96.36.19964
In one of the client apps, it said that MEBX was in client mode. Perhaps it needs to be in Admin mode?
(I tried to do this, but it wanted to see a provisioning server or something, and "SCS").
I suspect it got into Client mode when I used ACUWizard on COLORADO to try to configure it, including changing the password for the "Admin" user to a new password.
The purpose for which I need AMT is to allow me to remote power-cycle the machine. Also to be able to use VNC client to access the BIOS on reboot, and see any errors occurring at reboot.
On the server by default there was no installation of the windows service "Intel(R) Management and Security Application Local Management Service".
To install this I had to download an installer from the SuperMicro FTP site, and this installer was quite old (2009), so might be obsolete??
Edited (8th July 2017) to add website screenshots and MEBX photos:
Web Interface 1:
Web Interface 2:
Web Interface 3:
Web Interface 4:
Web Interface 5: