[quote=“Nate Baker, post: 24539, member: 23116”]I know this thread is old, but wondering if anyone else has had success with this?

Doug, your method sounds like it would work great, but I’m wondering if that would work with critical drivers such as storage and network? Or do you need to have the storage and network drivers in the image already, and install the rest of the drivers using that method? It seems like since that oobeSystem pass is the last pass, it would need the storage and network drivers by that point.

Thanks,
Nate[/quote]

Sorry for the late reply. You are correct, Nate. I inject mass storage and LAN drivers into my base image for all the models of computers we deal with here before sysprep.

I wanted to update my post in case others where having the same issue. I have not figured out the problem with capturing/deploying a resizeable image on Win7 but I did get a decent work around in place. Basically I used Stephen Perkins [URL=‘http://fogproject.org/forum/threads/resizing-partition-with-windows-7-image.250/#post-1332’]post[/URL] idea of just adding a command to my unattend.xml to extend the OS partition during sysprep since I was able to capture and deploy a non-resizeable image with no problem.

Thanks Stephen, I just used your technique and it worked great. I had tried scripting it but the scripts apparently wouldn’t work probably due to permissions.

Great! Glad you got it working.

That is interesting. I find this strange as I have created over the past couple of months single partition resize-able images as well as dual partition resize-able images (for windows 7) and all has worked flawlessly. Now all of a sudden I am having problems both capturing and deploying them. I have not changed anything on my FOG server and have been using it to image XP machines for the past 2 years. Although others have posted having similar problems I have seen no real viable solutions to speak of. I don’t understand how the scripts can appear to be changed/wrong as I have not updated my FOG server so why the errors?

What happens if you do a deploy-debug and then manually dd the d1.mbr to the hdd? Does that work okay?

Thanks for the reply Bobfrid. I am using an Autounattend.xml to create the single or double partition setup. I am using FOG .29 running on Ubuntu 10.04 server. I have been using this setup for awhile now with windows xp with no issues. I have created the image on physical machines (several types) but am currently working in a VirtualBox virtual machine running on Linux Mint 12.

Playing around this afternoon I was able to manually capture the image by using the commands in the /bin/fog script (partimage save …) but when I deployed it it wouldn’t boot. I’ll continue playing around next week…

I am developing my Windows 7 image and am having a couple of problems. I posted in a separate post but this sounds like similar issues and seems to be an active post.

1. When I try to capture a Windows 7 Enterprise image with 1 partition it immediately fails when starting the partimage (blue screen).

2. I have successfully captured an image with 2 partitions (Includes the 100mb part) but when I try to deploy it I get a BOOTMGR is missing error.

As it is I cannot seem to either create or deploy a Windows 7 image in FOG. I have tried this on various hardware as well as in a virtual machine all with the same result. Others have commented in my post to having the same issue. Any ideas??

Sorry, Tim, I should have mentioned that I am running on .29 so I am not sure if the script changed at all but it certainly sounds like the same problem. If you are getting the same error about the backup path doesn’t exist (right after the blue screen goes by - you have to scroll up to see the message) then I assume it is the same issue. What do you mean by swapping out the older version of the script?

Hi Tim,

I am having the same issue and mention it under my BOOTMGR is missing post (I should have created a new post). I don’t have a resolution but I have noticed that there seems to be an error in the FOG script ( /bin/fog ) If you scroll up using the <shift> key and the <page up> key after the blue screen flashes by in debug mode you should see an error. There appears to be an error on line 624 that causes this. I fixed that error in the script, however, now I am having a problem regarding partimage not being able to determine the file system type. I haven’t gone further yet to see if I can fix that. Any help is greatly appreciated!