+ Post New Thread
Results 1 to 13 of 13
O/S Deployment Thread, Injecting Drivers into Boot Image Issue in Technical; Afternoon All We've recently purchased several PC's with the Asus M5A78L-M motherboard at our school. When I'm trying to deploy ...
  1. #1

    Join Date
    Apr 2011
    Posts
    18
    Thank Post
    5
    Thanked 1 Time in 1 Post
    Rep Power
    0

    Unhappy Injecting Drivers into Boot Image Issue

    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

  2. #2
    cromertech's Avatar
    Join Date
    Dec 2007
    Location
    Cromer by the coast
    Posts
    731
    Thank Post
    177
    Thanked 109 Times in 97 Posts
    Rep Power
    54
    are you adding the 32-bit as well as the 64 bit drivers?

  3. #3

    Join Date
    Apr 2011
    Posts
    18
    Thank Post
    5
    Thanked 1 Time in 1 Post
    Rep Power
    0
    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

  4. #4
    cromertech's Avatar
    Join Date
    Dec 2007
    Location
    Cromer by the coast
    Posts
    731
    Thank Post
    177
    Thanked 109 Times in 97 Posts
    Rep Power
    54
    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

  5. Thanks to cromertech from:

    disco_samurai (18th October 2011)

  6. #5


    Join Date
    Mar 2009
    Location
    Leeds
    Posts
    6,647
    Thank Post
    229
    Thanked 865 Times in 743 Posts
    Rep Power
    297
    When you unmount the image you need to add a commit argument

  7. #6

    plexer's Avatar
    Join Date
    Dec 2005
    Location
    Norfolk
    Posts
    13,726
    Thank Post
    667
    Thanked 1,638 Times in 1,463 Posts
    Rep Power
    424
    The commit is there in the steps before the unmount.

    Have you then replaced the boot image in wds with your new one?

    Ben

  8. Thanks to plexer from:

    disco_samurai (18th October 2011)

  9. #7


    Join Date
    Mar 2009
    Location
    Leeds
    Posts
    6,647
    Thank Post
    229
    Thanked 865 Times in 743 Posts
    Rep Power
    297
    If your server is 08r2 you can add drivers to boot images via wds console

  10. #8

    Join Date
    Apr 2011
    Posts
    18
    Thank Post
    5
    Thanked 1 Time in 1 Post
    Rep Power
    0
    Quote Originally Posted by plexer View Post
    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

  11. #9

    Join Date
    Apr 2011
    Posts
    18
    Thank Post
    5
    Thanked 1 Time in 1 Post
    Rep Power
    0
    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

  12. #10

    Join Date
    Mar 2007
    Posts
    130
    Thank Post
    29
    Thanked 5 Times in 4 Posts
    Rep Power
    17
    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?

  13. #11

    Join Date
    Apr 2011
    Posts
    18
    Thank Post
    5
    Thanked 1 Time in 1 Post
    Rep Power
    0
    Quote Originally Posted by steele_uk View Post
    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

  14. #12
    jsnetman's Avatar
    Join Date
    Oct 2007
    Posts
    887
    Thank Post
    23
    Thanked 134 Times in 126 Posts
    Rep Power
    40
    "imagex /mountrw c:\wim\boot.wim 2 c:\wim\mount"

    Should the index number be 1 instead of 2 ?

  15. #13
    tommej's Avatar
    Join Date
    Oct 2009
    Location
    Lincolnshire
    Posts
    703
    Thank Post
    38
    Thanked 136 Times in 101 Posts
    Rep Power
    78
    ^^ 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.

SHARE:
+ Post New Thread

Similar Threads

  1. [WDS] Inject drivers into WIM file
    By dezt in forum O/S Deployment
    Replies: 6
    Last Post: 23rd June 2010, 10:28 AM
  2. Replies: 3
    Last Post: 11th June 2010, 04:18 PM
  3. Boot camp issues with group policy
    By HodgeHi in forum Wireless Networks
    Replies: 9
    Last Post: 30th October 2007, 09:08 PM
  4. Ghost boot disk issue???
    By amorouspxy in forum Windows
    Replies: 4
    Last Post: 24th May 2007, 09:28 PM
  5. Add Drivers To RIS Image
    By DSapseid in forum Windows
    Replies: 1
    Last Post: 14th May 2007, 08:44 AM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •