Posts made by madeyem

I haven’t tested it yet with the tower version, but when I do and somehow figure it out, I will post that here.

Those “error” messages are the usual ones, which show up on almost every computer. Just wait, after 1 or 2 min FOG should continue with whatever task.

Hi everyone,

I just want to confirm, that the quite new HP desktop model “HP EliteDesk 800 G1” is working properly with FOG 0.32 (Kernel 3.8.8). I tested it with the Small-Form-Factor version. I have the same model as a normal tower machine and will test it as well in the future.

Maybe someone with Wiki access can add the “HP EliteDesk 800 G1 SFF” to the working devices.

Thanks.

Edit (October 21st 2013):
According to JimW the tower version also works with FOG 0.32 and kernel 3.8.8. See post #9 in this thread.

Edit2 (October 23rd 2013):
I now can confirm that, too.

Maybe you have the same problem, that I had last year:

[url]http://fogproject.org/forum/threads/win-7-image-upload-no-partitions-found.1130/#post-5714[/url]

1. Download the specific kernel from here:

[url]http://sourceforge.net/projects/freeghost/files/Kernels/[/url]

2. Copy it to the FOG server to:

/tftpboot/fog/kernel/name_of_kernel

3. Go to Host Management in FOG GUI and choose the host, that is supposed to load the specific kernel. Under “Host Kernel” include the path to the specific kernel (leave out /tftpboot/ in the path): fog/kernel/name_of_kernel

4. Click “Update”.

That’s it. Now the chosen host should load the specific kernel.

You can register those machines manually, when you know their MACs. So there is no need to switch any kernels. Just put in the MAC, name the host (any name will be fine), and include the path to the working kernel.

Just in case you don’t know this:

You can choose which kernel to use for every host separately. Just copy all the kernels (in your case that would be 2) you need to the FOG server (/tftfboot/fog/kernel). Under “Host Management” click on the hosts, that don’t work with the default kernel (in your case the Acer laptops). Under “Host Kernel” include the path to the alternative kernel (in your case 2.6.37).

I guess that’s how it’s supposed to work, but I’ve never tested it yet. Within every storage group all images from the “Master node” should be copied to the other nodes.

All storage nodes, that belong to the same storage group, will contain the same images. You can create different storage groups and assign the nodes to them. The default storage group is called “default”.

If you want to use Sysprep with an unattend.xml, you have to run a batch script, in which you specify the location of the unattend.xml. Starting Sysprep via the GUI will always run the default Sysprep process.

For example, create a batch file with the following content:

[CODE]@echo off
cd c:\windows\system32\sysprep
sysprep /oobe /generalize /shutdown /unattend:C:*path to the unattend.xml*\unattend.xml[/CODE]

I always unplug additional HDDs before deploying/imaging, because I would assume FOG to act like that (i.e. not always take the first HDD for deploying/imaging). Maybe someone else has a real solution to this.

As far as I know you can delete the image definition as well as the image itself by ticking a box.

Just a quick question:

Is it possible to build a custom kernel using this HowTo, if one is using a server version of Ubuntu, which means with no GUI? Is there a command line version of the kernel editor (which would have to be a text file I guess)? Or would I really have to use a desktop version of Ubuntu?

I’m from Germany, but to be honest, the English version is fine with me.

If no kernel works:

• Take the HDD out of the machine, that can’t boot FOG
• Put it in a machine, that can boot FOG
• Assign the right image to that machine
• Choose “Shutdown after task completion” in task configuration
• Start task
• After task is finished, put the HDD back in the original machine
• Start the machine

This is a workaround, if you have generalized images (Sysprep for Windows).

I’m not using FOG in association with AD. So I can’t help you with this. Maybe you can find some advice in the FOG Wiki or in the forums.

If you don’t create a new image definition and assign it to the host you want to image, the old image will be overwritten.

Then maybe this thread and the included link will help you:

[url]http://fogproject.org/forum/threads/bypass-host-registration-0-32.3984/[/url]

I assume, that you haven’t registered your target machine in FOG:

1. Register the target machine (its MAC to be more exact) in FOG. You can do that by either using “Quick inventory” in the PXE bootmenu or by adding a host manually. The MAC has to be exactly right, the name however isn’t that important (just put a name in the field).

2. Assign the image you created to the target machine and choose the right operating system of the image. You do that in the host configuration menu.

3. Go to task management > List all hosts, find your target machine and click on the deploy arrow (the one facing down).

4. Boot up your target machine into PXE. The rest should happen automatically.

That is most likely a problem with permissions. Please search the forums, the Wiki or Google. There should be a lot of threads regarding this problem.