Dell Latitude e5430 some image and some do not
-
Hello,
I am trying to image a group of Dell Latitude e5430 laptops and I am having an issue with about half of them not taking an image. They are all the same model so I am at a loss.
I am using the base image with Multiple Partition Image - Single Disk (Not Resizable) and I tried Single Disk - Resizable as well. Has anybody else come across a situation like this?
Please help.
Thank you,
Maria -
We need more details, what exactly isn’t working? What version of FOG? Post a picture of the issue if you can please.
-
I agree having a picture of the exact error will give us a better understanding of where (in the deployment process) the error is being generated.
-
Hello,
I am sorry I should have included more information.
I have FOG v 1.2.0 running on Ubuntu 14.04. The laptops are PXE booting into FOG and I am ale to answer the questions. When I reboot the devices will connect to FOG and it appears that they are going to image; however, when the imaging process is complete the devices are not imaged and the screen is like the one in the picture below. Like I said earlier, I have successfully imaged this same model on about 30 devices and I have about 20 that will not image.
Any help you can offer would be appreciated.
-
@maria_reed We still don’t know where it’s failing, we still don’t have any errors from the imaging process. Please sit down and watch the entire imaging process, be ready to jot down any errors - and where they happen. We need to know exactly where the failure point is. If a photo is possible, please take one.
-
@Wayne-Workman I agree what we are seeing in the picture below is the results of some error not what caused it. It could be (if the fog client is installed) that the fog client service was not disabled when the system was captured which caused the FOG client to do stuff while OOBE was running.
This error (based on the picture) could be a windows OOBE issue and not related to FOG pushing the image to the computer.
-
@maria_reed Given that it works fine on other models, I’m guessing the issue here will come down to drivers. Some of them likely have slightly different hardware (bluetooth tends to be a bitch here) that will cause BSODs/reboots, etc
If not drivers, then most likely something to do with the unattend.xml file.