I’ve tested and it still doesn’t copy the drivers when they are there?

Thanks @Tom-Elliott, I have successfully captured and deployed Debian 9 clients both in virtual space and to real hardware. So, it looks like your fix works. I did notice some slower booting as you mentioned but that seemed to be minimized after I went through a full capture-deploy-capture sequence. Perhaps there was residual file system ambiguities that was affecting the boot times. In any event, the boot times smoothed out over time. The only slightly odd thing I did notice is sometimes the client would boot twice before the capture would actually start. I cannot reproduce this all the time. Just thought I would mention it if it makes you think of anything.

Thanks again; will this fix make it into 1.4.5?

Two other things to check are the bios versions identical, and is secure boot on or off.

@BedCruncher Maybe DNS handling in FOS is better than how it’s being handled when the OS is opened?

@Tom-Elliott
That did the trick, thanks!

@misaina said in Problem bootPXE Fog : Please enter tftp server:

Please enter tftp server

This usually means you don’t have your dhcp server setup correctly. What precisely do you have setup for dhcp option 66 {next-server} and dhcp option 67 {boot-file} ?

At this prompt “Please enter tftp server” if you key in the IP address of your FOG server you should see the FOG iPXE menu. This is not a solution just a test to prove you have something setup not right with dhcp.

@george1421
Hi George,
Thanks for your reply.
I had no infos in the apache logs, so i think you right there was a redirection.
So, i just uninstalled manually fog (mv /var/www/fog to fog.bak & /opt/fog to opt.bak), uninstall mysql with apt-get purge mysql-* and reinstall completly fog from the git dir.
Now it works.
Arnaud

@tyler2017 Thanks for responding as I don’t know what mac is what, I just took a guess and it was wrong. Thanks for trying the other and glad it helped.

@Quazz The standard stuff. The page could not be reached. I also was wondering if I need to uninstall and reinstall FOG anyways, because we have DHCP servers setup on our network, and I skipped all of that through the initial config. Do you think this is maybe why I’m having issues now? I tried to setup the startup script in the CentOS 7 manual, but it seemed not to work. Thanks for any input.

@Quazz said in Deployement failed on smaller drive (message "Target partition size smaller"):

I’ve made it a habit to just start over every time.

We also find the same thing and create new every time.
FWIW: We use MDT to build the reference image, that way we have a consistent way to “start over every time”.

@Tom-Elliott

Thanks alot for pointing out on the nic cannot get an ip. we have did some digging on fog wiki and found out it is network switch issue.

Thanks alot again.

So I was able to do a “Full disk Repair” and then use command line to shut down the system which seemed to fix the error I was having and am now doing a successful capture! Thank You!

@mtanigawa lol, what would you suggest to make it infiltrate better? I can change the article if you can come up with something better.

@george1421 I have removed the the global parameters and still exhibiting the same behavior. It is weird that this happened right after I made that change. I think something might have gotten corrupted, but I am not sure what to do at this point.

@SquidgyHobo RHEL 5.3 isn’t supported by FOG.

RHEL 5.3 also it went EOL from Redhat Jan 2011. I would not even use that in my environment since it is susceptible to a handful of nasty and well publicized vulnerabilities.

RHEL / Centos 6.5+ and 7.x are currently supported, as well as the Debian variants.

I downloaded the package again and the installation worked.

I don’t know what happened but its now working.

HenryI did an experiment, a simple multicast send and receive on a private network contains only the Access Point and one station. The results are:

With the station sends and the Access Point receives multicast data using 224.0.0.1, the rate is over 20 Mbit/sec. With the Access Point sends and the station receives multicast data using 224.0.0.1, the rate is over very slow even less than 2 Mbit/sec.
I have no clue!!

@george1421

Awesome! It works!

Thanks a lot.

I’ll have a look at dmidecode when things settle down a little thanks.

@Tom-Elliott
@george1421 after updating to the latest version the deployments to the NCR still fail. I am able to image PCs and laptops so I will just use a different solution for the NCRs and leave it at that. Thanks everyone for all of your help and assistance!

Thanks,

Anthony

You can also turn off DHCP config generation by setting bldhcp to 0 in .fogsettings