I'm attempting to capture and deploy a same hardware, NON-sysprep'ed reference image. Currently, I'm capturing via Custom Task Sequence and deploying via Custom Task Sequence. However, it fails everytime. What is the appropriate procedure? Or, what do I need to do differently to make this work. My steps and errors are below. I've created a Package that contains ImageX. My capture TS has two tasks: Map Network Drive (net use g: \\<sccmserver> /user:"<domain\user> <password>) Step always succeeds. Capture Image (imagex.exe /capture d: g:\image.wim "Windows 7 x64" /verify /check; contains Package with ImageX) Step seemingly succeeds. My deploy TS has three tasks: Format and Partition (Primary Partition, use 100% drive, Make boot partition, NTFS Quick Format, Variable "C") Step seemingly succeeds. Map Network Drive (net use g: \\<sccmserver> /user:"<domain\user> <password>) Step always succeeds. ImageX Apply Image (imagex.exe /verify /check /apply g:\image.wim 1 C:\) Step FAILS. The error I receive is: The task sequence execution engine failed executing the action (ImageX Apply) in the group () with the error code 2 Action output: ication) progress: 51 secs remaining [ 96% ] Applying (with verification) progress: 42 secs remaining [ 97% ] Applying (with verification) progress: 31 secs remaining [ 98% ] Applying (with verification) progress: 21 secs remaining [ 99% ] Applying (with verification) progress: 10 secs remaining [ ERROR ] C:\_SMSTaskSequence\Packages\BC100025\imagex.exe (Error = 32) [ ERROR ] C:\Windows\winsxs\x86_microsoft-windows-w..nfrastructure-ws232_31bf3856ad364e35_6.1.7600.16385_none_f28e06e62fa99b35\ws2_32.dll (Error = 32) Process completed with exit code 2 Error restoring image. The process cannot access the file because it is being used by another process. Command line returned 2 Entering ReleaseSource() for C:\_SMSTaskSequence\Packages\BC100025 reference count 1 for the source C:\_SMSTaskSequence\Packages\BC100025 before releasing Delete source directory C:\_SMSTaskSequence\Packages\BC100025 Released the resolved source C:\_SMSTaskSequence\Packages\BC100025. The operating system reported error 2: The system cannot find the file specified.

You can't deploy a non-sysprepped image with imageX. It will BSOD when it boots up. John Marcum | http://myitforum.com/cs2/blogs/jmarcum/|

Then, how do you (easily) capture and deploy a Windows 7 x64 reference machine without sysprep'ing it via SCCM 2007?

I don't think the senario you describe is supported by ConfigMgr 2007. Ronni Pedersen | Configuration Manager MVP | Blog: http://www.ronnipedersen.com/ | Twitter @ronnipedersen

Image X is not intended to be a backup and recovery tool. It is not designed to lay down a non-sysprepped image and it will not work. (at least not with Vista or higher OS's) there's some stuff you can do to get the computer back up and running after you lay down a non-sysprepped image but it's a pain and it's not supported. If you are capturing the image with SCCM or MDT it's sysprepped unless you changed some of the default settings. John Marcum | http://myitforum.com/cs2/blogs/jmarcum/|

I personally always create a non syspreped version of my reference builds before creating the syspreped version. here is how i do this http://blog.coretech.dk/mip/capture-none-syspreped-image-using-sccm-running-imagex-from-a-ts/ Michael Petersen http://blog.coretech.dk/mip/

I personally always create a non syspreped version of my reference builds before creating the syspreped version using the MDT integration. here is how I do this http://blog.coretech.dk/mip/capture-none-syspreped-image-using-sccm-running-imagex-from-a-ts/. Michael Petersen http://blog.coretech.dk/mip/

I personally always create a non syspreped version of my reference builds before creating the syspreped version using the MDT integration. here is how I do this http://blog.coretech.dk/mip/capture-none-syspreped-image-using-sccm-running-imagex-from-a-ts/. Michael Petersen http://blog.coretech.dk/mip/ Michael, So, this process described will create an entire image of any reference machine, correct? If so, how do you then deploy it? What are the steps for adding it back to SCCM and restoring/deploying it? Thanks, Matt

just create a TS that 1. formats the disk, 2 add the image. Thats it, once the image file has been applied, the TS will finish, and the machine will reboot to the OS! You must ofsause add it the image to sccm ad distribute it to a DP,Michael Petersen http://blog.coretech.dk/mip/

just create a TS that 1. formats the disk, 2 add the image. Thats it, once the image file has been applied, the TS will finish, and the machine will reboot to the OS! You must ofsause add it the image to sccm ad distribute it to a DP, Michael Petersen http://blog.coretech.dk/mip/ Seems easy enough! So, a Format and Partition and then "Apply Image" task should work? Any chance that you could export your task sequences - just to ensure that I'm doing the right things?

Matt, Did this work for you?Find this post helpful? Does this post answer your question? Be sure to mark it appropriately to help others find answers to their searches.

Chase - I'm actually out of office today and awaiting answer from my coworkers. I'll let you know as soon as I hear from them. All tasks within both task sequences ran successfully! Just need acknowledgement that the target computer is up and running.

I'm going to be amazed if this works. It shouldn't work. Unless I am misunderstanding what you are trying to do. John Marcum | http://myitforum.com/cs2/blogs/jmarcum/|

So far, it failed. I'm going to run another task sequence against the deployed image (that could also be included in the Deploy TS) and see if the system comes up... I'm still hopeful that this will work.

Did it BSOD? If so I "think" there's way to get it back up but it's nothing you'd want to do in produciton. I can't recall the exact procedure but i think you have to get into BCDEDIT and make some changes or something like that. When you lay down a non-sysprepped vista or higher machine with imagex it hoses up the boot loader. John Marcum | http://myitforum.com/cs2/blogs/jmarcum/|

Hi John What is it that shouldn't work?? I apply non syspreped images using sccm all the time... At most of my customers, I have just one image containing n index files where half are non syspreped, and the other half are sysprped... I gues it a little like VPC snapshots!Michael Petersen http://blog.coretech.dk/mip/

I've only tried it once and it didn't work. I read or saw somewhere and explanation as to why it doesn't work and that was because imagex is not intended to do that. Of course I didn't apply mine with SCCM. I just booted into PE, formatted the disk and used imagex /appy to lay down the image. Maybe SCCM is doing something that I am not aware of. John Marcum | http://myitforum.com/cs2/blogs/jmarcum/|

It did work with the addition of one more task to my Deployment Task Sequence: run command line; bcdboot.exe C:\Windows. All is working wonderfully now. Thank you for your help, Michael!

Good to see you got it working... Just wanted to mention that i don't add the bcdboot.exe and it works for me.. I'm going to write a blog post on it soon!!Michael Petersen http://blog.coretech.dk/mip/

It did work with the addition of one more task to my Deployment Task Sequence: run command line; bcdboot.exe C:\Windows. All is working wonderfully now. Thank you for your help, Michael! Matt, Did you check the option to make the partition bootable on the format step? This may be why Michael doesn't need to do the bcdboot and you do. I saw this before when trying to use the "prestaged media" in R3. One person said you need bcdboot and the other didn't. The outcome was needing the format step to make it bootable. Matt and Michael, What do you have in your format step? Find this post helpful? Does this post answer your question? Be sure to mark it appropriately to help others find answers to their searches.

My Format and Partition: Properties> "Disk number: 0" "Disk type: Standard(MBR)" >Volume> "Partition Name: OS" "Partition Type: Primary" "Use a percentage of remaining free space - 100%" "Make this the boot partition IS checked" "File System: NTFS - Quick format IS checked" "Variable - C"