Focus is on how to self-activate your Intel® vPro™ Technology.
Hi Dan,
We have a couple of resources for USB provisioning. tcduncan just posted a USB key provisioning tool over the weekend at http://communities.intel.com/docs/DOC-1430. There are also some guidelines for configuring the keys and knowing which ones to use with the different PC manufacturers in the Known Issues and Best Practices wiki at http://communities.intel.com/docs/DOC-1247. Please let me know if this does not solve your problem - I'm always looking to grow this document and am happy to research issues.
Thanks!
Michele
Download the Intel AMT SDK from here: http://softwarecommunity.intel.com/articles/eng/1023.htm
The USBfile utility included in the SDK allows you to create the key that you described. The readme.txt includes instructions to use the tool.
i downloaded the 3.0 sdk and can't seem to find any usbfile utility
The readme.txt is here:
Intel_AMT_Release_3.0_148862\Windows\Intel AMT SDK\Samples\Configuration\USBFile
The executable is here:
intel_amt_release_3.0_148862\windows\intel amt sdk\bin\configuration\configscripts
thanks, i found it just after submitting my last comment. will give it a try
i played with usbfile and the creat_usbfile script and both provide good insight into their use. i found an anomaly, however. if i use usbfile.exe to create a single psk (no -gen option) and therefore non-consumable key set, it works as advertised. the problem is that it does not generate the xml file (using -xml option) that i can then import into the scs. is there any way to make it generate the file to then add to the repository?
The SCS does not support xml file import. SCS supports setup.bin file import only. Do you still need an xml file for the single non-consumable key given this information?
i was not aware that the setup.bin could be imported directly into scs. so, no, i do not believe there is a need for xml import. as long as there is an easy way for the credentials created by the tool to be imported into scs, that is all that is needed
thanks
i have not found documentation or guides on properly configuring a usb key for provisioning multiple vpro desktops with a single issued certificate key. the goal is to issue a key with a vpro management console and then use the same key on more than one desktop. when i try it, the first desktop removes the key after provisioning itself so it is no longer available. i will appreciate any feedback on how to do this
regards
dan felman
dan.felman@hp.com