of course you have to have a dhcp server who say to the clients where to try the pxe boot!

Sorry that I never updated this post in a timely manner. Right after I started this thread, I went on a 2 week vacation, and when I got back, I had been so busy that I didn’t have the time. As of today, I have a working FOG Server. I know now that the black screen with white writing is the partition and mbr screen. This is the screen that would flash right before the computers would reboot. I know now that the problem was that we didn’t completely clear out the old partitions before imaging, so the image had about 5 partitions and some were logical, which I know now that FOG doesn’t like. Now, I have the standard 100 mb system partition and then the 😄 partition, and everything is working great. I imaged my first 10 computers today in under 40 minutes. Thank you all for your help!

Looks like this was fixed by r2226. Cheers.

Nevermind. I forgot to add next-server xxx.xxx.xxx.xxx to the config file. The clients now PXE boot fine.

ok it had a small scrit that it had run, from there it finished at the [root@roxborough /]# so where to look now for the log file?

I’ve located a problem - it was Cisco switch which I’ve changed.

Command ‘spanning-tree portfast’ on configure terminal for ports fixed the problem and Fog works 😉

this is known and expected behavior. Multiple Partitions - Single Disk recreates the partition structure of the original image, and you can not create partitions on a drive that are larger then the drive can contain.
the “way I can change that so that a 160GB HDD will work instead of requiring at least a 320GB” would be to use a Single Disk - Resizable image type, which shrinks the partitions to the smallest size possible for the data on the drive before pulling an image, then expands the drive to the full drive when downloading the image to a new computer.

After I changed image and clicked update, page loaded again with old image… in log file for apache was only script ‘/var/www/html/fog/management/ajax/dashboard.bandwidth.php’ not found or unable to start, so I searched forum found article fog-upgrade-from-0-3-2-to-fog-1-0-1-php-errors-centos-6-5.10680 so I decided to make new install again. And now its working fine (import hosts too).

I don’t know something broke in previous install, but everything in foginstall.log seemed ok.
Thank you for fog and your support!

in the footer of your fog web page, there’s a link to a page with the fog client software and fogcrypt

Nvm, still can’t figure this thing out. About to just go buy parts and RAID 5 my linux machine itself. I know I can get the storage node to work locally. But I just can’t figure out this NAS deal.
Maybe it’s because it NEEDS a username and password? Not sure how specific NFS is but I know it doesn’t ask for it there when I want to mount the nas. I can mount it just fine with CIFS. Infact when I mount it as a CIFS and add that as a node on fog it even gives me the available space pie chart and all. But all in all we need NFS for all of this to work client side.

Here’s what I currently did:

On the Imation DataGuard T5R (IP: 192.168.2.201) I made a /Images share out there. This NAS is kind of goofy so it could full well be the NAS. The NAS isn’t on the Active Directory but the computers are. So even though I don’t have the NAS on the AD I still needed to add my username and pass to it as a user and it let me in. So thinking that way I added fog as a user also to see if that could rule it out.

My /etc/exports say:
[CODE]/fogimages *(ro,sync,no_wdelay,insecure_locks,no_root_squash,insecure,fsid=1,)
/fogimages/dev *(rw,sync,no_wdelay,no_root_squash,insecure,fsid=2,)
[/CODE]

I also added the .mntcheck files in these folders. I never did “Touch” those files so that will be next on the list.

My NAS line in /etc/fstab looks like this:
[QUOTE]192.168.2.201:/Images /fogimages nfs defaults 0 0
[/QUOTE]

When I was done with all of that I made sure I did the exportfs command and even restarted services.

When I try to mount again I still get this:
[CODE]mount -t nfs 192.168.2.201:/Images /fogimages
mount.nfs: access denied by server while mounting 192.168.2.201:/Images
[/CODE]

I have tried doing all of this in Fog itself too. [IMG]http://fogproject.org/forum/gyazo.com/8948a37556ff51c00f362e942e4c0538[/IMG]

I have tried different variations of the Image Path also. Some forums have mentioned that some NAS systems don’t grab the share correctly. So try to find a more direct path. So I tried /Nas1/Images <-- (Logical Drive/ImageFolder). Nadda. Next I logged into the NAS through SSH and found an even more absolute path. Tried that and still nothing. This is going to haunt me, haha. [IMG]http://gyazo.com/8cf806729d6dbcfcbe45edc7d23deaaa[/IMG]

I know I can get this working with Clonezilla but I really love the way Fog is laid out. Clonezilla I need to always go to the machine and follow the 15 steps and make sure I even have the correct paths. Fog, you just do it once and after that you click a button to start anything you want. It’s super nice.

So if anybody has some ideas that maybe I am missing or if I’m SOL with this NAS possibly let me know! Thank you. : )

i have this same issue. i made sure i have the latest php5. help please.

No, UAC is not disabled, the user doesn’t have administrative permissions either.
But it should not be the case when a service with credentials executes the scripts.

But even a simple “copy these files to desktop” batch file doesn’t run.

For now things are done manually, as it seems the great devs, are in the progress, of making a new service client.

Hey It is working now…
i have changed option 67 at dhcp server from undionly.kpxe to undionly.kkpxe
and updated init.xz and init_32.xz from the url
[url]https://svn.code.sf.net/p/freeghost/code/trunk/packages/web/service/ipxe/init.xz[/url]
[url]https://svn.code.sf.net/p/freeghost/code/trunk/packages/web/service/ipxe/init_32.xz[/url]

Thank you soooooo much!!! That is all that it took. I ran the commands and then restarted the clients, and they started right away. I can’t tell you how much this helps me. We have to have over 40 computer imaged and handed out by September 1, and we were about to loose our minds. We lost our licensing for Norton Ghost, which we hated anyway, so we started to look at Fog. Now that it is working, we can start imaging on Monday! Thanks!

[quote=“Tom Elliott, post: 35659, member: 7271”]Kernels are now updated and available in svn or from my website.

[url]https://svn.code.sf.net/p/freeghost/code/trunk/packages/web/service/ipxe/bzImage[/url] (64bit)
[url]https://svn.code.sf.net/p/freeghost/code/trunk/packages/web/service/ipxe/bzImage32[/url] (32bit)[/quote]

You’re amazing! I downloaded the new kernels and replaced the old ones and my PE 2900 is now uploading an image to my Fog server!

Thank you so much for your help. This is a huge step in being able to replace our existing Acronis system with Fog.

Wel,

On DMI Information is not showing up .

I check it with a newly registered Host, and i take a previous on, delete it and re-register it, but still not showing up.
I’m starting to think that this could be we a compatibility problem?

I’ve tried upload task and then download task and it works like charm
Thanks a lot everyone 😉

Of course the way via snapin would be the alternative.

I just wanted to try the clientupdater service for the first time and exactly the required file was forgotten in the sourcode ;(

can you give me the wiki path for tftp issues