I am trying to image a lab of Dell Precision 1700's.
-
I am able to send the image up. I have to first turn off secure boot and turn on legacy roms. After I do this I am able to pxe boot. It appears that I am able to bring the image down to a new computer. However, the new computer will not boot. It reads “This computer needs to be repaired.”
Server
- FOG Version: 1.2.0
- OS: Win 10 Pro
Client
- Service Version:
- OS:
Description
-
Well a couple of things jump out at me in this post.
- Yes secure boot needs to be disabled otherwise the FOS Engine (the custom linux operating system that captures and deployed images will not be able to run). This is a given.
- For UEFI systems you must send the uefi iPXE menu kernel to the target computer. So for uefi systems you must send ipxe.efi and for bios (legacy) systems you must send undionly.kpxe to the target computer. Otherwise the FOG iPXE menu will never start. If you have a windows 2012 dhcp server then you can have this file name change happen automatically for you.
- How are you prepairing this computer for cloning? Are you syspreping it or just shutting it down, and then uploading your golden image or are you running sysprep to get this system ready for cloning?
Lets start with those questions.
-
As far as syspreping goes…I have not. I am new to this school district and they have not had to sysprep in the past. Since being here I have sent three images up. This being the 4th. Two of them I have brought back down without syspreping. One of the two was a cart of 30 computers.
-
@smazzola Is this the first uefi system you are attempting to image?
What value do you have in your dhcp system for dhcp option 67 {boot-file}?
-
Did you create your image on the source computer while it was in UEFI or Legacy mode?
Did you setup the destination computer’s BIOS to boot to match the mode the OS was created in?
[ Standing in between extinction in the cold and explosive radiating growth ]
-
@sudburr The questions you asked were exactly what I was thinking.
@smazzola I’ve actually seen the error the OP is describing before. I believe it happens when you take an image of a machine either in BIOS and deploying to UEFI, or taking the image in UEFI and deploying to BIOS. I’m pretty sure it’s the former but it’s been a good while since people at my work have made this sort of mistake. This sometimes is fine, and the image (if Windows) may even be able to repair itself (switch it’s disk from MBR to GPT, swap around other files).
For one, it sounds like you’ve not setup your DHCP to do both BIOS and UEFI, because you had to mess with the firmware settings to get it to upload. Follow this article and that will be fixed for you, you can upload in Legacy or UEFI after following this:
https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence
If you have issues with it, create a new thread, we will help. We’re good at this.Second, When you go about making an image, first decide if you want the image to be Legacy or UEFI, because it matters. It really sucks (and I speak from experience) when you don’t plan this out, and you end up having to go around manually changing the firmware setting on a thousand computers so that the new master image will work on them. Plan this out, build an image using the settings that all computers of that model already have. Then, your image will deploy to the others fine.
-
I created the image in UEFI mode. I had to turn on the Legacy Roms in order to get the device to pxe. However, I never took the device out of UEFI mode. I used the same settings on the machine I brought the image down to.
-
@smazzola said in I am trying to image a lab of Dell Precision 1700's.:
I created the image in UEFI mode. I had to turn on the Legacy Roms in order to get the device to pxe. However, I never took the device out of UEFI mode. I used the same settings on the machine I brought the image down to.
But, the image was captured in UEFI mode. This hasn’t changed. The destination computers must be configured in exactly the way the source computer was configured - before you changed things around - in order for the image to boot as expected on the destination computers.
Please read through my previous post.
