If you poke around the forums, you’ll find threads that describe the development as not “ceased”, but at a “slow pace”.

But even if development is at a “slow pace”, you’re sure to find FOG worth learning and setting up if you’re pushing out more than a few new computers a week.

For example, once you have FOG setup, this guide will walk you through a great way of creating a standard image that be deployed against a wide range of hardware:
[url]http://fogproject.org/forum/threads/windows-7-deployment-fog-sad2-driver-tool.380/[/url]

FOG has some management tools that are cool: I like to have the user’s name as part of the computer name. Thus, when a computer changes hands, a rename is needed. Instead of doing this from the computer, I get into FOG and rename it.

Summary: When uploading a Windows 7 x64 image, FOG gets about a quarter way through, around [FONT=Helvetica Neue][COLOR=#333333] around 2 GB (2,147,483,647) out of 8 GB[/COLOR][/FONT], before “politely” shutting down. I’m looking at the logs and don’t see any record of the image being made.

Please guide me in troubleshooting.

The story: I’m feeling like such an idiot! The Ubuntu OS prompted me to upgrade the system. Since one of the reasons I went with FOG was to understand Linux, I agreed to the upgrade.

After the upgrade, everything appears to be normal. But my one critical imaging solution has failed. When deploying a Windows 7 image that has worked fine for about a dozen sessions, FOG popped up a box asking for the path to the second part of the image. Since I wanted to tweak the Windows 7 master a bit anyhow, I just deleted the image, made my tweaks, and tried an upload. And it failed.