2 Replies Latest reply on Feb 25, 2011 5:45 PM by brunodom

    SCCM Reports Client is "Detected" but Client Reports "Already Provisioned"

    cambot2k

      I've been banging my head against the wall for the past few days trying to get AMT to work with SCCM. Here is our setup:

       

      • Windows 2003 Server SP2 (Soon to be upgraded once new hardware arrives)
      • ConfigMgr 2007 R2 is installed and configured with OOB Service Point roll
      • Hotfix 942841 is installed

       

      • The ConfigMgr AMT Provisioning Certificate has been created as specified from our CA and the root cert hash value has been added to our test client machines.
      • The ConfigMgr AMT Web Server Certificate Template has been created as specified.

      Note: It would be nice to not have to touch all the computers that we would like to have this work on but for now I would just like to prove that it is possible to set this up despite my current skeptisism. If we can make it work we will more then likely purchase a preconfigured cert.

      • The computers have had their passwords changed since I had to do so in order to add the hash value. That password has been specified in Provision and Discovery Accounts.
      • AD Container has been created and SCCM server has been given full control

       

      • Test client machines have been added to a collection with allow out of band provisioning enabled.
      • On the SCCM server two machines report it is "Detected" while the other reports "Not Supported". I have got a single computer to say provisioned once but I'm not sure how and I cannot connect to it with the console or the web interface, it does show up in the AD container.

       

      If I right click on one of the discovered machines and choose discover management controller this is the resulting log...

      SMS_EXECUTIVE started SMS_AMT_OPERATION_MANAGER as thread ID 3872 (0xF20).    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:06 AM    2684 (0x0A7C)

      WinRM OOB is installed.    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:06 AM    3872 (0x0F20)
      Initialize AMT Operation Manager inbox for Discovery, Operation Manager, Provision and WOL...    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:06 AM    3872 (0x0F20)
      Auto-worker Thread Pool: Initializing completion port    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:06 AM    7096 (0x1BB8)
      Auto-worker Thread Pool: Successfully initialized completion port='21d4'    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:06 AM    7096 (0x1BB8)
      Auto-worker Thread Pool: Creating an event to signal thread shutdown    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:06 AM    7096 (0x1BB8)
      CBaseCounter::Initialize - Registered performance counter "Total number of packets sent"    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:06 AM    3872 (0x0F20)
      CBaseCounter::Initialize - Registered performance counter "Number of packets per minute"    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:06 AM    3872 (0x0F20)
      CBaseCounter::Initialize - Registered performance counter "Total number of packets failed"    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:06 AM    3872 (0x0F20)
      CBaseCounter::Initialize - Registered performance counter "Total number of requests pending"    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:06 AM    3872 (0x0F20)
      Registered connection type for SQL Server 'ROCKY2SQL' and database 'smscof'.    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:06 AM    3872 (0x0F20)
      HandleAMTOMRegistryChanges(): RegisterSqlDatabaseConnectionType() returned 0x0    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:06 AM    3872 (0x0F20)
      Hello listener port has been reconfigured.    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:06 AM    3872 (0x0F20)
      AMT Operation Manager hello listener thread created successfully with id 0x1d24.    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:06 AM    3872 (0x0F20)
      Server listens on port 9971 for incoming connections.    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:06 AM    7460 (0x1D24)
      Waiting for incoming hello message from AMT devices...    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:06 AM    7460 (0x1D24)
      Initialize all workers on AMT Operation Manager...    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:06 AM    3872 (0x0F20)
      AMT Discovery Worker: Initializing Discovery Worker    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:06 AM    3872 (0x0F20)
      AMT Provision Worker begin to initialize.    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:06 AM    3628 (0x0E2C)
      Send request to AMT proxy component to remove the alias .forestry.oregonstate.edu from DNS.    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:06 AM    3872 (0x0F20)
      Successfully created instruction file for AMT proxy task: C:\SMS\inboxes\amtproxymgr.box    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:06 AM    3872 (0x0F20)
      AMT WOL Worker: Worker thread 8044 started    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:06 AM    8044 (0x1F6C)
      AMT WOL Worker: Can not retrieve a packet from completion port. Error: 6    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:06 AM    8044 (0x1F6C)
      AMT WOL Worker: Worker thread 5116 started    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:06 AM    5116 (0x13FC)
      AMT WOL Worker: Worker thread 7360 started    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:06 AM    7360 (0x1CC0)
      AMT WOL Worker: Can not retrieve a packet from completion port. Error: 6    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:06 AM    5116 (0x13FC)
      AMT WOL Worker: Can not retrieve a packet from completion port. Error: 6    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:06 AM    7360 (0x1CC0)
      AMT WOL Worker: Worker thread 4552 started    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:06 AM    4552 (0x11C8)
      AMT WOL Worker: Worker thread 7176 started    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:06 AM    7176 (0x1C08)
      AMT WOL Worker: Can not retrieve a packet from completion port. Error: 6    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:06 AM    7176 (0x1C08)
      AMT WOL Worker: Worker thread 496 started    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:06 AM    496 (0x01F0)
      AMT WOL Worker: Can not retrieve a packet from completion port. Error: 6    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:06 AM    496 (0x01F0)
      AMT Discovery Worker: Wakes up to process instruction files    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:06 AM    6700 (0x1A2C)
      AMT Discovery Worker: Wait 3600 seconds...    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:06 AM    6700 (0x1A2C)
      AMT WOL Worker: Initializing completion port    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:06 AM    8164 (0x1FE4)
      AMT Provision Worker finish initializing.    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:06 AM    3628 (0x0E2C)
      AMT WOL Worker: Successfully initialized completion port='22e0'    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:06 AM    8164 (0x1FE4)
      AMT WOL Worker: Wakes up to process instruction files    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:06 AM    8164 (0x1FE4)
      AMT WOL Worker: Wait 3600 seconds...    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:06 AM    8164 (0x1FE4)
      AMT WOL Worker: Current size of the worker thread pool is 10.    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:06 AM    3872 (0x0F20)
      Clear all translators.    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:06 AM    3872 (0x0F20)
      AMT Opearation Manager certificate monitor thread created successfully with id 0x1adc.    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:06 AM    3872 (0x0F20)
      All initialization work is done. Wait for registry trigger or stop signal...    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:06 AM    3872 (0x0F20)
      Get active directory domain name of current computer is forestry.oregonstate.edu.    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:06 AM    6876 (0x1ADC)
      Get certificate data from database.    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:06 AM    6876 (0x1ADC)
      Found new provision server certificate with hash 3E08F8FABE0B3D83BAC1FCA6533454D539CE0F89.    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:06 AM    6876 (0x1ADC)
      Get ROOT HASH of provision server 55A0E55012F6F028FA4184AE45E1CB43F933861F.    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:06 AM    6876 (0x1ADC)
      Push back new found provision certificate to memory for future use.    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:06 AM    6876 (0x1ADC)
      AMT WOL Worker: Worker thread 6924 started    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:06 AM    6924 (0x1B0C)
      AMT Operation Worker: Wakes up to process instruction files    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:06 AM    8100 (0x1FA4)
      AMT Operation Worker: Wait 3600 seconds...    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:06 AM    8100 (0x1FA4)
      AMT Maintenance Worker: Wakes up to process instruction files    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:06 AM    7356 (0x1CBC)
      AMT Maintenance Worker: Wait 3600 seconds...    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:06 AM    7356 (0x1CBC)
      AMT WOL Worker: Worker thread 7004 started    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:06 AM    7004 (0x1B5C)
      AMT WOL Worker: Worker thread 4512 started    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:06 AM    4512 (0x11A0)
      AMT WOL Worker: Worker thread 7492 started    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:06 AM    7492 (0x1D44)
      AMT Provision Worker: Wakes up to process instruction files    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:06 AM    3628 (0x0E2C)
      AMT WOL Worker: Can not retrieve a packet from completion port. Error: 6    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:06 AM    4552 (0x11C8)
      AMT Provision Worker: Wait 3600 seconds...    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:06 AM    3628 (0x0E2C)
      AMT Discovery Worker: Wakes up to process instruction files    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:15 AM    6700 (0x1A2C)
      AMT Discovery Worker: Reading Discovery Instruction C:\SMS\inboxes\amtopmgr.box\disc\{AAD2E3A8-CC51-44BA-BECF-4A5973DA69BE}.RDC...    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:15 AM    6700 (0x1A2C)
      AMT Discovery Worker: Execute query exec AMT_GetThisSitesNetBiosNames NULL, 'GUID:ab6cb525-d42c-4342-8fa9-6d018aea5bf4', 'COF'    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:15 AM    6700 (0x1A2C)
      AMT Discovery Worker: CSMSAMTDiscoveryWorker::RetrieveInfoFromResource - Found machine PROTON (PROTON.forestry.oregonstate.edu), ID: 12278 - 10.207.13.24 from Resource GUID:ab6cb525-d42c-4342-8fa9-6d018aea5bf4.    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:15 AM    6700 (0x1A2C)
      AMT Discovery Worker: Execute query exec AMT_GetAMTMachineProperties 12278    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:15 AM    6700 (0x1A2C)
      AMT Discovery Worker: Execute query exec AMT_GetProvAccounts    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:15 AM    6700 (0x1A2C)
      AMT Discovery Worker: Finish reading discovery instruction C:\SMS\inboxes\amtopmgr.box\disc\{AAD2E3A8-CC51-44BA-BECF-4A5973DA69BE}.RDC    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:15 AM    6700 (0x1A2C)
      AMT Discovery Worker: Parsed 1 instruction files    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:15 AM    6700 (0x1A2C)
      AMT Discovery Worker: There are 1 tasks in pending list    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:15 AM    6700 (0x1A2C)
      AMT Discovery Worker: Send task  to completion port    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:15 AM    6700 (0x1A2C)
      Auto-worker Thread Pool: Current size of the thread pool is 1    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:15 AM    6700 (0x1A2C)
      AMT Discovery Worker: 1 task(s) are sent to the task pool successfully.    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:15 AM    6700 (0x1A2C)
      STATMSG: ID=7203 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_AMT_OPERATION_MANAGER" SYS=SMS SITE=COF PID=2512 TID=6700 GMTDATE=Tue Feb 22 19:16:15.091 2011 ISTR0="1" ISTR1="0" ISTR2="0" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:15 AM    6700 (0x1A2C)
      Auto-worker Thread Pool: Work thread 7244 started    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:15 AM    7244 (0x1C4C)
      AMT Discovery Worker: Wait 20 seconds...    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:15 AM    6700 (0x1A2C)
      AMT Discovery Worker: Wakes up to process instruction files    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:15 AM    6700 (0x1A2C)
      AMT Discovery Worker: Wait 20 seconds...    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:15 AM    6700 (0x1A2C)
      AMT Discovery Worker: Wakes up to process instruction files    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:15 AM    6700 (0x1A2C)
      AMT Discovery Worker: Wait 20 seconds...    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:15 AM    6700 (0x1A2C)
      CAMTDiscoveryWSMan::DoConnectToAMTDevice: Failed to establish tcp session to 10.207.13.24:16993.    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:16 AM    7244 (0x1C4C)
      CSMSAMTDiscoveryTask::Execute - DDR written to C:\SMS\inboxes\auth\ddm.box    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:18 AM    7244 (0x1C4C)
      Auto-worker Thread Pool: Succeed to run the task . Remove it from task list.    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:18 AM    7244 (0x1C4C)
      AMT Discovery Worker: Wakes up to process instruction files    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:35 AM    6700 (0x1A2C)
      AMT Discovery Worker: Wait 3600 seconds...    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:35 AM    6700 (0x1A2C)
      Auto-worker Thread Pool: Work thread 7244 has been requested to shut down.    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:58 AM    7244 (0x1C4C)
      Auto-worker Thread Pool: Work thread 7244 exiting.    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:58 AM    7244 (0x1C4C)
      Auto-worker Thread Pool: Current size of the thread pool is 0    SMS_AMT_OPERATION_MANAGER    2/22/2011 11:16:58 AM    7096 (0x1BB8)

       

      Here is the log on that same machine:

      <![LOG[BEGIN]LOG]!><time="10:15:00.105+480" date="02-22-2011" component="oobmgmt" context="" type="1" thread="4020" file="amtprovisionendpoint.cpp:825">
      <![LOG[!! Device is already provisioned]LOG]!><time="10:15:00.230+480" date="02-22-2011" component="oobmgmt" context="" type="1" thread="4020" file="amtprovisionendpoint.cpp:850">
      <![LOG[END]LOG]!><time="10:15:00.230+480" date="02-22-2011" component="oobmgmt" context="" type="1" thread="4020" file="amtprovisionendpoint.cpp:881">

       

      I have absolutely no idea what the problem is so any advice is helpful. Thank you all in advance for your help!

        • 1. Re: SCCM Reports Client is "Detected" but Client Reports "Already Provisioned"
          cambot2k

          Progress!! I was finally able to get a computer to provision successfully and connect to it via the OOB Console. The problem was with the AMT Web Server Cert Template. Unfortuately it took forever to figure that out because the person controlling the CA insisted that they did it right the first time. If we purchase a provisioning cert from GoDaddy will we be able to provision the remainder of our computers without having to visit each machine? Secondly is there a way in SCCM to make an advertisement mandatory and then force the computer to PXE boot using AMT. I know I can PXE boot one computer at a time using the OOB Console but I would certainly hope there was another way.

          • 2. Re: SCCM Reports Client is "Detected" but Client Reports "Already Provisioned"
            brunodom

            Cameron,

             

                 Yes, you can use GoDaddy to provision the remaining machines without touch each one.

                 Unfortunately, OOB console will not allow you to do multiple operation on multiple machines at same time (e.g. based on a collection), but you can do it customizing PowerShell scripts.

             

            Best Regards!

            --Bruno Domingues