Idid try cloning the SATA to the NVMe (I use Macrium Reflect from a bootable USB stick) and Macrium sees the SATA drive as having 2 dynamic partitions. When I drag them to the NVMe to clone, Macrium shows them as normal partitions. After the clone, though, the system will not boot from the NVMe as it does not see any file system on it.
Do yourself a favor and just do a clean install of Windows, re-install the tax software, and learn how to bring over the appropriate files. Then, install Veeam Endpoint and get a good backup of that system ongoing.
I do it all the time. The BIOS still allows the change.
Bad info. Sorry- 7060 does not allow legacy.
Try doing the win10 upgrade and gpt change on the 7010. Then clone it to an SSD then put into the 7060.
MMTool loads uCodes as you feed, so if you leave some in, the new will be inserted under that. If updating them all, I always leave one, then remove all below it, then insert the newer one of the last remaining, then delete it (same method used to ensure whichever you want is first/at top)
What you asked about in regards to the various volumes (like 0A only having three entries), this is normal, these are all different BIOS volumes. Open BIOS in UEFITool and you will see as you expand the volumes.
Be VERY careful what you edit in this BIOS, I see at the BIOS side Intel Boot Guard profile #5 FVME is enabled, so I assume Measured or Verified Boot is enabled and key burned into the PCH FPF fuses, so you can ONLY edit areas of the BIOS not colored when looking at BIOS with UEFITool NE Alpha 51 or above)
This can be confirmed with this command, ran from V12 ME Info from the ME System tool v12 package (link below, tools in section "C") >> MEInfowin.exe -verbose
@DeathBringer I have just finished preparing a bootable USB drive as per instructions and was going to attempt to show you information from CHIPSEC as requested.
However upon powering on the 35w 7060 refurb board (first time boot for this board) I was confronted with the Dell Service Menu as shown below :
Also watch for padding above/below microcode modules and FIT module, if they are there in stock they must be there when you are done. If they are missing in stock they should not be added when you are done.
I grabbed your FULLDUMP.BIN ONLY updated CPU microcodes (Added x2 + UPD All to 1/9/2020 version) using MMTool 5.02.0024, then FIT was fixed by MMTool on rebuild, nothing else was updated or touched - Did not touch ME FW/PMC etc
I would do it differently if done manually, probably just like DeathBringer did, I only used MMTool because you said you had issue so I wanted to check to confirm if using .0024 all was OK and it was
I've created this image (golden image or clone) on the same hardware (not that it matters w/ sysprep). I then sysprep the machine and shut it down. Next I take an image of this machine to clone on the other machines.
Next on the new desktop to be cloned, I go into UEFI and change to UEFI mode with secureboot OFF and storage to AHCI. Then I reboot into Clonezilla and restore the disk image to the new machine. It restores fine but when I reboot I get: Inaccessible Boot Device" and the machine crashes. This image has worked on dozens of prior Dell Optiplex 7060's.
I am slightly resurrecting this post because I continue to have this issue. I have just completed the upgrade for the SDA to 7.2.97. I was hoping that upgrading to the latest version would be something different for Dell Optiplex 5060 and 7060 machines with a boot manager password. But, I still get a pxelogin.php message after inputting the boot manage password. I can image Optiplex 5050 with no issues. I am using the same port. I am using a newer KBE I created in August for both. Any other ideas from the great Kace crowd would be helpful. Thanks.
We have had some issues it seems with the 7060's. It was hit and mis. I uploaded the nic drivers to the \\k2000ip\drivers\kbe_windows_x64\custom\7060\Network folder. You can download them from the Dell website. I had to recreate my KBE environment that we use to the latest version for our Win10 v1809. Once I completed this, the issue stopped.
If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
At this point I've tried to image with the boot sequence set to Legacy and I've tried it in UEFI as well and both give the same result. In the format boot sequence of MDT by default it formats BIOS and I've even gone so far as to swap the boot formatting scripts in MDT to "trick" it into formatting UEFI and even that didn't work, still same result of the computer not recognizing or detecting that there is a valid boot partition at all.
Thanks for trying to help me with this. This issue is only on the Dell Optiplex 7060 desktop model. Every other system we have done doesn't have the problem. Optiplex 7010, 7050, 7090 and a multitude of Latitude laptops have no issues whatsoever with MDT image deployment. I've contacted Dell support to try and get some information and all they had was a generic response stating that "It seems to be a software issue" and to get help I can pay for such and such support plan.
This is a frustrating problem because my employer had purchased an entire computer lab's worth (32 units) of these Optiplex 7060's and we can't get them to image properly so the students are stuck using the old computers until we can get this figured out. Another solution that I tried was imaging the system with an OS post-install step in MDT called "Convert MBR to GPT" which runs an executable thats built into the System32 folder in Windows that essentially swaps the boot formatting from BIOS to UEFI. This did work but made the systems unstable and they would BSOD so it wasn't a viable solution at all.
A helpful video about Dell device for your reference. Please make sure the BIOS time is correct.
How To Fix Dell Computer Hard Drive Not Detected / Hard Drive Not Found / Hard Drive Not Installed
Does the image you're deploying include the right storage driver for the target? I had similar issue with the 7080. Looks like the 7060 is the same. The Intel Rapid Storage Driver is required on the deployed machine so it can recognize the SSD storage
In our Project TinyMiniMicro series, we are looking at systems from major vendors that occupy around 1L in space. This segment was largely enabled by the 35W TDP CPUs that helped keep power and noise down for offices. Over time, customers asked for more performance both from higher-end GPUs but also moving to standard desktop CPUs. As a result, we get systems like the Dell OptiPlex 7060 Micro we are looking at in this article.
In Project TinyMiniMicro we are purchasing a large number of these devices from different sources. While a standard STH review is of a new product, these TMM nodes occasionally have specs that differ from what one would expect. In all of these pieces, we are going to talk about what makes the nodes unique. We are now well over 20 different nodes to increase diversity. We are testing these on a more circular economy/ extended lifecycle basis to see how they can be deployed after their initial use as corporate desktops.
The purpose of purchasing this particular unit is that we wanted to see the impact of having a 65W TDP desktop part in one of these nodes since most of the units we have been looking at utilize lower power 35W TDP CPUs.
We are going to go into the hardware overview, then into the key specs. We are then going to talk a bit about performance and power consumption before getting to our lessons learned from these units and our final words.
In the front of the chassis, we get headphone/ mic jacks as well as two USB ports. One is a USB 3.1 Gen1 Type-A port and the other is a USB 3.1 Gen2 Type-C port that allows for 10Gbps devices to be connected. For a bit of comparison here, the Dell OptiPlex 3070 Micro we reviewed had two Type-A ports but the Dell OptiPlex 7070 Micro had a similar configuration. We prefer the versions with a higher-speed Type-C port.
On the rear of the unit, one gets two DisplayPort headers as standard. There is an optional slot above the NIC where ours has a VGA port for a third display output. That spot can also be blank, Serial, DP, HDMI, or Type-C. The NIC is an Intel i219LM instead of a Realtek unit on the lower-end system. This is required to support vPro.
We also have four USB Type-A ports. All four are Gen1 5Gbps ports. The 7070 Micro has two of these ports as 10Gbps Gen2 ports. 10Gbps ports are handy if you want to support fast USB storage devices such as the Icy Dock EZ-Adapter Ex MB931U-1VB U.2 to USB 3.2 Gen2 or the Crucial 1TB X8 USB 3.2 Gen2 SSD. The practical implication is that these ports offer speeds with sequential transfers almost twice that of SATA. One will finally notice that we have dual antenna headers in our unit. Dell has some nice WiFi antennas that have great mounting options, but our unit did not come with those.
Opening the system is done via a single thumbscrew. You can tell that this is a really well-designed system because that thumbscrew is retained on the chassis, there is no losing it. The fit and finish for the OptiPlex Micros are excellent with very smooth open/ close.
This hard SATA connector is located next to the space for the optional expansion slot. In our unit, we have a VGA header with the video port connected. One can see the internal Type-C port header labeled just above that.
3a8082e126