[quote=“falko, post: 12387, member: 48”]it sure can, but only if it is the default windows 7 install (two partitions, 100mb + rest of disk for )

I have been using the default windows 7 install with single partiton re-sizable option in the fog web ui for a very long time. with a 100gb hd for the master image I have had it successfully deploying to 250gb, 500gb etc

edit: above setup is with virtualbox and FOG 0.32[/quote]

[SIZE=3]When uploaded will the image also shrink to the least required about of space? My virtual HD is 60gb, but when I upload my image it’s ~15gb total. It’s been almost a year so I don’t remember what exactly brought me to thinking 100mb had to go, but i think it was because before getting rid of the second partition, the image was only uploading via RAW (wasting 45GB of space on my server and ensuring I couldn’t ever deploy to a smaller then 60gb HD. However unlikely that would be ) My early attempts in creating fog images weren’t on virtuals, and after reading what x23piracy had to say its possible the machines I was working on had UEFI enabled and maybe that brought me to that conclusion.[/SIZE]

[SIZE=2]I’m gonna have to test this come Tuesday, If FOG can shrink the size of the image with the 100mb included, I will be extremely happy. That will save me tons of work![/SIZE]

AFAIK fog cannot resize images with multiple partitions

I figured out my problem, but never posted the solution. Well that came back to bite when I was making a new image. I forgot that I had this problem before and ran into it again. Searching the internet I stumbled back on this forum. Well this is how I fixed my problem. I’m not going to pretend I know the technical reasons for this but when I originally made my image I had used gparted to initialize and format the disk to avoid windows making the system reserve partition. My guess was that was sufficient for windows to boot, but when part image looked at the disk, it found something it didn’t like and reverted to raw instead of NTFS for the upload. I fixed\worked around the problem by first mounting my newly created virtual disk on an existing windows virtual, then initializing and formatting it using disk management. The bummer is I couldn’t use the image I already built. But now I know how to avoid that in the future.

Im using vmware to build my image. I mistakenly didn’t change my hard drive to IDE before installing windows and therefore built a custom kernel for vmware. But when I went to upload my image, it would upload raw, even though I have the image configured for 1 partition re-sizable. (I do not have 100mb partition). Any Ideas?

Well I’ve tried deploying the image in different HDD modes. Didn’t make any difference. I have attempted yet to upload an image in legacy mode. I will be testing that next.

I’m using an 80GB hard drive to build the image, and not the factory drives. The image is a single partition and I’m pre-formatting the entire hard drive with one partition before installing windows so the windows 7 installer wont create the 100mb system reserved partition.

Yesterday I used the image I built on the dell to deploy to 30 Lenovo 1578-g2u, 25 Lenovo 7844-P9U, 20 Dell gx620, and 2 custom rigs each with different Gigbyte motherboards, 1 of the Gigbyte machines had the same problem with the Dell and Lenovo images as the dells did with the lenovo built image. I really hope to figure this out because I have several hundred of these gigabytes with at least 8 different motherboard models. I would prefer not to have to build a specific image for them.

I haven’t tried that yet, but I will because this problem is interesting. The images that wont deploy to the dell’s where captured using a Lenovo 7099-u2u system. Oddly, If I capture the image using a dell gx620 everything works fine and I can deploy between the lenovos and dells. For immediate purposes I’m just gonna build my image on a dell to get this project done. Hopefully when im done I can research the problem more.

I’ve only every seen that screen update in unicast.

Im trying to deploy a windows 7 image to some gx620 computers. For some reason fog will not transmit the image. the kernel loads correctly, when I reach the screen where you would normally see fog sending the image over, on these machines it begins the completion process instead. If I send one of my XP images to the machine everything works fine. I can deploy this windows 7 image to all my other hardware just not these gx620. I’ve tried using a different kernels like 2.6.39.1 and the same problem happens. Any Ideas?