topic Re: Issue running remote discovery in Intel vPro® Platform

Issue running remote discovery

HMads — Tue, 09 Oct 2018 13:07:08 GMT

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) : 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...

Re: Issue running remote discovery

idata — Wed, 10 Oct 2018 02:00:28 GMT

Hello Heine Koldbro Madsen,

Thanks for joining the community.

To answer your question about UUID it is the Universally Unique Identifier of the Intel AMT device.

Second the most obvious question about the AMT not found error would be Is the machine AMT capable? Since you said you can access MEBX though Ctrl+P it means most likely the machine is AMT capable but is it already provisioned? You could provision the machine using the ACUConfig tool from the SCS package.

We will wait for your updates.

Jose A.

Re: Issue running remote discovery

HMads — Thu, 11 Oct 2018 06:56:21 GMT

Hi...

The machine is AMT capable. and has previously been configured just fine.

AMT settings have been reset from bios several times

If i run ACUConfig.exe with the status option it says it's not provisioned.

/Heine

Re: Issue running remote discovery

idata — Thu, 11 Oct 2018 23:23:15 GMT

Hello Heine Koldbro Madsen,

Since it says it's not provisioned, does it allow you to continue and complete the provisioning process? Does it gives you any error message or does it completes but then it just doesn't work?

On the same folder where the ACUconfig tool is saved, every time you start the tool it will create a ACUconfig log. Could you please send us that log?

Jose A.

Re: Issue running remote discovery

HMads — Fri, 12 Oct 2018 11:39:43 GMT

Hi...

I have been using all day on this issue.. and something is not working.

On the RCS server I used the RCSutils to install a certificate bought from Comodo with the /RCSUser option set to NetworkService.

I get this

Command: RCSUtils.exe /Certificate view /rcsuser NetworkService

Intel(R) SCS Utils starting:

Getting the certificates from the user NT AUTHORITY\NETWORK SERVICE personal Certificate store

Enumerating the user certificate store succeeded.

The 2 certificate(s) found in the store:

Certificate Subject: CN=rcs.domain.com, OU=COMODO AMT SSL, OU=Hosted by Hosted by TRUSTZONE, OU=Domain Control Validated - Thumbprint: XXXXXXXXXXXXXXXXXXXXXXXXXXX, Contains private key: Yes, Valid until: 09-10-2020 01:59:59, PKI Configuration(ZTC): True, Mutual TLS: False

Certificate Subject: CN=XXXXX - Thumbprint: XXXXXXXXXXXXXXXXXX, Contains private key: Yes, Valid until: 14-09-2028 15:50:37, PKI Configuration(ZTC): False, Mutual TLS: False

-------------------------------------------------------------------------------

Exit status for the running user NT AUTHORITY\SYSTEM:

Success.

Running "RCSUtils.exe /certificate validate XXXXXXXXXXX /RCSUser NetworkService /log file _validate.log"

12-10-2018 12:20:59: -------------------------------------------------------------------------------

12-10-2018 12:20:59: Intel(R) SCS Utils log, running user: NT AUTHORITY\SYSTEM

12-10-2018 12:20:59: -------------------------------------------------------------------------------

12-10-2018 12:20:59: Validating XXXXXXXXXXX Certificate in the user NT AUTHORITY\NETWORK SERVICE certificate store

12-10-2018 12:20:59: The certificate path found contains:

- Certificate subject CN=rcs.domain.com, OU=COMODO AMT SSL, OU=Hosted by TRUSTZONE, OU=Domain Control Validated, Thumbprint XXXXXXXXXXXXXXXXXXXXXXXXXXXX,

- Certificate subject CN=COMODO SHA-2 Pro Series Secure Server CA, O=COMODO CA Limited, L=Salford, S=Greater Manchester, C=GB, Thumbprint 5DBAFB06715C7E327C9831AB354A88747E41344A,

- Certificate subject CN=AAA Certificate Services, O=Comodo CA Limited, L=Salford, S=Greater Manchester, C=GB, Thumbprint D1EB23A46D17D68FD92564C2F1F1601764D8E349,

The certificate is not valid for Intel(r) RCS Mutual TLS(HTTPS) connection and is valid for Intel(r) RCS remote PKI(ZTC) connection

12-10-2018 12:20:59: Verifying the certificate from the user certificate store succeeded.

12-10-2018 12:20:59: -------------------------------------------------------------------------------

12-10-2018 12:20:59: Exit status for the running user NT AUTHORITY\SYSTEM:

12-10-2018 12:20:59: Success.

So i guess the certificate is installed just fine, or am I wrong here? Is it a problem that it sees two certificates?

It says the fist certificate is valid for PKI Configuration(ZTC) but not the second one, which is OK since is a certificate that's from out own internal ca.

When i start the RCSServer service i get this in the log:

2018-10-12 12:27:47: Thread:3300(DETAIL) : RCS Server , Category: ServiceSettings Source: Src\ServiceSettings.cpp : ServiceSettings::ServiceSettings::Init Line: 146: Start ServiceSettings

2018-10-12 12:27:47: Thread:7084(INFO) : RCS Server , Category: -------------- Source: Src\RCSServer.cpp : CServiceModule::Run Line: 1313: ------------------------------------

2018-10-12 12:27:47: Thread:7084(INFO) : RCS Server , Category: Source: Src\RCSServer.cpp : CServiceModule::Run Line: 1314: Start Server version: 12.0.0.129 ------------

2018-10-12 12:27:47: Thread:7084(INFO) : RCS Server , Category: -------------- Source: Src\RCSServer.cpp : CServiceModule::Run Line: 1315: ------------------------------------

2018-10-12 12:27:47: Thread:7084(DETAIL) : RCS Server , Category: ServiceSettings Source: Src\ServiceSettings.cpp : ServiceSettings::ServiceSettings::Init Line: 146: Start ServiceSettings

2018-10-12 12:27:47: Thread:7084(INFO) : RCS Server , Category: Source: Src\RCSServer.cpp : CServiceModule::Run Line: 1350: Start Server version: 12.0.0.129 ------------

2018-10-12 12:27:47: Thread:7084(DETAIL) : RCS Server , Category: Source: Src\RCSServer.cpp : CServiceModule::Run Line: 1354: Enhanced Security is enabled.

2018-10-12 12:27:47: Thread:7084(DETAIL) : Initialize, Category: CAInterfaceInternal Source: CAInterfaceInternal.cpp : CAInterfaceNamespace::CAInterfaceInternal::Init Line: 183: Start CAInterfaceInternal

2018-10-12 12:27:47: Thread:7084(DETAIL) : ACU Configurator, Category: ADInterfaceInternal Source: ADInterfaceInternal.cpp : ADInterfaceNamespace::ADInterfaceInternal::Init Line: 87: Start ADInterfaceInternal

2018-10-12 12:27:47: Thread:7084(DETAIL) : SCS Configurator, Category: Start vProConfiguration Source: vProConfigurationInternal.cpp : vProConfigurationNamespace::vProConfigurationInternal::Init Line: 42:

2018-10-12 12:27:47: Thread:7084(DETAIL) : RCS Server , Category: DmpStorage Source: DmpStorageInternal.cpp : DmpRepositoryNamespace::DmpStorageInternal::Init Line: 32: Start DmpStorage

2018-10-12 12:27:47: Thread:7084(DETAIL) : RCS Server , Category: ProfileStorage Source: ProfileStorageInternal.cpp : ProfileRepositoryNamespace::ProfileStorageInternal::Init Line: 37: Start ProfileStorage

2018-10-12 12:27:47: Thread:7084(DETAIL) : RCS Server , Category: ProfileStorage Source: ProfileAccessorDB.cpp : ProfileRepositoryNamespace::ProfileAccessorDB::GetAll Line: 121: Entering

2018-10-12 12:27:47: Thread:7084(DETAIL) : RCS Server , Category: ProfileStorage Source: ProfileAccessorDB.cpp : ProfileRepositoryNamespace::ProfileAccessorDB::GetAll Line: 124: Exiting

2018-10-12 12:27:47: Thread:7084(DETAIL) : RCS Server , Category: BareMetalHelper Source: BareMetalHelperInternal.cpp : BareMetalHelperNamespace::BareMetalHelperInternal::Init Line: 39: Start

2018-10-12 12:27:48: Thread:1896(INFO) : RCS Server , Category: CA Mediation Plugins Source: CaMediationCOMInterface.cpp : CAInterfaceNamespace::CAMediationComInterface::init Line: 173: RCS failed to load a valid 3rd party Certificate Authority mediation DLL file, so RCS disabled the option. (0xc0003f5e).

2018-10-12 12:27:48: Thread:1896(DETAIL) : RCS Server , Category: CA Mediation Plugins Source: c:\workst\f5ded80e061e568\products\scs\modules\cainterface\CaMediationCOMInterface.h : CAInterfaceNamespace::ProcessManager::TerminateIfFilenameMatches Line: 69: Entering

2018-10-12 12:27:48: Thread:7084(ERROR) : RCS Server , Category: Initial 3rd party CA Mediation DLL. Source: Src\RCSServer.cpp : CServiceModule::Run Line: 1438: RCS failed to load a valid 3rd party Certificate Authority mediation DLL file, so RCS disabled the option. (0xc0003f5e).

2018-10-12 12:27:52: Thread:1916(INFO) : GetRCSVersion, Category: Responding to Get Source For AMT Request Source: Src\RCS_RemoteConfigurationService_WMIProvider.cpp : RCS_RemoteConfigurationService::GetRCSVersion Line: 1992:

2018-10-12 12:27:52: Thread:1932(DETAIL) : RCS Server , Category: JobController Source: Src\JobController.cpp : JobController::run Line: 297: Start

2018-10-12 12:27:52: Thread:1932(DETAIL) : RCS Server , Category: GetJobsByQuery Source: Job.cpp : JobsNameSpace::Job::GetJobsByQuery Line: 662: Start

2018-10-12 12:27:52: Thread:1932(DETAIL) : RCS Server , Category: GetJobsByQuery DATA_NOT_FOUND Source: Job.cpp : JobsNameSpace::Job::GetJobsByQuery Line: 679: Data was not found.

2018-10-12 12:27:52: Thread:1932(DETAIL) : RCS Server , Category: JobController Source: Src\JobController.cpp : JobController::run Line: 322: Iteration

2018-10-12 12:27:52: Thread:1932(DETAIL) : RCS Server , Category: JobController Source: Src\JobController.cpp : JobController::run Line: 352: Ne...

Re: Issue running remote discovery

idata — Mon, 15 Oct 2018 04:54:13 GMT

Hello Heine Koldbro Madsen,

We will engage our engineering department about your issue. In the mean time could you please attach an screenshot of the certificate window in both the RCS server and the remote AMT machine?

Jose A.

Re: Issue running remote discovery

idata — Fri, 19 Oct 2018 05:06:08 GMT

Hello Heine Koldbro Madsen,

I am following up on this issue just to ask if you were able to gather the requested information (screenshot of the certificate window in both the RCS server and the remote AMT machine).

If you need more time just let us know.

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.

Re: Issue running remote discovery

idata — Mon, 22 Oct 2018 19:25:22 GMT

I received the exact same error message and code number, but came back to my test machine a day later to see the "Remote Configuration" Task Sequence had run and produced the exact same code (32). If that's not strange enough, AMT was configured and I was able to remotely access the device using MeshCommander (Intel Manageability Commander alternative).

Re: Issue running remote discovery

idata — Tue, 23 Oct 2018 04:58:25 GMT

Hello Heine Koldbro Madsen,

The behavior you describe is certainly strange. Were you able to gather a screenshot of the certificate window in both the RCS server and the remote AMT machine?

Please provide this info so we can proceed to engage our engineering department.

Jose A.

Re: Issue running remote discovery

idata — Tue, 23 Oct 2018 15:53:21 GMT

I'm probably in a slightly different scenario compared to the original poster... I have to use an internal certificate as I have a legacy domain name.

I assumed everything was fine as the SCCM Task Sequences that the SCS add-on installs list error code 32 as a success:

Re: Issue running remote discovery

idata — Wed, 24 Oct 2018 00:40:35 GMT

Hello Sean Eatch,

We will try to check with our engineering department about this particular issue. We will let you know if further information is needed.

Regards.

Jose A.