Quantcast
Channel: Intel Communities : Discussion List - Intel® vPro™ Platform
Viewing all articles
Browse latest Browse all 632

Error Intel vPRO with SCCM 2012 R2 - OOB AMT

$
0
0

I am running SCCM 2012 R2 to make the provisioning of vPRO, but I'm encountering some difficulties.

 

 

At first when efetued the configuration of Intel SCS 9, unable to login normally efetued some tests shutdown and power on and functioned normally. The next day when I got to the office, was no longer running the web interface, I'm not getting login. No changes were made in the environment during this period. When I try to make the AMT discovery in SCCM, it generates me the error "Failed to establish tcp session" and gives me the IP and the host port 16993. If I place the PSK or PKI configuration within the MEBx, it generates a user and password error saying it can not authenticate with the Admin user.

 

 

Already redid the procedure following the Intel and Microsoft manual, but the error persists. SCCM can identify the version of vPRO, but the status it says "Can not Stand", regardless of the version ... 4.x, 5.x and 6.x, it displays the same message every time.

 

 

This is the log of the error when I'm not using PSK setting in the MEBx that is generated in the AMT discovery of SCCM

 

 

 

================================================================

 

 

AMT Discovery Worker: Wait 9 seconds... SMS_AMT_OPERATION_MANAGER 05/12/2014 14:49:47 2984 (0x0BA8)

Discover INFRANOTE using IP address 10.234.9.13 SMS_AMT_OPERATION_MANAGER 05/12/2014 14:49:46 4492 (0x118C)

CAMTDiscoveryWSMan::DoConnectToAMTDevice: Failed to establish tcp session to 10.234.9.13:16993. SMS_AMT_OPERATION_MANAGER 05/12/2014 14:49:48 4492 (0x118C)

DoPingDiscoveryForAMTDevice succeeded. SMS_AMT_OPERATION_MANAGER 05/12/2014 14:49:48 4492 (0x118C)

Discovery to IP address 10.234.9.13 succeed. AMT status is 0. SMS_AMT_OPERATION_MANAGER 05/12/2014 14:49:48 4492 (0x118C)

CSMSAMTDiscoveryTask::Execute, discovery to INFRANOTE succeed. AMT status is 0. SMS_AMT_OPERATION_MANAGER 05/12/2014 14:49:48 4492 (0x118C)

 

 

================================================================

 

And this is the log generated when using PSK / PKI configuration in MEBx:

 

================================================================

DoPingDiscoveryForAMTDevice succeeded.SMS_AMT_OPERATION_MANAGER08/12/2014 17:01:255336 (0x14D8)
Error 0x80090304 returned by InitializeSecurityContext during follow up TLS handshaking with server.SMS_AMT_OPERATION_MANAGER08/12/2014 17:01:255336 (0x14D8)
**** Error 0x1d38b100 returned by ApplyControlTokenSMS_AMT_OPERATION_MANAGER08/12/2014 17:01:255336 (0x14D8)
DoSoapDiscovery failed with user name: admin.SMS_AMT_OPERATION_MANAGER08/12/2014 17:01:265336 (0x14D8)
Error 0x80090304 returned by InitializeSecurityContext during follow up TLS handshaking with server.SMS_AMT_OPERATION_MANAGER08/12/2014 17:01:265336 (0x14D8)
**** Error 0x1d38b100 returned by ApplyControlTokenSMS_AMT_OPERATION_MANAGER08/12/2014 17:01:265336 (0x14D8)
DoSoapDiscovery failed with user name: admin.SMS_AMT_OPERATION_MANAGER08/12/2014 17:01:265336 (0x14D8)
Flag iWSManFlagSkipRevocationCheck is not set.SMS_AMT_OPERATION_MANAGER08/12/2014 17:01:265336 (0x14D8)
session params : https://FQDN COMPUTER:16993   ,  11001SMS_AMT_OPERATION_MANAGER08/12/2014 17:01:265336 (0x14D8)
ERROR: Invoke(get) failed: 80020009argNum = 0SMS_AMT_OPERATION_MANAGER08/12/2014 17:01:265336 (0x14D8)
Description: A security error occurredSMS_AMT_OPERATION_MANAGER08/12/2014 17:01:265336 (0x14D8)
Error: Failed to get AMT_SetupAndConfigurationService instance.SMS_AMT_OPERATION_MANAGER08/12/2014 17:01:265336 (0x14D8)
DoWSManDiscovery failed with user name: admin.SMS_AMT_OPERATION_MANAGER08/12/2014 17:01:265336 (0x14D8)
Flag iWSManFlagSkipRevocationCheck is not set.SMS_AMT_OPERATION_MANAGER08/12/2014 17:01:265336 (0x14D8)
session params : https://FQDN COMPUTER:16993   ,  11001SMS_AMT_OPERATION_MANAGER08/12/2014 17:01:265336 (0x14D8)
ERROR: Invoke(get) failed: 80020009argNum = 0SMS_AMT_OPERATION_MANAGER08/12/2014 17:01:265336 (0x14D8)
Description: A security error occurredSMS_AMT_OPERATION_MANAGER08/12/2014 17:01:265336 (0x14D8)
Error: Failed to get AMT_SetupAndConfigurationService instance.SMS_AMT_OPERATION_MANAGER08/12/2014 17:01:265336 (0x14D8)
DoWSManDiscovery failed with user name: admin.SMS_AMT_OPERATION_MANAGER08/12/2014 17:01:265336 (0x14D8)
Start Kerberos DiscoverySMS_AMT_OPERATION_MANAGER08/12/2014 17:01:265336 (0x14D8)
Flag iWSManFlagSkipRevocationCheck is not set.SMS_AMT_OPERATION_MANAGER08/12/2014 17:01:265336 (0x14D8)
session params : https://FQDN COMPUTER:16993   ,  484001SMS_AMT_OPERATION_MANAGER08/12/2014 17:01:265336 (0x14D8)
ERROR: Invoke(get) failed: 80020009argNum = 0SMS_AMT_OPERATION_MANAGER08/12/2014 17:01:265336 (0x14D8)
Description: A security error occurredSMS_AMT_OPERATION_MANAGER08/12/2014 17:01:265336 (0x14D8)
Error: Failed to get AMT_SetupAndConfigurationService instance.SMS_AMT_OPERATION_MANAGER08/12/2014 17:01:265336 (0x14D8)
DoKerberosWSManDiscovery failed.SMS_AMT_OPERATION_MANAGER08/12/2014 17:01:265336 (0x14D8)
Flag iWSManFlagSkipRevocationCheck is not set.SMS_AMT_OPERATION_MANAGER08/12/2014 17:01:265336 (0x14D8)
session params : https://10.234.10.84:16993   ,  15001SMS_AMT_OPERATION_MANAGER08/12/2014 17:01:265336 (0x14D8)
ERROR: Invoke(get) failed: 80020009argNum = 0SMS_AMT_OPERATION_MANAGER08/12/2014 17:01:265336 (0x14D8)
Description: A security error occurredSMS_AMT_OPERATION_MANAGER08/12/2014 17:01:265336 (0x14D8)
Error: Failed to get AMT_SetupAndConfigurationService instance.SMS_AMT_OPERATION_MANAGER08/12/2014 17:01:265336 (0x14D8)
DoWSManDiscovery failed with user name: admin.SMS_AMT_OPERATION_MANAGER08/12/2014 17:01:265336 (0x14D8)
Flag iWSManFlagSkipRevocationCheck is not set.SMS_AMT_OPERATION_MANAGER08/12/2014 17:01:265336 (0x14D8)
session params : https://10.234.10.84:16993   ,  15001SMS_AMT_OPERATION_MANAGER08/12/2014 17:01:265336 (0x14D8)
ERROR: Invoke(get) failed: 80020009argNum = 0SMS_AMT_OPERATION_MANAGER08/12/2014 17:01:265336 (0x14D8)
Description: A security error occurredSMS_AMT_OPERATION_MANAGER08/12/2014 17:01:265336 (0x14D8)
Error: Failed to get AMT_SetupAndConfigurationService instance.SMS_AMT_OPERATION_MANAGER08/12/2014 17:01:265336 (0x14D8)
DoWSManDiscovery failed with user name: admin.SMS_AMT_OPERATION_MANAGER08/12/2014 17:01:265336 (0x14D8)
Discovery to IP address 10.234.10.84 succeed. AMT status is 1.SMS_AMT_OPERATION_MANAGER08/12/2014 17:01:265336 (0x14D8)
CSMSAMTDiscoveryTask::Execute, discovery to "COMPUTER NAME succeed. AMT status is 1.SMS_AMT_OPERATION_MANAGER08/12/2014 17:01:265336 (0x14D8)
CSMSAMTDiscoveryTask::Execute - DDR written to C:\Program Files\Microsoft Configuration Manager\inboxes\auth\ddm.boxSMS_AMT_OPERATION_MANAGER08/12/2014 17:01:265336 (0x14D8)
CStateMsgReporter::DeliverMessages - Queued message: TT=1201 TIDT=0 TID='Unspecified' SID=10 MUF=0 PCNT=1, P1='FQDN' P2='' P3='' P4='' P5=''SMS_AMT_OPERATION_MANAGER08/12/2014 17:01:275336 (0x14D8)
CStateMsgReporter::DeliverMessages - Created state message file: C:\Program Files\Microsoft Configuration Manager\inboxes\auth\statesys.box\incoming\w73tgg1d.SMXSMS_AMT_OPERATION_MANAGER08/12/2014 17:01:275336 (0x14D8)
General Worker Thread Pool: Succeed to run the task "FQDN". Remove it from task list.SMS_AMT_OPERATION_MANAGER08/12/2014 17:01:275336 (0x14D8)
General Worker Thread Pool: Work thread 5336 has been requested to shut down.SMS_AMT_OPERATION_MANAGER08/12/2014 17:01:275336 (0x14D8)
General Worker Thread Pool: Work thread 5336 exiting.SMS_AMT_OPERATION_MANAGER08/12/2014 17:01:275336 (0x14D8)
General Worker Thread Pool: Current size of the thread pool is 0SMS_AMT_OPERATION_MANAGER08/12/2014 17:01:273696 (0x0E70)
AMT Discovery Worker: Wakes up to process instruction filesSMS_AMT_OPERATION_MANAGER08/12/2014 17:01:453728 (0x0E90)
AMT Discovery Worker: Wait 3600 seconds...SMS_AMT_OPERATION_MANAGER08/12/2014 17:01:453728 (0x0E90)

 

 

 

 

 

 

 

Could anyone help?

 

 

Thank you.


Viewing all articles
Browse latest Browse all 632

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>