Hi,
check this link:
[url]http://[serverip]/fog/client/[/url]
you will find the client service download and a zip with a prep utility you have to execute immediatelly before you do the image
(executing prep, reboot > image.)
AFAI know this part is missing in the wiki but iam not sure 
Greetz X23
Hi,
same issue here i edited the files chad-bisd mentioned but the issue is still there…
How to debug that? It seems this problem is older than a year why does no one is fixing it?
Is the FOG Project dead?
Making a scheduled image is not possible and the hole sense of the fog installation is questionable.
It’s nice to make images manual but without task scheduling it’s quiet useless for me.
Any help for fixing that out would be great.
Also i have a rewritten post_stage2.php here that kicks ass to the ftp connection, after enough testing i will release that for all.
Come on guys lets fix that great FOG schedule thing, help please.
Greetz X23
Hi,
i could manage my problem.
Two NFS shares on the Windows NFS Server:
[QUOTE]- /images pointing to E:\images (for the mount on the fog machine (unbuntu)
The need of a FTP Server only for moving files is more then a face palm, but i will take a look at the scripts. Maybe iam good enough to fix that for myself and the rest.
Greetz X23
Hi,
first of all thanks for this nice product, iam pretty new to FOG so i tried to start using it and i had the following issue:
I’ve installed fog on a ubuntu running on a virtual box vm (8GB) Partition. After the initial setup was done i’ve tested a little image that fitted into the 8GB Partition, everything went well.
Then i decided to use my allready existing TFTP Server and for Storage a NFS Share with more space.
So i disabled the default storage node and added my bigger NFS share
NFS Share (big) : E:\Images -name:images (on a windows machine)
Then when i try to make an image on that share it will be created but in the end it cannot be moved, then i realised that i also need an ftp server on the storage node so i installed filezilla server, then moving was possible but it could not create the image name folder.
Second issue the image was created in storagenoderoot/macadress instead of storagenoderoot/dev/macaddress like it does with original setup, then when image is finished it seems it could not create the image dir folder , if i create it by hand the image is moved to its destination folder like configured in the image settings for that client.
I thougth i had the exact same base with my existing tftp and nfs share but something seems different, isn’t it enough to have a nfs share that is named images on whatever server and a ftp server that is pointing to the same directory? For my testing purposes i use user acount (ftp and so on) with maximum privilegues.
Iam confused and dont understand why the process will not work the same way.
Any ideas?
How to configure a alternativ NFS share (other computer) correctly to use it like with the default storage node?
Is it enough to have a share called /images ?
What about the FTP Server in the first moment i asked my self for what the hell is a dedicated FTP Server needed on another storage node when its only job is to get a connection where files are moved.
EDIT:
LOL i found this:
[url]http://fogproject.org/wiki/index.php/FOGUserGuide#Advanced_Installations[/url]
[QUOTE]Hopefully someone will re-write POST_Stage2.php to change this at some point as if you already have the NFS share mounted why do we do this bit with ftp? [/QUOTE]
What ever is it needed that the FTP root points to the same directory that the nfs share is using?
The FTP Account FOG is using has fully user privilegues!
Help please 
Greetz X23