Posts made by madeyem

If I understand you correctly, this is exactly what FOG is supposed to do after the image process is finished.

FOG will capture your entire partition(s)/disk. If you have more than one partition or even more than one disk, you can choose an adequate image type. For more information click on the question mark next to the drop down menu of the image type.

You can disable the host lookup by going to Other Information > FOG Settings and setting the value of [FONT=arial]“[COLOR=#333333]FOG_HOST_LOOKUP” to 0.[/COLOR][/FONT]

[FONT=arial][COLOR=#333333]Your browser might then stop crashing.[/COLOR][/FONT]

[FONT=arial][COLOR=#333333]Edit: Please don’t post the same message in 3 different threads.[/COLOR][/FONT]

Ok, I forgot to to put the MAC-address of the laptop into the same network as FOG. So the laptop wasn’t able to receive the image. :oops: Sorry…

Hi everyone,

I want to deploy an image to a Thinkpad T510, but the imaging process always hangs at the Please wait…-blue screen.

I’ve tried different kernels, with and without the “nomodeset” argument, but had no success yet. However, the operating system (Windows 7), which was installed on the machine and working properly before, isn’t booting anymore. So I guess, that the MBR has been overwritten/destroyed by FOG.

The image is:
Windows 7 SP1 x64
Single-Partition Resizable

FOG 0.32 on Ubuntu Server 10.04 LTS

I’ve successfully imaged Thinkpads (other types) before, but this model isn’t working. Maybe someone has a hint or an idea. Thanks!

FOG itself can create raw images (see Image type after going to Image Management and choosing an image). Maybe someone can give you a more detailed answer.

If you have an ATI/AMD graphics card in your computer, try setting “nomodeset” under “Host Kernel Arguments” in Host Management.

Why should * be a placeholder and if so, for what? Pausing is working, I’m talking about cancelling the upload/download, which sometimes would be useful, because you wouldn’t have to use the GUI to do a clean cancellation. Sometimes you have no computer at hand (in the same room) besides the one you’re imaging.

So, I’m assuming, that it’s a bug. A not so important bug though…

Hi everyone,

when you’re uploading or deploying an image, according to the blue imaging screen one should be able to pause or cancel the imaging process. To cancel one should press *. Pausing works fine, but cancelling has never worked for me yet.

Is this a bug in FOG 0.32?

I know how to cancel a task in the FOG GUI, but every now and then it may be helpful to cancel the process on the computer, that is being imaged/deployed.

If it’s a bug, maybe the developers could try to fix it in FOG 0.33.

At the moment FOG isn’t able to deploy UEFI based images properly (at least due to my experience). You could try to disable UEFI in the BIOS settings and instead use the so called “legacy mode”, which is an emulated BIOS.
If you then install e.g. Windows, you’ll have one 100 MB start partition and the system partition instead of one UEFI, one (Windows) start partition and the system partition.

I have (as well as many people I guess) this problem as well (but in my case (Germany) the time is only 1 hour off). Have been trying to fix this by messing with the time settings on the FOG server (Ubuntu Server 10.04 LTS), but had no success. Isn’t that much of a problem, so I can live with it. But if there is a simple solution, I would take it.

I installed FOG 0.32 on Ubuntu Server 10.04 LTS and it worked at the first try without any problems. You may try that one.

I assume, that you’re able to choose the new group (of the host) in the same menue “Add to group”? I’m not sure, because i don’t use host groups.

Go to Host management > List all hosts.

Choose the host by klicking the checkbox next to the hostname. Scroll down to the bottom of the page and assign the new group in the menu next to “Add to group”. This group has to exist first.

[quote=“gneville, post: 10439, member: 3313”]- Other machines not able to PXE boot off of Fog PC.[/quote]

I’m not sure, if you got this right, but maybe that’s your mistake:

You have to configure your DHCP to tell your clients where to find the FOG Bootimage [options 66 (IP of your FOG server) & 67 (name of the bootfile)]. You usually don’t configure that on your FOG server, unless your FOG server is also your DHCP. But I would assume, that you have another DHCP running in your environment. Without that information clients aren’t able to boot FOG.

In some cases a few clients might just not be able to boot FOG due to the BIOS or a not supported network card. Sometimes the needed drivers are not included in the FOG kernel as well. However, the majority of (up to date) clients should be able to boot FOG.

Copy the images to the same location on the new fog server as they were stored on the old one, which would be in /images. As long as the permissions are set correctly, you can as well copy the images to a different location/folder. But make sure, that the path in the image definition is correct.

Other information > FOG Settings > [FONT=Ubuntu][COLOR=#333333]FOG_HOST_LOOKUP[/COLOR][/FONT]

[FONT=Ubuntu][COLOR=#333333]Set the value to 0.[/COLOR][/FONT]

Had the same issue.

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

Hope this works for you, too.

One more question:
How long are you waiting, while FOG is “resizing partition” before you interrupt the process? This might take a couple of minutes depending on the disk/partition. At least in your screenshot, there is no error message.

There is no need to use “multi partition”, even if there’s the 100 MB system partition. Try “single partition”, as long as you only have one partition (besides the 100 MB) on the disk.

Edit: This might not solve your problem, but it’s good to know and maybe worth to try.