[quote=“ajcke, post: 12462, member: 97”]Is there a way to delay rename and domain join for x minutes? I have scripts in my answer file setup to run upon first logon. The clients are getting renamed and restarted before the scripts can finish running.

The main script activates Windows 7. If you know of another way to do this that would probably solve this issue as well.[/quote]

Try to stop the FOG Service at the beginning of your script and starting it at the end of it.
If the FOG Service is running it will rename your PC and reboot it, so this will avoid that reboot at least while your script is running.

Awesome glad you fixed it 🙂 Enjoy your FOG server ^^

Ok, well… I’m a little bit ashamed now. It was my own stupidity.
I thought it takes the DMI field when pressing “Add Association”, but you can, or must change the DMI field with the “Update Settings” button. Just tested, Capone works like butter! Very cool.

I had the same problem when running dedup on FreeNAS under ZFS.

In the end, I decided that the RAM hit and risk was not worth the savings.

Hi,

create a md5 checksum:
[CODE]md5sum filename[/CODE]

find the matching md5 checksum here:
[url]http://sourceforge.net/projects/freeghost/files/Kernels/[/url]

click on a kernel version then click the (i)nformation icon you will then see two checksum’s sha1 and md5:
[IMG]http://i.imgur.com/FgNVzWs.png[/IMG]

Greetz X23

ok I got past that issue by following the following form Thread [url]http://fogproject.org/forum/threads/problems-when-installing-on-rhel-6-3.4017/#post-10653[/url]

but now I am getting the following error
Setting up and starting VSFTP Server…Failed!

at first I thought it was because I had the ClearOS FTP app installed which I believe uses proftpd, so I uninstalled it, but I still get the same error. is there an install log I can check or something to find out why?

Awesome thanks I will give this a try I did all but the recreation of the images previously, well tried it and didn’t work but I will try it again.

Thanks

I do have a new Win 2008 server. It replaced a Win 2003. Could that be the culprit?

Hi,

is there a partimage update that can handle guid?

If the old image has been overwritten with a new image then someone must have forgot to associate the computer with a new image file / definition. Some of our engineers make this mistake too.

You have only 3 options:

Try a Linux file recovery tool on the FOG server. Upload again from any of the 200+ workstations that has the image. If you can find one that’s not been used great. Recreate the image from scratch.

Start backing up your storage node at least 1 a month.

Try a different kernel, you may want to include the drivers and make your own, it’s surprisingly easy, most problems stem from the fact that the drivers aren’t in the kernel, they’ve tried to put as many as possible in there but some are still missing.

You can change your kernel in your Fog Management screen and try an older kernel and see if that helps, if not try these step below.

[INDENT][B]How to Build a Custom Kernel for FOG Server using Ubuntu 12.04[/B]

First, make sure you have [B]G++ (GNU C++ compiler) and QT4 (Qt 4 Designer) [/B]installed through the Ubuntu software center.

Next, pick a Linux kernel you want to use to compile the kernel at [URL=‘http://www.kernel.org/’]www.kernel.org[/URL]. (Used linux-3.10-rc2.tar.xz for this document;[url]https://www.kernel.org/pub/linux/kernel/v3.x/testing/linux-3.10-rc2.tar.xz[/url]) Download the file to the ‘home/user/Downloads/’ directory. (default)

Then, download the Fog installation package installer. (Current version 0.32;[url]http://sourceforge.net/projects/freeghost/files/FOG/fog_0.32/fog_0.32.tar.gz/download[/url]) Make sure to download to the ‘home/user/Downloads/’ directory. (default)

Now we will extract the files to their proper locations.

First, extract the FOG installer to the download folder. (see below for command)
[B]sudo [/B][B][FONT=Tahoma]tar -xvf /home/user/Downloads/fog_0.32.tar.gz[/FONT][/B]

Then, we will want to extract the kernel to the ‘/usr/src/kernels/’ directory. If the directory does not exist create it. You will also need to copy the tar.gz file to the kernels directory in order to extract properly. (see below for commands)
[B]sudo mkdir /usr/src/kernels/[/B]
[B]sudo cp /home/user/Downloads/linux-3.10-rc2.tar.xz /usr/src/kernels/[/B]
[B]cd /usr/src/kernels/[/B]
[B]sudo tar –xvf linux-3.10-rc2.tar.xz[/B]

Now we can either use CORE or Kitchen Sink to create the kernel.

To use [B]Core[/B] use the following command:
[B]sudo cp [/B][B][FONT=Tahoma]/home/username/Downloads/fog_0.32/kernel/core.config /usr/src/kernels/linux-3.10-rc2/.config[/FONT][/B]

To use [B]Kitchen Sink[/B] use the following command:
[B]sudo cp [/B][B][FONT=Tahoma]/home/username/Downloads/fog_0.32/kernel/kitchensink.config /usr/src/kernels/linux-3.10-rc2/.config[/FONT][/B]

Once the .config file is copied to /usr/src/kernels/ you can now run the make xconfig command.
[B]cd /usr/src/kernels/linux-3.10-rc2[/B]
[B]sudo make xconfig[/B]

Now the kernel editor should pop-up after a few seconds. Here is where you will locate and select/deselect drivers you want to load to your custom kernel. (see screenshot for example)

[IMG]http://i.imgur.com/a49MUxh.jpg?1[/IMG]

Once you are done with your selections just [B]save and quit[/B].

Now you have to run one final command to write the kernel file.

For 64-bit systems:
[B][FONT=Tahoma]sudo make ARCH=i386 bzImage[/FONT][/B]

[FONT=Tahoma]For 32-bit systems:[/FONT]
[B][FONT=Tahoma]sudo make bzImage[/FONT][/B]

[FONT=Tahoma]You may get a few prompts during the compile, I just used default options (enter). It will take a while (10-30 minutes) to compile the kernel so be patient.[/FONT]

[FONT=Tahoma]Now that you have created a custom kernel you will need to copy/cut the file to your FOG server.[/FONT]
[FONT=Tahoma]Go to the [B]/usr/src/kernels/linux-3.10-rc2/arch/x86/boot/[/B] directory to find the new [B]bzImage[/B] file you created. That is the file you need to import to your FOG server kernels directory in order to use it. (You can rename it or use the new kernel as the default kernel for FOG to use if you leave the name bzImage)[/FONT]

[FONT=Tahoma]The directory where you should paste the new kernel is /tftpboot/fog/kernel/ on the FOG server.[/FONT]

[FONT=Tahoma]Make sure you assign the custom kernel to the proper host in the FOG management GUI and then you should be able to Upload/Deploy. You might need to add the host manually; you’ll just need the MAC address of the NIC for the host.[/FONT]

[B][I][FONT=Tahoma]Written by Ozzy[/FONT][/I][/B][/INDENT]
[INDENT]Thanks to ozzy for the write up, you can find the post here:[/INDENT]
[INDENT][url]http://fogproject.org/forum/threads/hard-disk-not-found-lenovo.4159/[/url][/INDENT]

So, doing a sector-by-sector worked perfectly. However, it did take 10.5 hours to deploy the image. Being as I need to deploy this same image to 25 other laptops, this method would be pretty painful. Going to try some more testing with multi-partition, single disk today.

Thanks. We will work through this and come up with a solution!