@Wayne-Workman thanks, I was meant to say that I had been through that article after searching the forums and finding similar posts.

I also rebooted the server and also tried again after updating, I know it doesn’t really help us in finding what went wrong but I ended up rolling back my FOG VM a few days (both master and node was able to deploy after this). I then updated the master to the latest (to match the storage node) and both are able to deploy images.

thanks again

@Bob-Henderson If you update, we think the bandwidth graph is fixed.

And, it’s fine - I was lost in outer space for months when I started messing with fog. I think I still am sometimes.

@BardWood do you have a hub (as opposed to a switch)? I’m just asking, because there’s something you can do to help solve this.

Have you tried it with a different mechanical HDD? I’ve had hard drives fail right after chkdsk /F /V /R /X reported that there are no errors or bad sectors.

Nvm, I tried another kernel, Version : 4.1.2 and it worked.
Case closed

@Sebastian-Roth
Yes, very much under time pressure in the business at the moment… I had to rebuild another Fog server… and I uploaded my 2 main images onto it manually… so I didnt use any of the backup procedure.
This is all a consequence of being forced by company circumstances to run things into production without any testing time…
the joy of decisions being made above your head and you just being told to get on with it!

@dolf Perhaps this deserves a video.

@Wayne-Workman The problem has been solved. Thanks.

@mabarton I briefly went over this thread because it’s been a while. Have you individually tried every EFI exit type?

I’m on Ubuntu 14.04 though…
Anyway, it’s working with php5.

@Joe-Gill Great job. Boo @Microsoft. Booooo

@jayrob86 this is where it gets a bit complicated if you want to reverse engineer stuff.

The post download scripts are saved on the FOG server, but they are executed by the FOS engine (the linux operating system that captures and deploys images to the target computer).

So to answer your question, the function.sh script is in the init(s) (virtual hard drive that is downloaded to the client along with the kernel (bzImage) when pxe booting).

So you next question may be how can I peek into the inits? There is a wiki for that: https://wiki.fogproject.org/wiki/index.php?title=Modifying_the_Init_Image

The file is in /usr/share/lib/fog (or something like that, its in /usr/share…)

@Tom-Elliott Sorry for the delay - I am on an isolated network for my FOG Server - so right now only 3 machines in the FOG environment.

@Tom-Elliott All fixed and working thanks all can be marked as solved!

Personally, I would setup a test FOG environment just get FOG working.
I was in the same boat quite a number of weeks ago.
Setting up FOG on your established network will be tough to get right.
Use the standalone approach firstly.
It probably took me 40 to 50 hours of work to get a solution.
Last week using my Fog server , I was able to image 50 PCs in Win7 Sysprepped mode ready to join the domain.
My breakthru was seeing FOG actually working when I used a VMbox setup on my own PC following a YouTube tutorial.

good luck

When I can, I will be copying the sql table over to the new server.
I will update as to success when trying to push an image out.

DANG… Once again stupid I feel … Tried to update VIA SVN but original install install was GIT. Ran update on GIT and pow fixed.
Close please… LOL

@Tom-Elliott And you can’t calculate all the hours you’ve saved for other admins.

@george1421 So sorry for the late reply (2 months even) but this sorted my issue out

Thanks