Posts made by dr6figures

Thanks [URL=‘http://fogproject.org/forum/members/mentaloid.4362/’][B]Mentaloid[/B][/URL] for your reply.

No, I am not using Multicast. The last time I used it (with FOG .32), when I went to deploy Multicast, the switch and PCs chocked (it said something ridiculous like 10 hours or so to deploy the image). I don’t know if the switch supports it or not. Unicast to 1 PC does yield much better download speeds, at least 3 GB/min, sometimes more. When you start adding, though, the speed decreases to around 900 KB/min to 1ish GB/min for all 15 PCs being imaged. The switch is a gigabit switch. All 15 nodes are Dell 780s with Gigabit ethernet, and the server also has 2x 1 GB ethernet ports. The server runs Ubuntu 14.04 LTS. (I built the server in early July.)

So, if I try to implement bonding, I take it that it will not help much if the switch doesn’t support it? The reason I ask is that when I looked into this, there were several bond modes and only mode 4 (802.3ad) specifically specified needing support on the switch end.

Thanks again!

Hi Everyone,

First, many, MANY thanks (I’m not shouting in anger, just expressing my sincere appreciation) to everyone who helped bring FOG to reality, especially those who have worked hard to make it Windows 8 friendly. I have used FOG now since 2008, and 1.2.0 has been awesome in helping me handle my Windows 8 deployments!

As to my question… I use FOG on an isolated network, just for imaging. I run Ubuntu Server OS and use FOG for DHCP to dole out IP addresses to 15 client machines. The image that I push down to these machines is roughly 37 GB in size. It takes about 35 – 40 minutes to push down the image to all clients (Dell Optiplex 780s).

I’ve been reading up on NIC bonding and FOG since the server has 2 ethernet interfaces. If I enable NIC bonding on the server, would that improve deployment time? Could I be a little more creative and add a storage node with dual NICs and nic bonding to deploy images along with the main server for a faster deployment?

I would just like to see if there is anything that I can do to improve the deployment time.

Thanks in advance for your help!

Got it! Thanks Junkhacker! I am looking forward to upgrading my FOG server with 1.0.0 this summer.

Hi Everyone,

Just tested Fog 1.0.0. What a tremendous improvement! Thanks to all who put in the hard work necessary to bring this to life.

I have a question… in previous FOG versions, when I would go to deploy an image, one of the final screens before the task was queued asked me if I wanted to shut down the PC when the imaging was complete. When I just tried Fog 1.0.0, when I deployed a test image, the task went right into the queue without asking me if I wanted to shut the PC down. Was this something that I missed, or was this something that was removed totally?

Thanks for your help, and great job everyone!

Hi Kevin,

Do you have a “how to” for using bypass host registration? I looked at the wiki at [url]http://www.fogproject.org/wiki/index.php/Bypass_Host_Registration[/url] but am not sure what to do with noreg.gz or bypass.gz.

I work for a college. There is a good chance that, due to hardware refresh, we may be getting in several (190) new computers this summer and I would like to be able to push a default image to them without host registration and am interested in your process.

Thanks in advance!

Hi fellow IT Folks,

First off, I just want to say that FOG is the best piece of software I have ever had the privilege of using, bar none. I like its flexibility, I like what it can do, and I like what I can do with it. I used to use DRBL back in the day, and once I got the feel for using FOG, FOG became the replacement, and I haven’t looked back since. So I want to give a wholehearted thanks to everyone who works endlessly to keep this project alive. FOG simply is awesome!

I have a question that I am hoping someone can help me with. I work in a community college as a computer lab manager. Part of the way I have implemented FOG is to have a master FOG server on a cart with 2 to 3 other FOG servers serving as storage nodes. I then take this cart, plug all FOG computers into a gigabit switch, and then connect all of the clients that I want to image to the switch as well. At the most, there are 16 clients; at the least, there are 10. Taking the scenario where I image 16 computers at a time, I access the FOG web console and configure the storage nodes in the following manner:

Master FOG server, 4 max clients assigned to this storage node.
Storage Node 1, 4 max clients assigned to this storage node.
Storage Node 2, 4 max clients assigned to this storage node.
Storage Node 3, 4 max clients assigned to this storage node.

This way, the imaging load is evenly distributed across the 4 nodes. (Or so I think.)

When I image, I create a group in FOG that I put the hosts in, configure the image and OS associations and do a unicast restore on the group because if I try multicasting, it chokes the switch. Overall it takes about 30 – 45 minutes to push the image out to all 16 clients. The image that I am pushing out is about 40 GB uncompressed.

Since I just took this job in August, I did a quick-assemble on the fog carts with what I had at the time – retired Dell Optiplex computers with 2 GB of RAM. I put 300 GB HDDs in all units, and I am only pushing the one image.

I would like to better implement FOG in my next round of imaging while still retaining the carts and isolated server setup. Does it sound like I am on the right track? Do I have the storage nodes assigned properly for even load balancing, or is there a better way to assign hosts to storage nodes?

I’m interested to know, how do you have FOG implemented?

Thank you for your time, and I welcome any and all suggestions.