[Fog] FOG 0.30 Released!

[Cools]

FOG 0.30 Released!
Get it here..

FOG 0.30 Released! | fogproject.org

[reggiep]

In case anyone is interested in what's changed this is directly from the change log...

Version 0.30
------------

*Rebuilt init image (ALL Thanks to Aaron Bergz!!!!) details below
**Converted to Busy Box
**Added detection for number of CPUs
**Parallel upload image compression
**Added drive write cache check.

*Update memtest from 4.0 to 4.2
*Updated kernel to version 2.6.37 (core)
*Added kernel branch - core
*Added additional search fields to the host search from the inventory table
*Updated chntpass support to scan partitions looking for sam file

[dhicks]

In case anyone is interested in what's changed this is directly from the change log...

Thanks - we run FOG on Debian, which we need to move to a different machine/VM system, so I'm wondering if we should simply install a new Debian VM from scratch and install a new copy of FOG on that rather than try and move our old server accross. Would you know if you can move disk images between versions of FOG okay?

[Domino]

You can indeed.

Well previously you could, I've no idea about this new version, but I see no reason why not

[Chad]

I've found deploying images to PCs with 0.30 is a lot slower than when I was using 0.29 and the latest (0.30) kernel. Has anybody else played with this yet?

After some experimentation I replaced the 0.30 init.gz with the one from 0.29 and my image times are really fast again, so it's something to do with the new busybox init.gz but I've not had time to hunt it down further yet.

[Universally_challenged]

Hi guys. i put my first Fog server in a production enviroment the day before this was released. anyway, does anybody use the "rename host" function. Im finding its borked my AD. The images are syspreped and set to automaticly join the domain. Then FOG's client gets involved and changes the host name, which changes it locally, but not in the AD causing me to have to leave, and then rejoin the domain after deleting the computer out of the AD.
As it never promps for and AD authentication im guessing its just some forced reg injection.

I know the FOG client can add a machine to a domain, but i'd rather sysprep did it. But would this solve the problem?

Thoughts.....

[reggiep]

I'm not completely understanding what your problem is but...
We have used the rename function in the past with no problems. It just went ahead and called the machine whatever it was called in fog and then rebooted it with the new name. That then showed up in AD.
We now use a sysprep that doesn't join the domain and let fog both rename the machine and then join it to the network.

[dhicks]

Well previously you could, I've no idea about this new version, but I see no reason why not

Thinking about it, FOG disk images are just Partimage images, and I don't think the version of Partimage used will have changed, so there should be no issue with simply copying image files over.

[Universally_challenged]

hey reggiep. all sorted now.

[reggiep]

hey reggiep. all sorted now.

What did you do?

[armadillo]

Hi Guys,
Does fog support windows7 imaging and does it work on server 2008R2 AD?

Thanks in advance.

[CyberNerd]

Hi Guys,
Does fog support windows7 imaging and does it work on server 2008R2 AD?

Thanks in advance.

it supports win7 and will image a 2008 server but needs to run on a linux box

[Domino]

It supports Windows 7 fine, but runs on a linux OS

you could run in it a VM ontop of server 2k8 though

[armadillo]

Thanks a lot chaps; I am thinking in running it ona ubuntu box, or would you advise debian instead?

[CyberNerd]

Thanks a lot chaps; I am thinking in running it ona ubuntu box, or would you advise debian instead?

debian might be better in the longer term. if you choose ubuntu make sure you get the long term release