Microsoft* has complete and up-to-date documentation on the Microsoft TechNet site: http://technet.microsoft.com/en-us/library/cc161989.aspx http://technet.microsoft.com/en-us/library/cc161989.aspx.
You might want to look at the guide Intel put together for Microsoft* ConfigMgr SP2 here: /docs/DOC-5973 http://communities.intel.com/docs/DOC-5973
Or take a look at the older training video for Microsoft* ConfigMgr SP1 here: http://www.vproexpert.com/sccm_vpro/introduction/introduction.html http://www.vproexpert.com/sccm_vpro/introduction/introduction.html
Intel introduced "Host Based Configuration" this year to simplify the setup and configuration of Intel AMT 6.2 and 7.0 and later systems. Look here for the latest on this new feature: /docs/DOC-6474 http://communities.intel.com/docs/DOC-6474
We got the new certificate from verisign which was successfully imported into our SCCM server. Also this certificate was exported to create a .pfx file. A certificate template was created successfully from the Enterprise CA Server. Thereafter when we are trying to configure OOB Management Properties, we are getting the below error while browsing the AMT Provisioning Certificate.
The error is " The input certificate is not a valid AMT provisioning certificate, Please check your certificate file. This certificate was purchased from verisign for the v-pro setup.
Exactly the same error message here - certificate ordered via verisign, document followed to the tee and getting the same message as above.
Did you ever get this resolved?
Let's take a look at how the provisioning certificates you have are built. First, verify that it has the proper object identifier set. It should be: 2.16.840.1.1137126.96.36.199. You can verify this by looking at the certificate details under and looking at the certificate policies field. In addition, also check the subject field in this same view. You should also see the following OU listed:
OU = Intel(R) Client Setup Certificate
Be sure to check both the spelling and placement of spaces.