Recently I logged into the event viewer on the web based active management console and noticed that my server is stuck repeating:
"Operating system lockup or power interrupt."
Starting operating system boot process.
Add-in card Starting ROM initialization.
The server is a TS-140 Xeon server running Windows 8.1 pro with 16GB of ECC, the OS is on a 500gb hd and there's an intel raid 0 array (this gave me an error since I created it after installing windows).
Posting on behalf of one of my customers.
We have a PCIE card with 4 indemendent Broadwell-U processor complexes. Since we don't have a physical serial console connected to the Broadwell-U processors, so we relay on AMT to provide the serial console using the AMT SOL feature.
AMT is provisioned directly on each Broadwell-U via a utility that uses the AMT SDK. It follows the procedures indicated in the AMT SDK for EHBC, configuring each Broadwell-U to AdminControl Mode. AMT SOL and VNC are enabled as well.
I enabled AMT on a client and I cannot add the client in the Platform Solution Manager software on my system. When I add the client, put in the username and password, I get "Unauthorized". I even created another user account through the http://ip:16992 address and tried that versus the admin account which just resulted in the same error. This web access also doesn't allow you to remote access, which would be nice. However, really want to get this vPro Platform Solution Manager up and running. I have tried just about everything.
I am not able to build the linux sample code for WS-Managed. got following error.
/usr/bin/ld: cannot find -lsynclibUbuntu_X64
/usr/bin/ld: cannot find -lxerces-depdomUbuntu_X64
/usr/bin/ld: cannot find -lxerces-cUbuntu_X64
/usr/bin/ld: cannot find -lwsman_clientppUbuntu_X64
/usr/bin/ld: cannot find -lwsman_clientUbuntu_X64
/usr/bin/ld: cannot find -lwsman_curl_client_transportUbuntu_X64
/usr/bin/ld: cannot find -lwsmanUbuntu_X64
collect2: error: ld returned 1 exit status
make: *** [eventLogReader] Error 1
I have an unsolvable problem: I am unable to login into AMT through WEB interface and OpenMDTK tools (commander and director). Instead I am able to log into MEBx.
Audit Log (also known as Access Monitor) is an feature introduced in AMT 4.0 that provides a place to record events and introduces a new type of user called Auditor.
Key features of the Audit Log are: