TKilmer50

Thanks. This is the direction I went. We have a GPO that doesn't allow downloads from windows updates and - even with the stand alone installer - it downloads from windows update anyway; another point of frustration with Win 8. The method you posted works well; thanks. Zemerick: When a log abruptly stops, you'll want to chase down the new log location. It moves (or some become more useful/less useful) as the task sequence hits various steps. I used dir /s *.log | more to help find all the log files in various directories. The log you posted should give you some direction to dig in; i'm not familiar with that particular error. Good luck!

Update: Random error that is worth sharing: My 0x80004005 error i was getting is a generic error. Using F8 and looking at the X:\Windows\TEMP\SMSTSLog\smsts.log I find the following (Note: you can only open this log if you click 'Restart now' to dismiss windows in SCCM. It won't restart until you close the command prompt but it will release the smsts.log file lock so you can open it): After applying the OS (the very last step), it appears the system is attempting to reboot using a C++ file that it cannot find. It is looking on the E drive for some reason. In the format UEFI task sequence step, I added the 'Make boot drive' to disk 0 GPT which resolved the issue. (Shown below with most of the deployment task sequence I used (minus applications/packages): (Since I'm in a sharing mood: for those of you curious about the misspelled 'Assign C:\ Boot Drive' this is a left over from Windows 7. I didn't try the task sequence without it but I suspect i still needed it. See here for details.) Another side note: when capturing the windows 8 image, i noticed it made a 1-1 and a 2-2 image. 2-2 had my OS. I didn't run into any issues because i noticed this but it is easy to miss otherwise. Back to the iaStorA issue: I retried adding all the drivers to the boot image andhit the same error again. Again i removed the drivers from the boot image (They are still available in the apply device driver task sequence step, just not injected into the x86 Boot Image). Here are the drivers in my boot image: I believe my deployment is mostly successful, waiting for it to finish but it seems to be progressing nicely. Deployment successful. On to testing and installing apps for compatibility issues. Two drivers missing on install. I'll hunt those down later. Rocket Man: if you could share how you added .net 3.5 SP1 to your image I'd be interested. Otherwise, I'll hack away until I get it done (i downloaded the stand alone from MS but it failed during the image task sequence. I'm thinking there has to be a configuration manager 'add roles or features' step that I can use.

I am working on an SCCM deployment for the HP ElitePad as we speak. Testing this week. The issue I am running into right now is, as soon as the OS starts "Setup Windows and Configuration Manager" I get a "Installation drive does not meet requirements" in the X:\Windows\TEMP\SMSTSLog\WindowsSetupLogs\setuperr.log. The generic task sequence error code is 0x80004005. A google search for that + elitepad yeilds an HP site saying "Install CU1 for SCCM 2012 SP1 on a Server 2012 OS". Excellent advice except I have CU2 installed. Dead end. Anyway, to respond to your issue: I had the exact same error. I removed all the storage drivers from the WIN PE 4.0 Driver pack from the boot image and I got past this issue. I suspect that the newest drivers have issues so maybe I'll go back to the February 2013 set and try those (per the SCCM deployment PDF). I'm working off a hodge podge (one set from july 2013 if i recall correctly) of drivers and I get those errors and my error I described above - maybe they are all related. Side note for anyone else starting this process: The Win PE 4.0 networking drivers (only has SMSC sub folder) aren't enough to get the proper device driver for the usb to ethernet in the version of the Elitepad I'm working with. I took ALL the drivers (broadcom, nxp, qualcomm, and smsc from the Windows 8 Elitepad x86 Driver Pack) and added them to the boot image and it allowed me to start the task sequence (aka: get past 'Preparing networking connections' in Win PE). For the guy that posted his step by step, it is appreciated! I'll attempt those steps and scrap my currently deployment attempt including dumping all drivers and my captured image (didn't have the Windows 8 KB in it). For an "enterprise ready" device, this elitepad via sccm insanely nitpicky about it's setup... (To be fair, Windows 8 is as well. Lets hope 8.1 is a major improvement!)