Intel vPro® Platform
Intel Manageability Forum for Intel® EMA, AMT, SCS & Manageability Commander
2949 Discussions

Yet "Detected" AMT Status

idata
Employee
‎07-23-2009 03:01 AM
3,033 Views

Hi all,

I have SCCM SP2 and also some AMT machines. I performed full unprovision for one of them and imported it successfully via "Import single computer".

My AMT's version is 3.0.2 and it uses PSK so I use also the WS-Man Translator (The PID and PPS were inserted to wstranscfg.exe) - it is enabled in the Out Of Band Management component, and I can see that it works (https://<sccm's https:// fqdn>/wstrans).

I use also my own Root CA for certificates, and the same certificate was inserted to both SCCM and the translator.

The passwords in the MEBx were changed and the new password is in the Out Of Band Management component and the translator.

Everything in the setup and the environment is looking OK - but the computers' status stays "Detected"...

I've tried to look at other posts here with the same problem - nothing was helpful. (DHCP option 15 is enabled, the DNS contains the AMT's records in forward and reverse lookup zones, the certificates looks correct...).

The problem occurs already in the translator - wstrans.log:

http://intel.com/wbem/wscim/1/amt-schema/1/AMT_SetupAndConfigurationService.Get http://intel.com/wbem/wscim/1/amt-schema/1/AMT_SetupAndConfigurationService.Get() WSTRANS 7/23/2009 11:34:41 AM 5 (0x0005)

 

Using Discovery Routing WSTRANS 7/23/2009 11:34:41 AM 5 (0x0005)

 

proxy target is psk://:16993/ WSTRANS 7/23/2009 11:34:41 AM 5 (0x0005)

 

IP: WSTRANS 7/23/2009 11:34:41 AM 5 (0x0005)

 

Using factory account WSTRANS 7/23/2009 11:34:41 AM 5 (0x0005)

 

Using psk 4444-4444 WSTRANS 7/23/2009 11:34:41 AM 5 (0x0005)

 

GetPasswordModel() WSTRANS 7/23/2009 11:34:41 AM 5 (0x0005)

 

Submit to psk://:16993/GeneralInfoService 23 WSTRANS 7/23/2009 11:34:41 AM 5 (0x0005)

 

proxy target is psk://:16993/ WSTRANS 7/23/2009 11:34:41 AM 5 (0x0005)

 

IP: WSTRANS 7/23/2009 11:34:41 AM 5 (0x0005)

 

Using factory account WSTRANS 7/23/2009 11:34:41 AM 5 (0x0005)

 

Using pki WSTRANS 7/23/2009 11:34:41 AM 5 (0x0005)

 

GetPasswordModel() WSTRANS 7/23/2009 11:34:41 AM 5 (0x0005)

 

Submit to psk://:16993/GeneralInfoService 23 WSTRANS 7/23/2009 11:34:41 AM 5 (0x0005)

 

proxy target is https://<AMT's https:// FQDN>:16993/ WSTRANS 7/23/2009 11:34:41 AM 5 (0x0005)

 

IP: WSTRANS 7/23/2009 11:34:41 AM 5 (0x0005)

 

Using factory account WSTRANS 7/23/2009 11:34:41 AM 5 (0x0005)

 

GetPasswordModel() WSTRANS 7/23/2009 11:34:41 AM 5 (0x0005)

 

Discovery failed for https://<AMT's https:// FQDN>:16993 WSTRANS 7/23/2009 11:34:41 AM 5 (0x0005)

 

fault() WSTRANS 7/23/2009 11:34:41 AM 5 (0x0005)

 

Request from "172.31.60.8:5721" for "https://je-dev-ms0.jer.isr.dev.daliot.com/wstrans/dsc/eoi20/<AMT's https://je-dev-ms0.jer.isr.dev.daliot.com/wstrans/dsc/eoi20/ IP>/wsman" WSTRANS 7/23/2009 11:34:41 AM 5 (0x0005)

 

Using Basic Authentication WSTRANS 7/23/2009 11:34:41 AM 5 (0x0005)

 

ActiveThreads 1 WSTRANS 7/23/2009 11:34:41 AM 5 (0x0005)

 

http://intel.com/wbem/wscim/1/amt-schema/1/AMT_SetupAndConfigurationService.Get http://intel.com/wbem/wscim/1/amt-schema/1/AMT_SetupAndConfigurationService.Get() WSTRANS 7/23/2009 11:34:41 AM 5 (0x0005)

 

Using Discovery Routing WSTRANS 7/23/2009 11:34:41 AM 5 (0x0005)

 

proxy target is psk://:16993/ WSTRANS 7/23/2009 11:34:41 AM 5 (0x0005)

 

dns: WSTRANS 7/23/2009 11:34:41 AM 5 (0x0005)

 

Non-factory account WSTRANS 7/23/2009 11:34:41 AM 5 (0x0005)

 

Using psk 4444-4444 WSTRANS 7/23/2009 11:34:41 AM 5 (0x0005)

 

GetPasswordModel() WSTRANS 7/23/2009 11:34:41 AM 5 (0x0005)

 

Submit to psk://:16993/GeneralInfoService 23 WSTRANS 7/23/2009 11:34:41 AM 5 (0x0005)

 

proxy target is psk://:16993/ WSTRANS 7/23/2009 11:34:41 AM 5 (0x0005)

 

dns: WSTRANS 7/23/2009 11:34:41 AM 5 (0x0005)

 

Using factory account WSTRANS 7/23/2009 11:34:41 AM 5 (0x0005)

 

Using pki WSTRANS 7/23/2009 11:34:41 AM 5 (0x0005)

 

GetPasswordModel() WSTRANS 7/23/2009 11:34:41 AM 5 (0x0005)

 

Submit to psk://:16993/GeneralInfoService 23 WSTRANS 7/23/2009 11:34:41 AM 5 (0x0005)

 

proxy target is https://<AMT's https:// IP>:16993/ WSTRANS 7/23/2009 11:34:41 AM 5 (0x0005)

 

dns: WSTRANS 7/23/2009 11:34:41 AM 5 (0x0005)

 

Non-factory account WSTRANS 7/23/2009 11:34:41 AM 5 (0x0005)

 

GetPasswordModel() WSTRANS 7/23/2009 11:34:41 AM 5 (0x0005)

 

Discovery failed for https://<AMT's https:// IP>:16993 WSTRANS 7/23/2009 11:34:41 AM 5 (0x0005)

 

fault() WSTRANS 7/23/2009 11:34:41 AM 5 (0x0005)

 

Request from "172.31.60.8:5726" for "https://je-dev-ms0.jer.isr.dev.daliot.com/wstrans/dsc/eoi20/<AMT's https://je-dev-ms0.jer.isr.dev.daliot.com/wstrans/dsc/eoi20/ IP>/wsman" WSTRANS 7/23/2009 11:34:41 AM 5 (0x0005)

 

Using Basic Authentication WSTRANS 7/23/2009 11:34:41 AM 5 (0x0005)

 

ActiveThreads 1 WSTRANS 7/23/2009 11:34:41 AM 5 (0x0005)

 

http://intel.com/wbem/wscim/1/amt-schema/1/AMT_SetupAndConfigurationService.Get http://intel.com/wbem/wscim/1/amt-schema/1/AMT_SetupAndConfigurationService.Get() WSTRANS 7/23/2009 11:34:41 AM 5 (0x0005)

 

Using Discovery Routing WSTRANS 7/23/2009 11:34:41 AM 5 (0x0005)

 

proxy target is psk://:16993/ WSTRANS 7/23/2009 11:34:41 AM 5 (0x0005)

 

dns: WSTRANS 7/23/2009 11:34:41 AM 5 (0x0005)

 

Non-factory account WSTRANS 7/23/2009 11:34:41 AM 5 (0x0005)

 

Using psk 4444-4444 WSTRANS 7/23/2009 11:34:41 AM 5 (0x0005)

 

GetPasswordModel() WSTRANS 7/23/2009 11:34:41 AM 5 (0x0005)

 

Submit to psk://:16993/GeneralInfoService 23 WSTRANS 7/23/2009 11:34:41 AM 5 (0x0005)

 

proxy target is psk://:16993/ WSTRANS 7/23/2009 11:34:41 AM 5 (0x0005)

 

dns: WSTRANS 7/23/2009 11:34:41 AM 5 (0x0005)

 

Using factory account WSTRANS 7/23/2009 11:34:41 AM 5 (0x0005)

 

Using pki WSTRANS 7/23/2009 11:34:41 AM 5 (0x0005)

 

GetPasswordModel() WSTRANS 7/23/2009 11:34:41 AM 5 (0x0005)

 

Submit to psk://:16993/GeneralInfoService 23 WSTRANS 7/23/2009 11:34:41 AM 5 (0x0005)

 

proxy target is https://<AMT's https:// IP>:16993/ WSTRANS 7/23/2009 11:34:41 AM 5 (0x0005)

 

dns: WSTRANS 7/23/2009 11:34:41 AM 5 (0x0005)

 

Non-factory account WSTRANS 7/23/2009 11:34:41 AM 5 (0x0005)

 

GetPasswordModel() WSTRANS 7/23/2009 11:34:41 AM 5 (0x0005)

 

Discovery failed for https://<AMT's https:// IP>:16993 WSTRANS 7/23/2009 11:34:41 AM 5 (0x0005)

 

fault() WSTRANS 7/23/2009 11:34:41 AM 5 (0x0005)

X...

0 Kudos

Link Copied

7 Replies
idata
Employee
‎07-23-2009 02:35 PM
747 Views

I would suggest updating the Firmware of your AMT machines as 3.0 had some known issues.

What OEM/Model are they?

Josh

0 Kudos
Copy link
idata
Employee
‎07-26-2009 12:47 AM
747 Views
In response to idata

The problematic computer is Lenovo ThinkCentre M57p, vPro.

Thanks in advance.

In response to idata
0 Kudos
Copy link
idata
Employee
‎07-28-2009 08:35 AM
747 Views
In response to idata

Make sure to check out the latest ME Firmware release from Lenovo (3.2.3 I believe)

After you get your system updated, you should have an easier time provisioning.

http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-69827 http://www-307.ibm.com/pc/support/site.wss/document.do?sitestyle=lenovo&lndocid=MIGR-69827

thanks!

Josh

In response to idata
0 Kudos
Copy link
idata
Employee
‎08-11-2009 09:54 AM
747 Views

0

0 Kudos
Copy link
idata
Employee
‎08-11-2009 09:54 AM
747 Views

0

0 Kudos
Copy link
idata
Employee
‎08-11-2009 09:55 AM
747 Views

0

0 Kudos
Copy link
idata
Employee
‎08-11-2009 09:55 AM
747 Views

0

0 Kudos
Copy link
Reply

Community support is provided Monday to Friday. Other contact methods are available here.

Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.

For more complete information about compiler optimizations, see our Optimization Notice.