Re: Issues running maintenance task on FW 12.0.6.1120

HMads · ‎03-26-2019

Hi,

We are having issues running the maintenance task on computers running FW version 12.0.6.1120.

The Maintenance task i working fine on FW version 11.8.60

ACUConfig.exe i version 12.0.0.129

We use SCCM to run the Maintenance Task Sequence and a RCS server.

Here's the log from a failing maintenance:

2019-03-26 07:55:23: Thread:16976(INFO) : ACU Configurator , Category: HandleOutPut Source: CmdUtils.cpp : Cmd::HandleOutput Line: 79: Starting log 2019-03-26 07:55:23
2019-03-26 07:55:23: Thread:16976(DETAIL) : ACU.dll, Category: SetCompatibilityMode Source: ACUDll.cpp : SetCompatibilityMode Line: 196: 12.0.0.129
2019-03-26 07:55:23: Thread:16976(DETAIL) : ACU.dll, Category: SetCompatibilityMode Source: ACUDll.cpp : SetCompatibilityMode Line: 228: Set compatibility mode to 10.0.
2019-03-26 07:55:23: Thread:16976(INFO) : ACU Configurator, Category:  Source: Src\ActivatorMain.cpp : wmain Line: 372: ACUConfig 12.0.0.129
2019-03-26 07:55:23: Thread:16976(INFO) : ACU Configurator, Category: -Maintain AMT via RCS- Source: Src\ActivatorMain.cpp : wmain Line: 414: PCXXXXXX.Here.is.My.Domain.com: Starting to maintain AMT via RCS: Synchronize Network, Synchronize Clock, Reissue Certificates, Renew Active Directory Password, Renew Administrator Password...
2019-03-26 07:55:23: Thread:16976(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : CheckAMT Line: 85: Entering
2019-03-26 07:55:23: Thread:16976(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
2019-03-26 07:55:23: Thread:16976(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : FWUpdateData Line: 46: Entering
2019-03-26 07:55:23: Thread:16976(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : FWUpdateData Line: 64: Exiting
2019-03-26 07:55:23: Thread:16976(INFO) : ACU Configurator , Category: AMT Mode Source: HECIDiscovery.cpp : CheckAMT Line: 426: Intel(R) AMT  in PROVISIONING_MODE_ENTERPRISE
2019-03-26 07:55:23: Thread:16976(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : GetPKIDNSSuffix Line: 960: Entering
2019-03-26 07:55:23: Thread:16976(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : GetPKIDNSSuffix Line: 989: Exiting
2019-03-26 07:55:23: Thread:16976(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : CheckAMT Line: 548: Exiting
2019-03-26 07:55:26: Thread:16976(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : GetAmtFQDN Line: 1448: Entering
2019-03-26 07:55:26: Thread:16976(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : GetAmtFQDN Line: 1529: Exiting
2019-03-26 07:55:26: Thread:16976(INFO) : ACU Configurator , Category: Discovery Source: HostBasedSetup.cpp : HostBasedSetup::Discovery Line: 432: Calling function Discovery...
2019-03-26 07:55:26: Thread:16976(INFO) : ACU Configurator , Category: Local System Account Source: HostBasedSetup.cpp : HostBasedSetup::GetLocalSystemAccount Line: 217: Calling function GetLocalSystemAccount over MEI...
2019-03-26 07:55:26: Thread:16976(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
2019-03-26 07:55:26: Thread:16976(INFO) : ACU Configurator , Category: Local System Account Source: HostBasedSetup.cpp : HostBasedSetup::GetLocalSystemAccount Line: 255: Function GetLocalSystemAccount over MEI ended successfully
2019-03-26 07:55:29: Thread:16976(INFO) : ACU Configurator , Category: Discovery Source: HostBasedSetup.cpp : HostBasedSetup::Discovery Line: 479: Host Based Setup is supported
2019-03-26 07:55:29: Thread:16976(INFO) : ACU Configurator , Category: Discovery Source: HostBasedSetup.cpp : HostBasedSetup::Discovery Line: 518: Current Control Mode: 2 (Admin)
2019-03-26 07:55:29: Thread:16976(INFO) : ACU Configurator , Category: Discovery Source: HostBasedSetup.cpp : HostBasedSetup::Discovery Line: 557: Allowed Control Modes: 2 (Admin) and  1 (Client)
2019-03-26 07:55:29: Thread:16976(INFO) : ACU Configurator , Category: Discovery Source: HostBasedSetup.cpp : HostBasedSetup::Discovery Line: 561: Function Discovery ended successfully
2019-03-26 07:55:31: Thread:16976(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : UuidDiscovery Line: 1536: Entering
2019-03-26 07:55:31: Thread:16976(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : UuidDiscovery Line: 1554: Exiting
2019-03-26 07:55:31: Thread:16976(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.6.1120, 	isMobile:False, 	provisioningTlsMode:2, 	uuid:10B42280-C944-11E8-A1B1-9225B8141500, 	isClientConfigEnabled:True, 	hostBasedSupport:True, 	configurationState:2, 	FQDN:PCXXXXXX.Here.is.My.Domain.com, 	embeddedConfigurationAllowed:True. 	isLANLessPlatform:False. 	PKIDNSSuffix: Empty. 
2019-03-26 07:55:31: Thread:16976(DETAIL) : ACU Configurator , Category: -Start- Source: ACUDll.cpp : RemoteConfiguration Line: 3581: ***** Start RemoteConfiguration ******
2019-03-26 07:55:33: Thread:16976(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : TcpIpDiscovery Line: 1561: Entering
2019-03-26 07:55:33: Thread:16976(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : TcpIpDiscovery Line: 1680: Exiting
2019-03-26 07:55:35: Thread:16976(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : GetAmtFQDN Line: 1448: Entering
2019-03-26 07:55:35: Thread:16976(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : GetAmtFQDN Line: 1529: Exiting
2019-03-26 07:55:35: Thread:16976(DETAIL) : ACU.dll, Category: GetNetworkSettings Source: ACUDllWin.cpp : LoadNetworkSettings Line: 996: RCSaddress=RCSSERVER.Here.is.My.Domain.com, RCSWMIUser=, RCSProfileName=RN_IntelAMT
2019-03-26 07:55:36: Thread:16976(DETAIL) : NetworkSettingClass, Category: LoadSourceForAMTName Source: NetworkSettingsClass.cpp : NetworkSettings::NetworkSettingClass::LoadSourceForAMTName Line: 576: PCXXXXXX.Here.is.My.Domain.com
2019-03-26 07:55:36: Thread:16976(DETAIL) : ACU.dll, Category: Configure AMT Source: ACUDllWin.cpp : MI_MaintainAMT Line: 958: RCSaddress=RCSSERVER.Here.is.My.Domain.com, RCSWMIUser=, UUID=10B42280-C944-11E8-A1B1-9225B8141500, RCSProfileName=RN_IntelAMT, AMTVersion=12.0.6.1120Configure AMT Name= True. Configure AMT IPv4= True. AMT Name= Host Name- PCXXXXXX Domain Name- Here.is.My.Domain.com . Source For AMT Name= Host Name- PCXXXXXX Domain Name- Here.is.My.Domain.com . Default OS Name= Host Name- PCXXXXXX Domain Name- Here.is.My.Domain.com . Host IPv4= IPv4 Address- 10.2.25.219 IPv4 SubNet- 255.255.252.0 IPv4 Gateway- 10.2.24.1 IPv4 Primary DNS- 10.253.128.70 . Configure AMT IPv4 to DHCP mode= True. AMT IPv4= IPv4 Address- 10.2.25.219 . 
2019-03-26 07:55:36: Thread:16976(INFO) : ACU Configurator , Category: WMI Access Layer Source: WMIAccess.cpp : WMI_IsRcsBusy Line: 683: Success. (0) (retry set to = 3)
2019-03-26 07:55:37: Thread:16976(INFO) : ACU Configurator , Category: WMI Access Layer Source: WMIAccess.cpp : WMI_IsRcsBusy Line: 759: Success. (0) (RCS not busy.)
2019-03-26 07:55:37: Thread:16976(INFO) : ACU Configurator , Category: WMI Access Layer Source: WMIAccess.cpp : WMI_IsRcsBusy Line: 783: Success. (0) (RCS is currently handling = 0 threads)
2019-03-26 07:55:54: Thread:16976(DETAIL) : ACU Configurator , Category: -END- Source: ACUDll.cpp : RemoteConfiguration Line: 3879: ***** END RemoteConfiguration ******
2019-03-26 07:55:54: Thread:16976(ERROR) : ACU Configurator, Category: Exit Source: Src\ActivatorMain.cpp : configurator::LogAndExit Line: 227: ***********Exit with code 49. Details: Failed to do the requested maintenance tasks on 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.

Please advise

Emeth_O_Intel · ‎03-27-2019

Hello Heine, Thank you so much for contacting us about this concern. I was reviewing the RCS Logs provided and I noticed the following error: "2019-03-26 07:55:54: Thread:16976(ERROR) : ACU Configurator, Category: Exit Source: Src\ActivatorMain.cpp : configurator::LogAndExit Line: 227: ***********Exit with code 49. Details: Failed to do the requested maintenance tasks on 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." Could you please so kind and provide us the steps that you are following in order to performe the update installation just to double check if there is a missing step on this process. Also, how many systems are showing you this error? Are all the systems at the same location? Please let us know the outcome in order to proceed with the next step. Regards, Emeth O. Intel Customer Support Technician. Under Contract to Intel Corporation.

Emeth_O_Intel · ‎04-01-2019

Hello Heine, I am following up your thread in order to check if there is anything else that I can assist you with. If so, please do not hesitate and let me know and I will be more than happy to assist you. Regards, Emeth O. Intel Customer Support Technician. Under Contract to Intel Corporation.

Emeth_O_Intel · ‎04-04-2019

Hello Heine, Due to the fact that we haven't seen any activity on this thread, I will proceed and close the thread. Please, if you have any other question or issue in the future do not hesitate and contact us back, and we will be more than happy to assist you. Regards, Emeth O. Intel Customer Support Technician. Under Contract to Intel Corporation.