SCCM Vpro Detected instead of Not Provisioned
I am trying to get my clients setup in SCCM 2007 R3 for Out of Band Management. All the machines are coming in as Detected instead of Not Provisioned. Here is a snippet of the amtopmgr.log. I am not getting any entries in the client oobmgmt.log. I checked an can see that the Provisioning cert matches the Go Daddy Cert in Vpro. The machines vary from HP DC7900, 8000 and 8540p's. Along with some MPC 385's. AMT Discovery Worker: Reading Discovery Instruction C:\Program Files\Microsoft Configuration Manager\inboxes\amtopmgr.box\disc\{9BEE2DA9-ED95-40E4-AC1E-B0ECC25B1C22}.RDC... SMS_AMT_OPERATION_MANAGER 4/6/2011 3:58:17 PM 2628 (0x0A44) AMT Discovery Worker: Execute query exec AMT_GetThisSitesNetBiosNames NULL, 'GUID:0737D6E0-49BC-4623-AB20-B19E2D8287E8', 'NTC' SMS_AMT_OPERATION_MANAGER 4/6/2011 3:58:17 PM 2628 (0x0A44) AMT Discovery Worker: CSMSAMTDiscoveryWorker::RetrieveInfoFromResource - Found machine A201-43764 (A201-43764.NTC.EDU), ID: 225 - 10.1.33.41 from Resource GUID:0737D6E0-49BC-4623-AB20-B19E2D8287E8. SMS_AMT_OPERATION_MANAGER 4/6/2011 3:58:17 PM 2628 (0x0A44) AMT Discovery Worker: Execute query exec AMT_GetAMTMachineProperties 225 SMS_AMT_OPERATION_MANAGER 4/6/2011 3:58:17 PM 2628 (0x0A44) AMT Discovery Worker: Execute query exec AMT_GetProvAccounts SMS_AMT_OPERATION_MANAGER 4/6/2011 3:58:17 PM 2628 (0x0A44) AMT Discovery Worker: Finish reading discovery instruction C:\Program Files\Microsoft Configuration Manager\inboxes\amtopmgr.box\disc\{9BEE2DA9-ED95-40E4-AC1E-B0ECC25B1C22}.RDC SMS_AMT_OPERATION_MANAGER 4/6/2011 3:58:17 PM 2628 (0x0A44) AMT Discovery Worker: Parsed 1 instruction files SMS_AMT_OPERATION_MANAGER 4/6/2011 3:58:17 PM 2628 (0x0A44) AMT Discovery Worker: There are 1 tasks in pending list SMS_AMT_OPERATION_MANAGER 4/6/2011 3:58:17 PM 2628 (0x0A44) AMT Discovery Worker: Send task to completion port SMS_AMT_OPERATION_MANAGER 4/6/2011 3:58:17 PM 2628 (0x0A44) Auto-worker Thread Pool: Current size of the thread pool is 1 SMS_AMT_OPERATION_MANAGER 4/6/2011 3:58:17 PM 2628 (0x0A44) Auto-worker Thread Pool: Work thread 5200 started SMS_AMT_OPERATION_MANAGER 4/6/2011 3:58:17 PM 5200 (0x1450) AMT Discovery Worker: 1 task(s) are sent to the task pool successfully. SMS_AMT_OPERATION_MANAGER 4/6/2011 3:58:17 PM 2628 (0x0A44) Server unexpectedly disconnected when TLS handshaking. SMS_AMT_OPERATION_MANAGER 4/6/2011 3:58:17 PM 5200 (0x1450) STATMSG: ID=7203 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_AMT_OPERATION_MANAGER" SYS=WAUSCCM1 SITE=NTC PID=2100 TID=2628 GMTDATE=Wed Apr 06 20:58:17.782 2011 ISTR0="1" ISTR1="0" ISTR2="0" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_AMT_OPERATION_MANAGER 4/6/2011 3:58:17 PM 2628 (0x0A44) **** Error 0x4fcb878 returned by ApplyControlToken SMS_AMT_OPERATION_MANAGER 4/6/2011 3:58:17 PM 5200 (0x1450) AMT Discovery Worker: Wait 20 seconds... SMS_AMT_OPERATION_MANAGER 4/6/2011 3:58:17 PM 2628 (0x0A44) session params : https://A201-43764.NTC.EDU:16993 , 11001 SMS_AMT_OPERATION_MANAGER 4/6/2011 3:58:17 PM 5200 (0x1450) AMT Discovery Worker: Wakes up to process instruction files SMS_AMT_OPERATION_MANAGER 4/6/2011 3:58:17 PM 2628 (0x0A44) AMT Discovery Worker: Wait 20 seconds... SMS_AMT_OPERATION_MANAGER 4/6/2011 3:58:17 PM 2628 (0x0A44) AMT Discovery Worker: Wakes up to process instruction files SMS_AMT_OPERATION_MANAGER 4/6/2011 3:58:17 PM 2628 (0x0A44) ERROR: Invoke(get) failed: 80020009argNum = 0 SMS_AMT_OPERATION_MANAGER 4/6/2011 3:58:17 PM 5200 (0x1450) AMT Discovery Worker: Wait 20 seconds... SMS_AMT_OPERATION_MANAGER 4/6/2011 3:58:17 PM 2628 (0x0A44) Description: The I/O operation has been aborted because of either a thread exit or an application request. SMS_AMT_OPERATION_MANAGER 4/6/2011 3:58:17 PM 5200 (0x1450) Error: Failed to get AMT_SetupAndConfigurationService instance. SMS_AMT_OPERATION_MANAGER 4/6/2011 3:58:17 PM 5200 (0x1450) session params : https://10.1.33.41:16993 , 15001 SMS_AMT_OPERATION_MANAGER 4/6/2011 3:58:17 PM 5200 (0x1450) ERROR: Invoke(get) failed: 80020009argNum = 0 SMS_AMT_OPERATION_MANAGER 4/6/2011 3:58:17 PM 5200 (0x1450) Description: The I/O operation has been aborted because of either a thread exit or an application request. SMS_AMT_OPERATION_MANAGER 4/6/2011 3:58:17 PM 5200 (0x1450) Error: Failed to get AMT_SetupAndConfigurationService instance. SMS_AMT_OPERATION_MANAGER 4/6/2011 3:58:17 PM 5200 (0x1450) CSMSAMTDiscoveryTask::Execute - DDR written to C:\Program Files\Microsoft Configuration Manager\inboxes\auth\ddm.box SMS_AMT_OPERATION_MANAGER 4/6/2011 3:58:17 PM 5200 (0x1450) Auto-worker Thread Pool: Succeed to run the task . Remove it from task list. SMS_AMT_OPERATION_MANAGER 4/6/2011 3:58:17 PM 5200 (0x1450) AMT Discovery Worker: Wakes up to process instruction files SMS_AMT_OPERATION_MANAGER 4/6/2011 3:58:37 PM 2628 (0x0A44) AMT Discovery Worker: Wait 3600 seconds... SMS_AMT_OPERATION_MANAGER 4/6/2011 3:58:37 PM 2628 (0x0A44) Thanks, Ross
April 6th, 2011 5:04pm

Hey Ross, So your not getting a Successful Activated the device message in oobmgmt.log? Have a look at this question. May help: http://social.technet.microsoft.com/Forums/en-ZA/configmgrgeneral/thread/d7587a7b-3265-4e67-a13d-c23ebf50cd6c. It's not the same issue but should give you some information on how to troubleshoot. Blair Muller
Free Windows Admin Tool Kit Click here and download it now
April 6th, 2011 7:59pm

Thanks for the reply. I worked through each of the posts and links in the thread. I still can't get the machines out of Detected mode. Most of the issues were with cert issues and I checked to make sure that the cert in the amtopmgr.log is the same as the one on the machines. Are there other steps I can take to narrow down the problem? The error messages in the log are rather ambiguous. Thanks, Ross
April 7th, 2011 10:12am

Hey Ross, Every issue I have dealt with has always been to do with Certificates. I do know that it takes 24 to go from detected to provisioned. I do suggest you go to the Intel community (Microsoft Manageability) to get your answer. I assume you tried to force provisioning using the vp script or wbemtest and watched the logs to see if there is any errors? It would be great if you posted back once you get your answer from the Intel community. Regards, Blair Blair Muller
Free Windows Admin Tool Kit Click here and download it now
April 7th, 2011 6:50pm

The issue was a combination of two problems. The first was that the workstation cert security did not have autoenrollment enabled on it. The second problem was that the machines needed to be unprovisioned for some reason. Even though they had never been provisioned before. Thanks, Ross
April 13th, 2011 9:21am

Wouldn't it be nice if you told exactly 'what' you mean by: "the workstation cert security did not have autoenrollment enabled on it" Do I go to the 'workstation' (each one) and set security in some location? You really did NOT tell us 'how' you set the security. Please elaborate. Thanks.tnjman
Free Windows Admin Tool Kit Click here and download it now
May 12th, 2012 12:19am

Wouldn't it be nice if you told exactly 'what' you mean by: "the workstation cert security did not have autoenrollment enabled on it" Do I go to the 'workstation' (each one) and set security in some location? You really did NOT tell us 'how' you set the security. Please elaborate. Thanks. tnjman this example may help you: http://technet.microsoft.com/en-us/library/cc731242.aspxDon
May 12th, 2012 1:07am

Thank you - although that is rather vague, it is somewhat helpful, but NOBODY has said, "Oh, by the way, you need to FIRST set this Group Policy for 'auto-enrolmment,' before provisioning." I think, if this is needed, it is a MAJOR HOLE in most of the existing instructions! And, I thank you for trying to help. I did not set that on the entire domain, just on 2 of the OUs in question. Still, nothing is provisioning yet. Another Microsoft article mentioned if you install HECI & AMT, you MUST install .NET *first* - if you do not, then provisioning will not work - and that may be the case here. I think, as would be NORMAL for a tech, our tech first installed ALL DRIVERS, FIRMWARE, etc; and THEN installed .Net. Has anyone seen this to be true or false? Why would it matter if a .NET piece is installed BEFORE the AMT/HECI pieces? Thanks for any insights.tnjman
Free Windows Admin Tool Kit Click here and download it now
May 18th, 2012 5:20pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics