2 Replies Latest reply on Aug 25, 2011 5:13 PM by stepland

    clients showing up as detected but.....

    stepland

      Hi, I have quite a few machines that actually got provisioned...went through the provisioning process, got certificates, got AD object etc...but still showing up in sccm as detected...this is occuring on 3 different versions of amt and to make this even more interesting all these 3 version have some systems showing up as provisioned in sccm just fine but others as detected....

       

      versions are

      5.0.1  

      5.0.3

      5.2.1

       

      here is what there logs continuously get....

       

      <![LOG[Retrying to activate the device.]LOG]!><time="20:00:04.530+180" date="05-24-2011" component="oobmgmt" context="" type="1" thread="2496" file="amtprovisionendpoint.cpp:398">
      <![LOG[New OTP generated]LOG]!><time="20:00:04.874+180" date="05-24-2011" component="oobmgmt" context="" type="1" thread="2496" file="amtprovisionendpoint.cpp:253">
      <![LOG[Successfully activated the device.]LOG]!><time="20:00:06.952+180" date="05-24-2011" component="oobmgmt" context="" type="1" thread="2496" file="amtprovisionendpoint.cpp:431">
      <![LOG[END]LOG]!><time="20:00:06.952+180" date="05-24-2011" component="oobmgmt" context="" type="1" thread="2496" file="amtprovisionendpoint.cpp:881">

       

       

       

       

       

      also,

       

      some versions of amt 5.2.1 and 3.2.1 keep getting this in the oobmgmt.log but never get provisioned or get certs and AD object created

       

      <![LOG[BEGIN]LOG]!><time="19:51:41.487+180" date="05-24-2011" component="oobmgmt" context="" type="1" thread="5496" file="amtprovisionendpoint.cpp:825">
      <![LOG[!! Device is already provisioned]LOG]!><time="19:51:41.565+180" date="05-24-2011" component="oobmgmt" context="" type="1" thread="5496" file="amtprovisionendpoint.cpp:850">
      <![LOG[END]LOG]!><time="19:51:41.565+180" date="05-24-2011" component="oobmgmt" context="" type="1" thread="5496" file="amtprovisionendpoint.cpp:881">

       

      but other amt clients with versions 5.2.1 and 3.2.1 provision just fine.....

       

      none of these machines were ever provisioned for amt before

        • 1. Re: clients showing up as detected but.....
          brunodom

          Stéphane,

           

               Detected status, means that AMT capability is present, but  SCCM is unable to provision it a couple of reasons: already provisioned with a 3rd party console or SMB mode, AMT password changed (Remote Admin of MEBx), etc.

               Try the amtopmgr.log to see what's happening and as a test, make a full unprovisioning in one of these machines, better if BIOS allows factory default mode and try the provision process again.

           

          Best Regards!

          --Bruno Domingues

          • 2. Re: clients showing up as detected but.....
            stepland

            Hi Bruno, i still have quite a few of these machines like this.

             

            reset them all to factory default, removed AD object, certificate and clients came back with the same problem...sccm still says detected, but certificate was issued, AD object created and oobmgmt log says device already provisioned??

             

            seems to be alot of issues with older versions of mebx..pretty much all the newer version of amt provision just fine.

             

            thanks