[quote=“Blackout, post: 417, member: 1”]The problem is that HTTP POST (the method used currently to upload snapins) was never designed to upload large amounts of data. 2mb is the default, this gives you an idea of the sizes it was originally designed to send.

The snapin code needs to be updated to use a modern Flash or HTML5 uploader.

For the time being, you should upload large snapins manually.
[LIST=1]
[]Download FileZilla - [url]http://filezilla-project.org/[/url]
[]Create a profile for your FOG server
[LIST=1]
[]File -> Site Manager
[]Click ‘New Site’
[]Host: [I]<your_server_hostname_or_ip>[/I]
[]Port: 22
[]Protocol: SFTP - SSH File Transfer Protocol
[]Logon Type: Normal
[]Username: root
[]Password: [I]<your_password>[/I]
[]Now click ‘Connect’
[/LIST]
[]Navigate to: /opt/fog/snapins/
[]Upload snapin exe file
[]Profit
[/LIST]
[/quote]

Sorry to jump in on a thread, but you have 99% answered a question I had about large snapins. After getting the file to /opt/fog/snapins
what do I need to do to make FOG do to see the files ?

I think we are going to go with adding PCs manually before imaging as a workaround just now. Does anyone know how to manually add multiple computers to AD from a text / csv file etc?

You can password protect all options on the menu. apart from the boot from PC…

One thing to try is to delete the group and recreate it. I did that just now and am able to image a group (even as we speak, from the comfort of my rocking chair in my living room!) that had the same problem. I am not sure that it fixed the problem, but that is all I did to this group of 20 pc’s.

If the computer is already registered just click host management and find the computer on the fog web.

Well, today I had time to work on the project. First, the hard drive isn’t the issue and single cast deploy worked fine. Second, When I arrived on sight the lab was dismantled so I had to resort to using a Treadnet 10/100mbps 5 port switch connected to a Managed Cisco Switch which was also connected to a Cisco Router. I then proceed to request a managed switch for use however all that was around at the time was some old netgear switches which had been pulled from the active network for being unreliable and the other one was replaced as it only had 10/100 ethernet ports along with 2 10/100/1000 ports. The two gigabyte switches just didn’t want to work correctly so I decided to try the old 10/100 netgear switch and reset the settings but wasn’t able to access the webadmin panel for it as it seems I need to first console in and change some settings even thought I held the reset button on the front. I wasn’t able to find the needed cable in the storage room so I am assuming we know longer have it and doubt i’ll get the budget to replace it. At this time Multicast just seems to be unfeasible with the current equipment.

Thanks for the reply, I guess it was just wishful thinking that there would be a place to configure it.

I was playing with the same idea of running FOG on a VM and allocate all physical resources to it. It seems like there’s some network slow down in the emulation layer and I couldn’t get more that 250MB/min. Where as on the same physical server if I did a raw Ubuntu 11.10/FOG0.32 install I could get steady 1.6GB/min speeds. I think you’ll find you’ll be much better off on a dedicated server even if it’s not a super beefy machine. I also messed around with Bonding mulitple NICs and got nothing but trouble unless you just want it as a hot backup. There are a lot more errors when trying to load balance and ended up not being worth the trouble.

[quote=“Amir, post: 785, member: 335”]There are several places that you can check in order to make sure that your new hosts are communicating with the right FOG server IP address specified on /tftpboot/pxelinux.cfg/default[/quote]
I forgot all about the ip addresses passed in the append lines of the default config file! That did it!
I’m going to add this to the wiki page for [URL=‘http://www.fogproject.org/wiki/index.php?title=Change_FOG_Server_IP_Address’]changing the IP address of a FOG server[/URL].

I had the same exact issue before with Optiplex 790 Series. In order to resolve this issue you need to rebuild your FOG kernel with the latest KITCHENSINK and import your drivers.

[url]http://fogproject.org/wiki/index.php?title=Building_a_Custom_Kernel[/url]

Hope it helped.

If your systems are outdated and do not support PXE boot on BIOS you can still boot them via PXE by using RBFG bootdisk. RBFG stands for Remote Boot Floppy Generator which creates the capability for those clients that natively do not support boot via PXE.
In order to create this bootdisk, either you need to have a Windows 2000 Server Disk or if you do not have one then follow the instruction on this site: [url]http://registration.argontechnology.com/rbfg/index.shtml[/url]

Hope it helps you.

Depends on your distro, in ubuntu try “nano /etc/dhcp3/dhcpd.conf” and look for “option routers”.