Solved: Re: AMT - device in 'detected' status

egonz6 · ‎12-13-2011

Hello everyone,

I'm trying to get Out of Band working (I'm using System Configuration Manager), and the two machines that I'm testing for this purpose seems to be stuck at 'Detected' status. I gone over the configuration steps for SCCM twice, but I can't seem to pinpoint what I've missed (I'm pretty sure this part was done correctly).

The machines at hand are DELL Optiplex 990 (AMT v7.1.20 and v7.1.13), and the only thing I've manually done is reset the password from 'admin' to my own custom password (previously I tried the default password, but I got the same error messages in the logs).

Also, I noticed that one of the Optiplex does show some information passed on by SCCM, but I can't figure out why it keeps showing 'Detected' as its status.

Being my first time trying to get Out of Band working, I really don't know where to start my troubleshooting efforts here.

Here's the log from amtopmgr.log file (this portion of the log is when I perform a "Discover AMT Status" task.

AMT Discovery Worker: Wakes up to process instruction files SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:47 PM 4528 (0x11B0)AMT Discovery Worker: Wait 3600 seconds... SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:47 PM 4528 (0x11B0)AMT Discovery Worker: Wakes up to process instruction files SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:47 PM 4528 (0x11B0)AMT Discovery Worker: Reading Discovery Instruction C:\Program Files\Microsoft Configuration Manager\inboxes\amtopmgr.box\disc\{7D90B636-860E-4509-9101-748A98871927}.RDC... SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:47 PM 4528 (0x11B0)AMT Discovery Worker: Execute query exec AMT_GetThisSitesNetBiosNames NULL, '16777231', 'LAB' SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:47 PM 4528 (0x11B0)AMT Discovery Worker: CSMSAMTDiscoveryWorker::RetrieveInfoFromResource - Found machine X1212 (X1212.GLLAB2.COM), ID: 16777231 IP: 172.16.16.69 from Resource 16777231. SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:47 PM 4528 (0x11B0)AMT Discovery Worker: Execute query exec AMT_GetAMTMachineProperties 16777231 SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:47 PM 4528 (0x11B0)Discovery will use ip resolved from netbios: SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:47 PM 4528 (0x11B0)172.16.16.69 SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:47 PM 4528 (0x11B0)AMT Discovery Worker: Execute query exec AMT_GetProvAccounts SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:47 PM 4528 (0x11B0)AMT Discovery Worker: Finish reading discovery instruction C:\Program Files\Microsoft Configuration Manager\inboxes\amtopmgr.box\disc\{7D90B636-860E-4509-9101-748A98871927}.RDC SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:47 PM 4528 (0x11B0)AMT Discovery Worker: Parsed 1 instruction files SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:47 PM 4528 (0x11B0)AMT Discovery Worker: Send task X1212.GLLAB2.COM to completion port SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:47 PM 4528 (0x11B0)General Worker Thread Pool: Current size of the thread pool is 1 SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:47 PM 4528 (0x11B0)AMT Discovery Worker: 1 task(s) are sent to the task pool successfully. SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:47 PM 4528 (0x11B0)STATMSG: ID=7203 SEV=I LEV=M SOURCE="SMS Server" COMP="SMS_AMT_OPERATION_MANAGER" SYS=SCCM2012-RC1.GLLAB2.COM SITE=LAB PID=2256 TID=4528 GMTDATE=Tue Dec 13 18:53:47.749 2011 ISTR0="1" ISTR1="0" ISTR2="0" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:47 PM 4528 (0x11B0)AMT Discovery Worker: There are 1 tasks in pending list SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:47 PM 4528 (0x11B0)AMT Discovery Worker: Wait 20 seconds... SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:47 PM 4528 (0x11B0)AMT Discovery Worker: Wakes up to process instruction files SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:47 PM 4528 (0x11B0)AMT Discovery Worker: There are 1 tasks in pending list SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:47 PM 4528 (0x11B0)AMT Discovery Worker: Wait 20 seconds... SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:47 PM 4528 (0x11B0)General Worker Thread Pool: Work thread 3188 started SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:47 PM 3188 (0x0C74)Discover X1212 using IP address 172.16.16.69 SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:47 PM 3188 (0x0C74)DoPingDiscoveryForAMTDevice succeeded. SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:47 PM 3188 (0x0C74)Error 0x80090325 returned by InitializeSecurityContext during follow up TLS handshaking with server. SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:47 PM 3188 (0x0C74)**** Error 0x2040b350 returned by ApplyControlToken SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:47 PM 3188 (0x0C74)DoSoapDiscovery failed with user name: admin. SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:47 PM 3188 (0x0C74)Error 0x80090325 returned by InitializeSecurityContext during follow up TLS handshaking with server. SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:48 PM 3188 (0x0C74)**** Error 0x2040b350 returned by ApplyControlToken SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:48 PM 3188 (0x0C74)DoSoapDiscovery failed with user name: admin. SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:48 PM 3188 (0x0C74)Flag iWSManFlagSkipRevocationCheck is not set. SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:48 PM 3188 (0x0C74)session params : https://X1212.GLLAB2.COM:16993 https://X1212.GLLAB2.COM:16993 , 11001 SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:48 PM 3188 (0x0C74)ERROR: Invoke(get) failed: 80020009argNum = 0 SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:48 PM 3188 (0x0C74)Description: The I/O operation has been aborted because of either a thread exit or an application request. SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:48 PM 3188 (0x0C74)Error: Failed to get AMT_SetupAndConfigurationService instance. SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:48 PM 3188 (0x0C74)DoWSManDiscovery failed with user name: admin. SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:48 PM 3188 (0x0C74)Flag iWSManFlagSkipRevocationCheck is not set. SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:48 PM 3188 (0x0C74)session params : https://X1212.GLLAB2.COM:16993 https://X1212.GLLAB2.COM:16993 , 11001 SMS_AMT_OPERATION_MANAGER 12/13/2011 1:53:48 PM 3188 (0x0C74)<...

idata · ‎12-14-2011

hi

detect mean that MSSCCM identify that your platfrom is provisioned but cannot access to the FW (user unauthorized)

if you provisioned using MSSCCM and the MSSCCM identify the platfrom as detected, then add a user with your custom password to MSSCCM discovery users.

goto Computer Configuration --> Out Of Band Management--> Provisioning Setting, add a new user (try user name 'admin' and password your custom password).

good luck

View solution in original post

idata · ‎12-14-2011

did you update Discovery user to match your costum password? (in SCCM configuration option under Provisioning Setting, add a user with the name admin and your custom password)

egonz6 · ‎12-15-2011

I did more troubleshooting, and anytime I leave the 'admin' password as default, the status shows as 'detected'. However, if I change it (and, yes, I do add the 'admin' account with the custom password in the Provisioning section in SCCM) then the status shows 'Not Supported'.

When the machine reports 'Not Supported', then I have to back in to MBEx and set it's settings back to factory defaults, to make it report 'Detected' again.

I've tried almost every possible recommendation I've found, and nothing seems to work.

idata · ‎12-14-2011

hi

detect mean that MSSCCM identify that your platfrom is provisioned but cannot access to the FW (user unauthorized)

if you provisioned using MSSCCM and the MSSCCM identify the platfrom as detected, then add a user with your custom password to MSSCCM discovery users.

goto Computer Configuration --> Out Of Band Management--> Provisioning Setting, add a new user (try user name 'admin' and password your custom password).

good luck

egonz6 · ‎12-15-2011

Hi David, yes I've done that as well.

If I change the password, then SCCM reports 'Not Supported' and then I have to reset MBEx to factory defaults. Only when I leave the default password it shows 'Detected'. However, I can't make it past this though.

idata · ‎06-26-2012

Anyone find solution for this? I am having similar issue..... Showing up as detected in SCCM 2012 console but getting the following error in the amtopmgr.log.

Error 0x80090304 returned by InitializeSecurityContext during follow up TLS handshaking with server. SMS_AMT_OPERATION_MANAGER 6/26/2012 4:40:10 PM 4624 (0x1210)

**** Error 0x1ed8b420 returned by ApplyControlToken SMS_AMT_OPERATION_MANAGER 6/26/2012 4:40:10 PM 4624 (0x1210)

DoSoapDiscovery failed with user name: admin. SMS_AMT_OPERATION_MANAGER 6/26/2012 4:40:10 PM 4624 (0x1210)

idata · ‎06-29-2012

The error, "Error 0x80090325 returned by InitializeSecurityContext during follow up TLS handshaking with server." means that the TLS handshake was not successful. In my case this was related to using the wrong hash for my internal CA; for some reason I was thinking I needed to use the hash from the Provisioning certificate.

It can still go into "Detected" mode even though the TLS handshake failed. According to Microsoft "Not Supported" means one of two things: 1) system does not support AMT; or 2) "...computer has AMT capability, but the AMT network interface is closed because the time limit for out of band provisioning has expired". However, I have seen it appear if the network connection is not open on the AMT interface; e.g. you haven't started the RCFG Configuration.

Once you have the hash correct, you should be able to get to at least the "Not Provisioned" state.