I am using the ACU Wizard to create a bootable USB stick to enable AMT on an HP Prodesk 800 G4 (can't manually enable as it's using MEBx v12 and I cannot find documentation on that version). I select the required options but when it starts, I get an error about half way through that says:
"Keys copied to the USB drive with the following error(s):The file is not located in the correct position on the USB drive (the first file on the drive). Click Ignore to continue or click Retry to reattempt copying the keys to the drive."
I've tried ignoring the error and it finishes, however the stick does not boot in any machine. I've tried Configurator Download Package 188.8.131.52 (newest) and v184.108.40.206 (the only other one I can find) and both produce the same error each time. I have tried multiple USB sticks both 3.0 and 2.0 with no luck.
I am not sure how to create these boot sticks at this point.
1) I downloaded the Configurator_download_package_220.127.116.11 Archive from https://www.intel.com/content/www/us/en/software/setup-configuration-software.html
2) I extracted the archive
3) Ran ACUWizard.exe as administrator
4) Selected "Create Settings to Configure Multiple Systems"
5) Selected the 'Tools' menu then 'Prepare a USB Key for Manual Configuration...'
6) Changed options to config shown above
7) Hit OK
Again, I tried the previous version of the Configurator with the same results.
I had actually thought about trying another laptop yesterday but got busy with another issue. I just tried on a Windows 7 64bit machine and it created the boot stick without any errors. Seems to be an issue with Windows 10 - I will try it again on another laptop with Win10 and see what happens.
Thanks for your assitance, Emeth!
Edit: I just tried another Windows 10 desktop and got the same error I was getting before. Seems this tool doesn't like Windows 10.
Sure, here are my system specs:
HP Elitebook 840 G4 Touch
Intel i7-7500U 2.7GHZ
Windows 10 1709
Windows ver. 16299.1004
Please let me know if you require further details.
I followed the instructions from one of Intel's AMT videos found at https://www.intel.com/content/www/us/en/support/articles/000026592/technologies.html - it specifically says that the host system does not need to be vPro enabled. Please see the attached screen shot.
Also, the system I was able to create the USB stick on is running an i5-6200U which is not vPro compatible either.
The computer I was trying to enable AMT on is an HP Prodesk 800 G4. I am able to access the MEBx and enable AMT (I think) but all efforts to connect to it remotely using Meshcommander are unsuccessful (can't authenticate). This is the reason I wanted to create the USB boot stick because that was the only option I had yet to try (won't even boot on that desktop by the way). This is an issue I'm working on with HP although they're not having much luck figuring that out either. Unless Intel happens to have updated documentation for the MEBx v.12 and higher.
We got a couple of your NUC devices (BLKNUCi5DNKPC1) and they couldn't have been easier to setup and connect to. I would love to replace all of our remote user equipment with those but I can't find any with dual display port connections as all our staff use those type of monitors.
Anyway, if you come up with any updates to the ACU wizard and would like me to test on my laptop to see if it works or not, just reply to this thread and I'll set aside some time to assist with that.
Yes, sorry missed your last comment. The USB stick is created and boots on the Prodesk I was working with. Didn't configure it properly but that's a separate issue. I still am not sure why I can't create them on my laptop but I have an alternative if needed.
Once I have the USB created, I haven't run into an issue booting AMT enabled systems (well I did with an HP desktop but I figured out that you had to specifically enable USB provisioning for AMT in the regular BIOS) but all systems I've been working on have the most up to date BIOS.
I just installed v18.104.22.168 and attempted to create a USB bootable stick. Unfortunately the application crashes about 20 seconds after starting. I tried a few times and it crashed each time. Is there a place where it generates logs I can send you?