Thanks, I'll have a look at that tomorrow, the UEFITool looks new to me.

So I've just been running through the Clean process on my spi.bin file, built "outimage.bin", it's smaller in size than my dumped image, 7664K instead of 32768K, expected? Is this because it's been cleaned of data?

Step 15 on your Clean instructions says 'once your new cleaned+configured SPI/BIOS dump or Engine region is flashed on the target system...', can I check that the command you'd run would be

fptw64 -f outimage.bin
 

followed by shutdown, remove the jumper, boot then run "fptw64 -greset"

Thanks again.

Zitat von plutomaniac im Beitrag #18

---

Zitat von osk866 im Beitrag #17

---

So I've just been running through the Clean process on my spi.bin file, built "outimage.bin", it's smaller in size than my dumped image, 7664K instead of 32768K, expected? Is this because it's been cleaned of data?

---

No, you've done something wrong. The resulting size should be 32MB in your case. I assume you have wrongfully enabled Number of Components to 0 or similar. The guide never says to set that when working with full SPI/BIOS images.

---

I found this thread when I was trying to figure out why my Optiplex 5070 didn't have KVM capabilities in the MEB.

I've read through this and downloaded version 12 of the tools. If I'm understanding what I've read correctly, if I'm only trying to enable the full AMT for just this system I don't need to do any of the cleanup, I just need to extract my current spi.bin, update the fields in FIT, then flash just the updated spi.bin.

After going through the correct section I find I still have the same issue. I have the following from ME Analyzer:

╔═════════════════════════════════════════════╗
║ spi.bin (1/1) ║
╟─────────────────────────────┬───────────────╢
║ Family │ CSE ME ║
╟─────────────────────────────┼───────────────╢
║ Version │ 12.0.81.1753 ║
╟─────────────────────────────┼───────────────╢
║ Release │ Production ║
╟─────────────────────────────┼───────────────╢
║ Type │ Extracted ║
╟─────────────────────────────┼───────────────╢
║ SKU │ Corporate H ║
╟─────────────────────────────┼───────────────╢
║ Chipset │ CNP/CMP-H B,A ║

The closest RGN file is 12.0.70.1652_COR_H_BA_PRD_RGN.bin, there isn't a RGN file for 12.0.81.1753 in the repository. Is the "BA" in the filename for the Chipst?

Updated:

I checked the closest file in ME Analyzer and the ARB Security Version number and Version Control Number are different as are Size. The other differences I would expect, such as Type (Stock vs. Extracted), FWUpdate Support (Impossible vs. No), Date, File System State (Initialized vs. Unconfigured) Flash Image Tool (12.0.33.1442 vs. missing completely), and Latest (Yes vs. No).

Okay, I followed the steps and generated the new .bin and programmed it. I shutdown, removed the jumper, powered back up and did the -greset. That caused the system to reboot after it completed and I then went in and reconfigured the ME.

After that I connected using MessCommander and the option for Remote Desktop was there but disabled. I enabled it and was able to connect.

Thanks again for your help!

Zitat von alphasite im Beitrag #25

---

removed the jumper

---