The problem only rears its head when I deploy to unpartitioned drives. If I create a partition manually it doesn’t seem to care. In fact, I don’t even have to create two partitions (the 100MB system partition, and a secondary remainder partition). I can even create just a single FAT32 partition, and as long as the original image was created NTFS, it will overwrite the partition I created and replace it with the proper partitions including the system partition.

Well, you hit the nail on the head.

All that was necessary was just changing the Host OS setting to Vista instead of Windows 7 and then it was able to create partitions and then clone just fine. I was even able to use other images that were created with the “Windows 7” setting, as long as the Host OS for that host was set to Vista.

Could anyone explain what is different about these settings?

I will try this today. I have been using multi-partition single images of Windows 7 and setting the type to Windows 7. I will try with Windows Vista and report back.

Maybe this is a dumb question, but should Fog deploy images to blank hard drives?

For some reason, Fog is not creating partitions for me. If I manually create a blank partition on the hard drive, then my deployment will work fine, however I would prefer Fog being able to do this for me.

Currently, when I try to deploy an image to a blank drive it will attempt to start copying over the image, and then report:
ntfs-3g: No mountpoint specified.
Shortly after, it will reboot, thinking the deployment went OK, but nothing was ever transferred.