FOG uses NFS to send unicast images to computers.

Oma, the best way to get the updated kernel is to download it from here and move it to the correct folder:

[url]http://sourceforge.net/projects/freeghost/files/Kernels/Kernel-3.8.8.core/[/url]

or

[url]http://sourceforge.net/projects/freeghost/files/Kernels/Kernel-3.14.0.TomElliott/[/url]

Give this a shot:

sudo gedit /var/www/fog/management/includes/tasks.confirm.include.php
Search for: &$tmp
Replace with: $tmp
Replace All (there were somewhere around twenty instances)
Save
Close
Then try to schedule your upload task again.

Should be fixed now.

I’ll get that fixed shortly.

Syed,

I would also look into this utility, [url]http://en.community.dell.com/techcenter/systems-management/w/wiki/1952.dell-client-configuration-toolkit-cctk.aspx[/url]. We run the full Latitude lineup where I work, this is what I use when I need to make changes “enterprise” wide to machines. I package BIOS settings with this utility and push them out through our deployment software. (Unfortunately, it’s not FOG).

I was doing some searching and found 2 things you might be interested in:

1. [url]http://blogs.technet.com/b/panosm/archive/2011/07/07/windows-7-steadystate-solution-simplified.aspx[/url]
2. [url]http://www.steadierstate.com/[/url]

Looks like both utilize being able to boot VHD’s. May be worth looking into.

At my place of employment, we have about 10,000 computers and had a setup very similar to yours. Let me start by answering your questions right off the bat.

1. No, it will not cause any conflicts if setup correctly. For awhile we had WDS and FOG running at the same time without any problems. We had a WDS.iso that we created that would point to the WDS server and image our Windows 7 machines that way. All we did was add that iso to the FOG boot menu. Simple :). We had our network guys setup FOG on the DHCP server (prots 66 and 67) and never had a problem.

2. The security risks are all dependent on what you choose to run. Apache itself is not a concern. You won’t have FOG sitting in the DMZ, so your employment’s firewall should block almost everything going out anyways. The concern is what version of Linux you choose to install FOG on. The more features you install, the more security risks you add. I personally am an Ubuntu guy, so I install FOG on Ubuntu server. It’s all command line, no GUI. This means that the server is fast to boot, very little to crash, and extremely robust. I ended up having to install a GUI so others could administer the server if I was not available, so LXDE core to give an absolute minimum GUI experience for others. But again, less is more when it comes to security.

Now a question I have for you. Especially with the transition to Windows 7, is there a reason that you can’t have your machines on the domain? It seems like it could be very easy to just group all of your machines into a new OU. Group policy is a very powerful tool and you can really tweak how you want your computers to work and behave. With Windows 7, you can have a whole new level of control that didn’t exist in XP, and can install templates (ADM and ADMX’s) to control programs even furhter. Granted you can’t do “frozen” profiles by default, but you can at least limit what gets installed in the first place, which is half the battle.

Unfortunately we have since discontinued FOG as people higher than me decided that we could no longer use it, in favor of another product. I do however, still have a full lab setup at home to do testing on, including WDS and SCCM, so I still get my fair share of FOG in :). I will say, FOG was, and still is BY FAR the fastest and easiest imaging solution that I have used.

The setting should be under the video\display settings on that virtual machine and should be a value you can increase. Sorry for not knowing exactly where, we are a VMware shop here, but there aren’t many differences between settings on a VM with the type 1 hypervisors.

+1 for Deploystudio. As much as we like FOG, we still use Deploystudio for our Macs. It’s similar to a Lite-Touch\Zero Touch deployment through SCCM for Windows. Rock solid, relatively fast to setup, but just like anything else, you need to spend the time to set it up correctly for it to really save you time down the road.

you could always try [CODE]sudo gedit /tftpboot/pxelinux.cfg/default[/CODE] or the tried and true [CODE] sudo chmod 777 /tftpboot/pxelinux.cfg/default[/CODE] that will give all permissions to the file.