Windows Deployment problems

The setup I had in place has worked for going on two years. All of a sudden the boot images are not working saying that a network driver is missing during the PXE boot to windows setup. It has been a while since I have set this up so I may be doing it wrong. First I grabbed the boot.wim off of a windows 7 x64 CD. I use DISM GUI to add the network drivers I need, specifically for dell 7010 workstations. I do not use a force unassigned option. Add the boot image to WDS after I have committed the drivers. Boot the system across the network and I get a matching network card driver was not found. Some driver that I think is the right one just causes it to blue screen. I only use DISM GUI cause it is easier. If I use WDS to add drivers I get the same so it doesn't matter it seems
LVL 2
stlhostAsked:
Who is Participating?
 
stlhostAuthor Commented:
There is no pro1000 directory. When you extract there is a few directories labeled E1D or E#D. There is a Windows_xArchitech folder for every versions of windows there is from Vista to 8. However I used 7Zip to extract the actual setup file and I found a Win 7 x64 folder in there. This worked just fine.
0
 
David Johnson, CD, MVPOwnerCommented:
0
 
stlhostAuthor Commented:
This is where I get my drivers from. I just extract the network drivers and add it to my boot image.
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
stlhostAuthor Commented:
Still looking for assistance with this.
0
 
David Johnson, CD, MVPOwnerCommented:
do you have 2 network adapters in this machine intel and broadcom? which one is blue screening?
0
 
stlhostAuthor Commented:
No, there is only one. Intel
0
 
David Johnson, CD, MVPOwnerCommented:
and you are installing a client o/s?  intel has made me have to patch the driver for my server o/s (had to modify the .inf and then create new .cat's and signatures
0
 
stlhostAuthor Commented:
Yes, this is part of the deployment portion but I can't get that far without fixing the boot part.
0
 
David Johnson, CD, MVPOwnerCommented:
you can use an x86 boot.wim if you are stuck with an x86 driver.. with your x64 boot.wim you are using the 64 bit driver.. which one did you inject?
0
 
stlhostAuthor Commented:
x64. Didnt think to try a x86 thought it was specific to be honest. Doesn't matter during the boot?
0
 
David Johnson, CD, MVPOwnerCommented:
you can boot and install an x86 or x64 o/s using an x86 boot but not the converse
x64 boot only x64 o/s
0
 
David Johnson, CD, MVPOwnerCommented:
from the pro1000 directory?
0
 
Seth SimmonsSr. Systems AdministratorCommented:
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.