I am trying to deploy a wim image via TS to the 755, 760, 789 & 790 (in ATA mode). This wim image started as a ghost image that I tweaked so that the same image would deply on each of the machines. I can deploy the same (sysprepped) ghost image to each machines and on next boot-up, it goes through the sysprep process and works as planned. I've captured the (sysprepped) system image into a wim file and created a task sequence to deploye via SCCM. Everything goes well with the 755 & 760, however, the 780 and 790 fail by way of a continuous reboot loop. Here's the funny thing though...the TS sequence completes as expected...it when the computer boots up the first time and goes through the sysprep process that the problem occurs? The PC boots into windows(sysprep) with the first blue screen saying"Please wait while windows prepares to start"...yada yada...then right after completing the final step part (the screen after "Applying Network Settings")...the computer reboots one last time to complete the sysprep process...then blam, CONTINUOUS REBOOTS. My guess is that it is a controller issue (becasue of the continual reboot), but why then does the sysprep ghost image deploy work just fine? Any help or insight anyone can provide will be greatly appreciated...

Press F8 during the initial boot of the XP to get the "Windows Advanced Options Menu", then select "Disable automatic restart on system failure" so you can see what BSOD you are having. If it's 0x0000007B it's missing storage drivers / JohanRegards / Johan Arwidmark Twitter: @jarwidmark Blog: http://www.deploymentresearch.com FB: www.facebook.com/deploymentresearch

Johan, I did like you suggested and what i get is a "UNMOUNTABLE_BOOT_VOLUME"...stop 0x000000ED (0x89D13030,0xC000014F,0x00000000,0x00000000) I am going to google search these, but curious if you have any additional input. Just FYI reminder, the exact same TS deployed to the 755 & 760 work just fine? Why do the 780 & 790 behave this way? WTF?

We used Dell at a prior job, and we couldn't use ATA mode on certain models. Some worked and some did not. Have you tried changing that on the 780's and 790's?--Joe.

I am assuming the WIM you are pushing has all the drivers built into it for each computer model? So one image with alot of fluff? Maybe the wrong driver is being applied? What kind of drives does the 755 and 760 have (IDE, SATA) and what kind of drives the 780 and 790 have? To make life easier on yourself you may look into creating 1 wim and using task sequence to apply only the drivers needed. This can be done using WMI query in a task sequence. This way you dont have all your drivers for different models on computers that dont need them. This is basically how it works : Applies the OS, does a WMI query to get the model of PC and will keep going through each task sequence till it matches. I dont have a link right now but Windows-Noob has some pretty nice guides to follow.

Yeah, making that change on a couple machines would be the logical move, but this deployment has 3000+ machines(755,760,780, and soon 790's) already in use and set to ATA mode in bios. Not practical to go to each and change the setting.

The 760, & 780 actually have the same ATA controller driver, so I'm really confused why the 780 has issues when the 760 doesn't. 780 & 790 have same issues as well. http://www.delltechcenter.com/page/Operating+System+Deployment+-+XP+Mass+Storage+Driver+Reference Once again, the crazy thing is I have a (sysprepped) ghost image that works for all the systems...its only when I run things through SCCM. Just FYI here's the process for creating my ghost and WIM 1. Run sysprep.exe on base system with my sysprep.inf file (shutdown after) 2. Boot into my WINPE USB and run GHOST to save my image (reboot) 3. Boot into my WINPE USB and run CAPTURE to create WIM for SCCM When I GHOST any machine (755,760,780,790) with created ghost image everything is fine. When I TS with WIM image, everything with TS runs through fine, the machine reboots and goes through sysprep process (which means IT HAS BOOTED INTO WINDOWS). The problem comes after this step...it finishes and then reboots in preparation to come into normal windows...at which point the drive shows "UNMOUNTABLE_BOOT_VOLUME) I'm at a loss for what to try next?

Ok...so here's the latest that I've discovered: When the Task Sequence portion completes, (from the F8 command prompt) I did a "List Volume" from diskpart to check the status of the drive. I have a System Drive C: labeled "SYSTEM", NTFS, which is Volume 0 & a hidden partition of 47MB to mimic the Dell Utility partition that is labeled "OEM", RAW and Volume 1. I also confirmed this from Diskpart in a WINPE prior to boot. When the PC reboots and goes into Windows Setup and does it thing, then it reboots again. Now before the next boot attempt I once again check the status via diskpart. Now I have a C: drive, with no label, RAW, which is Volume 0 & a hidden partition of 47MB that is labeled "OEM", RAW and Volume 1 Hence the UNMOUNTABLE_BOOT_VOLUME! But why. Anyone with ideas please help...THANKS! Once again FYI...same TS on a 755 or 760...NO PROBLEMS

Sounds like the good old WinPE uberbug :) Does these machines by any chance have the new 4k drives? (Advanced Format Hard Drives)? If so, make sure the value for the ExtendOemPartition key in sysprep.inf is changed from 1 to 0. / JohanRegards / Johan Arwidmark Twitter: @jarwidmark Blog: http://www.deploymentresearch.com FB: www.facebook.com/deploymentresearch

Johan, Swapped the disk from the 760 into the 780 and ran my TS again....AND BAM, IT WORKED!!! Not sure about the 4k drives with Advanced Format Hard Driver stuff, but this tells me that it has something to do with harddrives...so I'm guessing you're right. Thanks so much! Next step is to try the ExtendOemPartition key in my sysprep.inf and give it another go with the stock drives in the 780 & 790. I will post the results when I have them. Thanks again for the info...spent boo-koo hours trying to figure out what was the issue. Now I know where I should go from here!

Sounds like the good old WinPE uberbug :) Does these machines by any chance have the new 4k drives? (Advanced Format Hard Drives)? If so, make sure the value for the ExtendOemPartition key in sysprep.inf is changed from 1 to 0. / Johan Regards / Johan Arwidmark Twitter: @jarwidmark Blog: http://www.deploymentresearch.com FB: www.facebook.com/deploymentresearch I can confirm that this solved the problems I had when HP decided to swap to 4K disks. Same HP productnumber(this was Elite 8200 SFF desktops) so there is no way to tell in advance if they are equipped with 4K or not, but if you open the case you can look at the HDDsticker for an "AF" logo. Took me a few Days to find...