3 Replies Latest reply on Feb 28, 2011 10:13 AM by jjcopela

    Intel vPro stage 1 not finished fully

    jhans

      Hi

      We try to provision some pc's. The log indicates a problem at the end  of stage 1. Does anyone have an idea what the cause can be?

       

      Environment:

      SCCM SP2

      Windows Server 2008

      Client Web Server Certificate requested and enrolled (CA Server)

      Active Directory object created

      Provision record displayed in AMT Bios on client

       

      Thanks in advance

      Joachim

       

      >>>>>>>>>>>>>>>Provision  task  begin<<<<<<<<<<<<<<<     SMS_AMT_OPERATION_MANAGER    11.02.2011 12:04:42    3928 (0x0F58)
      Provision target is indicated with SMS resource id. (MachineId = 325  PCName.xyz.xyz.to)    SMS_AMT_OPERATION_MANAGER    11.02.2011  12:04:42    3928 (0x0F58)
      Found valid basic machine property for machine id = 325.     SMS_AMT_OPERATION_MANAGER    11.02.2011 12:04:42    3928 (0x0F58)
      Warning: Currently we don't support mutual auth. Change to TLS server  auth mode.    SMS_AMT_OPERATION_MANAGER    11.02.2011 12:04:42    3928  (0x0F58)
      The provision mode for device PCName.xyz.xyz.to is 1.     SMS_AMT_OPERATION_MANAGER    11.02.2011 12:04:42    3928 (0x0F58)
      Check target machine (version 5.2.10) is a SCCM support version.  (TRUE)    SMS_AMT_OPERATION_MANAGER    11.02.2011 12:04:42    3928  (0x0F58)
      The IP addresses of the host PCName.xyz.xyz.to are 140.100.4.22.     SMS_AMT_OPERATION_MANAGER    11.02.2011 12:04:42    3928 (0x0F58)
      Attempting to establish connection with target device using SOAP.     SMS_AMT_OPERATION_MANAGER    11.02.2011 12:04:42    3928 (0x0F58)
      Found matched certificate hash in current memory of provisioning  certificate    SMS_AMT_OPERATION_MANAGER    11.02.2011 12:04:42    3928  (0x0F58)
      Create provisionHelper with (Hash:  56854C463AB15163FC2DFE025641D2D5111F83AB)     SMS_AMT_OPERATION_MANAGER    11.02.2011 12:04:42    3928 (0x0F58)
      Set credential on provisionHelper...    SMS_AMT_OPERATION_MANAGER     11.02.2011 12:04:42    3928 (0x0F58)
      Try to use provisioning account to connect target machine  PCName.xyz.xyz.to...    SMS_AMT_OPERATION_MANAGER    11.02.2011  12:04:42    3928 (0x0F58)
      HTTP digest authentication failed with status = 401.     SMS_AMT_OPERATION_MANAGER    11.02.2011 12:04:46    3928 (0x0F58)
      Fail to connect and get core version of machine PCName.xyz.xyz.to using  provisioning account #0.    SMS_AMT_OPERATION_MANAGER    11.02.2011  12:04:46    3928 (0x0F58)
      Try to use default factory account with MEBX password to connect target  machine PCName.xyz.xyz.to...    SMS_AMT_OPERATION_MANAGER    11.02.2011  12:04:46    3928 (0x0F58)
      Fail to connect and get core version of machine PCName.xyz.xyz.to using  default factory account with MEBX password.     SMS_AMT_OPERATION_MANAGER    11.02.2011 12:04:46    3928 (0x0F58)
      Try to use default factory account to connect target machine  PCName.xyz.xyz.to...    SMS_AMT_OPERATION_MANAGER    11.02.2011  12:04:46    3928 (0x0F58)
      Succeed to connect target machine PCName.xyz.xyz.to and core version  with 5.2.10 using default factory account.     SMS_AMT_OPERATION_MANAGER    11.02.2011 12:04:50    3928 (0x0F58)
      GeneralInfo.GetProvisioningState finished with HResult = 0x0, status =  0x0, clientError = 0.    SMS_AMT_OPERATION_MANAGER    11.02.2011  12:04:53    3928 (0x0F58)
      Get device provisioning state is In Provisioning     SMS_AMT_OPERATION_MANAGER    11.02.2011 12:04:53    3928 (0x0F58)
      Passed OTP check on AMT device PCName.xyz.xyz.to.     SMS_AMT_OPERATION_MANAGER    11.02.2011 12:04:57    3928 (0x0F58)
      Machine PCName.xyz.xyz.to will be added and published to AD and OU is  LDAP://OU=OOBM Clients,DC=xyz,DC=xyz,DC=to.     SMS_AMT_OPERATION_MANAGER    11.02.2011 12:04:57    3928 (0x0F58)
      Send request to AMT proxy component to add machine PCName.xyz.xyz.to to  AD.    SMS_AMT_OPERATION_MANAGER    11.02.2011 12:04:57    3928 (0x0F58)
      Successfully created instruction file for AMT proxy task: C:\Program  Files (x86)\Microsoft Configuration Manager\inboxes\amtproxymgr.box     SMS_AMT_OPERATION_MANAGER    11.02.2011 12:04:57    3928 (0x0F58)
      Processing provision on AMT device PCName.xyz.xyz.to...     SMS_AMT_OPERATION_MANAGER    11.02.2011 12:04:57    3928 (0x0F58)
      Found client certificate already being generated for AMT device  PCName.xyz.xyz.to.    SMS_AMT_OPERATION_MANAGER    11.02.2011  12:04:57    3928 (0x0F58)
      Start 1st stage provision on AMT device PCName.xyz.xyz.to. (SOAP)     SMS_AMT_OPERATION_MANAGER    11.02.2011 12:04:57    3928 (0x0F58)
      SecurityAdministration.ClearTLSCredentials finished with HResult = 0x0,  status = 0x0, clientError = 0.    SMS_AMT_OPERATION_MANAGER     11.02.2011 12:05:00    3928 (0x0F58)
      AMT Provision Worker: Wakes up to process instruction files     SMS_AMT_OPERATION_MANAGER    11.02.2011 12:05:02    4128 (0x1020)
      AMT Provision Worker: Wait 20 seconds...    SMS_AMT_OPERATION_MANAGER     11.02.2011 12:05:02    4128 (0x1020)
      Auto-worker Thread Pool: Current size of the thread pool is 1     SMS_AMT_OPERATION_MANAGER    11.02.2011 12:05:02    340 (0x0154)
      NetworkTime.GetLowAccuracyTimeSynch finished with HResult = 0x0, status =  0x0, clientError = 0.    SMS_AMT_OPERATION_MANAGER    11.02.2011  12:05:04    3928 (0x0F58)
      NetworkTime.SetHighAccuracyTimeSynch finished with HResult = 0x0, status  = 0x0, clientError = 0.    SMS_AMT_OPERATION_MANAGER    11.02.2011  12:05:06    3928 (0x0F58)
      NetworkAdmin.SetHostName finished with HResult = 0x0, status = 0x0,  clientError = 0.    SMS_AMT_OPERATION_MANAGER    11.02.2011 12:05:09     3928 (0x0F58)
      NetworkAdmin.SetDomainName finished with HResult = 0x0, status = 0x0.     SMS_AMT_OPERATION_MANAGER    11.02.2011 12:05:12    3928 (0x0F58)
      AMT Provision Worker: Wakes up to process instruction files     SMS_AMT_OPERATION_MANAGER    11.02.2011 12:05:22    4128 (0x1020)
      AMT Provision Worker: Wait 20 seconds...    SMS_AMT_OPERATION_MANAGER     11.02.2011 12:05:22    4128 (0x1020)
      SecurityAdministration.SetTLSCertificateWithKeyPair finished with  HResult = 0x0, status = 0x0.    SMS_AMT_OPERATION_MANAGER    11.02.2011  12:05:23    3928 (0x0F58)
      SecurityAdministration.SetTlsServerAuthentication finished with HResult =  0x0, status = 0x0, clientError = 0.    SMS_AMT_OPERATION_MANAGER     11.02.2011 12:05:26    3928 (0x0F58)
      SecurityAdministration.GetDigestRealm finished with HResult = 0x0,  status = 0x0, clientError = 0.    SMS_AMT_OPERATION_MANAGER     11.02.2011 12:05:30    3928 (0x0F58)
      SecurityAdministration.SetAdminAclEntryEx finished with HResult = 0x0,  status = 0x0, clientError = 0.    SMS_AMT_OPERATION_MANAGER     11.02.2011 12:05:33    3928 (0x0F58)
      We can't set MEBx password at this time. Admin may have already changed  this.    SMS_AMT_OPERATION_MANAGER    11.02.2011 12:05:33    3928  (0x0F58)
      Error: Failed to finish critical setup and configuration step.  (pProvisionHelper->CommitChanges)    SMS_AMT_OPERATION_MANAGER     11.02.2011 12:05:33    3928 (0x0F58)
      Error: Can't finish provision on AMT device PCName.xyz.xyz.to with  configuration code (126)!    SMS_AMT_OPERATION_MANAGER    11.02.2011  12:05:33    3928 (0x0F58)
      >>>>>>>>>>>>>>>Provision  task end<<<<<<<<<<<<<<<     SMS_AMT_OPERATION_MANAGER    11.02.2011 12:05:33    3928 (0x0F58)

        • 1. Re: Intel vPro stage 1 not finished fully
          jjcopela

          Hi Joachim, can you take a look at your HMAN.log file and see if you can spot any errors in there like this:

           

          Unable to decode MBEx passwordBad Data. SMS_HIERARCHY_MANAGER.

           

          thanks!

          Josh

          • 2. Re: Intel vPro stage 1 not finished fully
            jhans

            Hi Josh

             

            thanks for your reply. In the morning I checked the log but didin't find any error mentioned by you. In the meantime the client is provisioned but I changed nearly nothing in my configuration. :-)

             

            So I assume the ceritifactes are well configured and it's as often maybe be more patient when configuring sccm.

             

            I'll try another PC today and if I'll find the reason for the above issue I'll publish the solution.

             

             

            Are there any other log files to monitor for Intel vPro related issues especially server logs other then autopmgr.log, autoproxymgr.log?

             

            Thanks anyway

             

            Joachim

            • 3. Re: Intel vPro stage 1 not finished fully
              jjcopela

              Hi Joachim,

              If you have a configured machine I would say your setup is correct.

              As far as being patient with the provisioning process, you are right, sometimes it can take a while to complete.

               

              For the log files, the most frequently used are the 2 you mention:

              amtproxymgr.log

              amtopmgr.log

               

              For Installation of Out Of Band Service Point:

              C:\Program Files\Microsoft Configuration Manager\Logs\AMTSPSetup.Log

               

              on the client side, you can always check:

              c:\windows\system32\ccm\logs\oobmgmt.log (32bit)

              c:\windows\syswow64\ccm\logs\oobmgmt.log (64bit)

              This log will show the progress of the auto-provision process.

               

              Once you have a machine provisioned and start launching the OOB Console, there is another log file that is helpful:

              adminui\adminuilog\oobconsole.log

               

              glad to hear you have a system provisioned!

               

              Josh