Hello Intel Community,

I am currently experiencing issues with Intel AMT and Meshcommander. I am having issues with installing the CentOS ISO via Intel AMT & Meshcommander. Also, while using MeshCommander I tend to lose connection to my AMT device whenever I reset or reboot my system. This in turn makes it difficult for me to install ISOs by resetting to the IDE-R CD . Could you please help me whenever you guys get the opportunity. Thank you for your time.

Connected to the Intel(R) Management Engine Interface driver, version

8.1.10.1275

Entering

Exiting

Intel(R) AMT  in PROVISIONING_MODE_ENTERPRISE

Entering

Exiting

Exiting

Entering

Exiting

Calling function Discovery...

Calling function GetLocalSystemAccount over MEI...

Connected to the Intel(R) Management Engine Interface driver, version

8.1.10.1275

Function GetLocalSystemAccount over MEI ended successfully

Host Based Setup is not supported (WS-MAN call Failed with gSoap error code: 24)

Function Discovery ended successfully

Entering

Exiting

GetHostAndMEInfo output data:

        IsAMT:True,

        isEnterpriseMode:True,

        configurationMode:2,

        isRemoteConfigEnabled:True,

        AMTversion:8.1.72.3002,

        isMobile:True,

        provisioningTlsMode:2,

        uuid:102FCB6E-7502-11E3-A3B1-D9EEE40120FF,

        isClientConfigEnabled:False,

        hostBasedSupport:False,

        configurationState:2,

        FQDN:w1.ex.local,

        embeddedConfigurationAllowed:False.

        isLANLessPlatform:False.

        PKIDNSSuffix: Empty.

***** Start RemoteConfiguration ******

Entering

Exiting

Entering

Exiting

RCSaddress=amt.ex.local, RCSWMIUser=, RCSProfileName=kerb-tls

***** END RemoteConfiguration ******

***********

Exit with code 75.

Details: Failed to complete remote configuration of this Intel(R) AMT device.

Failed to authenticate with the RCS.

A call to this function has failed -

Access denied

Hello,

We have a problem with the HP ProDesk 600G3.

With the default Bios version  (version 2.06) and AMT Provisioned Everything works fine.

Due to Meltdown and Spectre we are updating our machines. And After the bios updates it seems that we can't use UEFi PXE boot anymore.

We have tried every bios version higher then 00.02.06 Rev. until version 2.16a released on Apr 11, 2018.

The situation stays the same.

We use one AMT Profile for all our desktop computers and only the HP ProDesk 600G3 has this problem.

Other systems: Dell Optiplex 7010 (SFF), Dell Optiplex 9020 (SFF) and Dell Optiplex 7040 (SFF) are working fine.

HP business support can't find the reason.

The only way at this moment to make UEFi PXE boot working again is to unprovisioning the AMT profile.

This keeps working until the AMT profile is automatically pushed to the system agian.

Is this a known error? 

Can someone explain why this is happening and how to solve this problem?

Hello,

We started receiving new model Dell computers with MEBX v12.0 / Intel ME v12.0 firmware.

They are failing to Configure via the Intel RCS v10.0.11.35 Server in Database Mode.

However, Remote Configuration works successfully with all other Dell computers having the firmware MEBX v11.0 / Intel ME 11.8.50  and below.

I used the latest ACU Configurator v12.0.0.129 to attempt remote provisioning via the command line. This is the error I get in the output verbose log:

2018-07-20 15:34:14: Thread:8840(ERROR) : ACU Configurator, Category: Exit Source: Src\ActivatorMain.cpp : configurator::LogAndExit Line: 227: ***********Exit with code 75. Details: Failed to complete remote configuration of this Intel(R) AMT device. Failed while calling  WS-Management call  GetAmtVersion (CIM_SoftwareIdentity.Get). Intel(R) AMT connection error  0xc000521f: An SSL error occurred. Verify the username and password, and the PSK or certificate settings, where applicable. Valid certificate for PKI configuration not found.

All the target Workstation machines system info are:

* Windows 10 Enterprise v1709

* Intel MEI drivers only installed v1803.12.0.1093

Any advice on how to resolve this issue with our new Dell systems? Thanks.

I'm attempting to use the Intel AMT Configuration Utility and I'm receiving the following error:

"This configuration option is not available because the system does not support host-based configuration."

Hello Intel Community,

I am currently experiencing issues with Intel AMT and Meshcommander. I am having issues with installing the CentOS ISO via Intel AMT & Meshcommander. Also, while using MeshCommander I tend to lose connection to my AMT device whenever I reset or reboot my system. This in turn makes it difficult for me to install ISOs by resetting to the IDE-R CD . Could you please help me whenever you guys get the opportunity. Thank you for your time.

If I attempt to download Intel Drtiver & Support Assistant, I get the error message:

"oops, something went wrong while trying to scan. ...See....FAQ"

I have a new Asus ROG G703gs.  The implications are that one failure mode is

an old system. Not the case.

Another failure mode is that the manufacture using Intel products ('ASUS) does not want

the support assistant presumably because they might be using Intel product in a customized manner.

If the latter case is the cause, then that is fine. I understand, even though my current experience is

that ASus has no idea how to write solid software.

Any insight  into this matter?

bil

Hello,

We recently upgraded to SCCM 1702. Since we upgraded to the newer version, Intel AMT hasnt worked. So, what I did was I uninstalled intel SCS SCCM Addon and thought that i can redo and that might fix it. when i install Intel SCS SCCM Addon, I get the following:

This SCCM version is not 2012, its 1702. I can even uncheck that radio button. Not sure what is wrong in there.

If I keep it checked and the click on 'Next', i get the below screen, but I cant find the installer for solutions framework or platform discovery or intel AMT. Not sure if I have seperately download these installer. can anyone guide me through this please? Thank you.

Hi Guys,

I've been relatively ignorant to the fact that vPro exists, and only just started looking into it. I work at an IT help-desk and stumbled upon it, really.

We typically run with Lenovo T-series notebooks here, and they run a variety of setups (hardware). This specific machine runs an i7-7600U.

While I was setting up a brand new T470, I was using Lenovo's update utility and it wanted me to install both the Intel Management Engine firmware and software.

So looking into it, I figure it's something like a server motherboard's IPMI; a web panel that allows you to restart/shutdown, remote control, monitor hardware, etc.

I thought this would be a really useful feature, let me see if I can get it going.

Looking at the ARK Intel page for the specific CPU on this T470, I see a YES next to vPro. This means that the CPU that Intel make, supports this technology, correct?

The internet tells me that I need to use the key combo CTRL + P during startup to launch into the utility/configuration for it. Pressing that combo at (or before) the Lenovo splash screen shows a message something along the lines of: "Launching Intel ME utility". But then goes to windows.

I look at bit closer at Lenovo's website and I see this travesty:

Based off of this, looks like you only get vPro if you buy the mid tier i5.

So my question is: Does Lenovo control whether you use vPro based off of your motherboard? Given that all 3 of these Intel chips support it.

Hi there

We got the new HP Elitedesk 800 G4 DM 65W for testing purposes, the Machine has ME 12.0.2.1087 and our SCS has Version 12.0.0.129. We try to Provisiion the Machines in 2 Steps:

1. OneTouch-Provision with USB-Stick (set Adminpassword, our Certificate-Authorities Hash, DNS-Suffix and Configurationserver Adress).

2. We use the SCCM Tasksequences from the Addon to move the Machines to ACM and Remoteconfiguration

We updated the Tools for the Remoteconfiguration to version 12 as well.

We successfully can provision all the old Workstations like Elitedesk 800 G1 SFF, Elitedesk 800 G2 SFF and Elitedesk 800 G3 DM 35W.

Something very curious was that we had to shorten the password for the OneTouch-Provisioning from 29 Characters to 19 Characters that it would work with the HP 800 G4.

At first we thought it could have something to do with TLS but we disabled and uninstalled even the support for that on our SCS - As told all the old machines work, only the New HP doesn't.

Any advice would be deeply appreciated.

Below the Log of the Remote Configuration attempt:

2018-07-24 07:45:28: Thread:11272(INFO) : ACU Configurator , Category: HandleOutPut Source: CmdUtils.cpp : Cmd::HandleOutput Line: 79: Starting log 2018-07-24 07:45:28

2018-07-24 07:45:28: Thread:11272(DETAIL) : ACU.dll, Category: SetCompatibilityMode Source: ACUDll.cpp : SetCompatibilityMode Line: 196: 12.0.0.129

2018-07-24 07:45:28: Thread:11272(DETAIL) : ACU.dll, Category: SetCompatibilityMode Source: ACUDll.cpp : SetCompatibilityMode Line: 228: Set compatibility mode to 10.0.

2018-07-24 07:45:28: Thread:11272(INFO) : ACU Configurator, Category:  Source: Src\ActivatorMain.cpp : wmain Line: 372: ACUConfig 12.0.0.129

2018-07-24 07:45:28: Thread:11272(INFO) : ACU Configurator, Category: -Unknown Operation- Source: Src\ActivatorMain.cpp : wmain Line: 414: WS-FD99-005.kt.ur.ch: Starting to configure AMT via RCS...

2018-07-24 07:45:28: Thread:11272(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : CheckAMT Line: 85: Entering

2018-07-24 07:45:28: Thread:11272(DETAIL) : ACU Configurator , Category: -HECI- Source: HECIWin.cpp : HECIWin::Init Line: 191: Connected to the Intel(R) Management Engine Interface driver, version 12.0.0.2021

2018-07-24 07:45:28: Thread:11272(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : FWUpdateData Line: 46: Entering

2018-07-24 07:45:28: Thread:11272(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : FWUpdateData Line: 64: Exiting

2018-07-24 07:45:28: Thread:11272(INFO) : ACU Configurator , Category: AMT Mode Source: HECIDiscovery.cpp : CheckAMT Line: 426: Intel(R) AMT  in PROVISIONING_MODE_ENTERPRISE

2018-07-24 07:45:28: Thread:11272(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : GetPKIDNSSuffix Line: 960: Entering

2018-07-24 07:45:28: Thread:11272(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : GetPKIDNSSuffix Line: 989: Exiting

2018-07-24 07:45:28: Thread:11272(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : CheckAMT Line: 548: Exiting

2018-07-24 07:45:30: Thread:11272(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : GetAmtFQDN Line: 1448: Entering

2018-07-24 07:45:30: Thread:11272(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : GetAmtFQDN Line: 1529: Exiting

2018-07-24 07:45:31: Thread:11272(INFO) : ACU Configurator , Category: Discovery Source: HostBasedSetup.cpp : HostBasedSetup::Discovery Line: 432: Calling function Discovery...

2018-07-24 07:45:31: Thread:11272(INFO) : ACU Configurator , Category: Local System Account Source: HostBasedSetup.cpp : HostBasedSetup::GetLocalSystemAccount Line: 217: Calling function GetLocalSystemAccount over MEI...

2018-07-24 07:45:31: Thread:11272(DETAIL) : ACU Configurator , Category: -HECI- Source: HECIWin.cpp : HECIWin::Init Line: 191: Connected to the Intel(R) Management Engine Interface driver, version 12.0.0.2021

2018-07-24 07:45:31: Thread:11272(INFO) : ACU Configurator , Category: Local System Account Source: HostBasedSetup.cpp : HostBasedSetup::GetLocalSystemAccount Line: 255: Function GetLocalSystemAccount over MEI ended successfully

2018-07-24 07:45:31: Thread:11272(INFO) : ACU Configurator , Category: Discovery Source: HostBasedSetup.cpp : HostBasedSetup::Discovery Line: 479: Host Based Setup is supported

2018-07-24 07:45:31: Thread:11272(INFO) : ACU Configurator , Category: Discovery Source: HostBasedSetup.cpp : HostBasedSetup::Discovery Line: 518: Current Control Mode: 2 (Admin)

2018-07-24 07:45:31: Thread:11272(INFO) : ACU Configurator , Category: Discovery Source: HostBasedSetup.cpp : HostBasedSetup::Discovery Line: 557: Allowed Control Modes: 2 (Admin) and  1 (Client)

2018-07-24 07:45:31: Thread:11272(INFO) : ACU Configurator , Category: Discovery Source: HostBasedSetup.cpp : HostBasedSetup::Discovery Line: 561: Function Discovery ended successfully

2018-07-24 07:45:33: Thread:11272(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : UuidDiscovery Line: 1536: Entering

2018-07-24 07:45:33: Thread:11272(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : UuidDiscovery Line: 1554: Exiting

2018-07-24 07:45:33: Thread:11272(DETAIL) : ACU Configurator , Category: Returned data Source: ACUDll.cpp : GetHostAndMEInfo Line: 4479: GetHostAndMEInfo output data:  IsAMT:True,  isEnterpriseMode:True,  configurationMode:2,  isRemoteConfigEnabled:True,  AMTversion:12.0.2.1087,  isMobile:False,  provisioningTlsMode:2,  uuid:B54BA79A-72EE-D24B-3C30-33CB3687ABDA,  isClientConfigEnabled:True,  hostBasedSupport:True,  configurationState:2,  FQDN:WS-FD99-005.kt.ur.ch,  embeddedConfigurationAllowed:False.  isLANLessPlatform:False.  PKIDNSSuffix:kt.ur.ch

2018-07-24 07:45:33: Thread:11272(DETAIL) : ACU Configurator , Category: -Start- Source: ACUDll.cpp : RemoteConfiguration Line: 3581: ***** Start RemoteConfiguration ******

2018-07-24 07:45:35: Thread:11272(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : TcpIpDiscovery Line: 1561: Entering

2018-07-24 07:45:35: Thread:11272(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : TcpIpDiscovery Line: 1680: Exiting

2018-07-24 07:45:37: Thread:11272(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : GetAmtFQDN Line: 1448: Entering

2018-07-24 07:45:37: Thread:11272(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : GetAmtFQDN Line: 1529: Exiting

2018-07-24 07:45:37: Thread:11272(DETAIL) : ACU.dll, Category: GetNetworkSettings Source: ACUDllWin.cpp : LoadNetworkSettings Line: 996: RCSaddress=srv-sccm01.kt.ur.ch, RCSWMIUser=, RCSProfileName=KVUFullWS

2018-07-24 07:45:37: Thread:11272(DETAIL) : NetworkSettingClass, Category: LoadSourceForAMTName Source: NetworkSettingsClass.cpp : NetworkSettings::NetworkSettingClass::LoadSourceForAMTName Line: 576: WS-FD99-005.kt.ur.ch

2018-07-24 07:45:37: Thread:11272(DETAIL) : ACU.dll, Category: Configure AMT Source: ACUDllWin.cpp : MI_ConfigAMT Line: 655: RCSaddress=srv-sccm01.kt.ur.ch, RCSWMIUser=, UUID=B54BA79A-72EE-D24B-3C30-33CB3687ABDA, ConfigMode=3, PID=, RCSProfileName=KVUFullWS, AMTVersion=12.0.2.1087, OldADOU=, Configure AMT Name= True. Configure AMT IPv4= True. AMT Name= Host Name- WS-FD99-005 Domain Name- kt.ur.ch . Source For AMT Name= Host Name- WS-FD99-005 Domain Name- kt.ur.ch . Default OS Name= Host Name- WS-FD99-005 Domain Name- kt.ur.ch . Host IPv4= IPv4 Address- 10.41.99.15 IPv4 SubNet- 255.255.255.0 IPv4 Gateway- 10.41.99.254 IPv4 Primary DNS- 10.40.254.100 IPv4 Secondary DNS- 10.40.254.101 . Configure AMT IPv4 to DHCP mode= True. AMT IPv4= IPv4 Address- 10.41.99.15 .

2018-07-24 07:45:37: Thread:11272(INFO) : ACU Configurator , Category: WMI Access Layer Source: WMIAccess.cpp : WMI_IsRcsBusy Line: 683: Success. (0) (retry set to = 3)

2018-07-24 07:45:37: Thread:11272(INFO) : ACU Configurator , Category: WMI Access Layer Source: WMIAccess.cpp : WMI_IsRcsBusy Line: 759: Success. (0) (RCS not busy.)

2018-07-24 07:45:37: Thread:11272(INFO) : ACU Configurator , Category: WMI Access Layer Source: WMIAccess.cpp : WMI_IsRcsBusy Line: 783: Success. (0) (RCS is currently handling = 0 threads)

2018-07-24 07:45:52: Thread:11272(DETAIL) : ACU Configurator , Category: -END- Source: ACUDll.cpp : RemoteConfiguration Line: 3879: ***** END RemoteConfiguration ******

2018-07-24 07:45:52: Thread:11272(ERROR) : ACU Configurator, Category: Exit Source: Src\ActivatorMain.cpp : configurator::LogAndExit Line: 227: ***********Exit with code 75. Details: Failed to complete remote configuration of this Intel(R) AMT device. Final status of Intel(R) AMT is unknown because a failure occurred when configuring the system.  Intel(R) AMT operation failed.  Error while configuring Kerberos settings. Failed while calling  WS-Management call  SetKerberosSettings (AMT_KerberosSettingData.Get). Intel(R) AMT error  0x1: AMT Status code - An internal error has occurred in the Intel(R) AMT device. This might indicate an interface error, or an application error.

2018-07-24 07:45:52: Thread:9868(INFO) : ACU Configurator , Category: HandleOutPut Source: CmdUtils.cpp : Cmd::HandleOutput Line: 79: Starting log 2018-07-24 07:45:52

2018-07-24 07:45:52: Thread:9868(DETAIL) : ACU.dll, Category: SetCompatibilityMode Source: ACUDll.cpp : SetCompatibilityMode Line: 196: 12.0.0.129

2018-07-24 07:45:52: Thread:9868(DETAIL) : ACU.dll, Category: SetCompatibilityMode Source: ACUDll.cpp : SetCompatibilityMode Line: 228: Set compatibility mode to 10.0.

2018-07-24 07:45:52: Thread:9868(INFO) : ACU Configurator, Category:  Source: Src\ActivatorMain.cpp : wmain Line: 372: ACUConfig 12.0.0.129

2018-07-24 07:45:52: Thread:9868(INFO) : ACU Configurator, Category: -System Discovery- Source: Src\ActivatorMain.cpp : wmain Line: 414: WS-FD99-005.kt.ur.ch: Starting to discover the system information...

2018-07-24 07:45:52: Thread:9868(DETAIL) : ACU Configurator , Category: -Start- Source: ACUDllWin.cpp : SystemDiscovery Line: 57: ***** Start SystemDiscovery ******

2018-07-24 07:45:52: Thread:9868(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : HeciDiscovery Line: 555: Entering

2018-07-24 07:45:52: Thread:9868(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : CheckAMT Line: 85: Entering

2018-07-24 07:45:52: Thread:9868(DETAIL) : ACU Configurator , Category: -HECI- Source: HECIWin.cpp : HECIWin::Init Line: 191: Connected to the Intel(R) Management Engine Interface driver, version 12.0.0.2021

2018-07-24 07:45:52: Thread:9868(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : FWUpdateData Line: 46: Entering

2018-07-24 07:45:52: Thread:9868(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : FWUpdateData Line: 64: Exiting

2018-07-24 07:45:52: Thread:9868(INFO) : ACU Configurator , Category: AMT Mode Source: HECIDiscovery.cpp : CheckAMT Line: 426: Intel(R) AMT  in PROVISIONING_MODE_ENTERPRISE

2018-07-24 07:45:52: Thread:9868(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : GetPKIDNSSuffix Line: 960: Entering

2018-07-24 07:45:52: Thread:9868(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : GetPKIDNSSuffix Line: 989: Exiting

2018-07-24 07:45:52: Thread:9868(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : CheckAMT Line: 548: Exiting

2018-07-24 07:45:52: Thread:9868(DETAIL) : ACU Configurator , Category: -HECI- Source: HECIWin.cpp : HECIWin::Init Line: 191: Connected to the Intel(R) Management Engine Interface driver, version 12.0.0.2021

2018-07-24 07:45:52: Thread:9868(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : FWUpdateData Line: 46: Entering

2018-07-24 07:45:52: Thread:9868(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : FWUpdateData Line: 64: Exiting

2018-07-24 07:45:57: Thread:9868(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : PKIDiscovery Line: 894: Entering

2018-07-24 07:45:57: Thread:9868(DETAIL) : ACU Configurator , Category: Hash Handle Source: HECIDiscovery.cpp : GetPKIHashes Line: 1052: Hash Handles number:20

2018-07-24 07:45:57: Thread:9868(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : PKIDiscovery Line: 942: Exiting

2018-07-24 07:45:57: Thread:9868(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : GetAmtFQDN Line: 1448: Entering

2018-07-24 07:45:57: Thread:9868(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : GetAmtFQDN Line: 1529: Exiting

2018-07-24 07:45:57: Thread:9868(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : ConfServerDiscovery Line: 1196: Entering

2018-07-24 07:45:57: Thread:9868(DETAIL) : ACU Configurator , Category: Status message Source: HECIDiscovery.cpp : ConfServerDiscovery Line: 1250: AMT Status code - Essential data is missing from the AMT. (0xc0004a71)

2018-07-24 07:45:57: Thread:9868(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : ConfServerDiscovery Line: 1274: Exiting

2018-07-24 07:45:57: Thread:9868(DETAIL) : ACU Configurator , Category: ConfServerDiscovery Source: HECIDiscovery.cpp : HeciDiscovery Line: 809: AMT Status code - An internal error has occurred in the Intel(R) AMT device. This might indicate an interface error, or an application error. (0xc0004269) (ConfServerDiscovery)

2018-07-24 07:45:57: Thread:9868(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : ReInitPTHI Line: 1687: Entering

2018-07-24 07:46:02: Thread:9868(DETAIL) : ACU Configurator , Category: -HECI- Source: HECIWin.cpp : HECIWin::Init Line: 191: Connected to the Intel(R) Management Engine Interface driver, version 12.0.0.2021

2018-07-24 07:46:02: Thread:9868(DETAIL) : ACU Configurator , Category: GetPID Source: HECIDiscovery.cpp : HeciDiscovery Line: 816: AMT Status code - An internal error has occurred in the Intel(R) AMT device. This might indicate an interface error, or an application error. (0xc0004269) (GetPID)

2018-07-24 07:46:02: Thread:9868(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : ReInitPTHI Line: 1687: Entering

2018-07-24 07:46:07: Thread:9868(DETAIL) : ACU Configurator , Category: -HECI- Source: HECIWin.cpp : HECIWin::Init Line: 191: Connected to the Intel(R) Management Engine Interface driver, version 12.0.0.2021

2018-07-24 07:46:07: Thread:9868(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : LMSDiscovery Line: 1282: Entering

2018-07-24 07:46:08: Thread:9868(INFO) : ACU Configurator , Category: Discovery Source: HostBasedSetup.cpp : HostBasedSetup::Discovery Line: 432: Calling function Discovery...

2018-07-24 07:46:08: Thread:9868(INFO) : ACU Configurator , Category: Local System Account Source: HostBasedSetup.cpp : HostBasedSetup::GetLocalSystemAccount Line: 217: Calling function GetLocalSystemAccount over MEI...

2018-07-24 07:46:08: Thread:9868(DETAIL) : ACU Configurator , Category: -HECI- Source: HECIWin.cpp : HECIWin::Init Line: 191: Connected to the Intel(R) Management Engine Interface driver, version 12.0.0.2021

2018-07-24 07:46:08: Thread:9868(INFO) : ACU Configurator , Category: Local System Account Source: HostBasedSetup.cpp : HostBasedSetup::GetLocalSystemAccount Line: 255: Function GetLocalSystemAccount over MEI ended successfully

2018-07-24 07:46:08: Thread:9868(INFO) : ACU Configurator , Category: Discovery Source: HostBasedSetup.cpp : HostBasedSetup::Discovery Line: 479: Host Based Setup is supported

2018-07-24 07:46:08: Thread:9868(INFO) : ACU Configurator , Category: Discovery Source: HostBasedSetup.cpp : HostBasedSetup::Discovery Line: 518: Current Control Mode: 2 (Admin)

2018-07-24 07:46:08: Thread:9868(INFO) : ACU Configurator , Category: Discovery Source: HostBasedSetup.cpp : HostBasedSetup::Discovery Line: 557: Allowed Control Modes: 2 (Admin) and  1 (Client)

2018-07-24 07:46:08: Thread:9868(INFO) : ACU Configurator , Category: Discovery Source: HostBasedSetup.cpp : HostBasedSetup::Discovery Line: 561: Function Discovery ended successfully

2018-07-24 07:46:08: Thread:9868(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : LMSDiscovery Line: 1355: Exiting

2018-07-24 07:46:08: Thread:9868(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : SecurityDiscovery Line: 1373: Entering

2018-07-24 07:46:08: Thread:9868(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : SecurityDiscovery Line: 1408: Exiting

2018-07-24 07:46:08: Thread:9868(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : FeaturesDiscovery Line: 1426: Entering

2018-07-24 07:46:08: Thread:9868(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : FeaturesDiscovery Line: 1441: Exiting

2018-07-24 07:46:08: Thread:9868(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : UuidDiscovery Line: 1536: Entering

2018-07-24 07:46:08: Thread:9868(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : UuidDiscovery Line: 1554: Exiting

2018-07-24 07:46:08: Thread:9868(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : TcpIpDiscovery Line: 1561: Entering

2018-07-24 07:46:08: Thread:9868(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : TcpIpDiscovery Line: 1680: Exiting

2018-07-24 07:46:08: Thread:9868(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : HeciDiscovery Line: 874: Exiting

2018-07-24 07:46:08: Thread:9868(DETAIL) : ACU Configurator , Category: -HECI- Source: HECIWin.cpp : HECIWin::Init Line: 191: Connected to the Intel(R) Management Engine Interface driver, version 12.0.0.2021

2018-07-24 07:46:08: Thread:9868(DETAIL) : WS-FD99-005.kt.ur.ch, Category: TestAllConnections params Source: vProConfigurationInternal.cpp : vProConfigurationNamespace::vProConfigurationInternal::TestAllConnections Line: 548: Connection data - Connection type: HTTP, FQDN: WS-FD99-005.kt.ur.ch, IP: 10.41.99.15, UserName: $$OsAdmin

2018-07-24 07:46:08: Thread:9868(DETAIL) : WS-FD99-005.kt.ur.ch, Category: Test Connection Source: vProConfigurationInternal.cpp : vProConfigurationNamespace::vProConfigurationInternal::TestConnection Line: 796:

2018-07-24 07:46:08: Thread:9868(DETAIL) : WS-FD99-005.kt.ur.ch, Category: DiscoverAMTConnectionMode Source: vProConfigurationInternal.cpp : vProConfigurationNamespace::vProConfigurationInternal::TestConnection Line: 1145: Connection Info-WS-FD99-005.kt.ur.ch $$OsAdmin HTTP_CONN:

2018-07-24 07:46:08: Thread:9868(DETAIL) : WS-FD99-005.kt.ur.ch, Category: AMTCommunicator Source: WSMANCommunicator.cpp : AMTInterfaceNamespace::WSMANCommunicator::GetAmtVersion Line: 98: WS-Management call  GetAmtVersion (CIM_SoftwareIdentity.Get) ok

2018-07-24 07:46:08: Thread:9868(DETAIL) : WS-FD99-005.kt.ur.ch, Category: AMTCommunicator Source: WSMANCommunicator.cpp : AMTInterfaceNamespace::WSMANCommunicator::GetAmtUuid Line: 7866: WS-Management call  GetAmtUuid (AMT_SetupAndConfigurationService.GetUuid) ok

2018-07-24 07:46:08: Thread:9868(DETAIL) : WS-FD99-005.kt.ur.ch, Category: AMT Interface Source: vProConfigurationInternal.cpp : vProConfigurationNamespace::vProConfigurationInternal::TestConnection Line: 1329: AMT version-12.0.2, AMT SKU-0x4008, AMT Level-2

2018-07-24 07:46:09: Thread:9868(DETAIL) : WS-FD99-005.kt.ur.ch, Category: AMTCommunicator Source: WSMANCommunicator.cpp : AMTInterfaceNamespace::WSMANCommunicator::GetSupportedFeatures Line: 205: WS-Management call  GetSupportedFeatures (CIM_RegisteredProfile.Enumerate) ok

2018-07-24 07:46:09: Thread:9868(DETAIL) : WS-FD99-005.kt.ur.ch, Category: AMTCommunicator Source: WSMANCommunicator.cpp : AMTInterfaceNamespace::WSMANCommunicator::GetSupportedFeatures Line: 450: WS-Management call  GetSupportedFeatures (AMT_CryptographicCapabilities.Get) ok

2018-07-24 07:46:09: Thread:9868(DETAIL) : WS-FD99-005.kt.ur.ch, Category: AMTCommunicator Source: WSMANCommunicator.cpp : AMTInterfaceNamespace::WSMANCommunicator::GetSupportedFeatures Line: 472: WS-Management call  GetSupportedFeatures Wired (CIM_EthernetPort.Get) ok

2018-07-24 07:46:09: Thread:9868(DETAIL) : WS-FD99-005.kt.ur.ch, Category: AMTCommunicator Source: WSMANCommunicator.cpp : AMTInterfaceNamespace::WSMANCommunicator::GetSupportedFeatures Line: 525: WS-Management call  GetSupportedFeatures Wireless (CIM_EthernetPort.Get) ok

2018-07-24 07:46:09: Thread:9868(INFO) : WS-FD99-005.kt.ur.ch, Category: AMT Interface  Source: vProConfigurationInternal.cpp : vProConfigurationNamespace::vProConfigurationInternal::TestConnection Line: 1407: Wire support:************** 1

2018-07-24 07:46:09: Thread:9868(DETAIL) : WS-FD99-005.kt.ur.ch, Category: Get Kerberos Settings Source: vProConfigurationInternal.cpp : vProConfigurationNamespace::vProConfigurationInternal::GetKerberosSettings Line: 6210:

2018-07-24 07:46:09: Thread:9868(DETAIL) : WS-FD99-005.kt.ur.ch, Category: AMTCommunicator Source: WSMANCommunicator.cpp : AMTInterfaceNamespace::WSMANCommunicator::GetKerberosSettings Line: 6131: Failed while calling  WS-Management call  GetKerberosSettings (AMT_KerberosSettingData.Get). Intel(R) AMT error  0x1: AMT Status code - An internal error has occurred in the Intel(R) AMT device. This might indicate an interface error, or an application error.

2018-07-24 07:46:09: Thread:9868(DETAIL) : , Category: Retry connection Source: vProConfigurationInternal.cpp : vProConfigurationNamespace::vProConfigurationInternal::GetKerberosSettings Line: 6220: error status: 0xc0004269

2018-07-24 07:46:09: Thread:9868(ERROR) : WS-FD99-005.kt.ur.ch, Category: AMT Interface error Source: vProConfigurationInternal.cpp : vProConfigurationNamespace::vProConfigurationInternal::GetKerberosSettings Line: 6231: Error in GetKerberosSettings- Failed while calling  WS-Management call  GetKerberosSettings (AMT_KerberosSettingData.Get). Intel(R) AMT error  0x1: AMT Status code - An internal error has occurred in the Intel(R) AMT device. This might indicate an interface error, or an application error.

2018-07-24 07:46:09: Thread:9868(DETAIL) : WS-FD99-005.kt.ur.ch, Category: Get Machine Name Source: vProConfigurationInternal.cpp : vProConfigurationNamespace::vProConfigurationInternal::GetMachineName Line: 1993:

2018-07-24 07:46:09: Thread:9868(DETAIL) : WS-FD99-005.kt.ur.ch, Category: AMTCommunicator Source: WSMANCommunicator.cpp : AMTInterfaceNamespace::WSMANCommunicator::GetMachineName Line: 3109: WS-Management call  GetMachineName (AMT_GeneralSettings.Get) ok

2018-07-24 07:46:09: Thread:9868(DETAIL) : WS-FD99-005.kt.ur.ch, Category: GetMachineName Source: vProConfigurationInternal.cpp : vProConfigurationNamespace::vProConfigurationInternal::GetMachineName Line: 2051: WS-FD99-005.kt.ur.ch

2018-07-24 07:46:09: Thread:9868(DETAIL) : WS-FD99-005.kt.ur.ch, Category: Get Privacy Level Source: vProConfigurationInternal.cpp : vProConfigurationNamespace::vProConfigurationInternal::GetKerberosAESSupport Line: 2064:

2018-07-24 07:46:09: Thread:9868(DETAIL) : WS-FD99-005.kt.ur.ch, Category: Start function Source: vProConfigurationInternal.cpp : vProConfigurationNamespace::vProConfigurationInternal::GetKerberosAESSupport Line: 2067: GetKerberosAESSupport not needed

2018-07-24 07:46:09: Thread:9868(DETAIL) : WS-FD99-005.kt.ur.ch, Category: Get Wired Network Settings Source: vProConfigurationInternal.cpp : vProConfigurationNamespace::vProConfigurationInternal::GetWiredNetworkSettings Line: 2180:

2018-07-24 07:46:09: Thread:9868(DETAIL) : WS-FD99-005.kt.ur.ch, Category: AMTCommunicator Source: WSMANCommunicator.cpp : AMTInterfaceNamespace::WSMANCommunicator::GetWiredIPv6Settings Line: 1291: WS-Management call  GetWiredNetworkSettings (IPS_IPv6PortSettings.Get) ok

2018-07-24 07:46:10: Thread:9868(DETAIL) : WS-FD99-005.kt.ur.ch, Category: AMTCommunicator Source: WSMANCommunicator.cpp : AMTInterfaceNamespace::WSMANCommunicator::GetWiredIPv6Settings Line: 1299: WS-Management call  GetWiredNetworkSettings (CIM_ElementSettingData.Enumerate) ok

2018-07-24 07:46:10: Thread:9868(DETAIL) : WS-FD99-005.kt.ur.ch, Category: AMTCommunicator Source: WSMANCommunicator.cpp : AMTInterfaceNamespace::WSMANCommunicator::GetWiredNetworkSettings Line: 1422: WS-Management call  GetWiredNetworkSettings (EthernetPortSettingsObj.Get) ok

2018-07-24 07:46:10: Thread:9868(DETAIL) : WS-FD99-005.kt.ur.ch, Category: GetWiredNetworkSettings Source: vProConfigurationInternal.cpp : vProConfigurationNamespace::vProConfigurationInternal::GetWiredNetworkSettings Line: 2273: -IPv4 Address- 10.41.99.15

2018-07-24 07:46:10: Thread:9868(DETAIL) : WS-FD99-005.kt.ur.ch, Category: Enumerate Certs From Store Source: vProConfigurationInternal.cpp : vProConfigurationNamespace::vProConfigurationInternal::EnumerateCertsFromStore Line: 5997:

2018-07-24 07:46:10: Thread:9868(DETAIL) : WS-FD99-005.kt.ur.ch, Category: AMTCommunicator Source: WSMANCommunicator.cpp : AMTInterfaceNamespace::WSMANCommunicator::EnumerateCertsFromStore Line: 4877: WS-Management call  EnumerateCertsFromStore (AMT_PublicKeyCertificate.Enumerate) ok

2018-07-24 07:46:10: Thread:9868(DETAIL) : WS-FD99-005.kt.ur.ch, Category: Enumerate Trusted RootCerts Source: vProConfigurationInternal.cpp : vProConfigurationNamespace::vProConfigurationInternal::EnumerateTrustedRootCerts Line: 6038:

2018-07-24 07:46:10: Thread:9868(DETAIL) : WS-FD99-005.kt.ur.ch, Category: AMTCommunicator Source: WSMANCommunicator.cpp : AMTInterfaceNamespace::WSMANCommunicator::EnumerateTrustedRootCerts Line: 5351: Enumerate Trusted Root Certificates-

2018-07-24 07:46:10: Thread:9868(DETAIL) : WS-FD99-005.kt.ur.ch, Category: AMTCommunicator Source: WSMANCommunicator.cpp : AMTInterfaceNamespace::WSMANCommunicator::EnumerateTrustedRootCerts Line: 5356: WS-Management call  EnumerateTrustedRootCerts (AMT_PublicKeyCertificate.Enumerate) ok

2018-07-24 07:46:10: Thread:9868(DETAIL) : WS-FD99-005.kt.ur.ch, Category: Enumerate Network Interfaces Source: vProConfigurationInternal.cpp : vProConfigurationNamespace::vProConfigurationInternal::EnumerateNetworkInterfaces Line: 6091:

2018-07-24 07:46:10: Thread:9868(DETAIL) : WS-FD99-005.kt.ur.ch, Category: AMTCommunicator Source: WSMANCommunicator.cpp : AMTInterfaceNamespace::WSMANCommunicator::EnumerateNetworkInterfaces Line: 3589: WS-Management call  EnumerateInterfaces (AMT_EthernetPortSettings.Enumerate) ok

2018-07-24 07:46:10: Thread:9868(DETAIL) : WS-FD99-005.kt.ur.ch, Category: Get Amt Uuid Source: vProConfigurationInternal.cpp : vProConfigurationNamespace::vProConfigurationInternal::GetAmtUuid Line: 6251:

2018-07-24 07:46:10: Thread:9868(DETAIL) : WS-FD99-005.kt.ur.ch, Category: AMTCommunicator Source: WSMANCommunicator.cpp : AMTInterfaceNamespace::WSMANCommunicator::GetAmtUuid Line: 7866: WS-Management call  GetAmtUuid (AMT_SetupAndConfigurationService.GetUuid) ok

2018-07-24 07:46:10: Thread:9868(DETAIL) : WS-FD99-005.kt.ur.ch, Category: Get Control Mode Source: vProConfigurationInternal.cpp : vProConfigurationNamespace::vProConfigurationInternal::GetControlMode Line: 6285:

2018-07-24 07:46:10: Thread:9868(DETAIL) : WS-FD99-005.kt.ur.ch, Category: AMTCommunicator Source: WSMANCommunicator.cpp : AMTInterfaceNamespace::WSMANCommunicator::GetControlMode Line: 642: WS-Management call  GetControlMode (IPS_HostBasedSetupService.Get) ok

2018-07-24 07:46:10: Thread:9868(DETAIL) : WS-FD99-005.kt.ur.ch, Category: Get Digest Realm String Source: vProConfigurationInternal.cpp : vProConfigurationNamespace::vProConfigurationInternal::GetDigestRealmString Line: 6321:

2018-07-24 07:46:10: Thread:9868(DETAIL) : WS-FD99-005.kt.ur.ch, Category: Get Enabled Interfaces Source: vProConfigurationInternal.cpp : vProConfigurationNamespace::vProConfigurationInternal::GetEnabledInterfaces Line: 6355:

2018-07-24 07:46:10: Thread:9868(DETAIL) : WS-FD99-005.kt.ur.ch, Category: AMTCommunicator Source: WSMANCommunicator.cpp : AMTInterfaceNamespace::WSMANCommunicator::GetEnabledInterfaces Line: 4011: WS-Management call  GetEnabledInterfaces (AMT_WebUIService.Get) ok

2018-07-24 07:46:10: Thread:9868(DETAIL) : WS-FD99-005.kt.ur.ch, Category: AMTCommunicator Source: WSMANCommunicator.cpp : AMTInterfaceNamespace::WSMANCommunicator::GetEnabledInterfaces Line: 4027: WS-Management call  GetEnabledInterfaces (AMT_RedirectionService.Get) ok

2018-07-24 07:46:10: Thread:9868(DETAIL) : WS-FD99-005.kt.ur.ch, Category: AMTCommunicator Source: WSMANCommunicator.cpp : AMTInterfaceNamespace::WSMANCommunicator::GetEnabledInterfaces Line: 4079: WS-Management call  GetEnabledInterfaces (CIM_RedirectionService.Get) ok

2018-07-24 07:46:10: Thread:9868(DETAIL) : WS-FD99-005.kt.ur.ch, Category: AMTCommunicator Source: WSMANCommunicator.cpp : AMTInterfaceNamespace::WSMANCommunicator::GetKVMSettings Line: 7186: WS-Management call  GetKVMSettings (IPS_KVMRedirectionSettingData.Get) ok

2018-07-24 07:46:10: Thread:9868(DETAIL) : WS-FD99-005.kt.ur.ch, Category: Get PKI Capabilities Source: vProConfigurationInternal.cpp : vProConfigurationNamespace::vProConfigurationInternal::GetPKICapabilities Line: 6430:

2018-07-24 07:46:10: Thread:9868(DETAIL) : WS-FD99-005.kt.ur.ch, Category: AMTCommunicator Source: WSMANCommunicator.cpp : AMTInterfaceNamespace::WSMANCommunicator::GetPKICapabilities Line: 3785: WS-Management call  GetPKICapabilities (AMT_PublicKeyManagementCapabilities.Get) ok

2018-07-24 07:46:10: Thread:9868(DETAIL) : WS-FD99-005.kt.ur.ch, Category: Get Network Time Source: vProConfigurationInternal.cpp : vProConfigurationNamespace::vProConfigurationInternal::GetNetworkTime Line: 1509:

2018-07-24 07:46:10: Thread:9868(DETAIL) : WS-FD99-005.kt.ur.ch, Category: AMTCommunicator Source: WSMANCommunicator.cpp : AMTInterfaceNamespace::WSMANCommunicator::GetNetworkTime Line: 913: WS-Management call  GetNetworkTime (AMT_TimeSynchronizationService.InvokeGetLowAccuracyTimeSynch) ok

2018-07-24 07:46:10: Thread:9868(DETAIL) : WS-FD99-005.kt.ur.ch, Category: Get TLS Settings Source: vProConfigurationInternal.cpp : vProConfigurationNamespace::vProConfigurationInternal::GetTLSSettings Line: 6475:

2018-07-24 07:46:11: Thread:9868(DETAIL) : WS-FD99-005.kt.ur.ch, Category: AMTCommunicator Source: WSMANCommunicator.cpp : AMTInterfaceNamespace::WSMANCommunicator::GetTLSSettings Line: 5677: WS-Management call  GetTLSSettings (AMT_TLSSettingData.Enumerate) ok

2018-07-24 07:46:11: Thread:9868(DETAIL) : WS-FD99-005.kt.ur.ch, Category: Get Kerberos Settings Source: vProConfigurationInternal.cpp : vProConfigurationNamespace::vProConfigurationInternal::GetKerberosSettings Line: 6210:

2018-07-24 07:46:11: Thread:9868(DETAIL) : WS-FD99-005.kt.ur.ch, Category: AMTCommunicator Source: WSMANCommunicator.cpp : AMTInterfaceNamespace::WSMANCommunicator::GetKerberosSettings Line: 6131: Failed while calling  WS-Management call  GetKerberosSettings (AMT_KerberosSettingData.Get). Intel(R) AMT error  0x1: AMT Status code - An internal error has occurred in the Intel(R) AMT device. This might indicate an interface error, or an application error.

2018-07-24 07:46:11: Thread:9868(DETAIL) : , Category: Retry connection Source: vProConfigurationInternal.cpp : vProConfigurationNamespace::vProConfigurationInternal::GetKerberosSettings Line: 6220: error status: 0xc0004269

2018-07-24 07:46:11: Thread:9868(ERROR) : WS-FD99-005.kt.ur.ch, Category: AMT Interface error Source: vProConfigurationInternal.cpp : vProConfigurationNamespace::vProConfigurationInternal::GetKerberosSettings Line: 6231: Error in GetKerberosSettings- Failed while calling  WS-Management call  GetKerberosSettings (AMT_KerberosSettingData.Get). Intel(R) AMT error  0x1: AMT Status code - An internal error has occurred in the Intel(R) AMT device. This might indicate an interface error, or an application error.

2018-07-24 07:46:11: Thread:9868(DETAIL) : WS-FD99-005.kt.ur.ch, Category: Get Local Time Sync Enabled Source: vProConfigurationInternal.cpp : vProConfigurationNamespace::vProConfigurationInternal::GetLocalTimeSyncEnabled Line: 6958:

2018-07-24 07:46:11: Thread:9868(DETAIL) : , Category: Retry connection Source: vProConfigurationInternal.cpp : vProConfigurationNamespace::vProConfigurationInternal::GetLocalTimeSyncEnabled Line: 6968: error status: 0xc0004269

2018-07-24 07:46:11: Thread:9868(ERROR) : WS-FD99-005.kt.ur.ch, Category: AMT Interface error Source: vProConfigurationInternal.cpp : vProConfigurationNamespace::vProConfigurationInternal::GetLocalTimeSyncEnabled Line: 6979: Failed while calling  WS-Management call  GetKerberosSettings (AMT_KerberosSettingData.Get). Intel(R) AMT error  0x1: AMT Status code - An internal error has occurred in the Intel(R) AMT device. This might indicate an interface error, or an application error.  (0x1).

2018-07-24 07:46:11: Thread:9868(DETAIL) : ACU Configurator , Category: DiscoveryWSMan Source: HostBasedSetup.cpp : HostBasedSetup::DiscoveryWSMan Line: 1401: Calling functions in Discovery with WSMan ...

2018-07-24 07:46:11: Thread:9868(INFO) : ACU Configurator , Category: DiscoveryWSMan Source: HostBasedSetup.cpp : HostBasedSetup::DiscoveryWSMan Line: 1462: Host Based Setup is supported

2018-07-24 07:46:18: Thread:9868(DETAIL) : ACU Configurator , Category: SaveToRegstry Source: SystemDiscovery.cpp : MachineDataOp::SystemDiscovery::SaveToRegistry Line: 1082: Success.

2018-07-24 07:46:18: Thread:9868(DETAIL) : ACU Configurator , Category: System Discovery Source: ACUDllWin.cpp : SystemDiscovery Line: 139: System Discovery completed successfully. (0xc0002801)

2018-07-24 07:46:18: Thread:9868(DETAIL) : ACU Configurator , Category: -END- Source: ACUDllWin.cpp : SystemDiscovery Line: 145: ***** END SystemDiscovery ******

2018-07-24 07:46:18: Thread:9868(SUCCESS) : ACU Configurator, Category: Exit Source: Src\ActivatorMain.cpp : configurator::LogAndExit Line: 227: ***********Exit with code 0. Details: Success.

Does intel or anyone out there have a fix for the intel cpu skylake video flicker issue? this is really bad for intel to release CPU so fast but no support.?? AMD does not have these types of issues...

I would like to enable/disable vPro. on my HP Elitebook model 8460p with:

   1) Intel motherboard QM67, Revision 04,

   2) Intel Core i5-2520M 2.50GHz CPU

   3) socket 988BrPGA

   4) Technology 32nm

   5)  Family 6

   6) Extended Family 6

   7) Model A

   8) Extended Model 2A

   9) Stepping 7

  10)  Revision 02

What settings should I access.  Is there software I need to download?

I have some trouble in trying to remotely configure AMT computers.

Our infrastructure and configuration rely on a single RCS server, which does not require OTP nor hello messages (Settings -> Advanced Configuration Options -> None). Such server has been installed on the machine that also hosts our SCCM primary site and we also installed the SCCM addon. Our configuration is also based on mutual TLS authentication.

New AMT administrative BIOS password and "first configuration" are provided by a USB key and setup.bin file, that has been created with the following command:

usbfile -create setup.bin admin NEW_MEBx_ADMIN_PASSWORD -hash rootCA.cer ROOTCA_CERT_DESCR -fqdn SCS_SERVER_FQDN -dhcp 1 -dns DNS_SUFFIX -domname DNS_DOMAIN_NAME -uHash 1

Certificate templates and AMT service account have been properly configured. Latest BIOS and firmware versions have been deployed as a pre-requisite, prior to try the provisioning and the first configuration by USB key.

If we try to remotely configure the AMT device, by deploying the SCCM Task Sequence created by the addon, we have no problems only if the provisioned machine is located in the same LAN in which also the SCS server belongs to. In all other cases, it seems that the remote client tries to configure and use an OTP password to proceed with the enrollment: this evidence has been noticed by looking at the log file and by the network team. In fact, in this case it seems that the machine tries to reach the server on port 9971. Anyway, no other firewall restrictions are in place: all network traffic is open from the remote location and the VLAN which hosts the RCS server.

Is such behavior possible? I mean: the MEBx behaves differently and automatically recognizes if it is in the same LAN as for the provisioning server? In that case, is there a way to avoid this?

To provide a better explaination, I've attached two log files. The "OK" file is related to a properly configured machine (which was located on the same LAN of the RCS server), while the "KO" file is related to a failed provisioning attempt.

The failed attempt log file includes this line:

2018-07-12 16:37:25: Thread:12444(DETAIL) : ACU.dll, Category: GenerateOTP Source: ACUDll.cpp : GenerateOTP Line: 1178: Changing AMT state from IN-provisioning to Pre-Provisioning in order to set AMT OTP

which is never recorded in all provisioned machines that belongs to the same LAN in which the provisioning server is located

Thanks in advance

I Installed the Intel Managebility Commander on a SCCM server. I get the service installed and running and the right click menu entries work fine.

Is there a log for the service that i can monitor to see if things are working as expected and for troubleshooting?

Upon launching SCCMAddon.exe, I am prompted with the welcome screen which I click "next"  on. Then I come across the "select components" screen, with the three components: Intel Solutions Framework, Intel SCS platform discovery utility, and Intel AMT. I am not able to click next however, because I need to select a path for these components to reference, but for the life of me I CANNOT find "intel solutions framework" in the SCS_Package or the SCCMAddon_Package, which would allow me to select that file path. If anyone could link this download for me, or perhaps show me where to look(or what I'm even looking for) I'd be in your debt. I've just spent way to much time searching for this. Thank you!

Hi All,

I'm having a hard time installing the SCCm addon. It's having issues detecting the SCCm installation on the server.

I get the following in the ACCMAddon.log file

2018-09-18 11:30:38,334 - DEBUG: Starting

2018-09-18 11:30:38,342 - INFO : Starting Log

2018-09-18 11:30:38,343 - INFO : Version: 2.1.8.10

2018-09-18 11:30:38,470 - INFO : No previous settings found.

2018-09-18 11:30:38,878 - DEBUG: Entering SettingsViewModel.ctor

2018-09-18 11:30:41,113 - FATAL: Failed to identify the SCCM installation.

System.Management.ManagementException: Invalid namespace

   at SCSWMI.WMI_SCCM_Server_DAL.GetSCCMVersion(SCCM_Version& ver)

   at SCCMConfig.DAL.SCCMProber.GetVersion(WMI_SCCM_Server_DAL wql)

   at SCCMConfig.DAL.SCCMProber.Detect()

   at SCCMConfig.Actions.ActionPerformer.Detect()

   at Intel.SCS.ACIWizard.ViewModel.WelcomeViewModel.<Init>b__8()

Any ideas a very welcome.

SCCM is updated to latest 1806 version (5.00.8692.1000)

Hi All...

I'm having issues using powershell to communicate with my Intel AMT devices.

It's been working just fine before, but now i get a Schannel error 70 (protocol error)

I guess it's because of Intel AMT not supporting TLS 1.0 any longer.

How can i get the poweshell module to work again?

The AMT version on the client is 12.0.6 and FW is 12.0.6.1120

Please advice

/Heine

Please help me find work around on how to enable vpro feature of a non vpro processor?

Also if the non vpro proc works well with vpro networking.

Hi,

I get the following error installing RCS.

Any ideas why?

10:29:45,316 - INFO :  - Action 10:29:45: UPGRADE_RECRYPT.

10:29:45,317 - INFO :  - ProgressViewModel Installer_InstallationMessageEvent end: Action 10:29:45: UPGRADE_RECRYPT.

10:29:45,318 - INFO :  - InstallationManager HandleMessage end

10:29:45,448 - INFO :  - InstallationManager HandleMessage start

10:29:45,449 - INFO :  - ProgressViewModel Installer_InstallationMessageEvent start: Error 100. Incorrect function.

Failure occur while retrieving the upgrade properties. (Error performing inpage operation.

Part size is not 9 (0x3e7). )

10:29:45,450 - ERROR:  - Error 100. Incorrect function.

Failure occur while retrieving the upgrade properties. (Error performing inpage operation.

Part size is not 9 (0x3e7). )

/Heine

Hi...

I'm getting some errors when i try to run a Remote discovery on a PC with Intel vPro.

The log on the RCS server gives me the following error

2018-10-09 14:42:50: Thread:6296(ERROR) : RCS Server , Category: UpdateSystemInfo Source: Src\RCS_RemoteConfigurationService_WMIProvider.cpp : RCS_RemoteConfigurationService::DispatchMethods Line: 185: The parameter UUID is incorrect or missing.  AMT not found (0xc00003e8).

2018-10-09 14:42:50: Thread:6296(ERROR) : WMI Protocol, Category: UpdateSystemInfo Source: C:\workST\f5ded80e061e568\Products\SCS\Components\RCSServer\MethodCallData.h : SCS_WMI::WMICallDetails::SendErrorReport Line: 92: Finished operation with Error.   (0xc0001c89). The parameter UUID is incorrect or missing.  AMT not found (0xc00003e8).

On the client i get the following

2018-10-09 14:58:08: Thread:10912(INFO) : ACU Configurator , Category: HandleOutPut Source: CmdUtils.cpp : Cmd::HandleOutput Line: 79: Starting log 2018-10-09 14:58:08

2018-10-09 14:58:08: Thread:10912(DETAIL) : ACU.dll, Category: SetCompatibilityMode Source: ACUDll.cpp : SetCompatibilityMode Line: 196: 12.0.0.129

2018-10-09 14:58:08: Thread:10912(DETAIL) : ACU.dll, Category: SetCompatibilityMode Source: ACUDll.cpp : SetCompatibilityMode Line: 228: Set compatibility mode to 10.0.

2018-10-09 14:58:08: Thread:10912(INFO) : ACU Configurator, Category:  Source: Src\ActivatorMain.cpp : wmain Line: 372: ACUConfig 12.0.0.129

2018-10-09 14:58:08: Thread:10912(INFO) : ACU Configurator, Category: -System Discovery- Source: Src\ActivatorMain.cpp : wmain Line: 414: PC053779.XXXXXXX.XXX: Starting to discover the system information...

2018-10-09 14:58:08: Thread:10912(DETAIL) : ACU Configurator , Category: -Start- Source: ACUDllWin.cpp : SystemDiscovery Line: 57: ***** Start SystemDiscovery ******

2018-10-09 14:58:08: Thread:10912(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : HeciDiscovery Line: 555: Entering

2018-10-09 14:58:08: Thread:10912(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : CheckAMT Line: 85: Entering

2018-10-09 14:58:08: Thread:10912(DETAIL) : ACU Configurator , Category: -HECI- Source: HECIWin.cpp : HECIWin::Init Line: 191: Connected to the Intel(R) Management Engine Interface driver, version 12.0.0.2021

2018-10-09 14:58:08: Thread:10912(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : FWUpdateData Line: 46: Entering

2018-10-09 14:58:08: Thread:10912(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : FWUpdateData Line: 64: Exiting

2018-10-09 14:58:08: Thread:10912(INFO) : ACU Configurator , Category: AMT Mode Source: HECIDiscovery.cpp : CheckAMT Line: 426: Intel(R) AMT  in PROVISIONING_MODE_ENTERPRISE

2018-10-09 14:58:08: Thread:10912(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : GetPKIDNSSuffix Line: 960: Entering

2018-10-09 14:58:08: Thread:10912(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : GetPKIDNSSuffix Line: 989: Exiting

2018-10-09 14:58:08: Thread:10912(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : CheckAMT Line: 548: Exiting

2018-10-09 14:58:08: Thread:10912(DETAIL) : ACU Configurator , Category: -HECI- Source: HECIWin.cpp : HECIWin::Init Line: 191: Connected to the Intel(R) Management Engine Interface driver, version 12.0.0.2021

2018-10-09 14:58:08: Thread:10912(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : FWUpdateData Line: 46: Entering

2018-10-09 14:58:08: Thread:10912(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : FWUpdateData Line: 64: Exiting

2018-10-09 14:58:13: Thread:10912(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : PKIDiscovery Line: 894: Entering

2018-10-09 14:58:13: Thread:10912(DETAIL) : ACU Configurator , Category: Hash Handle Source: HECIDiscovery.cpp : GetPKIHashes Line: 1052: Hash Handles number:19

2018-10-09 14:58:13: Thread:10912(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : PKIDiscovery Line: 942: Exiting

2018-10-09 14:58:13: Thread:10912(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : GetAmtFQDN Line: 1448: Entering

2018-10-09 14:58:13: Thread:10912(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : GetAmtFQDN Line: 1529: Exiting

2018-10-09 14:58:13: Thread:10912(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : ConfServerDiscovery Line: 1196: Entering

2018-10-09 14:58:13: Thread:10912(DETAIL) : ACU Configurator , Category: Status message Source: HECIDiscovery.cpp : ConfServerDiscovery Line: 1250: AMT Status code - Essential data is missing from the AMT. (0xc0004a71)

2018-10-09 14:58:13: Thread:10912(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : ConfServerDiscovery Line: 1274: Exiting

2018-10-09 14:58:13: Thread:10912(DETAIL) : ACU Configurator , Category: ConfServerDiscovery Source: HECIDiscovery.cpp : HeciDiscovery Line: 809: AMT Status code - An internal error has occurred in the Intel(R) AMT device. This might indicate an interface error, or an application error. (0xc0004269) (ConfServerDiscovery)

2018-10-09 14:58:13: Thread:10912(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : ReInitPTHI Line: 1687: Entering

2018-10-09 14:58:18: Thread:10912(DETAIL) : ACU Configurator , Category: -HECI- Source: HECIWin.cpp : HECIWin::Init Line: 191: Connected to the Intel(R) Management Engine Interface driver, version 12.0.0.2021

2018-10-09 14:58:18: Thread:10912(DETAIL) : ACU Configurator , Category: GetPID Source: HECIDiscovery.cpp : HeciDiscovery Line: 816: AMT Status code - An internal error has occurred in the Intel(R) AMT device. This might indicate an interface error, or an application error. (0xc0004269) (GetPID)

2018-10-09 14:58:18: Thread:10912(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : ReInitPTHI Line: 1687: Entering

2018-10-09 14:58:23: Thread:10912(DETAIL) : ACU Configurator , Category: -HECI- Source: HECIWin.cpp : HECIWin::Init Line: 191: Connected to the Intel(R) Management Engine Interface driver, version 12.0.0.2021

2018-10-09 14:58:23: Thread:10912(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : LMSDiscovery Line: 1282: Entering

2018-10-09 14:58:24: Thread:10912(INFO) : ACU Configurator , Category: Discovery Source: HostBasedSetup.cpp : HostBasedSetup::Discovery Line: 432: Calling function Discovery...

2018-10-09 14:58:24: Thread:10912(INFO) : ACU Configurator , Category: Local System Account Source: HostBasedSetup.cpp : HostBasedSetup::GetLocalSystemAccount Line: 217: Calling function GetLocalSystemAccount over MEI...

2018-10-09 14:58:24: Thread:10912(DETAIL) : ACU Configurator , Category: -HECI- Source: HECIWin.cpp : HECIWin::Init Line: 191: Connected to the Intel(R) Management Engine Interface driver, version 12.0.0.2021

2018-10-09 14:58:24: Thread:10912(INFO) : ACU Configurator , Category: Local System Account Source: HostBasedSetup.cpp : HostBasedSetup::GetLocalSystemAccount Line: 255: Function GetLocalSystemAccount over MEI ended successfully

2018-10-09 14:58:25: Thread:10912(INFO) : ACU Configurator , Category: Discovery Source: HostBasedSetup.cpp : HostBasedSetup::Discovery Line: 479: Host Based Setup is supported

2018-10-09 14:58:25: Thread:10912(INFO) : ACU Configurator , Category: Discovery Source: HostBasedSetup.cpp : HostBasedSetup::Discovery Line: 518: Current Control Mode: 0 (Not provisioned)

2018-10-09 14:58:25: Thread:10912(INFO) : ACU Configurator , Category: Discovery Source: HostBasedSetup.cpp : HostBasedSetup::Discovery Line: 557: Allowed Control Modes: 2 (Admin) and  1 (Client)

2018-10-09 14:58:25: Thread:10912(INFO) : ACU Configurator , Category: Discovery Source: HostBasedSetup.cpp : HostBasedSetup::Discovery Line: 561: Function Discovery ended successfully

2018-10-09 14:58:25: Thread:10912(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : LMSDiscovery Line: 1355: Exiting

2018-10-09 14:58:25: Thread:10912(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : SecurityDiscovery Line: 1373: Entering

2018-10-09 14:58:25: Thread:10912(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : SecurityDiscovery Line: 1408: Exiting

2018-10-09 14:58:25: Thread:10912(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : FeaturesDiscovery Line: 1426: Entering

2018-10-09 14:58:25: Thread:10912(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : FeaturesDiscovery Line: 1441: Exiting

2018-10-09 14:58:25: Thread:10912(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : UuidDiscovery Line: 1536: Entering

2018-10-09 14:58:25: Thread:10912(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : UuidDiscovery Line: 1554: Exiting

2018-10-09 14:58:25: Thread:10912(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : TcpIpDiscovery Line: 1561: Entering

2018-10-09 14:58:25: Thread:10912(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : TcpIpDiscovery Line: 1680: Exiting

2018-10-09 14:58:25: Thread:10912(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : HeciDiscovery Line: 874: Exiting

2018-10-09 14:58:25: Thread:10912(DETAIL) : ACU Configurator , Category: SaveToRegstry Source: SystemDiscovery.cpp : MachineDataOp::SystemDiscovery::SaveToRegistry Line: 1082: Success.

2018-10-09 14:58:25: Thread:10912(WARN) : ACU.dll, Category: System Discovery Source: ACUDllWin.cpp : SystemDiscovery Line: 133: System Discovery failed to get data from this system.  Failed to save the discovery data in the RCS database.  The parameter UUID is incorrect or missing.  AMT not found

2018-10-09 14:58:25: Thread:10912(DETAIL) : ACU Configurator , Category: -END- Source: ACUDllWin.cpp : SystemDiscovery Line: 145: ***** END SystemDiscovery ******

2018-10-09 14:58:25: Thread:10912(WARN) : ACU Configurator, Category: Exit Source: Src\ActivatorMain.cpp : configurator::LogAndExit Line: 227: ***********Exit with code 32. Details: Intel(R) AMT operation completed with warnings: System Discovery failed to get data from this system.  Failed to save the discovery data in the RCS database.  The parameter UUID is incorrect or missing.  AMT not found

Please advise. What's the UUID? I have Intel Managability entry in bios, and can get into the MEBx with CTRL + P, so i believe that AMT is available on the system?