Want to make a note somewhere that you need to edit the MySQL database that contains the information of where your NFS datastore is to change the IP if you change the IP of your FOG server.

Thanks, guys. It just wasn’t intuitive to me that “groups” were for anything other than organization. It would be cool if this sort of info could be included in the UI in future builds.

I cannot find any information on this on the forum or the wiki. Am I missing something blindingly obvious?

[quote=“BryceZ, post: 9832, member: 2”]So you took out the Recovery partition during install of Windows? I think it’s listed as System Reserved under Disk Management.

I want to say that FOG was written to handle that partition being there or not, but I have a sneaking suspicion that removing that partition could cause problems. I don’t know that it would cause your RAW problems. I’m just thinking out loud.

I recall uploading raw to be a problem for someone a while back, so you might be able to dig through the forums and find some advice, but I don’t remember the resolution.[/quote]
There’s definitely no System Reserved partition in Disk Management.

[quote=“BryceZ, post: 9828, member: 2”]First: Which version of FOG are you using?
Second: When you say these are single partition are you saying you didn’t add any extra partitions or that you went into the advanced options when installing Windows and removed the recovery partition?[/quote]
Hi,

I’m using 0.32 and I didn’t add any partitions and Disk Manager does not report any partitions other than the one. This was Win7 installed straight from installation media with no 100MB partition reserved for BitLocker.

So, in this thread: [url]http://fogproject.org/forum/threads/how-much-space-do-i-need-for-a-new-image.3897/[/url] I thought FOG was just insisting on imaging machines as RAW rather than NTFS. I was wrong. Instead what is happening is that when it performs the partition resize, it trashes the file system. It takes about 3 or 4 minutes to resize the 465GB partition to the size of the data (about 24GB), then starts the imaging process as RAW and attempts to capture the entire 465GB hard drive. This has now happened with two machines, both of which had single-partition maps, one of which was sysprepped, the other wasn’t. Both are Windows 7.

I tried to change the subject line of my original post, but it wouldn’t let me and I’m sort of freaking out because I need this to start working this afternoon.

So, we are capturing our first image from a Windows 7 HP machine with a 500GB hard drive. The actual size of the data on the drive is about 28GB. I told FOG to create a new image that was a “Single Partition, NTFS Only, Resizable” image and then created a Basic Task to upload that image to the server.

The image started uploading, but it is now on 63.20GB of 500GB. Why, when I picked the correct image type and there is so much blank space? Does it actually need enough space to copy the entire drive, and THEN resizes it down?

Caveat: for some reason in the “save partition to image file” box under “Detected file system” it says “raw” rather than NTFS. Why would this be? Is this the reason it’s not working correctly?

Edit: What would cause the resizing process at the beginning of imaging not to work correctly? I did notice it try to resize the partition at the beginning of loading from PXE, and then afterwards it said “raw.” Now, the machine will not boot from the drive. So it appears what happened is the machine booted from PXE, botched the resize operation, and trashed the drive in the process, causing FOG to think “well, I can’t tell what kind of file system this is, so I’m assuming I’m capturing the whole thing.”

Also, when I tried to delete the bad image it failed, and I had to manually delete it from tftpboot.