3 Replies Latest reply on Sep 10, 2008 11:57 PM by billc

    Provisioning

    billc

       

      I met 1 issue on provision account during SCCM SP1 provision with vPro machine. Below is log data from AMTOPMGR.LOG. It indicate that SCCM use "provisioning account" to connect target machine. What is it meaning? ME admin or SCCM account? Does anyone what happen?

       

      The provision mode for device 192.168.10.35 is 1. $$<SMS_AMT_OPERATION_MANAGER><星期三 九月 03 16:10:07.220 2008 中国标准时间><thread=4488 (0x1188)>

      Attempting to establish connection with target device using SOAP. $$<SMS_AMT_OPERATION_MANAGER><星期三 九月 03 16:10:07.220 2008 中国标准时间><thread=4488 (0x1188)>

      Set credential on provisionHelper... $$<SMS_AMT_OPERATION_MANAGER><星期三 九月 03 16:10:07.220 2008 中国标准时间><thread=4488 (0x1188)>

      Try to use provisioning account to connect target machine 192.168.10.35... $$<SMS_AMT_OPERATION_MANAGER><星期三 九月 03 16:10:07.220 2008 中国标准时间><thread=4488 (0x1188)> Try to use provisioning account to connect target machine 192.168.10.35... $$<SMS_AMT_OPERATION_MANAGER><星期三 九月 03 16:10:07.220 2008 中国标准时间><thread=4488 (0x1188)> Error 0x80090304 returned by InitializeSecurityContext during follow up TLS handshaking with server.~ $$<SMS_AMT_OPERATION_MANAGER><星期三 九月 03 16:10:07.252 2008 中国标准时间><thread=4488 (0x1188)>

       

                             

      1. Error 0x92bb95c returned by ApplyControlToken~ $$<SMS_AMT_OPERATION_MANAGER><星期三 九月 03 16:10:07.252 2008 中国标准时间><thread=4488 (0x1188)>

       

      Fail to connect and get core version of machine 192.168.10.35 using provisioning account #0. $$<SMS_AMT_OPERATION_MANAGER><星期三 九月 03 16:10:07.252 2008 中国标准时间><thread=4488 (0x1188)>

       

       

       

       

       

      Thanks!

       

       

      Bill

       

       

        • 1. Re: Provisioning
          miroyer

           

          Bill,

           

           

          What make, model, and firmware version are you trying to provision? It is hard for me to assess the situation since I'm not seeing all the error codes in your post.  Have you referenced the following thread to see if this is your issue? Is the AMT status coming back as detected?

           

           

          http://communities.intel.com/openport/blogs/microsoft-vpro/2008/08/19/intel-amt-321-selfsigned-certificate-issue-and-working-around-it-for-microsoft-system-configuration-manager-sp1

           

           

          --Matt Royer

           

           

          • 2. Re: Provisioning
            billc

            System: HP vPro 7800

             

            Provision Model: enterprise/PKI

             

             

             

            MEBx version: AMT 3.2.1

             

             

             

            SCCM verison: Chinese edition SCCM SP1 build 6221 with hotfix KB956337 and KB955355

             

             

            AMT status: detected

             

             

             

            Error message:

             

             

             

            AMT Provision Worker: 1 task(s) are sent to the task pool successfully.~  $$<SMS_AMT_OPERATION_MANAGER><星期三 九月 03 16:11:19.650 2008 中国标准时间>

            Provision target is indicated with SMS resource id. (MachineId = 6502 192.168.10.35)  $$<SMS_AMT_OPERATION_MANAGER><星期三 九月 03 16:11:19.650 2008 中国

            Incoming Connection from 192.168.10.35:16994.  $$<SMS_AMT_OPERATION_MANAGER><星期三 九月 03 16:11:27.049 2008 中国标准时间><thread=3420 (0xD5C)>

            Incoming data is - Configuration version: PKI Configuration.  $$<SMS_AMT_OPERATION_MANAGER><星期三 九月 03 16:11:27.049 2008 中国标准时间><thread=3420 (0xD5C)>

            Count  : 2  $$<SMS_AMT_OPERATION_MANAGER><星期三 九月 03 16:11:27.049 2008 中国标准时间><thread=3420 (0xD5C)>

            UUID   : 81344A80-8FC5-11DD-871C-D0BA2CC213D8  $$<SMS_AMT_OPERATION_MANAGER><星期三 九月 03 16:11:27.049 2008 中国标准时间><thread=3420

            Found matched hash from hello message with current provision certificate. (Hash: BA8D299AB27F1B32FCE24A16BD09E4FC5F21495F)  $$<SMS_AMT_OPERATION_MANAGER><星期三 九月 03 16:11:27.065 2008 中国标准时间><thread=3420 (0xD5C)>

            AMT Provision Worker: Wakes up to process instruction files  $$<SMS_AMT_OPERATION_MANAGER><星期三 九月 03 16:11:40.373 2008 中国标准时间>

             

             

             

            Found valid basic machine property for machine id = 6502.  $$<SMS_AMT_OPERATION_MANAGER><星期三 九月 03 16:11:48.548 2008 中国标准时间><thread=1556 Generate bare metal provision task for AMT device 81344A80-8FC5-11DD-871C-D0BA2CC213D8.  $$<SMS_AMT_OPERATION_MANAGER><星期三 九月 03

            Incoming instruction file d:\Program Files\Microsoft Configuration Manager\inboxes\amtopmgr.box\prov\{9C9D474B-82B4-4292-BD64-D7438A287EF3}.PRV to Provision Found one 'Bare-Metal Provision' task with type 'Machine Resource' and target ID '6502' and IP address '3232238115'.  $$<SMS_AMT_OPERATION_MANAGER><星期三

            The provision mode for device 192.168.10.35 is 1.  $$<SMS_AMT_OPERATION_MANAGER><星期三 九月 03 16:11:48.580 2008 中国标准时间><thread=1556 (0x614)>

            Target machine 6502 is a AMT capable machine.  $$<SMS_AMT_OPERATION_MANAGER><星期三 九月 03 16:11:48.580 2008 中国标准时间><thread=3448 (0xD78)>

            Attempting to establish connection with target device using SOAP.  $$<SMS_AMT_OPERATION_MANAGER><星期三 九月 03 16:11:48.580 2008 中国标准时间>Warning: Found matched certificate hash in current memory of provisioning certificate  $$<SMS_AMT_OPERATION_MANAGER><星期三 九月 03 16:11:48.580 2008 中国标准时AMT Provision Worker: Parsed 1 instruction files  $$<SMS_AMT_OPERATION_MANAGER><星期三 九月 03 16:11:48.597 2008 中国标准时间><thread=3448 (0xD78)>

            Create provisionHelper with (Hash: A8941BE1083FA4B31E9A99D2505875B72F7C7155)  $$<SMS_AMT_OPERATION_MANAGER><星期三 九月 03 16:11:48.597 2008

            AMT Provision Worker: There are 1 tasks in pending list  $$<SMS_AMT_OPERATION_MANAGER><星期三 九月 03 16:11:48.597 2008 中国标准时间><thread=3448

             

             

             

            Set credential on provisionHelper...  $$<SMS_AMT_OPERATION_MANAGER><星期三 九月 03 16:11:48.597 2008 中国标准时间><thread=1556 (0x614)>

            Try to use provisioning account to connect target machine 192.168.10.35...  $$<SMS_AMT_OPERATION_MANAGER><星期三 九月 03 16:11:48.597 2008 中国标准时间>

            Error 0x80090304 returned by InitializeSecurityContext during follow up TLS handshaking with server.~  $$<SMS_AMT_OPERATION_MANAGER><星期三 九月 03 **** Error 0x7b6b95c returned by ApplyControlToken~  $$<SMS_AMT_OPERATION_MANAGER><星期三 九月 03 16:11:48.629 2008 中国标准时间><thread=1556 (0x614)>

            Fail to connect and get core version of machine 192.168.10.35 using provisioning account #0.  $$<SMS_AMT_OPERATION_MANAGER><星期三 九月 03 16:11:48.645

            Try to use default factory account with MEBX password to connect target machine 192.168.10.35...  $$<SMS_AMT_OPERATION_MANAGER><星期三 九月 03

             

             

             

            Error 0x80090304 returned by InitializeSecurityContext during follow up TLS handshaking with server.~  $$<SMS_AMT_OPERATION_MANAGER><星期三 九月 03 **** *****Error 0x7b6b95c returned by ApplyControlToken~  $$<SMS_AMT_OPERATION_MANAGER><星期三 九月 03 16:11:48.661 2008 中国标准时间><thread=1556

             

             

             

            Fail to connect and get core version of machine 192.168.10.35 using default factory account with MEBX password.  $$<SMS_AMT_OPERATION_MANAGER><星期三 九

            Try to use default factory account to connect target machine 192.168.10.35...  $$<SMS_AMT_OPERATION_MANAGER><星期三 九月 03 16:11:48.678 2008 中国标准时Error 0x80090304 returned by InitializeSecurityContext during follow up TLS handshaking with server.~  $$<SMS_AMT_OPERATION_MANAGER><星期三 九月 03 **** Error 0x7b6b95c returned by ApplyControlToken~  $$<SMS_AMT_OPERATION_MANAGER><星期三 九月 03 16:11:48.694 2008 中国标准时间><thread=1556 (0x614)>

            Fail to connect and get core version of machine 192.168.10.35 using default factory account.  $$<SMS_AMT_OPERATION_MANAGER><星期三 九月 03 16:11:48.694

            Try to use provisioned account (random generated password) to connect target machine 192.168.10.35...  $$<SMS_AMT_OPERATION_MANAGER><星期三 九月 03 Error 0x80090304 returned by InitializeSecurityContext during follow up TLS handshaking with server.~  $$<SMS_AMT_OPERATION_MANAGER><星期三 九月 03

             

             

             

            *****Error 0x7b6b95c returned by ApplyControlToken~  $$<SMS_AMT_OPERATION_MANAGER><星期三 九月 03 16:11:48.726 2008 中国标准时间><thread=1556

            Fail to connect and get core version of machine 192.168.10.35 using provisioned account (random generated password).  $$<SMS_AMT_OPERATION_MANAGER><星Error: Device internal error. Check Schannel, provision certificate, network configuration, device. (MachineId = 6502)  $$<SMS_AMT_OPERATION_MANAGER><星期三 九Error: Can NOT establish connection with target device. (MachineId = 6502)  $$<SMS_AMT_OPERATION_MANAGER><星期三 九月 03 16:11:48.742 2008 中国标准时间>

            • 3. Re: Provisioning
              billc

              The problem was solved. We forget open DNS scope 006 and 015 DNS Domain name ports.

               

              Bill