dobsonl 0 Posted October 18, 2012 Report post Posted October 18, 2012 Hi Has anybody seen this error before when capturing a windows 7 SP1 64bit image? It doesn't seem to make any difference if I run the task sequence on a Virtual machine or a physical machine The logs dont say anything, unless im looking at the wrong one.... which could well be the case as still relativly new to SCCM Thanks in advance Luke Quote Share this post Link to post Share on other sites
Rocket Man 40 Posted October 18, 2012 Report post Posted October 18, 2012 this error can happen if hardware is faulty...HDD etc.(the TS is unable to access the HDD)..but if it is happening on a Virtual Platform also then I'd say you can rule this out.....have you configured your Network Access Account? Also take a look at this http://social.techne...8b-6895fa83275c Quote Share this post Link to post Share on other sites
Oneone 12 Posted October 18, 2012 Report post Posted October 18, 2012 Could you post the smsts.log file? from C:\ At what stage is this? does it format and partition the disk? Quote Share this post Link to post Share on other sites
dobsonl 0 Posted October 18, 2012 Report post Posted October 18, 2012 Hi, I have checked the network access account and this is fine, i dont think its hard drive problems as the error arrives on a virtual machine and 2 different physical machines... As far as I can see it downloads the install files, then goes to the "applying image" stage then the blue windows 7 setup wallpaper appears briefly and that is where it fails, I have attached the log. Thank you for your advice so far smsts.log - just looking at why its not picked the drivers up, would this likely be the problem? Luke Quote Share this post Link to post Share on other sites
Iroqouiz 28 Posted October 18, 2012 Report post Posted October 18, 2012 There's a whole bunch of driver related error messages in that log file. Have you added NIC/HDD drivers to your boot image? Quote Share this post Link to post Share on other sites
dobsonl 0 Posted October 18, 2012 Report post Posted October 18, 2012 I thought I had, but looking at that now - looking as if they haven't imported. Quote Share this post Link to post Share on other sites
Rocket Man 40 Posted October 18, 2012 Report post Posted October 18, 2012 Just right click on the boot.wim.....properties and drivers tab... this should give you a list of all drivers that have been added to them! Dont forget to update the DPs afterwards in the event of injecting any new drivers to them Quote Share this post Link to post Share on other sites
tmiller_hockey 1 Posted December 12, 2012 Report post Posted December 12, 2012 Why would you need drivers in a Hyper-V VM? I'm having this problem as well. Quote Share this post Link to post Share on other sites
Peter33 48 Posted December 12, 2012 Report post Posted December 12, 2012 You usually don't need drivers for hyperv. Check the smsts.log for a detailed error description. Quote Share this post Link to post Share on other sites
tmiller_hockey 1 Posted December 12, 2012 Report post Posted December 12, 2012 Can't get to the log. Press F8 and no command prompt even though I have command support enabled. Other ideas?? Quote Share this post Link to post Share on other sites
Peter33 48 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
tmiller_hockey 1 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
Rocket Man 40 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
lucastee 0 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
gsankowsky 1 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