@george1421 Hello. When I referred to the image as “raw” it just means it’s the image I created without the sysprep. I always put a “raw” image so when I go to update the computers next year I do not have to start fresh. I can load that “raw” image onto a machine and make the changes I want and then upload a “final” image which is the one that is syspreped and ready to go.

When I put the image back onto a computer it took a matter of minutes, so that is fine. I can live with my “raw” image taking awhile to upload to FOG.

SOLVED IT

Thank you for all of your help. You guys were on the right track when you told me to try a different option 67. I, however, was not putting the option in the right scope. I was putting it in the default server options when I should have been putting it into our Tech LAN scope. Once I went into this scope and changed it to realtek.pxe and tried to boot the Lenovo Z-50 booted up just fine.

I’m learning a good deal about how the last person had our network set up every day. Check another thing off my list.

Question: Does the realtek.pxe take longer to work with imagines that the other? Usually, I can get an image done in a matter of minutes but I am uploading my raw file to FOG and I’m already at the 33-minute mark and it says there are 17 minutes left to go.

@Tom-Elliott Secure Boot was set to disable. I do see that under it says Secure Boot Status and that says Enabled. However, you can’t highlight the Secure Boot Status to change it. The BIOS is also updated to the most recent posted on Lenovo’s website.

@Tom-Elliott I went ahead and switched the machine to UEFI and put in ipxe.efi as the file. I got a message that said “EFI Network 0 for IPv4 has been blocked by the current security policy.”

@george1421 Yes, when I refer to the same error its the one from the above picture regarding the DHCP. Here are some more things I tried.

1. Not sure if spanning tree is enabled or not, but I can take a look in a bit. I did, however, take a Netgear Fast Ethernet switch and plug it into my Ethernet port on my wall, then plugged the computer into the Netgear Fast Ethernet switch. I also removed option 66 and option 67 for this test. I still got the message about DHCP failing.

2. The network adapter is Realtek PCIe GBE Family Controller. Hardware IDs are:

• PCI\VEN_10EC&DEV_8168&SUBSYS_380B17AA&REV_10
• PCI\VEN_10EC&DEV_8168&SUBSYS_380B17AA
• PCI\VEN_10EC&DEV_8168&CC_020000
• PCI\VEN_10EC&DEV_8168&CC_0200

We were using KACE for our imaging service before moving to FOG but ran into the issue of our new Lenovo laptops ( Lenovo V3330-15IKB) not being able to boot into it. Because of this, we switched over to FOG. However, these white Lenovo laptops (Lenovo Z-50) could boot into KACE just fine. I’m almost thinking I might have to run both FOG and KACE. However, I would rather just use FOG.

Thank you for your help in trying to figure this puzzle out.

@Tom-Elliott Hello. I went into the DHCP settings and enabled 66 with our FOG’s IP address and then I went into option 67 and tried putting in ipxe.pxe and realtek.pxe. We are still getting the same issue come up.

@george1421 I went in and enabled option 66 with our fog server IP address and then enabled option 67 with value undionly.kpxe. I’m still getting the same message showing up.

@Tom-Elliott Hello Tom. Thank you for the quick reply. Trying ipxe.pxe and/or realtek.pxe was next on my list. However, the person who setup FOG for us on a Linux VM has left and I am not sure how to do it. I was going to do some more research on it to see if I could figure it out. If you have an article you can link to save me the Google search, I’d appreciate it. If not I’ll be looking it up and giving this a try tomorrow. Thanks again!

Every device we image has got along with fog just fine- except these Lenovo z-50s.
not sure what to do next.