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.
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:
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.
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.
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.
Adrian,
All new requests should be placed on the fogproject forums here. The information on sourceforge was let up for historical purposes, records. It would not have been easy to move all the information from SF to here, but we didn’t want to delete any of the information either.
[quote=“andyroo54, post: 18229, member: 267”]
I love this idea, and agree with all of your points.
I love the idea of a Fog distro.[/quote]
Just wanted to chime in, this is actually in the works. I’ve recently moved and had to put this on the back burner for a bit, but i’m getting ready to pick it back up and get moving forward with a distro. Though, it will start as a virtual appliance first (which I have the first one completed), more of a proof of concept, before a live distro is made.
There are still some challenges with an appliance and distro that i’m working through, like being able to change the OS IP address after FOG has been configured. I’m slowly making progress through that. It’s just taking a lot of tweaking and lots more testing.
If everything is working for you, i’d say just keep it the way it is. No need to fix it if it isn’t broke. The only reason you may want to upgrade the compatibility to level 10 is that you can up your hard drive space from 2TB to 62TB per drive. We needed to do this for a couple of our servers, but it’s rare that you would need a VM with that kind of space. But then again, you’d need VMWare Workstation or vSphere to edit it from there.
Now if they offered HA for 2 free ESXi servers, just for absolute basic redundancy, i’d be in thrilled. We are on a strong push to move our teams to VM’s instead of having actual boxes at their desk for testing.
You can still do this if you leave the VMware compatibility at level 9. If you upgrade your VM’s to version 10, you need either vSphere or Workstation 10 to edit. However, you can still create VM’s with version 9 compatibility and still edit everything like you were able to before.
A couple of ideas found on Cisco forums, [url]https://supportforums.cisco.com/thread/2033218[/url]:
I found that you can also use Workstation 10 to edit the settings of the VM’s. Though the one feature, at least for me, to upgrade was the removal of the 32GB of RAM per server 
Having used RAID for a long time, RAID 10 isn’t significantly faster, but does allow for potentially more drive failures than RAID 5. I would strongly look up the RAID 5 write hole, [url]http://www.raid-recovery-guide.com/raid5-write-hole.aspx[/url]. While no RAID is perfect, 5 is being revisited as not being all that reliable due to the nature of the write hole. RAID 10 is a little better for this, but make sure you never lose power to the system when it’s writing or you’ll lose all the data as well.
However, for me, up time and reliability was more important to me than capacity. So RAID 10 was my choice. I could have a potential greater loss of drives at 1 time without losing everything, so RAID 10 was the route I chose to go. If I were to do it over, I may look into RAID 6 next time.
A note for those of you who use FOG on VMware. vSphere 5.5 was just announced 2 weeks which looks to provide pretty significant improvements over 5.1. Thankfully Workstation 10 already has these improvements so you can do some testing! You can review what’s new here
[URL=‘http://blogs.vmware.com/vsphere/2013/09/a-summary-of-whats-new-in-vsphere-5-5.html’] [SIZE=2]http://blogs.vmware.com/vsphere/2013/09/a-summary-of-whats-new-in-vsphere-5-5.html[/SIZE][/URL]
It was to long to post here.
wwyhy,
Here is what I posted in another thread:
[QUOTE]
That’s a known issue. What you need to do is go and download a kernel from here,[URL=‘http://sourceforge.net/projects/freeghost/files/Kernels/’]http://sourceforge.net/projects/freeghost/files/Kernels/ [/URL]then whichever kernel you download, you will need to rename to [B]bzImage[/B]. Once this is done, first rename the original kernel to something like bzImage.backup. This is located in /tftpboot/fog/kernel. Once you rename the kernel you downloaded, move it to this folder and you’ll be all set. Just note that it has to be spelled [B]bzImage[/B], all lowercase besides the I. If a capital letter is not right, it will not boot.
[/QUOTE]
Just an update, Falko and I ended up removing about 800 messages of spam earlier today. Everything should be back to normal on the forums.