FOG Does not Restore the 100MB Partition for Windows 7 Image
-
I would guess that the 100MB partition growing to 105MB might be related to the [FONT=Ubuntu][COLOR=#333333][B]FOG_UPLOADRESIZEPCT[/B] setting under[/COLOR][/FONT][B] Other Information > FOG Settings > General Settings. [/B]It’s default setting of 5% seems like it may be non-conicidental in this case.
-
Draylorre, did you get this figured out?
I have imaged Optiplex 755’s running Windows 7 many times with and without the 100MB system partition. I have never had any issues when I use the “Multiple Partition - Single Disk” option.
–astrouga
-
I have given up trying to get windows 7 to work with the resizable image type. I use the multiple partition - single disk. It still compresses the image and only stores actual data, so if a full load uses 70GB in windows, the image is around 50GB on the server.
-
I have always used 100mb + rest of disk (2 partitions) and set image to: Windows 7 | Single Partition (ntfs Resizable)
-
We have been able to use the NTFS Single Resizeable with our Dell computers by reinstalling Windows 7 scratch, delete all of the existing partitions, and let the Windows installer create all of the partitions including the 100MB partition. We were not able to use the NTFS Resizeable with the Pre-loaded OS that Dell installs on the new computers. I am not sure if that helps or not.
-
My experience is similar to Bounty’s. I have had limited success using the Single / Resizeable but the multiple partition always works so I don’t waster my time fooling with the Single option.
-
Depending on your install of Windows 7 will determine what image type you can select. Most of the major manufacturers have that little recovery partition that is preloaded into the OEM versions of Windows 7 that comes with the machines, therefore you either have to CAREFULLY remove the recovery partitions (there are many guides on the internet detailing this, but use with caution) or upload as Multiple Partition - Single Disk. However, if you are using a stand-alone install of Windows 7, the Single Disk - NTFS Resizable works just fine.
Again, I want to echo if you’re considering deleting the recovery partition to be very careful in doing so, depending on the OEM install, that partition may also contain the Bootmgr and other necessary startup files, so proceed with caution.
-
I use “Multiple Partition - single disk”, regardless of the number of partitions (one or more) and it always works. “Single Disk - NTFS Resizable” is broken though. I have tried many, many different Windows 7 stand-alone installs and it fails. I don’t think I have ever gotten it to work. Truthfully, given the number or people claiming that it fails, I don’t think it is reliable. I wouldn’t recommend it until .33 comes out. The developers are definitely aware of problems that I’ve had with it and are addressing it in the next release.
-
That’s odd Astrouga, maybe it’s dependent on the machines? I’ve never once had a problem with it, but as you said, I could be one of the rare ones from the sounds of it. Thanks for the info
-
Yeah, perhaps. I’ve just given up on the “single disk” for now. I’m going to test out the latest .33 beta trunk tomorrow. Looks like the NTFS resizable option is a work in progress though:
[url]http://freeghost.svn.sourceforge.net/viewvc/freeghost/trunk/?view=log[/url]
Cheers,
astrouga
-
Hmmm, interesting. I haven’t had any problems using a single resizable partition. I wonder if that’s because all of our machines still have the 100mb partition still in place when they are imaged, and perhaps the image just replaces the OS partition instead of the system reserved.
Our machines are all typically the Dell Latitude series (couple of Precisions, but they work too), and the master image came from a modified e6510 build (it’s been converted to a VM, since).
