SCCM MBEx no provisioning Status - need MEBx configurationsettings

idata · ‎10-07-2011

Hi,

we have made all the things which are mentioned in the document "Configuration Guide for Intel® vPro™ Technology with Microsoft* ConfigMgr SP2".

Our vpro Testclient (AMT Version 7) is detected in SCCM and the Version is shown. But we dont have a provisioning status in SCCM.

What configurations must be done in the MEBx Bios ? We only changed the first password while we login and insert our RootCA Thumbprint in the Hashestable. Are there any other configurations we must do for a Enterprise PKI Provisioning Mode?

another thing is that we insert the changed adminaccount password in the general register of the Outof Band Management configurations in SCCM. Is this correct? The changed pasword is although inserted in the provisioningconfigurations register. Is this correct? Our SCCM Enviroment is as mixed mode installed. In the amtopmgr.log we get the entry that the helo message failed to process. What we do wrong?

Bruno_Domignues · ‎10-10-2011

Hi,

What you made is correct!

SCCM reject hello packages since it's based on agent not on bare-metal, that is the reason you can see in amtopmgr.log these line of rejecting.

In order to see the status in SCCM console, there is a column that show this status, probably in not selected to show and you can do it in View pane.

If you can, clean information about your environment and send the piece of log that show the attempt to provision or at list the connection to vPro machine in order that I can provide you an insight about it.

Best Regards!

--Bruno Domingues

idata · ‎10-11-2011

Hi,

thanks for your answer. The entries from the amtlog are the following:

AMT Discovery Worker: Wakes up to process instruction files SMS_AMT_OPERATION_MANAGER 11.10.2011 09:17:43 3224 (0x0C98)

AMT Discovery Worker: Wait 3600 seconds... SMS_AMT_OPERATION_MANAGER 11.10.2011 09:17:43 3224 (0x0C98)

AMT Discovery Worker: Wakes up to process instruction files SMS_AMT_OPERATION_MANAGER 11.10.2011 09:17:43 3224 (0x0C98)

AMT Discovery Worker: Reading Discovery Instruction D:\SMS\inboxes\amtopmgr.box\disc\{53EB940C-C4C7-46B9-85F4-F5807906B512}.RDC... SMS_AMT_OPERATION_MANAGER 11.10.2011 09:17:43 3224 (0x0C98)

AMT Discovery Worker: Execute query exec AMT_GetThisSitesNetBiosNames 'VFM0033D', NULL, 'VFM' SMS_AMT_OPERATION_MANAGER 11.10.2011 09:17:43 3224 (0x0C98)

AMT Discovery Worker: Execute query exec AMT_GetAMTMachineProperties 313 SMS_AMT_OPERATION_MANAGER 11.10.2011 09:17:43 3224 (0x0C98)

AMT Discovery Worker: CSMSAMTDiscoveryWorker::RetrieveInfoFromCollection: Found machine client0001 - 192.168.203.126 from Collection VFM0033D. SMS_AMT_OPERATION_MANAGER 11.10.2011 09:17:43 3224 (0x0C98)

AMT Discovery Worker: Execute query exec AMT_GetProvAccounts SMS_AMT_OPERATION_MANAGER 11.10.2011 09:17:43 3224 (0x0C98)

AMT Discovery Worker: Finish reading discovery instruction D:\SMS\inboxes\amtopmgr.box\disc\{53EB940C-C4C7-46B9-85F4-F5807906B512}.RDC SMS_AMT_OPERATION_MANAGER 11.10.2011 09:17:43 3224 (0x0C98)

AMT Discovery Worker: Parsed 1 instruction files SMS_AMT_OPERATION_MANAGER 11.10.2011 09:17:43 3224 (0x0C98)

AMT Discovery Worker: There are 1 tasks in pending list SMS_AMT_OPERATION_MANAGER 11.10.2011 09:17:43 3224 (0x0C98)

AMT Discovery Worker: Send task to completion port SMS_AMT_OPERATION_MANAGER 11.10.2011 09:17:43 3224 (0x0C98)

Auto-worker Thread Pool: Current size of the thread pool is 1 SMS_AMT_OPERATION_MANAGER 11.10.2011 09:17:43 3224 (0x0C98)

AMT Discovery Worker: 1 task(s) are sent to the task pool successfully. SMS_AMT_OPERATION_MANAGER 11.10.2011 09:17:43 3224 (0x0C98)

STATMSG: ID=7203 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_AMT_OPERATION_MANAGER" SYS=provserver SITE=VFM PID=1952 TID=3224 GMTDATE=Tue Oct 11 07:17:43.717 2011 ISTR0="1" ISTR1="0" ISTR2="0" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_AMT_OPERATION_MANAGER 11.10.2011 09:17:43 3224 (0x0C98)

Auto-worker Thread Pool: Work thread 2728 started SMS_AMT_OPERATION_MANAGER 11.10.2011 09:17:43 2728 (0x0AA8)

AMT Discovery Worker: Wait 20 seconds... SMS_AMT_OPERATION_MANAGER 11.10.2011 09:17:43 3224 (0x0C98)

AMT Discovery Worker: Wakes up to process instruction files SMS_AMT_OPERATION_MANAGER 11.10.2011 09:17:43 3224 (0x0C98)

AMT Discovery Worker: Wait 20 seconds... SMS_AMT_OPERATION_MANAGER 11.10.2011 09:17:43 3224 (0x0C98)

Error 0x80090325 returned by InitializeSecurityContext during follow up TLS handshaking with server. SMS_AMT_OPERATION_MANAGER 11.10.2011 09:17:43 2728 (0x0AA8)

**** Error 0x1ebb968 returned by ApplyControlToken SMS_AMT_OPERATION_MANAGER 11.10.2011 09:17:43 2728 (0x0AA8)

Error 0x80090325 returned by InitializeSecurityContext during follow up TLS handshaking with server. SMS_AMT_OPERATION_MANAGER 11.10.2011 09:17:43 2728 (0x0AA8)

**** Error 0x1ebb968 returned by ApplyControlToken SMS_AMT_OPERATION_MANAGER 11.10.2011 09:17:43 2728 (0x0AA8)

Error 0x80090325 returned by InitializeSecurityContext during follow up TLS handshaking with server. SMS_AMT_OPERATION_MANAGER 11.10.2011 09:17:44 2728 (0x0AA8)

**** Error 0x1ebb968 returned by ApplyControlToken SMS_AMT_OPERATION_MANAGER 11.10.2011 09:17:44 2728 (0x0AA8)

session params : https://client0001.int:16993 https://client0001.int:16993 , 11001 SMS_AMT_OPERATION_MANAGER 11.10.2011 09:17:44 2728 (0x0AA8)

ERROR: Invoke(get) failed: 80020009argNum = 0 SMS_AMT_OPERATION_MANAGER 11.10.2011 09:17:44 2728 (0x0AA8)