- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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:
https://sccmguru.wordpress.com/2013/12/20/integrating-configuration-manager-2012-r2-with-intel-scs-9-0-part-1/ 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(DE...
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Your SystemDiscovery.log looks to be ok. In fact the discovery process write those information into Windows Registry and SCCM agent collect from these registries entries. Have you followed this documentation? https://downloadcenter.intel.com/download/24585 https://downloadcenter.intel.com/download/24585
Best Regards!
-Bruno Domingues

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page