Hi chad-bisd,

you’re right, I fixed my problem with recompiling a kernel and adding RAID support modules.

Thx

Downloaded and unpacked the newest Fog to get Fogcrypt and it works. Thanks to everyone for their helpful suggestions.

Please do not cross-post. Pick a forum and post your question. If you are not getting the response you need, feel free to PM a community manager and we can move it to a more relevant forum area or try to answer it ourselves.

I have merged your threads. If you feel this question is in the wrong forum, let me know.

Try moving to a Kitchen Sink kernel at [URL=‘http://fogclone/fog/management/index.php?node=about&sub=kernel’]http://FOGSERVERIP/fog/management/index.php?node=about&sub=kernel[/URL]

Chad as a side note to your statement. I have NetBios blocked on our domain and it still works.

if you are going to create a master image, you should probably go into the custom disk configuration in windows and choose to make the partition smaller than max disk size.

For example, I’m creating the master image for Windows 7 Pro on a new workstation that has a 1TB HDD, but I may need to deploy it to a bunch of workstations that have between 160GB and 1TB HDD. During the windows setup, choose the advanced options for disk setup, and make the window partition 80GB to 160GB depending on your needs. Leave the rest of the 1TB HDD unpartitioned (other than the special Win7 partition that it makes automatically).

If you do this, then you won’t have a problem choosing the Multiple Partition - Single Disk image type option in FOG and deploying to a variety of disks.

Another option, is to use GPARTED on a USB bootable flash drive, and reducing the size of the windows partition down before you take the master image. GPARTED should let you shrink the partition down without corrupting windows. Make sure to leave enough free space for Windows to operate, which I think is about 10% (so if you used 30GB for the install, don’t shrink below 33GB).

[quote=“chad-bisd, post: 11909, member: 18”]When I compiled my kernels, I used the core.config instead of the kitchensink one. That was my base settings, and I add and remove settings for the graphics drivers, etc. You have to research and find out what is breaking your setup, and see what to remove or add.[/quote]

Thanks a lot.

I understood by reading this forum that core.config was less complete than kitchensink.config.

Regards.

[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