@jflippen okay sounds good i will do that with our dhcp servers as well, they are 2016 though. Also you stated the thing about doing sysprep, is there any big benefit to doing sysprep before capturing the image? is it just since its a new windows experience everytime(is that the only benefit)? We use FOG for our computers in house but when i do sysprep it basically just adds a couple more steps so it doesn’t help me unless there is something major that im missing.
Posts made by lschnider
-
RE: Dell Latitude 5590 issues after imaging
-
RE: Dell Latitude 5590 issues after imaging
@george1421 @jflippen so when i create the base image in virtualbox as efi, i do sysprep and then turn of efi, do i need to change my dhcp server back to undionly.kpxe boot file to take the image from virtualbox as legacy and then change to ipxe.efi to push the image out to the uefi laptop?
-
RE: Dell Latitude 5590 issues after imaging
@george1421 actually i think it was an issue with the way our dhcp server replicates the backup, for some reason the primary changed itself back to undionly.kpxe when i changed that the second time, it started working and can boot into fog. now i will create my efi image and test it to see if it works.
-
RE: Dell Latitude 5590 issues after imaging
@george1421 we do have 2 dhcp servers but i made sure i changed that setting on both.
-
RE: Dell Latitude 5590 issues after imaging
@george1421 okay i might try to follow that tutorial, so for now i changed the option 067 boot file name to ipxe.efi and changed all the appropriate settings on the laptop. and then heres how it goes. it says checking media presence>media present>start pxe over IPv4>station ip is 10.2.227.200>nbp file name is undionly.kpxe> nbp file size is 97003 bytes>downloaded nbp successfully> then it doesnt boot into fog or anything
Im not sure where its getting the filename undionly.kpxe unless you have to change it in multiple spots. -
RE: Dell Latitude 5590 issues after imaging
@jflippen said in Dell Latitude 5590 issues after imaging:
you need to use ipxe.efi as your boot file
So we also have some HP’s that i have setup for legacy and they work great, does that mean when im going to image a legacy bios i have to change the dhcp boot file to undionly.kpxe for those and then to ipxe.efi for the uefi computers?
@Sebastian-Roth @george1421 -
RE: Dell Latitude 5590 issues after imaging
@jflippen thats what i did, i created a base image in virtual box but i didnt do it in efi setting from virtual box. Just to make sure we are talking about the same thing, in virtual box machine go to settings>system>extended features and check enable efi(special OSes only) correct? Also i never have been able to get these laptops to pxe boot in UEFI. where do you enable IPv4 in UEFI
-
Dell Latitude 5590 issues after imaging
I was able to send the image out to the laptop but I had to change bios setting to be able to PXE boot, the settings i changed were: I turned off secure boot, enabled Legacy ROM, and changed from UEFI boot to Legacy boot.
This laptop has an M.2 Card SATA. After i changed those settings, i was able to pxe boot and i did a full registration and deployed the image to the computer, but after it pushed the image out. The computer said no bootable device. so i changed the bios settings back to the way they were and still the same thing, its like it cant find the m2 card. -
RE: Could not mount images folder Error
@george1421 i actually dont need it enabled, i went ahead and set it to disabled permanently. I am now having a different issue but i will start a new discussion for that.
-
RE: Could not mount images folder Error
@Sebastian-Roth turns out that the RAM on the physical machine was actually bad.
-
RE: Could not mount images folder Error
@george1421 @Sebastian-Roth so i was able to capture and deploy an image. but i am only open to do it with the firewall turned off, i followed the tutorial again but cant seems to find what im missing on the firewall.
-
RE: Could not mount images folder Error
@george1421 the target computer had windows7 english on it before pushing out a new image.
-
RE: Could not mount images folder Error
@Sebastian-Roth So the image i captured was off of a VM and it has 8 gb of RAM allotted to it, but it let me capture it perfectly fine. But when i deploy the image is where its having issues. I’m also deploying to a physical machine. and it has 12 gb of RAM.
-
RE: Could not mount images folder Error
@george1421 it seems like its not creating a partition big enough when wiping the drive and then creating the partition to write the image to.
-
RE: Could not mount images folder Error
@george1421 just kidding, i was being dumb.
Yes that file is there. -
RE: Could not mount images folder Error
@george1421 How would i go about browsing to that folder. /images isnt showing anywhere.
-
RE: Could not mount images folder Error
@george1421 Okay i followed your tutorial and made sure everything was done correctly. Now i am able to capture an image with no problem but im getting a different error when trying to deploy an image.
I have tried two different hard drives, and the second one was a blank 500gb ssd. Both hard drives said the exact same free space.
-
RE: Could not mount images folder Error
@george1421 okay i tried to ftp and it says
I will try to get a picture of that error you asked about earlier.
-
RE: Could not mount images folder Error
@george1421 no i dont believe i have. Is there a way to tell if the password is like it should be?
-
RE: Could not mount images folder Error
@george1421 The date/time was wrong. I fixed that, i will try to run the capture again.