This is something that is really irritating me at the moment.
We're planning on rebuilding all our machines over the summer and as part of the rebuild we are going to upgrade to Windows7.
I've built myself a Windows 7 Pc, done all the tests of GPO's and software etc installed the software which needs to be available on all machines. The PC has been sysprepped and I have captured the image and stored it on the local machine (as I couldn't get it to connect to the WDS Server). The image has been taken from the PC and transferred onto the WDS server. From here I have taken the .wim file and used it to create an answer file to allow unattended installation.
So back to my test PC, I've started it up and booted it into the WDS and found the image I want to install and set it running. It gets through the first three stages (Copying Files, Expanding Files, Installing Features) but fails when it gets to "Installing Updates" with the following error message.
"Operation failed with 0x80070002. The system cannot find the file specified".
Anyone come across this before? Is there a solution?
This link isn't a fix for your issue but it sounds like something similar. The 0x8007002 sound like you got a windows update that has failed or not downloaded properly.
I have enough issues with the Windows 7 sysprep as it is but I'm wonder if when your problem might be to do with when grabbed the image of Windows 7 if it had automatic updates and was awaiting a reboot for an update it downloaded in the background.
I've actually just made a significant forward step though, in that I've managed to get the PC (which has 4Gb Ram in it) to roll out a base Windows 7 image unattended....so at least it's going in the right direction.
I will try uploading a new nic driver though :-) thaks again.
Try using the free MDT 2010 layer on top of WDS, it makes a lot of this stuff easier and automates a whole bunch of it. It does not take to long to setup and will save you a bunch of time and hassel in the end.
Turns out there was a problem with the boot.wim file, replaced and all now working :-)
Just a little tinkering with the answer file now to allow a full unattanded install to take place :-) Thanks for all the suggestions
Hello Iain - I am having the exact same problem - can you elaborate on the boot.wim file issue - I initially had problems creating it and injecting drivers and had to go to the older version of WAIK to create a working (seemingly) .wim file - what exactly was the issue and how did you resolve it?