Ok I managed to solve this based on a previous post where Tom had deleted files in /opt/fog/{service,etc}

I tried doing the above but still didn’t seem to resolve the problem. So I moved the existing fog folder in /opt to fog.backup. Then created the /opt/fog folder and copied the .fogsettings to it.

Performed a reinstall to pick up the existing settings and it now seems to be all ok without any errors.

I created a post a few days ago about booting a MDT iso image via the ipxe boot menu. This may help you on your quest as long as you are using a svn trunk. The only thing I think I would change from this post is to move the place I stored the iso image out of the fog directory directly. In the instructions I said to place the files in /var/www/html/fog/iso , moving forward I would put them in /var/www/html/iso This location is still addressable by apache but won’t collide with anything in the fog distro.

https://forums.fogproject.org/topic/6161/debian-8-fog-trunk-pxelinux-on-ms-server-and-ms-dhcp-help/15

Sorry I typically run all commands sans sudo simply because when I’m writing I’m usually under making the assumption that you are running it elevated already. I should’ve specified I suppose but at least you got it working.

Thanks for reporting back! Great that we could solve this. I really hope we never see anyone actually needing this cdc_ether module!!

@Warrender6 From what I can see in the two screenshots those files are probably on the same system (date and time). So I guess this is still FOG 1.2.0. I am still not sure if you can make this work with 1.2.0 but what is very clear is that init.xz is too small. Somehow got damaged?? You can download a copy straight from here: http://sourceforge.net/p/freeghost/code/HEAD/tree/tags/1.2.0/packages/web/service/ipxe/init.xz?format=raw

If you want to go FOG trunk we need more information on what went wrong. Exact error messages!

@ITSolutions Hi all,
Thanks a lot for help and for this best software around the world to deploy.
Regards

Autosolved:
“1” “fog” “xxxxx” “0000-00-00 00:00:00” “” “0”

@Tom-Elliott +1

I have no idea what is going on in this thread.

@megs In the future, please stop using acronyms in this manner. They are really confusing when not everyone is familiar and they are not defined early on in the OP.

This has been added to the WiKi to the best of my abilities. This was a difficult one because many of these things I myself do not have direct experience with, so I had to retain the formatting and color coding as closely as I could to preserve the originally presented material.

I’ve made this article exclusively about virtual HDDs as this is 95% of what these posts are about. I’ve simply removed the remarks about physical disks.

Here is the link: https://wiki.fogproject.org/wiki/index.php/Add_%26_Extend_a_2nd_Virtual_HDD

It appears this was Hanz’s fault. He had snapshots and what not and it broke the upload process.

@fakeblair Any news on this??

Have you tried undionly.kkpxe??

@jbsclm said:

@x9rok
It is some while since I last used it, but from what I remember, if there was no task for the PC you should get the FOG menu, which would then time out after the period set in the FOG GUI, if you didn’t select an option.
If you don’t get the FOG menu then it may be that the ipxe script needs changing to pass extra parameters to boot.php.

OP: From my post below the boot.php script is looking for the mac parameter to be passed to it. Without that I might understand why you are getting a different reaction.

http://${nextserver}/fog/service/ipxe/boot.php?mac=${net0/mac}

@Tom-Elliott awesome, thanks, it seems to be working ok now…

Are you still not able to register clients?

@pmonstad there was a bug for a while where the kernel directory was being passed as you saw but it is configurable through fog configuration -> fog settings -> tftp server kernel for or very close to it.

There were some changes made by Tom in the last days. I guess he fixed things for you as well. Marking this solved. Please report back if you see the issue coming up again or if you have other problems.

Fix pushed. Basically if there’s any “bad” characters, I replace them (for the html attributes) with _, this way the attribute is setup properly and can be edited.

no problem, i’ll update trunk later on this week and try again.

@x9rok Is there any way I could get you to help me with the working and installation process involved to get clam av to work…I’ve got it installed on server at this point.