Default storage location: /images/
Change storage location:
FOG Web GUI -> Storage Management -> All Storage Nodes -> Default member -> Image Location
If you want to place the images on an external drive/storage/computer, you will have to mount them first on your Fog server. You could try to set up a new storage node (might be the easiest way).
Delete: rm -R /images (or any other folderpath)
Make sure your new storage location works before you delete anything.
You could try and use a separate network card in the machine and see, if that works. I’ve experienced issues, when trying to PXE boot Dell Optiplex 780 machines. It has never worked with the onboard LAN port yet for some reason.
You have to boot from network using PXE. Usually you can press F12, while the machine boots up. Then you see the FOG menu. You might have the timeout set to 3 seconds or so. Log into the FOG webinterface > Other information > PXE boot menu. There you can increase the timeout.
[quote=“chad-bisd, post: 4566, member: 18”]A new storage node will contain the same images as your “main” server. It doesn’t really extend your storage space, but increases the amount of hosts you can deploy at a time.[/quote]
Besides setting up a new storage node you would have to create a new storage group as well and assign the new storage node to that group. Then you would have two different storages with different images on it. I tested this a couple of month ago and it was no problem.
I was just able to upload UEFI based images, but not to deploy them. I think that FOG 0.32 can’t handle this yet. So I posted a feature request. Maybe this feature will be integrated in future releases.
Ich würde dir wie mein Vorposter ebenfalls empfehlen Ubuntu 10.04 LTS als Basis für FOG zu benutzen. Damit hatte ich bisher keine Probleme. Falls du dann Probleme beim Imagen oder Deployen hast, müsste man im Einzelnen gucken, woran es liegen könnte.
Soweit ich weiß gibt es kein deutschsprachiges Forum für FOG.
Having a MSR partition means that Windows is installed in (U)EFI mode, not in the old MBR or “legacy” mode. I haven’t been able to deploy hosts with UEFI based images. So I would suggest that you reinstall Windows using the legacy mode.
if you want to delete the whole directory, try
rm -r /images
maybe you need to put a “sudo” in front of it.
This has been requested before:
[url]http://fogproject.org/forum/threads/having-a-next-user-level-besides-mobile-user.557/[/url]
I think that would be great, too. Especially a user profile, which enables a user to only modify the images created by himself, not images created by other users.
With the help of Michael’s thread here
I finally was able to solve my problem. In my case it seems as if the GUID partition table and the MBR were confusing each other, so the Linux-FOG-Kernel couldn’t find any partitions.
Here is what I did:
[B]Please note:[/B]
Since my computer was just a testing machine to create an image I did not backup anything before doing this. As recommended on the Fixparts webpage you should certainly do a backup (of MBR, system and data, or in other words everything ;-), if you’re going to do the following steps on an important machine/system.
[url]http://www.rodsbooks.com/fixparts/[/url] (look for the link “download page”)
Unzip the file and execute it with administration privileges. A command window will now pop up.
Type in “0:” (this command is just for Windows!) to define your first (and in my case only) HDD to be the one to analyse.
Now the tool suggests to delete the GPT signatures and asks you to confirm. If you want to use Linux as well as Windows on your disk you probably should not delete those signatures. But in my case I only want to use Windows, so I say yes.
After that exit the tool by typing “w” (write changes to disk and quit). Restart your computer to check if it still works.
Sysprep the OS and upload the image to FOG.
Thanks Michael!
This is also the solution to my problem described here:
[url]http://fogproject.org/forum/threads/win-7-image-upload-no-partitions-found.1130/[/url]
Some other things I’ve tried:
Nothing solved the problem yet.
If a developer reads this, maybe you can explain to me, when/why exactly FOG decides that “No partitions (were) found”. I don’t have any clue, because in this case that error message makes absolutely no sense to me. The OS is working fine and there are definitely partitions existent.
By the way, the steps prior to imaging are finished successfully. But then it goes “An error has been detected”…
Hi everyone,
I have a problem.
During my vacation my colleagues accidentally overwrote my master image. So I have to create a new one.
Device: HP 8200 Elite CMT
OS: Windows 7 Enterprise x64 with Service Pack 1
FOG 0.32 is running on an Ubuntu Server 10.04 LTS.
So I installed Windows using the legacy “BIOS” mode, because as some of you might know, there are problems with FOG when using (U)EFI. I installed all drivers and applications needed. Then I syspreped the machine using an unattend file, which I successfully used before.
When I try to upload the image, for some reason FOG says “No partitions found”. I can’t figure out why. The OS is definitely working fine. The HP computer shouldn’t be the problem, because I used the same type for imaging and deployment successfully in the past.
What I’ve tried so far:
Keep getting the same error.
Maybe some of you have any idea or hint for me.
Thanks in advance!
Hi,
i used Dell Optiplex 790 and 990 systems for testing purposes and e.g. a Western Digital WD800JD disk.
Now with HP 8200 Elite computers:
If i deactivate (U)EFI in the bios and use the legacy bios mode it mostly works fine (after using sysprep). So i strongly guess that FOG has an issue with the (U)EFI partition and its boot settings.
As i mentioned above FOG doesn’t even create the needed partitions (3 when installing Windows), so the imaging cannnot succeed.
Hi everyone,
first of all FOG is a very nice software!
Here is what i would like to be implemented within the next releases:
I install Windows 7 x64 on an UEFI-machine, which works fine. Then I image that machine by choosing the image to be a “Multiple Partition Image - Single disk” due to Windows-setup creating 3 partitions during the installation process. Imaging works fine as well. I end up having 4 files on my storage node:
[CODE]-rwxrwxrwx 1 root root 512 2012-03-26 14:20 d1.mbr
-rwxrwxrwx 1 root root 9524580 2012-03-26 14:20 d1p1.img
-rwxrwxrwx 1 root root 81928954 2012-03-26 14:20 d1p2.img
-rwxrwxrwx 1 root root 13405024509 2012-03-26 14:28 d1p3.img[/CODE]
Then if I deploy that image so the very same disk, which already has Windows 7 installed (incl. the 3 partitions mentioned above), that works fine as well.
But if i format the disk and delete all partitions (or just insert an empty disk), i am not able to deploy the image.
What i can do, is to start Windows-setup unto the point where it creates all the partitions, then abort setup and start deploying the image. The deployment finished correctly but the system won’t boot whatsoever. Unfortunately the Windows repair tool doesn’t fix the problem.
Maybe you can implement a corrrect deployment of UEFI-partitions including correct partitioning and boot-settings. That would be very nice!
Or just tell me, if I’m doing something wrong. 
Thanks in advance!