Success! Your solution of changing option #67 to ipxe.efi was correct. When I tried to implement it the first time, I inadvertently unchecked #66. Doesn’t work too well when there is no boot server address! LOL
Note: Undionly.kpxe doesn’t work with Windows 10 even if it is changed to Legacy boot mode. It has to be the ipxe.efi with Windows 10 in uefi boot mode.
Thank you!! You guys are the best!
I changed #67 to ipxe.efi and tried uploading an image from the Win10 client with “UEFI Only” chosen in the BIOS.
It showed, “TTFP …” and then went to a dark screen with a blinking cursor. I tried “Legacy Only”, and I also tried “Auto” where it would look at both modes. No dice, I’m afraid. So, I changed #67 back to “undionly.kpxe” so it would at least work with my Win7 population.
Thank you for responding! 
Points I didn’t clarify: My FOG “server” is not actually a server with RAID. It is an ordinary
computer with an Ubuntu 32-bit 16.04 installed and FOG installed. DHCP option is set for
“undionly.kpxe”. Also, the whole thing has worked fine up to now for my Windows 7 machines.
I’m able to register, upload an image, and farm out images without any problem.
The target computer is a Lenovo ThinkCentre M710S
It has a 1 TB 7200 RPM Sata hard drive.
It has 4 GBs of DDR4 RAM
Since it is not a Dell, I did not follow the advice given for step 2.
I hesitate to change option 67 to “ipxe.efi” because I don’t know if my Windows 7 machines will still
work with FOG if I do. We are just starting to convert to Windows 10, so I still have a huge family of
Windows 7 machines. My Windows 7 machines boot in legacy mode, so would FOG still work with
them if I change option 67 now?
The client computer has windows 10 version 1809, build 17763.557
The FOG server is a 32-bit Ubuntu 16.04 with Fog version 1.5.6
I changed Windows 10 to legacy boot mode to access the boot process
I was able to register the client machine with the FOG server, which shows they can communicate without a problem.
When the client machine is started, the pxe initiates normally and, when it sees there are no FOG commands, the white menu box appears with the default highlighted command being to boot from the hard drive, just like it normally does. The problem is that a black screen appears with a blinking cursor and remains indefinitely. There is no boot to the hard drive. If I boot and manually cancel the pxe boot with a keystroke, it has no problem booting from the hard drive. The problem seems to be with FOG correctly accessing the hard drive from its boot menu. Any ideas what to do?
@tom-elliott Wow, you’re awesome! We’re actually getting a new network because of E-Rate within the next month. I am logging your explanation/suggestions and will run this by the guys installing the switches. Thanks.
Yep, the “dumb mini-switch” eliminated the problem. So, if I carried around a small switch and plugged the network drop into it instead of directly into the clients, and then connected the clients to the dumb switch, that would work? I’d rather a permanent solution if possible.
I have FOG 1.5.2 on an UBUNTU server. When I try to register a client, however, I get:
Initializing random number generator.
Starting etho0 interface and waiting.
UDHCPC: started, v1.27.2
UDHCPC: sending discover
UDHCPC: sending discover
UDHCPC: sending discover
UDHCPC: no lease, failing
I tried researching on my own. I read somewhere that the original kernel 1.2.0 didn’t have this problem, but the newer ones do for some reason. How do I deal with this? My skills are very limited so I need a “solution for dummies”.
@Wayne-Workman I got a newer and more powerful machine. It is a 64 bit Dell Vostro with a 200 GB hard drive and 4 GB of Ram. I installed Ubuntu 16.10 and then FOG 1.3.0.
I was able to create an image container in FOG and register my host machine without a problem. I created a task to upload an image. It triggered the pixie boot in my host machine. As it was booting, everything appeared to be going well. All I saw was “ok” or “done” for every step of the process. When it went to the upload screen, however, it once again froze near the end of “creating a bitmap” and flashed an error message. I have attached a .jpg of it.
I would never “yell” at a person who - A - is kind enough to take the time to respond to my pleas for help and - B - has probably forgotten more about this stuff than I’ll ever know. LoL Believe me, I’m “Special Needs” compared to you guys.
I ran the command and the following appeared:
fog@fog-OptiPlex-745:~$ df -h
Filesystem Size Used Avail Use% Mounted on
udev 728M 0 728M 0% /dev
tmpfs 150M 17M 134M 11% /run
/dev/sda1 145G 6.4G 131G 5% /
tmpfs 748M 152K 748M 1% /dev/shm
tmpfs 5.0M 4.0K 5.0M 1% /run/lock
tmpfs 748M 0 748M 0% /sys/fs/cgroup
tmpfs 150M 108K 150M 1% /run/user/1000
fog@fog-OptiPlex-745:~$
I’m using a very old Dell 32 bit 745 Optiplex, and it only has a 70 GB drive.
Mod edited to use code boxes.
I followed the directions and installed fog with the configuration as directed. The client can be registered to fog even though I received an error message in the process. I was able to create an Image container on fog, and I was able to see the test machine there. I was able to create a task to have the client machine send up it’s Mint setup as an image to fog.
The problem: When I finished the task, a command was successfully sent to the client machine and it turned on. After spinning at DHCP for about a minute and a half, the following occurred:
udhcpc started
sending discover …
sending discover …
sending discover …
no lease, failing
After three cycles of this, it actually advanced to the upload image screen and started “Calculating Bitmap Process”. It reached 94.36% and froze:
An error has been detected.
Failed to complete capture (save partition)
Args passed /dev/sd.1 1 /images/002622f3573b all
I don’t know what to do now.
I have Ubuntu 16.10 installed on a Dell 32 bit 745 OptiPlex with 3 GB of memory. I have FOG 1.3.0 installed also on the machine.
This FOG server is NOT on the network, otherwise I could use DHCP to set up the 066 and 067 commands and then the scope, and my clients would be directed to the FOG server and download the correct file.
This FOG server is connected to a switch, and the clients will be connected to the switch. I want the clients to see the FOG server, show the menu, and pixie boot correctly. So far, my clients see nothing. What do I do to rectify this?
We have an Ubuntu server that acts as a Remote FOG server, and we use it to image Toshiba Minis. After setting it up, connecting it to a switch, and testing it on a client, we discovered that upon booting the client, it cannot detect FOG on the Remote FOG server. It spins and times out. I tried a different switch and client just in case, but the results are the same. When I tried the clients on the FOG server hooked into our LAN, it detects FOG and will boot to FOG. Any ideas?