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

SCCM Dell Optiplex 755 Not Provisioning

idata
Employee
‎10-04-2010 12:25 PM
1,322 Views

I have many Optiplex machines that have been rolled out to remote locations. All systems are AMT version 3.2.2 Dell optiplex 755. They fail to provision. Here is the amtopmgr.log:

AMT Provision Worker: Send task BRI-094915.network.com to completion port SMS_AMT_OPERATION_MANAGER 10/4/2010 1:50:22 PM 19836 (0x4D7C)

 

Provision target is indicated with SMS resource id. (MachineId = 23433 BRI-094915.network.com) SMS_AMT_OPERATION_MANAGER 10/4/2010 1:50:22 PM 1300 (0x0514)

 

The provision mode for device BRI-094915.network.com is 1. SMS_AMT_OPERATION_MANAGER 10/4/2010 1:50:22 PM 1300 (0x0514)

 

The IP addresses of the host BRI-094915.network.com are 10.10.31.85. SMS_AMT_OPERATION_MANAGER 10/4/2010 1:50:22 PM 1300 (0x0514)

 

Try to use provisioning account to connect target machine BRI-094915.network.com... SMS_AMT_OPERATION_MANAGER 10/4/2010 1:50:22 PM 1300 (0x0514)

 

Fail to connect and get core version of machine BRI-094915.network.com using provisioning account # 0. SMS_AMT_OPERATION_MANAGER 10/4/2010 1:50:22 PM 1300 (0x0514)

 

Try to use default factory account to connect target machine BRI-094915.network.com... SMS_AMT_OPERATION_MANAGER 10/4/2010 1:50:22 PM 1300 (0x0514)

 

Fail to connect and get core version of machine BRI-094915.network.com using default factory account. SMS_AMT_OPERATION_MANAGER 10/4/2010 1:50:22 PM 1300 (0x0514)

 

Try to use provisioned account (random generated password) to connect target machine BRI-094915.network.com... SMS_AMT_OPERATION_MANAGER 10/4/2010 1:50:22 PM 1300 (0x0514)

 

Fail to connect and get core version of machine BRI-094915.network.com using provisioned account (random generated password). SMS_AMT_OPERATION_MANAGER 10/4/2010 1:50:22 PM 1300 (0x0514)

 

AMT Provision Worker: Send task BRI-094915.network.com to completion port SMS_AMT_OPERATION_MANAGER 10/4/2010 1:50:42 PM 19836 (0x4D7C)

 

Provision target is indicated with SMS resource id. (MachineId = 23433 BRI-094915.network.com) SMS_AMT_OPERATION_MANAGER 10/4/2010 1:50:42 PM 18096 (0x46B0)

 

The provision mode for device BRI-094915.network.com is 1. SMS_AMT_OPERATION_MANAGER 10/4/2010 1:50:42 PM 18096 (0x46B0)

 

The IP addresses of the host BRI-094915.network.com are 10.10.31.85. SMS_AMT_OPERATION_MANAGER 10/4/2010 1:50:42 PM 18096 (0x46B0)

 

Try to use provisioning account to connect target machine BRI-094915.network.com... SMS_AMT_OPERATION_MANAGER 10/4/2010 1:50:42 PM 18096 (0x46B0)

 

Fail to connect and get core version of machine BRI-094915.network.com using provisioning account # 0. SMS_AMT_OPERATION_MANAGER 10/4/2010 1:50:42 PM 18096 (0x46B0)

 

Try to use default factory account to connect target machine BRI-094915.network.com... SMS_AMT_OPERATION_MANAGER 10/4/2010 1:50:42 PM 18096 (0x46B0)

 

Fail to connect and get core version of machine BRI-094915.network.com using default factory account. SMS_AMT_OPERATION_MANAGER 10/4/2010 1:50:42 PM 18096 (0x46B0)

 

Try to use provisioned account (random generated password) to connect target machine BRI-094915.network.com... SMS_AMT_OPERATION_MANAGER 10/4/2010 1:50:42 PM 18096 (0x46B0)

 

Fail to connect and get core version of machine BRI-094915.network.com using provisioned account (random generated password). SMS_AMT_OPERATION_MANAGER 10/4/2010 1:50:42 PM 18096 (0x46B0)

 

AMT Provision Worker: Send task BRI-094915.network.com to completion port SMS_AMT_OPERATION_MANAGER 10/4/2010 1:51:02 PM 19836 (0x4D7C)

 

Provision target is indicated with SMS resource id. (MachineId = 23433 BRI-094915.network.com) SMS_AMT_OPERATION_MANAGER 10/4/2010 1:51:02 PM 1300 (0x0514)

 

The provision mode for device BRI-094915.network.com is 1. SMS_AMT_OPERATION_MANAGER 10/4/2010 1:51:02 PM 1300 (0x0514)

 

The IP addresses of the host BRI-094915.network.com are 10.10.31.85. SMS_AMT_OPERATION_MANAGER 10/4/2010 1:51:02 PM 1300 (0x0514)

 

Try to use provisioning account to connect target machine BRI-094915.network.com... SMS_AMT_OPERATION_MANAGER 10/4/2010 1:51:02 PM 1300 (0x0514)

 

Fail to connect and get core version of machine BRI-094915.network.com using provisioning account # 0. SMS_AMT_OPERATION_MANAGER 10/4/2010 1:51:02 PM 1300 (0x0514)

 

Try to use default factory account to connect target machine BRI-094915.network.com... SMS_AMT_OPERATION_MANAGER 10/4/2010 1:51:02 PM 1300 (0x0514)

 

Fail to connect and get core version of machine BRI-094915.network.com using default factory account. SMS_AMT_OPERATION_MANAGER 10/4/2010 1:51:02 PM 1300 (0x0514)

 

Try to use provisioned account (random generated password) to connect target machine BRI-094915.network.com... SMS_AMT_OPERATION_MANAGER 10/4/2010 1:51:02 PM 1300 (0x0514)

 

Fail to connect and get core version of machine BRI-094915.network.com using provisioned account (random generated password). SMS_AMT_OPERATION_MANAGER 10/4/2010 1:51:02 PM 1300 (0x0514)

 

AMT Provision Worker: Send task BRI-094915.network.com to completion port SMS_AMT_OPERATION_MANAGER 10/4/2010 1:51:22 PM 19836 (0x4D7C)

 

Provision target is indicated with SMS resource id. (MachineId = 23433 BRI-094915.network.com) SMS_AMT_OPERATION_MANAGER 10/4/2010 1:51:22 PM 14468 (0x3884)

 

The provision mode for device BRI-094915.network.com is 1. SMS_AMT_OPERATION_MANAGER 10/4/2010 1:51:22 PM 14468 (0x3884)

 

The IP addresses of the host BRI-094915.network.com are 10.10.31.85. SMS_AMT_OPERATION_MANAGER 10/4/2010 1:51:22 PM 14468 (0x3884)

 

Try to use provisioning account to connect target machine BRI-094915.network.com... SMS_AMT_OPERATION_MANAGER 10/4/2010 1:51:22 PM 14468 (0x3884)

 

Fail to connect and get core version of machine BRI-094915.network.com using provisioning account # 0. SMS_AMT_OPERATION_MANAGER 10/4/2010 1:51:22 PM 14468 (0x3884)

 

Try to use default factory account to connect target machine BRI-094915.network.com... SMS_AMT_OPERATION_MANAGER 10/4/2010 1:51:22 PM 14468 (0x3884)

 

Fail to connect and get core version of machine BRI-094915.network.com using default factory account. SMS_AMT_OPERATION_MANAGER 10/4/2010 1:51:22 PM 14468 (0x3884)

 

Try to use provisioned account (random generated password) to connect target machine BRI-094915.network.com... SMS_AMT_OPERATION_MANAGER 10/4/2010 1:51:22 PM 14468 (0x3884)

 

Fail to connect and get core version of machine BRI-094915.network.com using provisioned account (random generated password). SMS_AMT_OPERATION_MANAGER 10/4/2010 1:51:22 PM 14468 (0x3884)

 

STATMSG: ID=7212 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_AMT_OPERATION_MANAGER" SYS=WFD-SCCM001 SITE=WFD PID=3396 TID=14468 GMTDATE=Mon Oct 04 17:51:22.840 2010 ISTR0="BRI-094915.network.com" ISTR1="0x 0" ISTR2="Can NOT establish connection with target device." ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8="" ISTR9="" NUMATTRS=0 SMS_AMT_OPERATION_MANAGER 10/4/2010 1:51:22 PM 14468 (0x3884)

If I reset BIOS and unplug machine as well as going into mebex and full un-provision they will provision and work. I can not go to each end site to lay hands on to make this work.

Any ideas?

Thanks.

0 Kudos

Link Copied

1 Reply
idata
Employee
‎10-25-2010 03:16 PM
458 Views

so there are a few questions on the environment but I will say that since you did a full un-provision thru MEBX and it did work, did you try using the inbound tool Unprovision., its part of the ME Intel SDK fond here - http://software.intel.com/en-us/articles/download-the-latest-intel-amt-software-development-kit-sdk/ http://software.intel.com/en-us/articles/download-the-latest-intel-amt-software-development-kit-sdk/

That said, what consoel version are you using to provision the platforms.

Can you ping the FQDN name? same with the IP address of the same system - potential option 15 in DHCP mismatch?

I am also concerned with the use of a space in the name - 23433 BRI-094915.network.com. of the system. that is why I'm asking if you can ping the FQDN. I know the list of characters that are not valid but do not find any reference to the use of a space. will keep looking on that practice. it may be aceptable for the DNS but coudl have an issue with the provisioning console, anothe rreason I need to knowthat.

we tested the space in the name and it did respond to ping that way. so I would still consider using the unprovision.exe in the SDK I listed - that will allow you to remotely reset all the platforms without touching them. Since the 3.2.20 FW is on the systems i am wondering when and how you updated the FW it is possible the ME did not reset properly upon the update. by doing the unprovision locally your resetting the FW - our remote tool should be able to do the same only remotely

0 Kudos
Copy link
Reply

Community support is provided during standard business hours (Monday to Friday 7AM - 5PM PST). 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.