Intel vPro® Platform
Intel Manageability Forum (Intel® EMA, AMT, SCS & Manageability Commander)
Announcements
This community is designed for sharing of public information. Please do not share Intel or third-party confidential information here.
2616 Discussions

Failed connect provisining machine via OOB

idata
Community Manager
1,241 Views

Dear All,

I've configured SCCM with Vpro machine correctly. Few machine has been provisioned but when triying connect with OOB console i got error message as below;

[4][12/24/2010 11:34:25 AM] :GetAMTPowerState fail with result:0x80338126

[4][12/24/2010 11:34:25 AM] :GetAMTPowerState fail with result:0x80338126

[4][12/24/2010 11:34:25 AM] :GetAMTPowerState fail with result:0x80338126

[4][12/24/2010 11:34:25 AM] :GetAMTPowerState fail with result:0x80338126

[4][12/24/2010 11:34:25 AM] :GetAMTPowerState fail with result:0x80338126

[4][12/24/2010 11:34:25 AM] :GetAMTPowerState fail with result:0x80338126

[4][12/24/2010 11:34:25 AM] :GetAMTPowerState fail with result:0x80338126

[4][12/24/2010 11:34:25 AM] :GetAMTPowerState fail with result:0x80338126

[4][12/24/2010 11:34:25 AM] :GetAMTPowerState fail with result:0x80338126

[4][12/24/2010 11:34:25 AM] :GetAMTPowerState fail with result:0x80338126

[4][12/24/2010 11:34:25 AM] :GetAMTPowerState fail with result:0x80338126

[4][12/24/2010 11:34:25 AM] :GetAMTPowerState fail with result:0x80338126

I also check my token size at SCCM console the size is 1604. Attached full OOB log.

Please Advise,

Thanks,

mailto:ezzy25@gmail.com ezzy25@gmail.com

0 Kudos
1 Reply
idata
Community Manager
134 Views

The problem likely is something related to certificates.

Are you able to perform collection based power control commands against the client? You can test this by right clicking on a client, choosing the out-of-band management menu and then power control. Try turning the system on or off. If this works, that means that AMT has a good certificate. If it doesn't work, try accessing the WebUI on the system using it's FQDN and see if your browser gives you any certificate errors.

If the test above is successful, the problem is likely with the way your CA chain is trusted. You may need to put the certs for all of your CA's into the trusted root store on the system you are running the SCCM console app on. This would include any intermediary CA's (like policy CA's) as well as the actual issuing CA.

Reply