1 Reply Latest reply on Jun 21, 2009 10:48 PM by huzairi

    Trouble provisioning vPro machines

    huzairi

      I am having trouble provisioning vPro machines, on my SCCM on all system column for AMT Status states as "Detected" after done the Alll system > Out of Band Management > Discover Management Controllers, none of the vpro's are discovered for provisioning, below is the error log from amtopmgr.log. Could someone please help me solving this matter.

       

      session params : http://vPro-1.systemcenter.org:16992   ,  111001            SMS_AMT_OPERATION_MANAGER       6/19/2009 4:11:54 PM          3768 (0x0EB8)

      Error 0x80090304 returned by InitializeSecurityContext during follow up TLS handshaking with server.                SMS_AMT_OPERATION_MANAGER       6/19/2009 4:11:54 PM    5156 (0x1424)

      **** Error 0x7efb970 returned by ApplyControlToken   SMS_AMT_OPERATION_MANAGER       6/19/2009 4:11:54 PM    5156 (0x1424)

       

       

      Here is another part of the log:

       

       

      Incoming Connection from 172.16.3.127:16994. SMS_AMT_OPERATION_MANAGER 6/19/2009 4:15:08 PM 2728 (0x0AA8)
      Incoming data is - Configuration version: PKI Configuration. SMS_AMT_OPERATION_MANAGER 6/19/2009 4:15:08 PM 2728 (0x0AA8)
      Count  : 12 SMS_AMT_OPERATION_MANAGER 6/19/2009 4:15:08 PM 2728 (0x0AA8)
      UUID   : 4C4C4544-0034-3210-804C-B4C04F593153 SMS_AMT_OPERATION_MANAGER 6/19/2009 4:15:08 PM 2728 (0x0AA8)
      Found matched hash from hello message with current provision certificate. (Hash: 6B15F75250275596BE3188A0969FA91942B8FEF5) SMS_AMT_OPERATION_MANAGER 6/19/2009 4:15:08 PM 2728 (0x0AA8)
      Error: AMT device 4C4C4544-0034-3210-804C-B4C04F593153 has not been imported to sms. Can not finish provisioning. SMS_AMT_OPERATION_MANAGER 6/19/2009 4:15:08 PM 2728 (0x0AA8)
      Waiting for incoming hello message from AMT devices... SMS_AMT_OPERATION_MANAGER 6/19/2009 4:15:08 PM 2728 (0x0AA8)

       

       

        • 1. Re: Trouble provisioning vPro machines
          huzairi

          I manage to have this issue resolved, what I did was on the detected machine I pushed the client onto them, and manually initiate the Machine Policy Retrieveal & Evaluation Cycle. Update collection membership, refresh and after a few minute those machine status became provisioned.