Currently Being Moderated
This is an archived version of the document. The current version can be viewed here.

SCCM SP1 / vPro Common Issues and Potential Resolutions

This is a living wiki to cover some of the more common configuration and setup issues that can cause SCCM SP1 and vPro interoperability issues. This is not a replacement for following steps defined in SCCM SP1 Help File Article: "Configuring Out of Band Management" or referencing the "Troubleshooting Out of Band Management" Article in the SCCM SP1 Help File.

 

 

 

 

 

 

 

 

 

 

Symptom: SCCM provisions a vPro Client successfully, but you are not able to invoke Collection power control operations or the Out of Band Console (does not connect)

 

 

Potential Root cause(s):

 

  • The current user logged on to the SCCM Console does not have sufficient right to perform the desired operation.

    • Verify that the user you are logged on with is listed or in a Kerberos group that is listed in the AMT User Account list. SCCM SP1 Help File Article: “How to Configure AMT Settings and AMT User Accounts"; Section: “To configure AMT settings and AMT User Accounts".

  • SCCM was unable to request or issue a Web Server Certificate on behalf of the vPro client during provision or the Web Server Certificates was issued to a different FQDN then the vPro Client.

    • Verify that you have created the Web Server Certificates template on your Certificate Authority and that your SCCM Primary Site Servers has the appropriate permission. SCCM SP1 Help File Article: "Step-by-Step Example Deployment of the PKI Certificates Required for AMT and Out of Band Management"; Section: "Preparing the Web Server Certificates for AMT-Based Computers".

    • Verify that you have configured the certificate template in the Out of Band Management Properties: General Tab. SCCM SP1 Help File Article: "How to Configure AMT Provisioning"; Section: "To configure the out of band management component for AMT provisioning"; Steps: 7-8.

 

 

 

 

 

 

 

 

 

 

Symptom: SCCM provisions a vPro Client successfully and you are able to invoke Collection based power operation; however, the Out of Band Console does not connect to the vPro Client.

 

 

Potential Root cause(s):

 

  • The current user logged on to the SCCM Console does not have sufficient right to perform the desired operation.

    • Verify that the user you are logged on with is listed or in a Kerberos group that is listed in the AMT User Account list. SCCM SP1 Help File Article: “How to Configure AMT Settings and AMT User Accounts"; Section: “To configure AMT settings and AMT User Accounts".
                SCCM has not be granted full control permissions on the out of band management OU

    • Verify that the SCCM Primary Site Servers has been granted full control permissions on the out of band management OU. SCCM SP1 Help File Article: "How to Prepare Active Directory Domain Services for Out of Band Management“

 

 

 

 

 

 

 

 

 

 

Symptom: I can not seem to get my vPro clients with firmware version less than 3.2.1 to provision or managed through SCCM.

 

 

Potential Root cause(s):

 

  • SCCM SP1 only natively supports vPro clients that are firmware version 3.2.1 or higher; to support vPro clients that have firmware versions less then 3.2.1 you are required to install and configure the Intel WS-MAN Translator.

    • Verify that you have installed and configured WS-MAN Translator properly. Please reference the following blog on how to configure and install the Intel WS-MAN Translator.

 

 

 

 

 

 

 

 

 

 

Symptom: When I do a "Discovery of Management Controller" within SCCM on a vPro client, on an entire collection, or as part of a Network Discovery, it does not appear to provision the vPro client.

 

 

Potential Root cause(s):

 

  • Performing a Discovery of Management Controller only determines if the vPro client is able to be provisioned. You still need to provision the vPro client either through the Out of Band Import Wizard or through the Client Agent.

 

 

 

 

 

 

 

 

 

 

Symptom: I recieve the following the message when I try to provision a vPro Client; "Warning: AMT device is a SMS client. Reject hello message to provision".

 

 

Potential Root cause(s):

 

 

 

 

 

 

 

 

 

 

 

Symptom: The AMT status states that it is "Detected" instead of "Not Provisioned" and I can not provision it.

 

 

Potential Root cause(s):

 

  • The Out of Band Service Point is able to determine that the client is AMT/vPro capable; however, it does not does know the AMT Remote Admin or the MEBx account password.

    • Verify that your AMT Remote Admin or the MEBx account are either "admin" (factory default) or what you have configured as the MEBx password in the Component Configuration -> Out of Band Management. The vPro MEBx password can be reset by logging into the MEBx local on the vPro client (via the ctrl-p during post) while the remote admin password can be reset by performing a full unprovision within MEBx.

 

 

 

 

 

 

 

 

 

 

Symptom: Not able to provision a vPro client through SCCM SP1 Client Agent based provision.

 

 

Potential Root cause(s):

 

  • The oobmgmt.log on the vPro Client states "AutoProvision policy disabled".

  • The oobmgmt.log on the vPro Client states "No compatible device detected".

    • Verify that the client you are trying to provision is vPro Client and that the AMT HECI driver is installed. HECI driver should be available from your OEM driver support website.

 

Comments

Delete Document

Are you sure you want to delete this document?