disco_samurai Posted October 17, 2011 Posted October 17, 2011 Afternoon All We've recently purchased several PC's with the Asus M5A78L-M motherboard at our school. When I'm trying to deploy one of our Windows 7 images via our WDS server I'm getting an error message stating that I need to install a compatible Windows PE network driver (this is AFTER connecting to the WDS Server but before choosing the image). I've not had this crop up before but with this being a new model motherboard it was kind of expected (its packing a Realtek 8111E PCIe Gb LAN onboard network card). I followed the instructions which talk you through injecting a new driver into your Boot image (as below) these instructions are from sysengineers . net =============================================================================== In this example the following environment setup was used. Latest WAIK installed on a laptop. WAIK provided commandprompt ran as adminstrator was used. # first create a directory called C:\wim md C:\wim # Next grab the boot.wim from your WDS machine or the windows install CD. pushd \\wdsservername.domain.ext\REMINST\ copy \boot\x64\images\boot.wim c:\wim\ # Create a mount folder and mount the image. md c:\wim\mount imagex /mountrw c:\wim\boot.wim 2 c:\wim\mount #next plug the driver into the image using dism dism /image:C:\wim\mount /add-driver /driver:C:\dell\drivers\R280807\windows-7-x64\E1k6264.inf The driver should be installed afterwards. # Commit all changes imagex /commit c:\wim\mount # Unmount the image imagex /unmount c:\win\mount. =================================================================================== This whole process seems to work fine and I injected the Windows 7 driver off the Motherboard disk into the Boot Image without a hitch. I tried to image the PC but got the exact same error message again. I've now injected EVERY LAN driver from the Motherboard DVD into the Build Image and again I'm still getting the error that no network driver can be found. I've restarted the WDS service and tried a few other things I've found on the net (pausing the network boot for a minute or so before letting it connect to the WDS Server) but nothing seems to work. This is the first time I've had to do this so I'm not sure if I'm missing something? My boot image is increasing in size so its definately taking the drivers into it fine as far as I can see. I can't find any other drivers on the net that I can try to inject either. The boot image works fine on the older ASUS M4 variants just not these new ones. Has anyone got any ideas? Its really frustrating me and we are looking at getting more of these PC's over Halfterm/Christmas. Thanks in advance for any help! Neal
cromertech Posted October 17, 2011 Posted October 17, 2011 are you adding the 32-bit as well as the 64 bit drivers?
disco_samurai Posted October 17, 2011 Author Posted October 17, 2011 Hi Matt Yup I've added the 32 bit and 64 bit versions of the Driver, I've added both versions for Windows 7 / Vista / XP as well. As far as I can see theres no LAN drivers on the CD that I haven't injected now! Cheers Neal
cromertech Posted October 17, 2011 Posted October 17, 2011 I have seen something similar before that was due to the boot image only being 32 bit. I had to enable the 64 bit boot image even if I wasn't using it to get it to work on some motherboards. I have to admit I've only ever used MDT to add drivers as it gives you a nice GUI and will only inject the drivers it needs for the motherboard. It takes a little bit of setting up but it's worth it for the time it saves. If you feel like giving it a go it may save a couple of headaches. There are quite a lot of articles on setting this up but I did mine following this Deploying Windows 7 - Part 1: Windows AIK 2.0 Enhancements 1
sted Posted October 17, 2011 Posted October 17, 2011 When you unmount the image you need to add a commit argument
plexer Posted October 17, 2011 Posted October 17, 2011 The commit is there in the steps before the unmount. Have you then replaced the boot image in wds with your new one? Ben 1
sted Posted October 17, 2011 Posted October 17, 2011 If your server is 08r2 you can add drivers to boot images via wds console
disco_samurai Posted October 18, 2011 Author Posted October 18, 2011 The commit is there in the steps before the unmount. Have you then replaced the boot image in wds with your new one? Ben Hi Ben Yeah I replaced the boot image after making the changes, I took the boot image offline on the WDS Server first replaced it then brought it back online. At one point I even restarted the WDS Service just to be on the safe side that its definately using the new Boot Image. I'm having a tinker now with MDT and having injected the drivers into the Boot Image using that it seems to be working (at least its getting me to the stage where I have to choose a task). Just need to wrap my head around adding my pre existing images. The guides posted by Matt are really handy actually and its definately easier to update the boot image this way than using the command prompt. I'll let you know how I get on. Cheers Neal
disco_samurai Posted October 18, 2011 Author Posted October 18, 2011 Right cracked it! I found a Windows 2000 driver for the network card on the net, injected that into my original Boot Image via the Deployment Tools command prompt and it now connects to the WDS server fine! Thanks for all your help with this, I'm definately going to look into setting up the MDT stuff its much easier to see whats going on. Cheers chaps Neal
steele_uk Posted December 8, 2011 Posted December 8, 2011 New to this, and am injecting my first driver using this guide. Once the changes have been committed is there a particular command to get the Boot.wim moved from C:\wim back to its original location or will straight forward copy/move do?
disco_samurai Posted December 8, 2011 Author Posted December 8, 2011 New to this, and am injecting my first driver using this guide. Once the changes have been committed is there a particular command to get the Boot.wim moved from C:\wim back to its original location or will straight forward copy/move do? Just a straight copy and move will do it mate, off your C: back onto your WDS server. I'd keep a copy of your old boot.wim just incase something didn't work out right! Cheers Neal
jsnetman Posted December 8, 2011 Posted December 8, 2011 "imagex /mountrw c:\wim\boot.wim 2 c:\wim\mount" Should the index number be 1 instead of 2 ?
tommej Posted December 8, 2011 Posted December 8, 2011 ^^ make sure you're injecting to the correct index or it won't be recognised. I did the same thing and it took me days to realise.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now