@george1421 @Sebastian-Roth Just wanted to give you an update. From what I can tell, the section of dhcpd.conf where you declare options, was missing a } so the file wasn’t reading the options I guess? I compared the file to an old server and that was the only difference I could find. I probably deleted it while editing the file at some point. Works like a charm now.

Hello!

So, we just set up a fog server, and are capturing our first image off of it. The primary drive is encrypted with LUKS. It seems like the capture is reading that drive as being full, and as a result is having to check every block. This is causing the capture to take 12+ hours. Also, this creates a massive storage issue, as this image should only be 20GB tops but is populating as a full 250GB. Encrypting after the fact isn’t really an option. Am I screwed? Or does someone have a solution?

@george1421 Thank you, does this still apply with Linux and Mac?

Good morning,

We already use Fog for one of our customers, however they only utilize one type of laptop, and only windows. I was wondering, is it possible to capture an image from say, a teeny tiny dell laptop, and deploy that image to a much larger laptop from a different vendor? My concern is driver and hardware incompatibility. Basically, do I need to build a different image for each OS and each laptop variant we have? Or can I build the image off of my smallest drive available and deploy that to any computer? This significantly changes the amount of storage I need. Hope that makes sense, and thanks for any help.

@george1421 @Sebastian-Roth Just wanted to give you an update. From what I can tell, the section of dhcpd.conf where you declare options, was missing a } so the file wasn’t reading the options I guess? I compared the file to an old server and that was the only difference I could find. I probably deleted it while editing the file at some point. Works like a charm now.

@george1421 1. Yes. 2. No.
I only have an issue in UEFI. The laptops I need to image, do not have a legacy option. Why is the laptop, not able to pull from ipxe.efi? I am sorry, I just feel like we are on 2 different pages right now.

@george1421 So far, no.

@george1421 Just to clarify, the server is specifically not deploying to these laptops. We were able to deploy to laptops with legacy bios from the same location.

@george1421 The Fog server does have 2 interfaces, they are just using the same physical nic. So I looked through the pcap in Wireshark and came across the following.

Option (129-135)
Parameter Request List Item: PXE - undefined (Vendor Specific)
Option (60)
Vendor class identifier: PXEClient:Arch:00007:UNDI:003016

Does that ring any bells? Other than that I didnt find anything glaring. If you know of something specific to look for it would be helpful.

@george1421 The FOG Server is the DHCP server, it is an Ubuntu 18.04.5 VM hosted on ESXi 6.5, which is hosted on a Dell R340. 2 Interfaces across one physical NIC, one to the corporate network, and the other for PXE boot.

Good morning,

After a lot of trial and tribulation myself and a network engineer were able to get our Fog (Ubuntu 18.04) server to deploy to the location we need it to. Bad news, it is only deploying to legacy machines. The laptops we need to image are Panasonic CF-54 Toughbooks, and they are all UEFI. Secure boot is disabled. We finally managed to snag the pop up message and it read as follows.

Station IP address is 172.25.25.60
Server IP Address is 172.25.25.50
NBP filename is ipxe.efi
NBP filesize is 0 bytes
PXE-E99: Unexpected Network Error.

If anybody has a clue, please let me know because I am lost. Unfortunately, I cannot provide screenshots of the activity or provide logs.