@Arrowhead-IT
I followed your advice RE: using diskpart and managed to get both my Dell 5450 latptop and HP 800-G1 desktops to boot legacy/MBR, install Windows 10 and can now successfully capture/deploy using single-disk resizable FOG image.

I’m pretty sure I had default GPT/UEFI Windows 10 multi-partition image capturing and deploying previously but maybe I imagined it?

Thanks for your help.

so I went ahead and tried sudo service tftpd-hpa restart and waited a few minutes. then tried to PXE boot and it worked. However, instead of registering the host, I inputted the MAC address thru the WEB GUI.

Well its seems were both right (sort of) I reverted the server via snapshot back to 1.2.0 and it deploys fine to the 80.3% errors then it performs the after imaging tasks, such as change host name/resize FS/clear task. So its probably been corrupt for awhile but have never noticed it, since it works fine.
It appears the trunk fog just errors out and then stops everything and reboots.

EDIT: I did try pushing a different image to the same PC and that worked fine.

Thanks for the help and sorry about wasting everyone’s time.

On an off topic, how well is the legacy client going to work with the trunk fog? Is best to just plan to upgrade the client at the same time as the server?

@Tom said:

My issue now is that the host is not booting to PXE.

Make sure UFW is off. Check this out: https://wiki.fogproject.org/wiki/index.php?title=Troubleshoot_TFTP

@Tom-Elliott
Yep no worries! Sorry… You fixed the initial problem. It did upload.

I’m finally getting around to resetting Fog from scratch. I’ve used it lovingly for about 5 years. For some reason I can’t use win10/education images, they upload but not work after download. I’ll let you know if I’m successful today with a fresh install and re-imaging Win10 education and also win10 enterprise, which has always worked for me before. I’m only using 64bit.

@Thiago It’s all good. Don’t feel like you did anything wrong. It’s why we asked the questions we did, and now we know why the problem occurred, and it made me ensure the code base was good to go too.

@mitzayapa Great to see that you were able to fix this yourself. Looking at the packet dump helps quite often!

@cschneider-tech said:

When I run command tftp <192.168.13.236> GET undionly.kxpe it returns “The system cannot find the file specified”

After reading the whole lot it all boils down to TFTP not delivering files properly. This can be caused by firewall settings on the FOG server, missconfigured TFTP, permissions on /tftpboot and many more things. Please follow this: https://wiki.fogproject.org/wiki/index.php/Troubleshoot_TFTP

@atarone where is 1.3.0 and why don’t I know about it? 1.3.0 is what we will label the latest trunk when we release but it has not reached that point yet. I’d have loved to have released by now but seeing as 1.3.0 will be the last of the php series, I’m trying very hard to make this version as stable as I can before it releases. I am not going to say yes it supports this or that thing because it isn’t guaranteed to work the same way for everybody. What I will say is if you need the support the latest development versions will most likely suit you better than anything else.

@j.schumacher99 can you run:

service httpd restart and get output from that?

Update for this topic.

After remounting the SAN to a different folder the image was still getting stuck in the dev directory. With @Tom-Elliott’s help we did an in-place upgrade to the latest Trunk. After doing this the image moved properly and there were no more issues. Thanks @Tom-Elliott! 🙂

Well then, marking this solved.

@Tom-Elliott
Everything appears to be fixed now! Thanks for your help!

FYI, my one image needed to be changed to Single-Disk (resizable) and I was updated to the latest SVN

Thanks for all your help!

@george1421
we have a few images. my script mount directly (i.e. mount /dev/sda2 /windows)
The problem is: now, our server will be used by another department with other config (i only know that they have 4 parts, using mbr) and sometimes the image name can change, disk layout too.
I like your idea and wanna let things more generalized as possible.
in any case, this is temporary until standardize all
Thanks a lot

Hi Wayne,

Thank you that worked perfectly!

@Wayne-Workman @Tom-Elliott

Today I updated to the latest version of fog (6042)… and deploy works well.
I’m very happy. Thanks for all.
Sorry for my english

@TThax use the ? to get the image listing. upgrading fog resets the image numbers. If using one of the listed numbers doesn’t work, it’s a bug. Post the issue in bug reports. (This is a fine example of what a “minor” bug is)

@Hanz What do the logs say for the multicast manager?

@Tom-Elliott Thx, that worked but now it finishes (I guess) and just loops. Ill post a seperate thread on that.