Hello,
I am trying to add the SCCM addon for AMT but in resource explorer it says RegKeytoMO_32 on all AMT items. and it seems to be aknown issue. most forums says that it will be solved by having latest the SW, which i have.
any help would be appreciated for pointing me in the right direction.
Info about the addon:
Intel SCS addon: 2.1 for SCCM 2.1.5
Intel SCS: 9.1.2.74
Many thanks in advance,
Per
I've been trying to configure alert based CIRA on my AMT. According to the documentation one of the ways to initiate remote access to the MPS is to generate an event.
So I have a client application which registers itself to AMT with agent presence. Once it registered, all its state events (running, expired, stopped, etc.) are written to the event log.
I want to tell AMT to initiate the remote connection MPS once there was an "Expired" event. However I didn't find any way to do this.
I'm using SCS tool to configure the AMT. The only thing related to the alert based remote access I've found there is the "Alert" checkbox in the "Remote Access" section. But I didn't found any way to specify which alert should initiate the connection.
Am I missing something?
I have purchased 3 DN2820FYKH NUC 1 of which was DOA of the other 2 they are proving hard to configure and use. On one I installed Mint 17.1, then lubuntu, then kodibuntu and gave up none of these could access the Toshiba MQ01abd100 1TB AF512e HDD so I bought a copy of Windows 8,1 x64 and Windows 7 SP1 x64. On the replacement for the DOA unit I loaded win 8.1 with no problems,Icould access HDD from windows. I wanted to know if the other OSes I listed would work, I tried kodibuntu and again could not access The hdd from the OS, reformatted with Gparted to NTFS and tried Windows 7 and got BSOD with error BIOS not fully ACPI compliant. I received this error on both of the functioning units, one with BIOS rev 0034 the other with rev 0048 The BIOS settings I used are:
Proceed with the installation of the operating system.
which I got from the Intel Downloadcenter. If you have installed win 7 on this model NUC please post your BIOS rev number and settings.
Hai,
i am facing an CPU FAN error,
My system configuration:
Asus H97 pro MB
Intel i3 4150 processor
Transcend 4GB ram
1 TB seagate HDD, i purchased 1 month before
Problem:
My CPU fan start after some seconds,
Different Test cases Result:
1.Fan starts after 22 sec,
2.Fan starts after 35 sec,
3.Fan starts after 10 sec.
please give solution to my problem
Hi guys,
We have configured an environment with Intel SCS and intel vpro enabled clients. We have successfully created policies and have distributed these to our clients. All of the funtions/settings are working as expected, we are using the following policy
Profile Name: KerberosProfile
Profile Type: Intel AMT
Network Settings
FQDN will be the same as the Primary DNS FQDN
IP will be taken from DHCP
Active Directory Integration
Active Directory OU:OU=AMT Objects,DC=Demo,DC=local
Access Control List (ACL)
User 1: administrator
User Type: Digest
User has both remote and local access to the realms listed below
Realms: Redirection, PT Administration, Hardware Asset, Remote Control, Storage, Event Manager, Storage Administration, Agent Presence Local, Agent Presence Remote, Circuit Breaker, Network Time, General Info, Firmware Update, EIT, Local User Notification, Endpoint Access Control, Endpoint Access Control Administrator, Event Log Reader, User Access Control
User 2: Demo.LOCAL\AMT-Admins
User Type: Active Directory
User has both remote and local access to the realms listed below
Realms: Redirection, PT Administration, Hardware Asset, Remote Control, Storage, Event Manager, Storage Administration, Agent Presence Local, Agent Presence Remote, Circuit Breaker, Network Time, General Info, Firmware Update, EIT, Local User Notification, Endpoint Access Control, Endpoint Access Control Administrator, Event Log Reader, User Access Control
User 3: adminkvm
User Type: Digest
User has both remote and local access to the realms listed below
Realms: Redirection, PT Administration, Hardware Asset, Remote Control, Storage, Event Manager, Storage Administration, Agent Presence Local, Agent Presence Remote, Circuit Breaker, Network Time, General Info, Firmware Update, EIT, Local User Notification, Endpoint Access Control, Endpoint Access Control Administrator, Event Log Reader, User Access Control
User 4: Demo.LOCAL\Domain Users
User Type: Active Directory
User has local access to the realms listed below
Realms: Redirection, PT Administration, Hardware Asset, Remote Control, Storage, Event Manager, Storage Administration, Agent Presence Local, Agent Presence Remote, Circuit Breaker, Network Time, General Info, Firmware Update, EIT, Local User Notification, Endpoint Access Control, Endpoint Access Control Administrator, Event Log Reader
Transport Layer Security (TLS)
Server authentication used for remote interface
Server Authentication Certificate Properties:
Certificate Authority: TEMPCA-IntelSCS.Demo.local\Demo Temp CA
Certificate Template: IntelTLSaccesscertificate
Common Names (CNs) in certificate: DNS Host Name (FQDN), Host Name, SAM Account Name, User Principal Name, UUID
Network Configuration
WiFi
Do not enable synchronization of Intel® AMT with host platform WiFi profiles
Wired 802.1x
802.1x setup: 802.1x Setup1
Protocol: EAP-TLS
Root Certificate Authority: Demo Temp CA, Demo, local
Certificate Authority: TEMPCA-IntelSCS.demo.local\Demo Temp CA
Certificate Template: IntelSCSprovisioningcert
Common Names (CNs) in certificate: DNS Host Name (FQDN), Host Name, SAM Account Name, User Principal Name, UUID
Do not allow roaming identity
Do not verify RADIUS server certificate subject name
Enable 802.1x for Intel® AMT even if host is not authorized for 802.1x
Keep 802.1x session after boot to allow PXE boot for 60 minutes
Trusted Root Certificates
Below are the trusted root certificates used in this profile:
Root certificate 1: Demo Temp CA, Demo, local
System Settings
Enabled Management Interfaces:
RFB password set
Power Management Settings: Always On (S0-S5), Timeout if idle: 0 minutes
The Intel® AMT clock will be synchronized with the operating system clock
Intel® AMT set to respond to ping requests
Fast Call for Help (within the enterprise network) is Disabled
Problem statement
Now since Intel AMT has been configured we can focus on the problem area:
We use PXE boot on a non 802.1x network to initially install machines. And during the install process machines are provisioned using Intel SCS, with the configuration described as above. When machine is running in full windows we are able to perform all actions like remote control, power feature like shutdown and cold reboot etc.
But if we now try to reinstall the machine the process fails.
Machines, where intel AMT has now been configured they can no longer PXE boot, neither on 802.1x enabled network nor on network without 802.1x. What we are seeing is that machines are able to PXE boot, but during the transfer of WINPE. The PXE boot process stards, boot.sdi is downloaded and then starts the process where WINPE is downloaded. This download fails randomly between 30%-70%. We are using IP helper, and have tried placing the machines on the SAME VLAN as the server, but we get Errorcode 1460 on WDS which indicated TFTP timeout. Just for the sake of testing, we have also tried to set DHCP options 66 and 67. But I must emphasize that, the SAME machine works just fine if we delete the Intel Vpro configuration from BIOS.
Conclusion:
We think that this problem is related to Intel AMT intercepting network communication. But what we find odd is that the problem occurs both on 802.1x enabled and network without 802.1x, why is PXE boot process being effected by enabling/configuring INTEL AMT? Has anyone seen this problem or anything like this? I am wondering if there can be something in the policy that we have attached. During testing, we have also tried to remove the following
Enable 802.1x for Intel® AMT even if host is not authorized for 802.1x
Keep 802.1x session after boot to allow PXE boot for 60 minutes
Thanking you all in advance for your contribution.
Best regards,
Sean
In the SCCM 2012 the “Out of Band Management Component properties” under the General tab, there is a place to select an AMT web server certificate template. Is this still used if the Intel SCS addon is installed? The directions from technet, (Creating and Issuing the Web Server Certificate for AMT-Based Computers) for configuring the certificate template differ from the directions in the Intel SCS user documentation from section:9.2.5 Defining Enterprise CA Templatese directions. Which type of cert is the correct one for this section?
I'm looking to setup AMT in my environment. We decided to use the SCCM add-on with RCS integration. I have two major security concerns with this: First, the instructions in the Intel(R)_SCS_Addon_SCCM_2012.pdf call for giving the Operations Administrator role to the Domain Computers group. That's was a huge security concern to me, since the Operations Administrator role is an extremely powerful one. I was able to find advice on this from another discussion that I found on this site.
This brings me to the second issue, on which I have yet to make any progress. In section 2.7 of the guide, it gives the option to run the packages used by the add-on either as the system account on the host computer (default) or designate an account for running the package. If I go with the system accounts, then it requires me to give every computer Remote Enable rights to the site_<sccm site code> namespace in WMI. This is opening up my SCCM infrastructure to any person who can run something as the system account on any host computer, which is not very difficult to do, so this is not a good option.
The second option (using a dedicated account) also has problems, as I need to grant this account admin rights to all of my hosts and open up the same WMI namespace to it. This is fine so long as I can keep this one account safe. But for this to work, the add-on has to use the “Run this step as the following account” option in the task sequence and store its credentials there. This is a problem, because that password can easily be extracted from any host computer which is able to run the task sequence. In order to verify this, I ran a test of it and was able to get the password for this account from a host, using one very simple step followed by a one-liner. I'm not going to post that here for obvious reasons. This is why Microsoft has multiple warnings about accounts used to “run as” from a task sequence. This issue presents a huge concern because the instructions are calling for this account to have admin rights to all of my hosts, plus the ability to remotely connect to SCCM's WMI namespace. I don't want to leave such a powerful account so exposed.
So, given all of the above, does anybody know of a reasonably secure way to handle this? This can't be the only way to make this work. Of all the companies using AMT, somebody else must have already discovered this problem and developed a more secure method.
Thank you,
-Joe
Hello,
I'm setting up a Supermicro server with an X10SAE board and I have issues getting AMT KVM to work.
I set everything in the AMT ME bootup interface and also configured via KVM Console (KVMControlApplication.exe) to "KVM Status: Enabled - all ports". Here, I was not sure which "Default visibile monitor" to choose, so I tried each of them. Result was always the same:
With any VNC viewer, I can connect to the server. I can authenticate and successfully log in. After that, the attached screen on the server shows a red/yellow flashing border and a connection icon in the right upper corner. When I move the mouse or press a keyboard key in the VNC client, I can see these actions being performed on the server screen.
BUT: The problem is, that the VNC client stays clear. Depending on the VNC client I use, the window stays always black or red. This is independent of the state the server is in, i.e. it's the same if the server is in POST/BIOS/booting up, or the operating system has fully booted. Nevertheless, the client gets notified by the changes of the screen resolution, so the VNC window changes size when the server changes from POST to booting up and then again when reaching the GUI.
Depending on the VNC server I use, the VNC client terminates after a short time (less than a minute) without comments, or tries to reestablish the connection. Interesting enough, Real VNC shows the error message
0x8086210E: Internal KVM failure
which is, according to the "Intel AMT implementation and Reference Guide" an "Internal failure". Not very helpful.
I'm stuck here. Help would be appreciated.
The Intel Active Management Technology webinterface shows:
Platform
Computer model: X10SAE
Manufacturer: Supermicro
Baseboard
Manufacturer: Supermicro
Product name: X10SAE
Version: 1.01
BIOS
Vendor: American Megatrends Inc.
Version: 3.0
Release date: 05/20/2015
Processor 1
Manufacturer: Intel
Family: Intel® Xeon® processor
Socket: SOCKET 0
Version: Intel(R) Xeon(R) CPU E3-1246 v3 @ 3.50GHz
Intel® Active Management Technology firmware version: 9.1.1-build 1000
Thanks in advance,
Christian
Are there any special considerations when using the networkservice account with the Intel SCS addons? The SCS and SCCM would be on the same machine. The SCCM machine account would already have local admin permissions on the clients.
I have installed window 7 64 bit and tried installing intel hd driver from various links but it keeps on giving me the error " this computer doesn't meet
the minimum requirements" however i am pretty sure that my system does fullfill the requirments
system:
lenovo g570
Intel Core i5 - 2410M CPU@2.30GHz 2.30GHz
4.00 GB Ram
64 Bit System type
1 GB Graphic Card Radeon Hd 6300M
Please help
Hello,
We are planning to implement out of band management. The plan is to provision AMT devices from SCCM using the add on package and manage devices from Intel Platform solution manager. We cam up with few points and i am trying to find out an answer. Can you please help understand below points or point to a blog or document that will help understand the process better. Thank you
Thank you
Hello:
I'm new to this forum so please be gentle! Apologies if this got posted to the wrong place.
I have an ASUS Deluxe X99 mother board with an Intel 5820 and 32GB of RAM. I recently installed a RAID1 array with 3 WD RED 4 TB SATA 3 drives as a data array using IRST through the MOBO Intel controller. There are also 2 SATA CDRWs plugged into the Intel SATA controller.
I am using a 240GB SSD as my boot drive and I have 3 Seagate and one Hitachi SATA drives as non RAID disks on the other MOBO SATA controller.
I am currently running Windows 7 64-bit.
Everything works fine, however, looking in perfmon the IAANTmon.exe process eats about 8% of the CPU in an otherwise idle system. This seems excessively high to me. I am well backed up so I tried killing the process and as expected the CPU load dropped by 8%, and the RAID array kept on working fine (as far as I could tell). Before I break down my RAID array I was wondering if this can be fixed.
Questions:
Does anyone know why this process uses so much CPU?
Does anyone know whether it is a configuration problem, with the CDRWs?
Any ideas on how to fix it?
Does it even really need to run? i.e. will the RAID array work correctly without it? Is it just for monitoring? Can I just stop the service from running?
Thanks for your help!
Rob
Hello,
We are planning to implement Out of band management and use SCCM add on package to configure devices and Intel platform solution manager to manage devices. We came up with below questions and i am trying to find answer. Appreciate if you can point to document or article that would help clarify some of the questions. Thank you.
Hi, I've got a X10SLQ (Supermicro) board, along with i7-4770 core.
I bought the new board to make use of the Active Management Technology (AMT) provided in the vPro.
Anyways the AMT webgui is functional during normal usage, however when the kernel panics (because I put together a faulty kernel code)
the web gui is non-responsive. (Exactly the time I need the AMT functionality to reboot the machine)
Is it normal for AMT to be non-responsive during a kernel panic (linux).
I've noticed that on the kernel panic, the ssh session was also shutdown immediately (my previous board took a while until it reported a broken pipe)
My board has 2 LAN ports. If I use the second LAN, and leave the first LAN unused (we use static IP, and if i do not allocate any IP to the first LAN)
would this make any difference?
Thanks,
I have to believe this is a common error encountered during the early stages of implementing AMT in an enterprise, but have yet to find any documentation or posts. I'm attempting to use configurator to provision an AMT system for AD authenticiation. When doing so I get the following error indicating that the password being set by configurator does not meet our domain policies.
ACU Configurator, Category: Exit: ************Exit with code 33. Details: Failed to configure this Intel(R) AMT device. An Active Directory interface internal error occurred. Active directory function padsUser->SetPassword failed with error -2147022651 (The password does not meet the password policy requirements. Check the minimum password length, password complexity and password history requirements.: LDAP Provider: ). AMT FQDN name could not be resolved (localhost).
We need to implement Fast call for help through intel vPro. D
I have a customer setting up a driver respository for their standard platforms. They need the drivers in the repository to be in sys/inf format for automatic builds on the target platforms. The Intel chipset driver is only available as an exe. Is there a way to get the inf type driver files from the exe?
Good Morning,
First sorry for my English guys.
I'm currently trying to implement V-PRO solution in my SCCM lab environment.
I have followed the procedure available on this website:
Integrating Configuration Manager 2012 R2 with Intel SCS 9.0 – Part 1 : Introduction | SCCM GURU
I have installed the Intel SCS 10 and my client computer is running the AMT version 9.0.
My problem is when I want to deploy the task sequences, Intel SCS Discovery completed succesfully but the Intel AMT Discovery failed.
I have tried to run it manually in running the file "discovery.bat" but it failed as well.
I would like to understand what it's going on ?
Is it a problem with certificates ?
I just would like to know where I have to investigate to fix the problem.
Here is the log file SystemDiscovery.log :
Thank you very much for precious help.
2015-08-12 12:18:29: Thread:5096(INFO) : ACU Configurator , Category: HandleOutPut Source: CmdUtils.cpp : Cmd::HandleOutput Line: 79: Starting log 2015-08-12 12:18:29
2015-08-12 12:18:29: Thread:5096(DETAIL) : ACU Configurator, Category: VerifyFileSignature Source: Src\ActivatorMain.cpp : configurator::VerifyDLL Line: 102: Verifying the digital signature of ACU.dll, this operation might take up to 3 minutes...
2015-08-12 12:18:29: Thread:5096(DETAIL) : VerifyFileSignature, Category: File: ACU.dll Source: Verifier.cpp : SCS_Crypt::Verifier::Authenticate Line: 235: Entering
2015-08-12 12:18:29: Thread:5096(DETAIL) : VerifyFileSignature, Category: File: ACU.dll Source: Verifier.cpp : SCS_Crypt::Verifier::Authenticate Line: 250: Exiting
2015-08-12 12:18:29: Thread:5096(DETAIL) : ACU.dll, Category: SetCompatibilityMode Source: ACUDll.cpp : SetCompatibilityMode Line: 220: Set compatibility mode to 10.0.
2015-08-12 12:18:29: Thread:5096(INFO) : ACU Configurator, Category: -System Discovery- Source: Src\ActivatorMain.cpp : wmain Line: 409: I0PTXLPT00.dtilab.lab: Starting to discover the system information...
2015-08-12 12:18:29: Thread:5096(DETAIL) : ACU Configurator , Category: -Start- Source: ACUDllWin.cpp : SystemDiscovery Line: 57: ***** Start SystemDiscovery ******
2015-08-12 12:18:29: Thread:5096(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : HeciDiscovery Line: 547: Entering
2015-08-12 12:18:29: Thread:5096(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : CheckAMT Line: 85: Entering
2015-08-12 12:18:29: Thread:5096(DETAIL) : ACU Configurator , Category: -HECI- Source: HECIWin.cpp : HECIWin::Init Line: 191: Connected to the Intel(R) Management Engine Interface driver, version 9.5.14.1724
2015-08-12 12:18:29: Thread:5096(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : FWUpdateData Line: 46: Entering
2015-08-12 12:18:29: Thread:5096(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : FWUpdateData Line: 64: Exiting
2015-08-12 12:18:29: Thread:5096(INFO) : ACU Configurator , Category: AMT Mode Source: HECIDiscovery.cpp : CheckAMT Line: 418: Intel(R) AMT in PROVISIONING_MODE_ENTERPRISE
2015-08-12 12:18:29: Thread:5096(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : GetPKIDNSSuffix Line: 951: Entering
2015-08-12 12:18:29: Thread:5096(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : GetPKIDNSSuffix Line: 980: Exiting
2015-08-12 12:18:29: Thread:5096(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : CheckAMT Line: 540: Exiting
2015-08-12 12:18:29: Thread:5096(DETAIL) : ACU Configurator , Category: -HECI- Source: HECIWin.cpp : HECIWin::Init Line: 191: Connected to the Intel(R) Management Engine Interface driver, version 9.5.14.1724
2015-08-12 12:18:29: Thread:5096(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : FWUpdateData Line: 46: Entering
2015-08-12 12:18:29: Thread:5096(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : FWUpdateData Line: 64: Exiting
2015-08-12 12:18:34: Thread:5096(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : PKIDiscovery Line: 882: Entering
2015-08-12 12:18:34: Thread:5096(DETAIL) : ACU Configurator , Category: Hash Handle Source: HECIDiscovery.cpp : GetPKIHashes Line: 1043: Hash Handles number:15
2015-08-12 12:18:34: Thread:5096(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : PKIDiscovery Line: 933: Exiting
2015-08-12 12:18:34: Thread:5096(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : GetAmtFQDN Line: 1439: Entering
2015-08-12 12:18:34: Thread:5096(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : GetAmtFQDN Line: 1520: Exiting
2015-08-12 12:18:34: Thread:5096(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : ConfServerDiscovery Line: 1187: Entering
2015-08-12 12:18:34: Thread:5096(DETAIL) : ACU Configurator , Category: Status message Source: HECIDiscovery.cpp : ConfServerDiscovery Line: 1241: AMT Status code - Essential data is missing from the AMT. (0xc0004a71)
2015-08-12 12:18:34: Thread:5096(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : ConfServerDiscovery Line: 1265: Exiting
2015-08-12 12:18:34: Thread:5096(DETAIL) : ACU Configurator , Category: GetPID Source: HECIDiscovery.cpp : HeciDiscovery Line: 804: AMT Status code - Command is not available in the current provisioning/boot state. (0xc000426b) (GetPID)
2015-08-12 12:18:34: Thread:5096(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : ReInitPTHI Line: 1678: Entering
2015-08-12 12:18:39: Thread:5096(DETAIL) : ACU Configurator , Category: -HECI- Source: HECIWin.cpp : HECIWin::Init Line: 191: Connected to the Intel(R) Management Engine Interface driver, version 9.5.14.1724
2015-08-12 12:18:39: Thread:5096(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : LMSDiscovery Line: 1273: Entering
2015-08-12 12:18:40: Thread:5096(INFO) : ACU Configurator , Category: Discovery Source: HostBasedSetup.cpp : HostBasedSetup::Discovery Line: 432: Calling function Discovery...
2015-08-12 12:18:40: Thread:5096(INFO) : ACU Configurator , Category: Local System Account Source: HostBasedSetup.cpp : HostBasedSetup::GetLocalSystemAccount Line: 217: Calling function GetLocalSystemAccount over MEI...
2015-08-12 12:18:40: Thread:5096(DETAIL) : ACU Configurator , Category: -HECI- Source: HECIWin.cpp : HECIWin::Init Line: 191: Connected to the Intel(R) Management Engine Interface driver, version 9.5.14.1724
2015-08-12 12:18:40: Thread:5096(INFO) : ACU Configurator , Category: Local System Account Source: HostBasedSetup.cpp : HostBasedSetup::GetLocalSystemAccount Line: 255: Function GetLocalSystemAccount over MEI ended successfully
2015-08-12 12:18:40: Thread:5096(INFO) : ACU Configurator , Category: Discovery Source: HostBasedSetup.cpp : HostBasedSetup::Discovery Line: 479: Host Based Setup is supported
2015-08-12 12:18:40: Thread:5096(INFO) : ACU Configurator , Category: Discovery Source: HostBasedSetup.cpp : HostBasedSetup::Discovery Line: 518: Current Control Mode: 2 (Admin)
2015-08-12 12:18:40: Thread:5096(INFO) : ACU Configurator , Category: Discovery Source: HostBasedSetup.cpp : HostBasedSetup::Discovery Line: 557: Allowed Control Modes: 2 (Admin) and 1 (Client)
2015-08-12 12:18:40: Thread:5096(INFO) : ACU Configurator , Category: Discovery Source: HostBasedSetup.cpp : HostBasedSetup::Discovery Line: 561: Function Discovery ended successfully
2015-08-12 12:18:40: Thread:5096(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : LMSDiscovery Line: 1346: Exiting
2015-08-12 12:18:40: Thread:5096(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : SecurityDiscovery Line: 1364: Entering
2015-08-12 12:18:40: Thread:5096(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : SecurityDiscovery Line: 1399: Exiting
2015-08-12 12:18:40: Thread:5096(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : FeaturesDiscovery Line: 1417: Entering
2015-08-12 12:18:40: Thread:5096(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : FeaturesDiscovery Line: 1432: Exiting
2015-08-12 12:18:40: Thread:5096(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : UuidDiscovery Line: 1527: Entering
2015-08-12 12:18:40: Thread:5096(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : UuidDiscovery Line: 1545: Exiting
2015-08-12 12:18:40: Thread:5096(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : TcpIpDiscovery Line: 1552: Entering
2015-08-12 12:18:40: Thread:5096(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : TcpIpDiscovery Line: 1671: Exiting
2015-08-12 12:18:40: Thread:5096(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : HeciDiscovery Line: 862: Exiting
2015-08-12 12:18:40: Thread:5096(DETAIL) : ACU Configurator , Category: -HECI- Source: HECIWin.cpp : HECIWin::Init Line: 191: Connected to the Intel(R) Management Engine Interface driver, version 9.5.14.1724
2015-08-12 12:18:40: Thread:5096(DETAIL) : I0PTXLPT999999.dtilab.lab, Category: TestAllConnections params Source: vProConfigurationInternal.cpp : vProConfigurationNamespace::vProConfigurationInternal::TestAllConnections Line: 549: Connection data - Connection type: HTTP, FQDN: I0PTXLPT999999.dtilab.lab, IP: 192.168.0.40, UserName: $$OsAdmin
2015-08-12 12:18:40: Thread:5096(DETAIL) : I0PTXLPT999999.dtilab.lab, Category: Test Connection Source: vProConfigurationInternal.cpp : vProConfigurationNamespace::vProConfigurationInternal::TestConnection Line: 797:
2015-08-12 12:18:40: Thread:5096(DETAIL) : I0PTXLPT999999.dtilab.lab, Category: DiscoverAMTConnectionMode Source: vProConfigurationInternal.cpp : vProConfigurationNamespace::vProConfigurationInternal::TestConnection Line: 1146: Connection Info-I0PTXLPT999999.dtilab.lab $$OsAdmin HTTP_CONN:
2015-08-12 12:18:41: Thread:5096(DETAIL) : I0PTXLPT999999.dtilab.lab, Category: AMTCommunicator Source: WSMANCommunicator.cpp : AMTInterfaceNamespace::WSMANCommunicator::GetAmtVersion Line: 98: WS-Management call GetAmtVersion (CIM_SoftwareIdentity.Get) ok
2015-08-12 12:18:41: Thread:5096(DETAIL) : I0PTXLPT999999.dtilab.lab, Category: AMTCommunicator Source: WSMANCommunicator.cpp : AMTInterfaceNamespace::WSMANCommunicator::GetAmtUuid Line: 7865: WS-Management call GetAmtUuid (AMT_SetupAndConfigurationService.GetUuid) ok
2015-08-12 12:18:41: Thread:5096(DETAIL) : I0PTXLPT999999.dtilab.lab, Category: AMT Interface Source: vProConfigurationInternal.cpp : vProConfigurationNamespace::vProConfigurationInternal::TestConnection Line: 1330: AMT version-9.5.14, AMT SKU-0x2008, AMT Level-2
2015-08-12 12:18:42: Thread:5096(DETAIL) : I0PTXLPT999999.dtilab.lab, Category: AMTCommunicator Source: WSMANCommunicator.cpp : AMTInterfaceNamespace::WSMANCommunicator::GetSupportedFeatures Line: 205: WS-Management call GetSupportedFeatures (CIM_RegisteredProfile.Enumerate) ok
2015-08-12 12:18:42: Thread:5096(DETAIL) : I0PTXLPT999999.dtilab.lab, Category: AMTCommunicator Source: WSMANCommunicator.cpp : AMTInterfaceNamespace::WSMANCommunicator::GetSupportedFeatures Line: 450: WS-Management call GetSupportedFeatures (AMT_CryptographicCapabilities.Get) ok
2015-08-12 12:18:42: Thread:5096(DETAIL) : I0PTXLPT999999.dtilab.lab, Category: AMTCommunicator Source: WSMANCommunicator.cpp : AMTInterfaceNamespace::WSMANCommunicator::GetSupportedFeatures Line: 472: WS-Management call GetSupportedFeatures Wired (CIM_EthernetPort.Get) ok
2015-08-12 12:18:42: Thread:5096(DETAIL) : I0PTXLPT999999.dtilab.lab, Category: AMTCommunicator Source: WSMANCommunicator.cpp : AMTInterfaceNamespace::WSMANCommunicator::GetSupportedFeatures Line: 502: WS-Management call GetSupportedFeatures Wireless (CIM_EthernetPort.Get) ok
2015-08-12 12:18:42: Thread:5096(INFO) : I0PTXLPT999999.dtilab.lab, Category: AMT Interface Source: vProConfigurationInternal.cpp : vProConfigurationNamespace::vProConfigurationInternal::TestConnection Line: 1408: Wire support:************** 1
2015-08-12 12:18:42: Thread:5096(DETAIL) : I0PTXLPT999999.dtilab.lab, Category: Get Kerberos Settings Source: vProConfigurationInternal.cpp : vProConfigurationNamespace::vProConfigurationInternal::GetKerberosSettings Line: 6211:
2015-08-12 12:18:42: Thread:5096(DETAIL) : I0PTXLPT999999.dtilab.lab, Category: AMTCommunicator Source: WSMANCommunicator.cpp : AMTInterfaceNamespace::WSMANCommunicator::GetKerberosSettings Line: 6091: WS-Management call GetKerberosSettings (AMT_KerberosSettingData.Get) ok
2015-08-12 12:18:42: Thread:5096(DETAIL) : I0PTXLPT999999.dtilab.lab, Category: GetKerberosSettings Source: vProConfigurationInternal.cpp : vProConfigurationNamespace::vProConfigurationInternal::GetKerberosSettings Line: 6239: EnableKerberos: True. kerberosRealm: dtilab.lab
2015-08-12 12:18:42: Thread:5096(DETAIL) : I0PTXLPT999999.dtilab.lab, Category: Get Machine Name Source: vProConfigurationInternal.cpp : vProConfigurationNamespace::vProConfigurationInternal::GetMachineName Line: 1994:
2015-08-12 12:18:42: Thread:5096(DETAIL) : I0PTXLPT999999.dtilab.lab, Category: AMTCommunicator Source: WSMANCommunicator.cpp : AMTInterfaceNamespace::WSMANCommunicator::GetMachineName Line: 3109: WS-Management call GetMachineName (AMT_GeneralSettings.Get) ok
2015-08-12 12:18:42: Thread:5096(DETAIL) : I0PTXLPT999999.dtilab.lab, Category: GetMachineName Source: vProConfigurationInternal.cpp : vProConfigurationNamespace::vProConfigurationInternal::GetMachineName Line: 2052: I0PTXLPT999999.dtilab.lab
2015-08-12 12:18:42: Thread:5096(DETAIL) : I0PTXLPT999999.dtilab.lab, Category: Get Privacy Level Source: vProConfigurationInternal.cpp : vProConfigurationNamespace::vProConfigurationInternal::GetKerberosAESSupport Line: 2065:
2015-08-12 12:18:42: Thread:5096(DETAIL) : I0PTXLPT999999.dtilab.lab, Category: Start function Source: vProConfigurationInternal.cpp : vProConfigurationNamespace::vProConfigurationInternal::GetKerberosAESSupport Line: 2068: GetKerberosAESSupport not needed
2015-08-12 12:18:42: Thread:5096(DETAIL) : I0PTXLPT999999.dtilab.lab, Category: Get Wired Network Settings Source: vProConfigurationInternal.cpp : vProConfigurationNamespace::vProConfigurationInternal::GetWiredNetworkSettings Line: 2181:
2015-08-12 12:18:42: Thread:5096(DETAIL) : I0PTXLPT999999.dtilab.lab, Category: AMTCommunicator Source: WSMANCommunicator.cpp : AMTInterfaceNamespace::WSMANCommunicator::GetWiredIPv6Settings Line: 1291: WS-Management call GetWiredNetworkSettings (IPS_IPv6PortSettings.Get) ok
2015-08-12 12:18:44: Thread:5096(DETAIL) : I0PTXLPT999999.dtilab.lab, Category: AMTCommunicator Source: WSMANCommunicator.cpp : AMTInterfaceNamespace::WSMANCommunicator::GetWiredIPv6Settings Line: 1299: WS-Management call GetWiredNetworkSettings (CIM_ElementSettingData.Enumerate) ok
2015-08-12 12:18:44: Thread:5096(DETAIL) : I0PTXLPT999999.dtilab.lab, Category: AMTCommunicator Source: WSMANCommunicator.cpp : AMTInterfaceNamespace::WSMANCommunicator::GetWiredNetworkSettings Line: 1422: WS-Management call GetWiredNetworkSettings (EthernetPortSettingsObj.Get) ok
2015-08-12 12:18:45: Thread:5096(DETAIL) : I0PTXLPT999999.dtilab.lab, Category: GetWiredNetworkSettings Source: vProConfigurationInternal.cpp : vProConfigurationNamespace::vProConfigurationInternal::GetWiredNetworkSettings Line: 2274: -IPv4 Address- 192.168.0.40 IPv4 SubNet- 255.255.255.0 IPv4 Primary DNS- 192.168.0.1
2015-08-12 12:18:45: Thread:5096(DETAIL) : I0PTXLPT999999.dtilab.lab, Category: Enumerate Certs From Store Source: vProConfigurationInternal.cpp : vProConfigurationNamespace::vProConfigurationInternal::EnumerateCertsFromStore Line: 5998:
2015-08-12 12:18:45: Thread:5096(DETAIL) : I0PTXLPT999999.dtilab.lab, Category: AMTCommunicator Source: WSMANCommunicator.cpp : AMTInterfaceNamespace::WSMANCommunicator::EnumerateCertsFromStore Line: 4876: WS-Management call EnumerateCertsFromStore (AMT_PublicKeyCertificate.Enumerate) ok
2015-08-12 12:18:45: Thread:5096(DETAIL) : I0PTXLPT999999.dtilab.lab, Category: AMTCommunicator Source: WSMANCommunicator.cpp : AMTInterfaceNamespace::WSMANCommunicator::EnumerateCertsFromStore Line: 4884: WS-Management call EnumerateCertsFromStore (CIM_ConcreteDependency.Enumerate) ok
2015-08-12 12:18:45: Thread:5096(DETAIL) : I0PTXLPT999999.dtilab.lab, Category: Enumerate Trusted RootCerts Source: vProConfigurationInternal.cpp : vProConfigurationNamespace::vProConfigurationInternal::EnumerateTrustedRootCerts Line: 6039:
2015-08-12 12:18:45: Thread:5096(DETAIL) : I0PTXLPT999999.dtilab.lab, Category: AMTCommunicator Source: WSMANCommunicator.cpp : AMTInterfaceNamespace::WSMANCommunicator::EnumerateTrustedRootCerts Line: 5350: Enumerate Trusted Root Certificates-
2015-08-12 12:18:46: Thread:5096(DETAIL) : I0PTXLPT999999.dtilab.lab, Category: AMTCommunicator Source: WSMANCommunicator.cpp : AMTInterfaceNamespace::WSMANCommunicator::EnumerateTrustedRootCerts Line: 5355: WS-Management call EnumerateTrustedRootCerts (AMT_PublicKeyCertificate.Enumerate) ok
2015-08-12 12:18:46: Thread:5096(DETAIL) : I0PTXLPT999999.dtilab.lab, Category: Enumerate Network Interfaces Source: vProConfigurationInternal.cpp : vProConfigurationNamespace::vProConfigurationInternal::EnumerateNetworkInterfaces Line: 6092:
2015-08-12 12:18:46: Thread:5096(DETAIL) : I0PTXLPT999999.dtilab.lab, Category: AMTCommunicator Source: WSMANCommunicator.cpp : AMTInterfaceNamespace::WSMANCommunicator::EnumerateNetworkInterfaces Line: 3588: WS-Management call EnumerateInterfaces (AMT_EthernetPortSettings.Enumerate) ok
2015-08-12 12:18:46: Thread:5096(ERROR) : I0PTXLPT999999.dtilab.lab, Category: EnumerateNetworkInterfaces bad catch Source: vProConfigurationInternal.cpp : vProConfigurationNamespace::vProConfigurationInternal::EnumerateNetworkInterfaces Line: 6203:
2015-08-12 12:18:46: Thread:5096(DETAIL) : I0PTXLPT999999.dtilab.lab, Category: Get Amt Uuid Source: vProConfigurationInternal.cpp : vProConfigurationNamespace::vProConfigurationInternal::GetAmtUuid Line: 6252:
2015-08-12 12:18:46: Thread:5096(DETAIL) : I0PTXLPT999999.dtilab.lab, Category: AMTCommunicator Source: WSMANCommunicator.cpp : AMTInterfaceNamespace::WSMANCommunicator::GetAmtUuid Line: 7865: WS-Management call GetAmtUuid (AMT_SetupAndConfigurationService.GetUuid) ok
2015-08-12 12:18:46: Thread:5096(DETAIL) : I0PTXLPT999999.dtilab.lab, Category: Get Control Mode Source: vProConfigurationInternal.cpp : vProConfigurationNamespace::vProConfigurationInternal::GetControlMode Line: 6286:
2015-08-12 12:18:46: Thread:5096(DETAIL) : I0PTXLPT999999.dtilab.lab, Category: AMTCommunicator Source: WSMANCommunicator.cpp : AMTInterfaceNamespace::WSMANCommunicator::GetControlMode Line: 642: WS-Management call GetControlMode (IPS_HostBasedSetupService.Get) ok
2015-08-12 12:18:46: Thread:5096(DETAIL) : I0PTXLPT999999.dtilab.lab, Category: Get Digest Realm String Source: vProConfigurationInternal.cpp : vProConfigurationNamespace::vProConfigurationInternal::GetDigestRealmString Line: 6322:
2015-08-12 12:18:46: Thread:5096(DETAIL) : I0PTXLPT999999.dtilab.lab, Category: Get Enabled Interfaces Source: vProConfigurationInternal.cpp : vProConfigurationNamespace::vProConfigurationInternal::GetEnabledInterfaces Line: 6356:
2015-08-12 12:18:46: Thread:5096(DETAIL) : I0PTXLPT999999.dtilab.lab, Category: AMTCommunicator Source: WSMANCommunicator.cpp : AMTInterfaceNamespace::WSMANCommunicator::GetEnabledInterfaces Line: 4010: WS-Management call GetEnabledInterfaces (AMT_WebUIService.Get) ok
2015-08-12 12:18:46: Thread:5096(DETAIL) : I0PTXLPT999999.dtilab.lab, Category: AMTCommunicator Source: WSMANCommunicator.cpp : AMTInterfaceNamespace::WSMANCommunicator::GetEnabledInterfaces Line: 4026: WS-Management call GetEnabledInterfaces (AMT_RedirectionService.Get) ok
2015-08-12 12:18:46: Thread:5096(DETAIL) : I0PTXLPT999999.dtilab.lab, Category: AMTCommunicator Source: WSMANCommunicator.cpp : AMTInterfaceNamespace::WSMANCommunicator::GetEnabledInterfaces Line: 4078: WS-Management call GetEnabledInterfaces (CIM_RedirectionService.Get) ok
2015-08-12 12:18:46: Thread:5096(DETAIL) : I0PTXLPT999999.dtilab.lab, Category: AMTCommunicator Source: WSMANCommunicator.cpp : AMTInterfaceNamespace::WSMANCommunicator::GetKVMSettings Line: 7185: WS-Management call GetKVMSettings (IPS_KVMRedirectionSettingData.Get) ok
2015-08-12 12:18:46: Thread:5096(DETAIL) : I0PTXLPT999999.dtilab.lab, Category: Get PKI Capabilities Source: vProConfigurationInternal.cpp : vProConfigurationNamespace::vProConfigurationInternal::GetPKICapabilities Line: 6431:
2015-08-12 12:18:46: Thread:5096(DETAIL) : I0PTXLPT999999.dtilab.lab, Category: AMTCommunicator Source: WSMANCommunicator.cpp : AMTInterfaceNamespace::WSMANCommunicator::GetPKICapabilities Line: 3784: WS-Management call GetPKICapabilities (AMT_PublicKeyManagementCapabilities.Get) ok
2015-08-12 12:18:46: Thread:5096(DETAIL) : I0PTXLPT999999.dtilab.lab, Category: Get Network Time Source: vProConfigurationInternal.cpp : vProConfigurationNamespace::vProConfigurationInternal::GetNetworkTime Line: 1510:
2015-08-12 12:18:46: Thread:5096(DETAIL) : I0PTXLPT999999.dtilab.lab, Category: AMTCommunicator Source: WSMANCommunicator.cpp : AMTInterfaceNamespace::WSMANCommunicator::GetNetworkTime Line: 913: WS-Management call GetNetworkTime (AMT_TimeSynchronizationService.InvokeGetLowAccuracyTimeSynch) ok
2015-08-12 12:18:46: Thread:5096(DETAIL) : I0PTXLPT999999.dtilab.lab, Category: Get TLS Settings Source: vProConfigurationInternal.cpp : vProConfigurationNamespace::vProConfigurationInternal::GetTLSSettings Line: 6476:
2015-08-12 12:18:47: Thread:5096(DETAIL) : I0PTXLPT999999.dtilab.lab, Category: AMTCommunicator Source: WSMANCommunicator.cpp : AMTInterfaceNamespace::WSMANCommunicator::GetTLSSettings Line: 5676: WS-Management call GetTLSSettings (AMT_TLSSettingData.Enumerate) ok
2015-08-12 12:18:47: Thread:5096(DETAIL) : I0PTXLPT999999.dtilab.lab, Category: AMTCommunicator Source: WSMANCommunicator.cpp : AMTInterfaceNamespace::WSMANCommunicator::GetTLSSettings Line: 5717: WS-Management call GetTLSSettings (AMT_TLSCredentialContext.Get) ok
2015-08-12 12:18:47: Thread:5096(DETAIL) : I0PTXLPT999999.dtilab.lab, Category: Get Kerberos Settings Source: vProConfigurationInternal.cpp : vProConfigurationNamespace::vProConfigurationInternal::GetKerberosSettings Line: 6211:
2015-08-12 12:18:47: Thread:5096(DETAIL) : I0PTXLPT999999.dtilab.lab, Category: GetKerberosSettings Source: vProConfigurationInternal.cpp : vProConfigurationNamespace::vProConfigurationInternal::GetKerberosSettings Line: 6239: EnableKerberos: True. kerberosRealm: dtilab.lab
2015-08-12 12:18:47: Thread:5096(DETAIL) : I0PTXLPT999999.dtilab.lab, Category: Get Local Time Sync Enabled Source: vProConfigurationInternal.cpp : vProConfigurationNamespace::vProConfigurationInternal::GetLocalTimeSyncEnabled Line: 6959:
2015-08-12 12:18:47: Thread:5096(DETAIL) : ACU Configurator , Category: DiscoveryWSMan Source: HostBasedSetup.cpp : HostBasedSetup::DiscoveryWSMan Line: 1401: Calling functions in Discovery with WSMan ...
2015-08-12 12:18:47: Thread:5096(INFO) : ACU Configurator , Category: DiscoveryWSMan Source: HostBasedSetup.cpp : HostBasedSetup::DiscoveryWSMan Line: 1462: Host Based Setup is supported
Hello,
I'm setting up a Supermicro server with an X10SAE board and I have issues getting AMT KVM to work.
I set everything in the AMT ME bootup interface and also configured via KVM Console (KVMControlApplication.exe) to "KVM Status: Enabled - all ports". Here, I was not sure which "Default visibile monitor" to choose, so I tried each of them. Result was always the same:
With any VNC viewer, I can connect to the server. I can authenticate and successfully log in. After that, the attached screen on the server shows a red/yellow flashing border and a connection icon in the right upper corner. When I move the mouse or press a keyboard key in the VNC client, I can see these actions being performed on the server screen.
BUT: The problem is, that the VNC client stays clear. Depending on the VNC client I use, the window stays always black or red. This is independent of the state the server is in, i.e. it's the same if the server is in POST/BIOS/booting up, or the operating system has fully booted. Nevertheless, the client gets notified by the changes of the screen resolution, so the VNC window changes size when the server changes from POST to booting up and then again when reaching the GUI.
Depending on the VNC server I use, the VNC client terminates after a short time (less than a minute) without comments, or tries to reestablish the connection. Interesting enough, Real VNC shows the error message
0x8086210E: Internal KVM failure
which is, according to the "Intel AMT implementation and Reference Guide" an "Internal failure". Not very helpful.
I'm stuck here. Help would be appreciated.
The Intel Active Management Technology webinterface shows:
Platform
Computer model: X10SAE
Manufacturer: Supermicro
Baseboard
Manufacturer: Supermicro
Product name: X10SAE
Version: 1.01
BIOS
Vendor: American Megatrends Inc.
Version: 3.0
Release date: 05/20/2015
Processor 1
Manufacturer: Intel
Family: Intel® Xeon® processor
Socket: SOCKET 0
Version: Intel(R) Xeon(R) CPU E3-1246 v3 @ 3.50GHz
1. ME Bios 10.0.0.0004 / ME 9.0.1.1333
2. Just 1 display is attached
3. I'm using the onboard graphics for the chip and the HDMI display. There is a DVI port on the motherboard, too, but I am not using that.
4. IP is 192.168.1.10. This is on the LAN.
5. Direct connection
Thanks in advance,
Hello all,
I initially had a Toshiba SSD 128 gb on my laptop, and IRST installed perfectly fine. However, I then purchased the Samsung 850 EVO 250 gb SSD.
I tried installing IRST again for my new SSD, and it said "The setup program ended prematurely because of the following error: This platform is not supported".
I found similar problems, such as this thread http://forums.toshiba.com/t5/General-Troubleshooting/Unable-to-install-Intel-Rapid-Storage-Technology-This-platform/td-p/398271.
I notice that IRST is not configured properly because I am currently on a Storahci instead of iastora. Anyone have any solutions to fix this problem?
I believe that my new SSD is not performing at its maximum performance and that I could improve it in every way.