Posts made by TBCS

To add a little bit more detail, we’ve imaged hundreds of machines and have only had this error on these.

I guess they’re technically Thinkpad Yoga 12s. We have to use an official lenovo ethernet adapter to image them.

When On UEFI, fog will be unable to mount the file system if a task is created.

When on BIOS, if a task is created, it hangs on init.xz.

I have a rather specific problem I’ll try to describe well. On SOME devices (not most of them) when attempting to PXE boot, it tries to boot from our SCCM server. We do not use SCCM for imaging, and the DHCP settings are set correctly on our DC. Both the devices that work, and those that don’t connect to the same DC in order to get the PXE DHCP information. We’ve imaged over 150 machines and captured many images, so the settings work on most devices. Since I set up the Fog server, a colleague of mine has been working on setting up an SCCM server, and I’m concerned there may be some setting on that that is grabbing the PXE requests? This is a pretty specific problem and I’m not sure where to go for help on this. To recap:

• Fog has been working with no problems for months (both BIOS & UEFI after following these directions: https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence)
• Since the Fog server was created, a colleague has been in the process of creating an SCCM server on our network
• On a handful of machines, when trying to PXE boot it lists the SCCM server’s IP and not the Fog server IP
• When looking at the DHCP settings on our DC, the SCCM server’s IP is nowhere to be found
• I’ve tried updating the BIOS on the affected machines and it doesn’t seem to make a difference

It works great after a BIOS Update. George you are so incredibly helpful. If I could send you cookies I would.

I’m running 1.5.5. I’ll try updating the firmware and get back to you on whether that makes a difference.

Having issues with this Lenovo Yoga 12. I get the exact same message regardless of legacy boot turned on or off. I followed this guide for Windows Server 2012, although looking at other posts I see some people have an entry for PXEClient:Arch:00000 which the Server 2012 guide doesn’t include, so I also didn’t include. How can I figure out this specific vendor ID to try other boot loaders? Or is that even what I should do?

@george1421 That was a really helpful guide. Easy to follow and now we’re ready for whatever type of boot we need.

Ok that makes sense, the boot loader (DHCP 067) is the part that I was the least familiar about (basically I just knew that I needed to write undionly.kpxe in there and didn’t really know what it meant). That makes a lot of sense when you put it that way. Thanks for your help!

So when I try to PXE boot, the Surface Pro 6 tells me roughly

Start PXE Boot from IPv4
Correct IP
Undionly.kpxe
Downloading NBP File
File Downloaded successfully

But then it just moves on. No error message, just a restart. Does anyone have any ideas for me? I’m very new to FOG and have had no trouble with any other machines I’ve tested it on.