Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Highlighted
Community Manager
1,472 Views

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

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 f...
0 Kudos
2 Replies
Highlighted
Community Manager
12 Views

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.

0 Kudos
Highlighted
Employee
12 Views

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 /community/openportit/vproexpert/blog/2010/10/18/version-2-of-the-powershell-module-for-intel-vpro-technology-released PowerShell scripts.

Best Regards!

--Bruno Domingues

0 Kudos