[quote=“ChrisG, post: 11916, member: 2515”]If you disable the service it will not pull the snapin. You are correct. The service must stay enabled otherwise it does not know it has a task waiting. When you say interactive message do you mean it prompts to install?[/quote]

Thanks you all of you!

I was the problem. When i create the sfx *.exe archive, i wanted to see the self extraction. In fact, if windows have not any message to display, it does not show anything.
Also, i confirm the service “interactive message” [B]MUST[/B] be actived.
Ps: I’m french, and I speak english like a spanish cow 🙂 lool

I changed the master user and password for my server login to match the same on the FOG system(for storage node).

Need some basic info.

What is running your DHCP services (FOG server, Windows, other appliance)?

Did you update your DHCP settings to include the PXE Boot info (next-server, filename, option 66 and 67)?

Is the client you’re trying to PXE boot in the same subnet and VLAN as your FOG server?

Can you get a picture of the screen with the pxe boot info and error messages, or a screen shot if you are using a VM?

Hi,

after reading and more reading into the wiki and kb i found the solution. It was a missunderstanding of how FOG is working.
I didnt knew that there can be only one local storage node on each fog server! stupid me 😉

Greetz X23

Yes, Define them for any scope that has computers or your clients don’t know where to look for the boot server (Fog server). Make sure that these options are not defined for other systems, IP phones sometimes use options 66 & 67.

Ideally if you had IP phones that use options 66 & 67 they would be on a different DHCP scope than your computers

Well thanks, I’m suppose to be getting some new equipment this summer to set up and I WILL be imaging with FOG, so I’ll remember this in case I run into issues!

First make sure your image is set up for MULTIPLE PARTITIONS aka the WHOLE disk.

Then take a look here: [url]http://fogproject.org/forum/threads/problem-uploading-ext3-ubuntu-image.459/[/url]

I found this from the link above. Others have had success, try this below:

Update: I finally tried manually using PartImage to pull the image with the plan to then copy it manually in to the server. In doing so, I saw that PartImage was erroring out (which FOG was hiding). Googling around found that running an fsck prior to uploading the image fixes the problem. I may dig in to the FOG code to see if I can make it automatically run an fsck prior to pulling any Linux image. For now, though, I just boot my source PC in to a live CD and fsck, then I upload the image. Works a treat.

Again, we nailed it. The solution was to disable the required SSL on the /var/www/fog/ directory. It was always on but since the upgrade it was keeping fog from sending the inventory.

Case closed for now.

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

Thanks for all the help, sorry I took so long to reply, tried several things and nothing seemed to work so just rebuilt the server.

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)

/dev pointing to E:\images\dev (for the mount for the pxe client)[/QUOTE]
The FTP Server running on the Windows machine:
[QUOTE]- user same as configured under the storage node root directory is E:\images[/QUOTE]
E: looks like:
[QUOTE]E:\images
E:\images.mntcheck
E:\images\dev
E:\images-mntcheck[/QUOTE]
Everything is running fine now 😉

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

Chad,

Thanks, that took care of it, deleted the old pxe boot file and voila’

Did you run the commands?

What was the outcome?

Awesome work Kamz87! It generally is something simple. I’ve had so many little things like that happen. Just make sure you always try and it never hurts to ask or read the wiki or forums for answers. Have a good one!

Installed 12.04 but ran into the same problem. I had thought that after physical machine restart, restarting tftpd-hpa, portmap and nfs-kernel-server had fixed the problem, but I came in today and ran into the problem again.

Many thanks, Jason, much appreciated. Cheers

Chris

Leon, are you still having issues?

From reading your statement I have gathered that you want to save your images from your FOG server on a network space, is this correct?

I know that FOG is going to need access to this folder with read and write permissions, I would first start with checking there and trying to make a public space where it will not be affected but network policies.

We use a Novell Network here and I run into problems with permissions all the time.

However I am not familiar with adding a space for the FOG server to save an image to, in my FOG server there is a drop down box where I can select “default” and possibly a node if I had installed one. I don’t know what is involved with locating the space on the network and adding it to the drop down list.

I would also install the Samba service of Ubuntu to help alleviate some of the problems your going to run into using a Linux box in Windows environment.

edit your /etc/rc.local

to include
[code]
/bin/sleep 30 && /etc/init.d/tftpd-hpa restart
[/code]

this should tell your linux to restart the service in 30 seconds after it starts this should take care of having to manually enter the command after a reboot.

I second the sysprep test. Sounds like Windows is confused about where the drive is located. Usually on dells, they are all on the same controller in the same slot, using the same hardware revisions. Maybe you have a different hardware setup due to ship dates or model revisions. Sysprep might help this.