And as of today the AMT Remote functionality does
NOT work anymore!!!
For both machines the AMT Manageability xxxxx Tool can not make a connection, so
NO Console anymore

Even the http(s) pages which should be available are not.
Soft & FW levels:
Code: Select all
MEBx Version 7.0.0.0061
FW Version 7.1.40.1161
UNS Version 7.1.80.1213
LMS Version 7.1.80.1213
MEI Driver Version 7.1.70.1198
SOL Driver Version 7.1.70.1199
On 1 machine tried different ip settings, which are pingable, but NO response for http(s) or Manageability.
Code: Select all
System.Net.WebException: The operation has timed out
at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
at System.Net.HttpWebRequest.GetRequestStream()
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at SecurityAdministrationService.Invoke(String methodName, Object[] parameters) in C:\Users\Public\Downloads\CommonComponents\Manageability Stack\WSDL\SecurityAdministrationInterface.cs:line 51
Is the only answer i get, even when i am with the console-PC on the same network!
This is very annoying and nowhere a solution.
Getting bored about all those windows issues every day ....
[UPDATE]
After switching off & on the AMT functionality within CTRL-P during machine boot on 1 machine, we have access again to the http://<IP>:16992 web-gui, which is enough for this machine. Taking over your own desktop isn't much fun if it's on the same machine (as this isn't working now, don't know if it did). This one should be able to take over the other Lenovo i7-2600's screen, and a VM within that other machine should be able to take over this screen

The other machine could not be rebooted, yet. This is the ESXi5.5 machine. Here the 16992 page first returned a 500 Server error page, now it does not respond at all. Waiting for the backups be made on the NAS environment so we can re-power all once again. Hopefully 2016 we don't need that too much.
DG.