Jump to content

Recommended Posts

Posted

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

  • Thanks 1
Posted
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?

Posted (edited)

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.

Edited by Chad
clarification
  • Thanks 1
Posted

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.....

Posted

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.

Posted
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.

Posted
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

Posted
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

Posted

I think the installer is only tested on ubuntu and fedora so either of those would seem a logical choice.

I use debian and haven't had any issues.

Posted
I use debian and haven't had any issues.

 

We have FOG running on Debian Lenny right now - I've just had too many issues with Ubuntu Server in the past, I just rather prefer Debian these days. Saying that, I'm not having a great deal of success installing Debian Squeeze on my own servers right at the moment - the GRUB2 bootloader (or, at least, it's installation/configuration from Debian) seems rather flakey.

Posted

On Xenserver I had to install the grub legacy package after an upgrade to Squeeze to get it to boot.

I guess you are running it on Xen though so maybe there is a different workaround but I imagine it's the same backend stuff trying to locate and execute the bootloader.

Our FOG system is still on debian lenny for the time being though.

  • Thanks 1
Posted
I guess you are running it on Xen though so maybe there is a different workaround but I imagine it's the same backend stuff trying to locate and execute the bootloader.

 

I think GRUB2 is just getting confused finding the boot partition at all - this is on my own (brand new) Atom-based server with two harddrives for storage and a USB stick as a OS/boot device. I had the same issue with my Core i3 server - I wound up swapping the USB stick for a USB harddrive and installing plain GRUB via SystemRescueCD. I'm just waiting for a new SATA controller card to arrive, then I'll plug another harddrive into this server and see how I get on with that.

 

Our FOG system is still on debian lenny for the time being though.

 

The school's FOG install will be running on Xenserver, so your advice above will come in very handy, thanks.

Posted (edited)
Hey guys i have just upgraded to 0.30 on unbuntu and when i try to upload a windows 7 image it freezes after 5 or 6 seconds help!!

 

Been troubleshooting a bit more today, it seems it is only intels DH55PJ motherboard with the issue. :confused:

 

http://dl.dropbox.com/u/11049959/Photo%20Mar%2002%2C%203%2040%2041%20PM.jpg

Edited by binglegc
Posted

Any chance of enlightening me on this a bit more, we too are experiencing very slow image deployment, that's if it starts at all.

 

Where about was the file you replaced? (running on a ubuntu server.)

 

John

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.

Posted (edited)
Any chance of enlightening me on this a bit more, we too are experiencing very slow image deployment, that's if it starts at all.

 

Where about was the file you replaced? (running on a ubuntu server.)

 

John

 

Crikey - we've had all sorts of issues with 0.30 to the point where we've replaced the init.gz with the 0.29 version and rolled back the default kernel to the previous one we were using.

 

Some of our machines imaged (upload and download) phenomenally fast though - triple the speed in some cases - others just stopped working with Fog. Everything worked with the 0.29 hence the roll back.

 

Quick image has stopped working also but we haven't had time to investigate this or to check if anything else is broken.

 

Cheers

 

HBJB

Edited by Heebeejeebee
erronious character removal

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...