You can image solaris if you use RAW image type I think. It does a DD copy and is slow, but may be what you need.

Yeah, its feature rich, and to be honest, its not slow at imaging or anything, its just very quirky. We’re running the new version and one of the guys is about to run the service pack on it. I’m just really not sold on it. It feels so uncomfortable to use and things seem to take forever to update and propagate down to the site servers. For instance, adding a machine to a deployment list takes hours to update sometimes, and other times only 10-15 minutes. As far as I am concerned, if its not there almost instantly, what use is it.

Fog is just stripped down and lightening fast. I’m wondering if there are any plans in future versions to add many more features to the project? How many of the suggested features actually make it into production copys of new FOG versions?

help -> trophies

I have read this article: [url]http://support.microsoft.com/kb/302577[/url] remember now that I got some issues with license key in the past, thanks Kevin for your help, anyway I’ll test this and will come back to you with feedback.

Thanks Chad,

I found this - [url]http://www.fogproject.org/wiki/index.php/FOGUserGuide#Full_Listing_of_Ports_used_by_FOG_server_and_client[/url]

Curious which of those would be required for snapin management/deployment.

Problem solved. I found a sneaky little 10/100 switch that was causing the pile up. Mods you can take this tread down.

I assume, that you’re able to choose the new group (of the host) in the same menue “Add to group”? I’m not sure, because i don’t use host groups.

You really only need a performance boost if you do multiple deploy or multiple upload tasks at the same time. If you are just looking to add storage, you can easily put in a bigger drive. If you want to span multiple drives, you’ll have to look at implementing some form of RAID.

Using a NAS, connected via the network card, would probably slow down your imaging process even to one machine unless you have a dedicated NIC for the NAS, and a dedicated one for the client network.

Not currently.

Edit the image, tftpboot/fog/bg.png to change the background of the pxe menu.

You can’t have different menus come up, however, you can create sub-menus within the main screen. A guide to doing this can be found here: [url]http://www.fogproject.org/wiki/index.php/Edit_PXE_menu_to_create_sub_menus[/url]. Then you can push any kernel you would like to the machines you need.

I wrote up a how-to on installing the bypass, it can be found here: [url]http://www.fogproject.org/wiki/index.php/Installing_the_FOG_Bypass_Host_Registration[/url] Let me know if you run into any problems!

Thank you guys. I will try this process.

We deployed about 200 Windows 7 desktops last summer with Fog and I’ll share what we did:

Build one machine as master
Run sysprep /oobe /generalize
Fog pulls an image from the master to the Fog server
We use Multicast to send images out to the other computers.

When the computers boot, they run the mini setup, ask for computer name, etc.

One thing is we use KMS licensing so individual computers do not have a license key. Depending on how you license, there may be additional stuff you need to do.

i am not saying this is the only way, but this worked well for us.

You can deploy the image to as many computers as you choose. Whether or not you can use the same key for all the computers is determined by the type of Microsoft licensing you have.

That’s a good point - if you don’t care about them being registered in the FOG database, that should work great.

Just a thought, and I have not tried this personally, but [URL=‘http://ipxe.org/’]ipxe[/URL] might work.

I haven’t seen anyone doing this yet, but I think you’ll probably want to look into [URL=‘http://ipxe.org’]iPXE[/URL].