Using Capture Media to create Image Fails with iastor error
I am trying to capture a system that is to be the Gold image. I have tried this on two separate machines, an Dell Latitude E5520 and an optiplex 390 and get the same problem on both. The system in Windows 7 Sp1 x86, and in the Task Sequence media Wizard I select the x86 boot PE, I have used Dells Drivers, and even verfiied that the Drivers in the WinPE Image that I added via SCCM do actually meet this drivers criteria (manually copied to a USB and then added to these machines to verify it). The Sysprep folder is created, and the Administrator password is Blank. The Capture ask me the normal information and then off it goes. After reboot it fails to get back into Windows stating it cannot find c:\windows\system32\dirvers\iastor.sys A Repair using the Windows 7 CD gets me back to normal but thus far I cannot seem to find what would cause this? Any other ideas out there? David Baur
December 2nd, 2011 4:11pm

Hi David, So, are you suggesting that after you capture this image, any machine you deploy the image to will have the missing iaStor.sys error message? It sounds like you need to build driver packages to target the appropriate mass storage drivers to the appropriate machines during deployment time. There are lots of different methodologies around architecting driver packages, however I typically build one driver package per make/model + target OS. It probably makes sense to take a step back and look at your reference build process. What steps do you have in your build sequence, prior to the capture step? Also, keep in mind that you may not need to inject any special drivers into the WinPE boot image. In many cases, the Windows 7-based WinPE boot images will already have the network and mass storage drivers that you need to deploy to most client hardware. It's usually worth starting with nothing, and only adding what you really need to. Another thing to think about ... are your boot images WinPE 3.0, or have you applied the Windows AIK supplement and updated your boot images to WinPE 3.1? Might be worth doing the latter. Hope this helps.If this post was helpful, please click the little "Vote as Helpful" button :) Trevor Sullivan Trevor Sullivan's Tech Room Twitter Profile
Free Windows Admin Tool Kit Click here and download it now
December 2nd, 2011 5:30pm

Thanks Trevor, but as stated that has been done already. During the Capture (from the SCCM Capture CD Created) It will not finish the capture, it fails after the reboot trying to capture. I have the Drivers in the WinPE Boot package. Which gets copied to the Capture Image CD. I even verified it was the correct one after the failure. The WinPE 3.1 is definitely something for me to try as well. Many Thanks!David Baur
December 2nd, 2011 5:54pm

Hi David, So, are you suggesting that after you capture this image, any machine you deploy the image to will have the missing iaStor.sys error message? It sounds like you need to build driver packages to target the appropriate mass storage drivers to the appropriate machines during deployment time. There are lots of different methodologies around architecting driver packages, however I typically build one driver package per make/model + target OS. It probably makes sense to take a step back and look at your reference build process. What steps do you have in your build sequence, prior to the capture step? Also, keep in mind that you may not need to inject any special drivers into the WinPE boot image. In many cases, the Windows 7-based WinPE boot images will already have the network and mass storage drivers that you need to deploy to most client hardware. It's usually worth starting with nothing, and only adding what you really need to. Another thing to think about ... are your boot images WinPE 3.0, or have you applied the Windows AIK supplement and updated your boot images to WinPE 3.1? Might be worth doing the latter. Hope this helps.If this post was helpful, please click the little "Vote as Helpful" button :) Trevor Sullivan Trevor Sullivan's Tech Room Twitter Profile
Free Windows Admin Tool Kit Click here and download it now
December 3rd, 2011 1:27am

Hi David, So, are you suggesting that after you capture this image, any machine you deploy the image to will have the missing iaStor.sys error message? It sounds like you need to build driver packages to target the appropriate mass storage drivers to the appropriate machines during deployment time. There are lots of different methodologies around architecting driver packages, however I typically build one driver package per make/model + target OS. It probably makes sense to take a step back and look at your reference build process. What steps do you have in your build sequence, prior to the capture step? Also, keep in mind that you may not need to inject any special drivers into the WinPE boot image. In many cases, the Windows 7-based WinPE boot images will already have the network and mass storage drivers that you need to deploy to most client hardware. It's usually worth starting with nothing, and only adding what you really need to. Another thing to think about ... are your boot images WinPE 3.0, or have you applied the Windows AIK supplement and updated your boot images to WinPE 3.1? Might be worth doing the latter. Hope this helps.If this post was helpful, please click the little "Vote as Helpful" button :) Trevor Sullivan Trevor Sullivan's Tech Room Twitter Profile
December 3rd, 2011 1:27am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics