Community
cancel
Showing results for 
Search instead for 
Did you mean: 
DDunp
Beginner
1,304 Views

ACUConfig Systemdiscovery failing

I'm using an Intel RCS 8.2 server and ACUConfig of the same version. I am trying to run System Discovery on an AMT 8.0 client. The command line I am using is:

ACUconfig /lowsecurity /NoFile /verbose /output File C:\Windows\Temp\ACUDiscovery.txt SystemDiscovery /ReportToRCS /RCSAddress . I am getting exit code 80: Failed to get the FQDN in (GetDNSLooupName). The log file contents:

2013-07-02 11:02:12: Thread:3204(INFO) : ACU Configurator , Category: HandleOutPut Source: Src\ActivatorUtils.cpp : HandleOutput Line: 210: Starting log 2013-07-02 11:02:12

2013-07-02 11:02:12: Thread:3204(DETAIL) : ACU.dll, Category: SetCompatibilityMode Source: Src\ActivatorDll.cpp : SetCompatibilityMode Line: 104: Set compatibility mode to 8.0.

2013-07-02 11:02:13: Thread:3204(INFO) : ACU Configurator, Category: -SystemDiscovery- Source: Src\ActivatorMain.cpp : wmain Line: 311: FEI0207733.pc.na.sys.ds.wolseley.com: Discovering the System information...

2013-07-02 11:02:13: Thread:3204(DETAIL) : ACU Configurator , Category: -Start- Source: Src\ActivatorDllWin.cpp : SystemDiscovery Line: 51: ***** Start SystemDiscovery ******

2013-07-02 11:02:13: Thread:3204(DETAIL) : ACU Configurator , Category: -Start- Source: Src\HECIDiscovery.cpp : HeciDiscovery Line: 467: ***** Start HeciDiscovery ******

2013-07-02 11:02:13: Thread:3204(DETAIL) : ACU Configurator , Category: -Start- Source: Src\HECIDiscovery.cpp : CheckAMT Line: 78: ***** Start CheckAMT ******

2013-07-02 11:02:13: Thread:3204(DETAIL) : ACU Configurator , Category: -HECI- Source: Src\HECIWin.cpp : HECIWin::Init Line: 185: Connected to the Intel(R) Management Engine Interface driver, version 8.0.0.1262

2013-07-02 11:02:13: Thread:3204(DETAIL) : ACU Configurator , Category: -Start- Source: Src\HECIDiscovery.cpp : FWUpdateData Line: 40: ***** Start FWUpdateData ******

2013-07-02 11:02:13: Thread:3204(DETAIL) : ACU Configurator , Category: -END- Source: Src\HECIDiscovery.cpp : FWUpdateData Line: 61: ***** END FWUpdateData ******

2013-07-02 11:02:13: Thread:3204(INFO) : ACU Configurator , Category: AMT Mode Source: Src\HECIDiscovery.cpp : CheckAMT Line: 382: Intel(R) AMT in PROVISIONING_MODE_ENTERPRISE

2013-07-02 11:02:13: Thread:3204(DETAIL) : ACU Configurator , Category: -END- Source: Src\HECIDiscovery.cpp : CheckAMT Line: 461: ***** END CheckAMT ******

2013-07-02 11:02:13: Thread:3204(DETAIL) : ACU Configurator , Category: -HECI- Source: Src\HECIWin.cpp : HECIWin::Init Line: 185: Connected to the Intel(R) Management Engine Interface driver, version 8.0.0.1262

2013-07-02 11:02:13: Thread:3204(DETAIL) : ACU Configurator , Category: -Start- Source: Src\HECIDiscovery.cpp : FWUpdateData Line: 40: ***** Start FWUpdateData ******

2013-07-02 11:02:13: Thread:3204(DETAIL) : ACU Configurator , Category: -END- Source: Src\HECIDiscovery.cpp : FWUpdateData Line: 61: ***** END FWUpdateData ******

2013-07-02 11:02:18: Thread:3204(DETAIL) : ACU Configurator , Category: -Start- Source: Src\HECIDiscovery.cpp : PKIDiscovery Line: 790: ***** Start PKIDiscovery ******

2013-07-02 11:02:18: Thread:3204(DETAIL) : ACU Configurator , Category: Hash Handle Source: Src\HECIDiscovery.cpp : GetPKIHashes Line: 873: Hash Handles number:15

2013-07-02 11:02:18: Thread:3204(DETAIL) : ACU Configurator , Category: -END- Source: Src\HECIDiscovery.cpp : PKIDiscovery Line: 837: ***** END PKIDiscovery ******

2013-07-02 11:02:18: Thread:3204(DETAIL) : ACU Configurator , Category: -Start- Source: Src\HECIDiscovery.cpp : GetAmtFQDN Line: 1256: ***** Start GetAmtFQDN ******

2013-07-02 11:02:18: Thread:3204(DETAIL) : ACU Configurator , Category: -END- Source: Src\HECIDiscovery.cpp : GetAmtFQDN Line: 1333: ***** END GetAmtFQDN ******

2013-07-02 11:02:18: Thread:3204(DETAIL) : ACU Configurator , Category: -Start- Source: Src\HECIDiscovery.cpp : ConfServerDiscovery Line: 1021: ***** Start ConfServerDiscovery ******

2013-07-02 11:02:18: Thread:3204(DETAIL) : ACU Configurator , Category: Status message Source: Src\HECIDiscovery.cpp : ConfServerDiscovery Line: 1082: Error message not found- 0x80008cd9. (0x80008cd9)

2013-07-02 11:02:18: Thread:3204(DETAIL) : ACU Configurator , Category: -END- Source: Src\HECIDiscovery.cpp : ConfServerDiscovery Line: 1095: ***** END ConfServerDiscovery ******

2013-07-02 11:02:18: Thread:3204(DETAIL) : ACU Configurator , Category: GetPID Source: Src\HECIDiscovery.cpp : HeciDiscovery Line: 715: AMT Status code - Invalid AMT mode. (0xc000426b) (GetPID)

2013-07-02 11:02:18: Thread:3204(DETAIL) : ACU Configurator , Category: -Start- Source: Src\HECIDiscovery.cpp : ReInitPTHI Line: 1449: ***** Start ReInitPTHI ******

2013-07-02 11:02:23: Thread:3204(DETAIL) : ACU Configurator , Category: -HECI- Source: Src\HECIWin.cpp : HECIWin::Init Line: 185: Connected to the Intel(R) Management Engine Interface driver, version 8.0.0.1262

2013-07-02 11:02:23: Thread:3204(DETAIL) : ACU Configurator , Category: -Start- Source: Src\HECIDiscovery.cpp : LMSDiscovery Line: 1102: ***** Start LMSDiscovery ******

2013-07-02 11:02:24: Thread:3204(INFO) : ACU Configurator , Category: Discovery Source: Src\HostBasedSetup.cpp : HostBasedSetup::Discovery Line: 410: Calling function Discovery...

2013-07-02 11:02:24: Thread:3204(INFO) : ACU Configurator , Category: Local System Account Source: Src\HostBasedSetup.cpp : HostBasedSetup::GetLocalSystemAccount Line: 199: Calling function GetLocalSystemAccount over MEI...

2013-07-02 11:02:24: Thread:3204(DETAIL) : ACU Configurator , Category: -HECI- Source: Src\HECIWin.cpp : HECIWin::Init Line: 185: Connected to the Intel(R) Management Engine Interface driver, version 8.0.0.1262

2013-07-02 11:02:24: Thread:3204(INFO) : ACU Configurator , Category: Local System Account Source: Src\HostBasedSetup.cpp : HostBasedSetup::GetLocalSystemAccount Line: 233: Function GetLocalSystemAccount over MEI ended successfully

2013-07-02 11:02:24: Thread:3204(INFO) : ACU Configurator , Category: Discovery Source: Src\HostBasedSetup.cpp : HostBasedSetup::Discovery Line: 454: Host Based Setup is supported

2013-07-02 11:02:24: Thread:3204(INFO) : ACU Configurator , Category: Discovery Source: Src\HostBasedSetup.cpp : HostBasedSetup::Discovery Line: 484: Current Control Mode: 0 (Not provisioned)

2013-07-02 11:02:24: Thread:3204(INFO) : ACU Configurator , Category: Discovery Source: Src\HostBasedSetup.cpp : HostBasedSetup::Discovery Line: 523: Allowed Control Modes: 2 (Admin) and 1 (Client)

2013-07-02 11:02:24: Thread:3204(INFO) : ACU Configurator , Category: Discovery Source: Src\HostBasedSetup.cpp : HostBasedSetup::Discovery Line: 527: Function Discovery ended successfully

2013-07-02 11:02:24: Thread:3204(DETAIL) : ACU Configurator , Category: -END- Source: Src\HECIDiscovery.cpp : LMSDiscovery Line: 1175: ***** END LMSDiscovery ******

2013-07-02 11:02:24: Thread:3204(DETAIL) : ACU Configurator , Category: -Start- Source: Src\HECIDiscovery.cpp : SecurityDiscovery Line: 1192: ***** Start SecurityDiscovery ******

2013-07-02 11:02:24: Thread:3204(DETAIL) : ACU Configurator , Category: -END- Source: Src\HECIDiscovery.cpp : SecurityDiscovery Line: 1218: ***** END SecurityDiscovery ******

2013-07-02 11:02:24: Thread:3204(DETAIL) : ACU Configurator , Category: -Start- Source: Src\HECIDiscovery.cpp : FeaturesDiscovery Line: 1235: ***** Start FeaturesDiscovery ******

2013-07-02 11:02:24: Thread:3204(DETAIL) : ACU Configurator , Category: -END- Source: Src\HECIDiscovery.cpp : FeaturesDiscovery Line: 1250: ***** END FeaturesDiscovery ******

2013-07-02 11:02:24: Thread:3204(DETAIL) : ACU Configurator , Category: -Start- Source: Src\HECIDiscovery.cpp : UuidDiscovery Line: 1339: ***** Start UuidDiscovery ******

2013-07-02 11:02:24: Thread:3204(DETAIL) : ACU Configurator , Category: -END- Source: Src\HECIDiscovery.cpp : UuidDiscovery Line: 1352: ***** END UuidDiscovery ******

2013-07-02 11:02:24: Thread:3204(DETAIL) : ACU Configurator , Category: -Start- Source: Src\HECIDiscovery.cpp : TcpIpDiscovery Line: 1358: ***** Start TcpIpDiscovery ******

2013-07-02 11:02:24: Thread:3204(DETAI...

0 Kudos
9 Replies
DDunp
Beginner
63 Views

The Output XML file contains the AMTFQDN value, and it populated with the correct value.

Alan_A_Intel
Employee
63 Views

Douglas,

When running ACUConfig with the commands you've listed, the AMT computer would need to already have a record in the RCS server. SystemDiscovery is a way to collect data about the AMT computer and store that data in either an XML file, and or in the systems registry. If your RCS server was setup in database mode, then you can also send this data to the database on the RCS server.

If your AMT system doesn't already have a record on your RCS server, then you can create one with the NotifyRCS command. After a record has been created you can update the AMT systems data with SystemDiscovery.

-Alan

idata
Community Manager
63 Views

Thanks, I'll give it a try.

According to the documentation, the NotifyRCS switch is for adding a configured AMT system to the RCS server in an unmanaged state. The system in question is not configured.

The documentation is a bit confusing on this point - hopefully something they can clarify in later releases.

idata
Community Manager
63 Views

It did not work. The NotifyRCS command failed. "The Intel AMT device is unconfigured. The NotifyRCS operation cannot be performed on unconfigured systems."

Alan_A_Intel
Employee
63 Views

Correct, the NotifyRCS command is for adding already configured AMT systems into RCS. I should have clarified that in my original answer.

So what exactly are you trying to do? Are you trying to configure your AMT system or just gather information on it?

idata
Community Manager
63 Views

I'm trying to gather information for unconfigured devices and send it to the RCS database.

Alan_A_Intel
Employee
63 Views

Douglas,

Is there a particular reason why you're trying to gather information from unconfigured systems rather than just configuring them?

DDunp
Beginner
63 Views

I'm testing the capabilities of the platform to see how much functionality actually works. I don't want to commit a production resource for a product that isn't going to work as documented.

DDunp
Beginner
63 Views

I heard back from our Intel contact - you can't run SystemDiscovery to capture data to the RCS database when the system is unconfigured. You can only run SystemDiscovery and capture the data locally.

Reply