- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
When I run the command manually on the target device from a command prompt. I receive below error message. I can ping and browse the AMT server and the laptop has Intel AMT enabled.
Exit with code 75. Details: Failed to complete remote configuration of this Intel(R) AMT device. Initial connection to the Intel(R) AMT device failed. A TCP error occurred. Make sure that the destination settings are correct and that a network connection exists to the target.
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello RKabi1,
Thank you for joining the community
Is this a new integration or existing and you are trying to add new systems? Could you tell if TLS is enabled on the profile you are trying to provision? On new systems with AMT v12 TLS 1.0 is deprecated thus it will throw an error when you enable TLS 1.0 and the AMT v12 system rejects it
Regards
Jose A.
Intel Customer Support Technician
Under Contract to Intel Corporation
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Jose, this is a new integration. I am trying to provision the first device. I will check if TLS 1.0 is enabled. Will let you know. Thanks for your help.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello RKabi1,
I am just following up to double check if you were able to do some progress on your new AMT integration. Otherwise let us know if you require more time to accomplish this.
If you consider the issue to be completed please let us know so we can proceed to mark this thread as resolved.
Regards
Jose A.
Intel Customer Support Technician
Under Contract to Intel Corporation
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Josh, thanks for following up. Sorry i was very busy this week. I will do this weekend and will let you know.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Jose, I can see AMT profile name is RcsTlsPrifile but do not see what version it is. Also on the target system installed MEBx version is 11.0.0.0010 and MEI driver version is 1904.12.0.1208
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Here is the log when I try to run remote provisioning script on the target laptop.
2019-08-31 15:23:58: Thread:13612(INFO) : ACU Configurator , Category: HandleOutPut Source: CmdUtils.cpp : Cmd::HandleOutput Line: 79: Starting log 2019-08-31 15:23:58
2019-08-31 15:23:58: Thread:13612(DETAIL) : ACU.dll, Category: SetCompatibilityMode Source: ACUDll.cpp : SetCompatibilityMode Line: 222: Set compatibility mode to 10.0.
2019-08-31 15:23:58: Thread:13612(INFO) : ACU Configurator, Category: Source: Src\ActivatorMain.cpp : wmain Line: 371: ACUConfig 11.1.0.75
2019-08-31 15:23:58: Thread:13612(INFO) : ACU Configurator, Category: -Unknown Operation- Source: Src\ActivatorMain.cpp : wmain Line: 414: Laptop02.command.com.au: Starting to configure AMT via RCS...
2019-08-31 15:23:58: Thread:13612(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : CheckAMT Line: 85: Entering
2019-08-31 15:23:58: Thread:13612(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.1208
2019-08-31 15:23:58: Thread:13612(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : FWUpdateData Line: 46: Entering
2019-08-31 15:23:58: Thread:13612(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : FWUpdateData Line: 64: Exiting
2019-08-31 15:23:58: Thread:13612(INFO) : ACU Configurator , Category: AMT Mode Source: HECIDiscovery.cpp : CheckAMT Line: 418: Intel(R) AMT in PROVISIONING_MODE_ENTERPRISE
2019-08-31 15:23:58: Thread:13612(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : GetPKIDNSSuffix Line: 955: Entering
2019-08-31 15:23:58: Thread:13612(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : GetPKIDNSSuffix Line: 984: Exiting
2019-08-31 15:23:58: Thread:13612(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : CheckAMT Line: 540: Exiting
2019-08-31 15:24:00: Thread:13612(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : GetAmtFQDN Line: 1443: Entering
2019-08-31 15:24:00: Thread:13612(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : GetAmtFQDN Line: 1524: Exiting
2019-08-31 15:24:01: Thread:13612(INFO) : ACU Configurator , Category: Discovery Source: HostBasedSetup.cpp : HostBasedSetup::Discovery Line: 432: Calling function Discovery...
2019-08-31 15:24:01: Thread:13612(INFO) : ACU Configurator , Category: Local System Account Source: HostBasedSetup.cpp : HostBasedSetup::GetLocalSystemAccount Line: 217: Calling function GetLocalSystemAccount over MEI...
2019-08-31 15:24:01: Thread:13612(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.1208
2019-08-31 15:24:01: Thread:13612(INFO) : ACU Configurator , Category: Local System Account Source: HostBasedSetup.cpp : HostBasedSetup::GetLocalSystemAccount Line: 255: Function GetLocalSystemAccount over MEI ended successfully
2019-08-31 15:24:02: Thread:13612(INFO) : ACU Configurator , Category: Discovery Source: HostBasedSetup.cpp : HostBasedSetup::Discovery Line: 479: Host Based Setup is supported
2019-08-31 15:24:02: Thread:13612(INFO) : ACU Configurator , Category: Discovery Source: HostBasedSetup.cpp : HostBasedSetup::Discovery Line: 518: Current Control Mode: 2 (Admin)
2019-08-31 15:24:02: Thread:13612(INFO) : ACU Configurator , Category: Discovery Source: HostBasedSetup.cpp : HostBasedSetup::Discovery Line: 557: Allowed Control Modes: 2 (Admin) and 1 (Client)
2019-08-31 15:24:02: Thread:13612(INFO) : ACU Configurator , Category: Discovery Source: HostBasedSetup.cpp : HostBasedSetup::Discovery Line: 561: Function Discovery ended successfully
2019-08-31 15:24:04: Thread:13612(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : UuidDiscovery Line: 1531: Entering
2019-08-31 15:24:04: Thread:13612(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : UuidDiscovery Line: 1549: Exiting
2019-08-31 15:24:04: Thread:13612(DETAIL) : ACU Configurator , Category: Returned data Source: ACUDll.cpp : GetHostAndMEInfo Line: 4470: GetHostAndMEInfo output data: IsAMT:True, isEnterpriseMode:True, configurationMode:2, isRemoteConfigEnabled:True, AMTversion:11.8.60, isMobile:True, provisioningTlsMode:2, uuid:4C4C4544-0035-3010-8035-B1C04F504832, isClientConfigEnabled:True, hostBasedSupport:True, configurationState:2, FQDN:Laptop02.command.com.au, embeddedConfigurationAllowed:False. isLANLessPlatform:False. PKIDNSSuffix: Empty.
2019-08-31 15:24:04: Thread:13612(DETAIL) : ACU Configurator , Category: -Start- Source: ACUDll.cpp : RemoteConfiguration Line: 3575: ***** Start RemoteConfiguration ******
2019-08-31 15:24:06: Thread:13612(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : TcpIpDiscovery Line: 1556: Entering
2019-08-31 15:24:06: Thread:13612(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : TcpIpDiscovery Line: 1675: Exiting
2019-08-31 15:24:09: Thread:13612(DETAIL) : NetworkSettingClass, Category: SetSourceForAMTName Source: NetworkSettingsClass.cpp : NetworkSettings::NetworkSettingClass::initializeData Line: 460: Get OS IP:Call to function failed with return code 0x80041002 - Not found
2019-08-31 15:24:11: Thread:13612(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : GetAmtFQDN Line: 1443: Entering
2019-08-31 15:24:11: Thread:13612(DETAIL) : AMT Discovery, Category: HECI Discovery Source: HECIDiscovery.cpp : GetAmtFQDN Line: 1524: Exiting
2019-08-31 15:24:11: Thread:13612(DETAIL) : ACU.dll, Category: GetNetworkSettings Source: ACUDllWin.cpp : LoadNetworkSettings Line: 996: RCSaddress=WIN2016.command.com.au, RCSWMIUser=command.com.au\RProAdmin, RCSProfileName=RcsTlsProfile
2019-08-31 15:24:11: Thread:13612(DETAIL) : NetworkSettingClass, Category: LoadSourceForAMTName Source: NetworkSettingsClass.cpp : NetworkSettings::NetworkSettingClass::LoadSourceForAMTName Line: 576: Laptop02.command.com.au
2019-08-31 15:24:11: Thread:13612(DETAIL) : ACU.dll, Category: Configure AMT Source: ACUDllWin.cpp : MI_ConfigAMT Line: 655: RCSaddress=WIN2016.command.com.au, RCSWMIUser=command.com.au\RProAdmin, UUID=4C4C4544-0035-3010-8035-B1C04F504832, ConfigMode=3, PID=, RCSProfileName=RcsTlsProfile, AMTVersion=11.8.60, OldADOU=, Configure AMT Name= True. Configure AMT IPv4= True. Source For AMT Name= Host Name- Laptop02 Domain Name- command.com.au . Default OS Name= Host Name- Laptop02 Domain Name- command.com.au . Configure AMT IPv4 to DHCP mode= True.
2019-08-31 15:24:57: Thread:13612(DETAIL) : ACU Configurator , Category: -END- Source: ACUDll.cpp : RemoteConfiguration Line: 3870: ***** END RemoteConfiguration ******
2019-08-31 15:24:57: Thread:13612(ERROR) : ACU Configurator, Category: Exit Source: Src\ActivatorMain.cpp : configurator::LogAndExit Line: 226: ***********Exit with code 75. Details: Failed to complete remote configuration of this Intel(R) AMT device. Initial connection to the Intel(R) AMT device failed. A TCP error occurred. Make sure that the destination settings are correct and that a network connection exists to the target.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello RKabi1,
Do you know what version of the SCCM and/or RCS server do you have installed? If by any chance you are sending the script from a v12 RCS server to a v11 target machine the TLS settings might not be compatible as v11 supports TLS 1.0 while v12 does not.
Jose A.
Intel Customer Support Technician
Under Contract to Intel Corporation
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello RKabi1,
I am just following up to double check if you were able to gather the requested information. Otherwise let us know if you require more time to accomplish this.
Regards
Jose A.
Intel Customer Support Technician
Under Contract to Intel Corporation
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi Jose, we had older version of SCCM revision 1806 which is being upgraded to 1902. I will try to do again when the upgrade is complete. Please close this case. I will open a new one, if required. Thank you for your support.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello RKabi1,
We will proceed to mark this thread as resolved. If you have further issues or questions just go ahead and create a new topic.
Jose A.
Intel Customer Support Technician
A Contingent Worker at Intel
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page