Peter33 Posted December 12, 2012 Report post Posted December 12, 2012 Sounds a bit strange. That never happened to me before. You might just recreate the boot wim, or double check that you applied the correct PE to your task sequence. If you have applied several optional task sequences to the same collection and boot your client with PXE, the PXE server will load a "random" PE out of these sequnces. In this case you have to apply a "reboot to assigned PE" as mandatory first step in your task sequence, to make sure the correct one will be used. Just by the way. You are not trying to build and capture a 64 bit windows 7 with a 32 bit PE? Because that would not work at all. Quote Share this post Link to post Share on other sites More sharing options...
tmiller_hockey Posted December 12, 2012 Report post Posted December 12, 2012 I recreated the Boot Images and redeployed them. I now have F8 access. I obtained the log and the only thing I notice is the following: !sVolumeID.empty(), HRESULT=80004005 Quote Share this post Link to post Share on other sites More sharing options...
Rocket Man Posted December 12, 2012 Report post Posted December 12, 2012 Have you tried recreating your system installer again and a new build&capture TS? If not I would use a new set of media files(use winRAR to extract them from the iso) and start over! For a Hyper-v VM you should not need drivers. Also just double check the network access account by veryfying it to the location of your system installer directory when adding the account. Rocket Man Quote Share this post Link to post Share on other sites More sharing options...
lucastee Posted December 13, 2012 Report post Posted December 13, 2012 I would suggest only adding the network interface drivers to the boot image. There is no real harm in adding more drivers, but the larger the boot file, the longer the deployment. If you're not too converned about adding a few extra minutes to the deployment time, then it shouldn't matter. However, deploying to 1000+ PCs, adding 3 minutes to each - you've added 50 hours of build time across the organisation. We have captured and deployed Windows 7 64-bit on both VM and physical hardware. The VMs are running VMWare. Quote Share this post Link to post Share on other sites More sharing options...
gsankowsky Posted December 13, 2012 Report post Posted December 13, 2012 I've had similar problems. Enable F8 prompt and use diskpart and create a partition before it starts deployment - I have had issued with partitions if a TS gets aborted. If it's a VM, disable the whole Apply Drivers step. Don't apply any drivers at all. Quote Share this post Link to post Share on other sites More sharing options...