no, mine is similar. Hopefully there is a solution to this in future releases

I’m using 0.32 and must be missing a step with Capone. I followed the instructions in the wiki. I pasted the capone text in the pxe menu but it didn’t show up. I was able to do enough reading and modified the default file to include a Capone option. I get an error saying that the OS type couldn’t be determined. Any suggestions?

No one here who can help me?

Thank you for that information. I added another init.gz file and the kernel from another server that is running fog version .029. This is awesome that you can have multiple kernels.

I got it working! thanks

the solution was right on the front page of the fog website for servers running debian

Fixed: My solution was to remove the /images directory and then make a new one seemed to have done the trick.

I am having a similar problem. Just set up a FOG server on CentOS 5.5. Followed the directions to upload first image. PXE booted, ran inventory. Set up image, added image to host, went to basic tasks and selected upload, selected upload image - and nothing. My FogTaskScheduler is running.

Ok that worked not sure why - can anyone shed any light on to why this would be the case — like to know how these systems work at a lower level. 🙂

OK - Fixed the TFTP - Reinstalled Thanks for the help!

Found the answer to my question…I was on the right track.

I’m guessing that d1.mbr, d1p1.img, and d1p2.img is the naming scheme used for a fixed-size/multiple partition, non-resizable image. So once I updated the image file config to that setting instead of single partition (realizable), it worked like a charm and imaged…

No can do, I really needed to get it going so I opted to redo my base Ubuntu install and start over. Everything’s working as expected now. Now the only thing I need to do is transfer over the rest of my images.

NVM. Excel was messing up the formatting. Opened it up in good ol’ Text Wrangler saved as csv, all is good.

Yes have tried Clonezilla but no luck.

Hi,
I am new to fog and am running 0.32 and I believe I am having the same issue. Does anybody know of a fix for this? If not which is the last stable build that I can try so I can get this working?

[quote=“Zardan, post: 1201, member: 185”]I think all Windows 7 editions got a trail period that can be reset 3 times (sysprep does this by default) so you can skip those and manually set the key and activate Windows after you have deployed the image.[/quote]

Perfect. Thank you sir!