+ Post New Thread
Results 1 to 13 of 13
O/S Deployment Thread, What did i miss? in Technical; Ready?... Ok, imported base OS to deploy to Netbooks, injected drivers. Deployed to Netbook...noticed that i had forgotten to add ...
  1. #1

    Little-Miss's Avatar
    Join Date
    Oct 2007
    Location
    London
    Posts
    5,556
    Thank Post
    2,377
    Thanked 753 Times in 461 Posts
    Blog Entries
    2
    Rep Power
    544

    What did i miss?

    Ready?...

    Ok, imported base OS to deploy to Netbooks, injected drivers.
    Deployed to Netbook...noticed that i had forgotten to add the display drivers - doh. Went back, added driver, updated package, redeployed, worked great.
    installed software needed and updates, happy with how it was, captured it....deployed to netbook, no dsiplay driver!!!

    What happened?

  2. #2

    witch's Avatar
    Join Date
    Nov 2005
    Location
    Dorset
    Posts
    11,333
    Thank Post
    1,389
    Thanked 2,396 Times in 1,688 Posts
    Rep Power
    706
    I don't know, but I have two sets of netbooks (samsung NB30s and N145s) in one school and one set in the other and although the images have the display driver on them, it doesnt seem to deploy properly and I always have to add the display driver at the end.

  3. Thanks to witch from:

    Little-Miss (23rd March 2012)

  4. #3

    Little-Miss's Avatar
    Join Date
    Oct 2007
    Location
    London
    Posts
    5,556
    Thank Post
    2,377
    Thanked 753 Times in 461 Posts
    Blog Entries
    2
    Rep Power
    544
    Ooohh, ok..

  5. #4

    plexer's Avatar
    Join Date
    Dec 2005
    Location
    Norfolk
    Posts
    13,657
    Thank Post
    656
    Thanked 1,624 Times in 1,453 Posts
    Rep Power
    422
    What display drivers are they?

    Ben

  6. #5
    simpsonj's Avatar
    Join Date
    Apr 2009
    Location
    Oxford
    Posts
    386
    Thank Post
    160
    Thanked 66 Times in 55 Posts
    Blog Entries
    8
    Rep Power
    22
    How did you inject the driver and how do you deploy your images? I ask because I'm fairly certain, though willing to be corrected, that when you sysprep a device, it strips the drivers out of the image being captured. To inject a driver into an image, assuming you are using WDS, you need to inject the driver like so:

    Adding Drivers to WDS (R2) - YouTube

  7. #6
    simpsonj's Avatar
    Join Date
    Apr 2009
    Location
    Oxford
    Posts
    386
    Thank Post
    160
    Thanked 66 Times in 55 Posts
    Blog Entries
    8
    Rep Power
    22
    Though re-reading your original post, it looks like you've already done what I've posted! Apologies...

  8. #7

    SYNACK's Avatar
    Join Date
    Oct 2007
    Posts
    11,220
    Thank Post
    873
    Thanked 2,716 Times in 2,301 Posts
    Blog Entries
    11
    Rep Power
    780
    The generalize stage rips out the drivers and some drivers are a bit dodgey about running in WinPE/MDT environment. Two options, if doing specific images for each type of machine sysprep with a leave drivers alone directive before taking the image or find a driver that will apply during MDT install. It can be easy just to add them after for a small amount.

    keepdrivers.xml
    Code:
    <?xml version="1.0" encoding="utf-8"?>
    <unattend xmlns="urn:schemas-microsoft-com:unattend">
        <settings pass="generalize">
            <component name="Microsoft-Windows-PnpSysprep" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="Error" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
                <PersistAllDeviceInstalls>true</PersistAllDeviceInstalls>
            </component>
        </settings>
        <cpi:offlineImage cpi:source="catalog://opsmgt/deploy$/operating systems/w7x64o14/sources/install_windows 7 enterprise.clg" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
    </unattend>
    sysprep /generalize /oobe /shutdown /unattend:keepdrivers.xml

    Above works for 64bit, this Sysprep a Windows 7 Machine - Start to Finish - Brian Lee Jackson talks about the tools used.

  9. #8
    DrPerceptron's Avatar
    Join Date
    Dec 2008
    Location
    In a house
    Posts
    926
    Thank Post
    34
    Thanked 134 Times in 114 Posts
    Rep Power
    41
    Is there anything in the OSDLOGS (C:\MININT\)

    I know in the past we had trouble with some display drivers (notably ones for some prehistoric machines), but since there are only 20 of these machines at our site, I ignored the whole thing.

  10. #9

    SYNACK's Avatar
    Join Date
    Oct 2007
    Posts
    11,220
    Thank Post
    873
    Thanked 2,716 Times in 2,301 Posts
    Blog Entries
    11
    Rep Power
    780
    I found it usually did this if the driver was installed by Windows update as those get yanked by sysprep, grrrr, intel drivers... shakes fist.

  11. #10

    Join Date
    May 2008
    Posts
    48
    Thank Post
    1
    Thanked 2 Times in 2 Posts
    Rep Power
    13
    I used to have problems with my image dynamically assigning the correct drivers into an image with Windows 7 when I was trying to create my "All In One" image that could go over any machine with only one task sequence. However, I have found that I have better luck when using selection profiles to inject my drivers into a machine (used with Lenovo X120E Netbooks with no problems). Have you tried Selection Profiles at all by chance? It seemed the way to go for us. That way, I have one base image that all of my task sequences use and I just create a task sequence for each machine that has the correct selection profile set for that machine. That way, I know that no other driver in my database should be conflicting with it. If you need some advice on setting up the profiles, just let me know or search around here as there is a lot of good info on these forums

  12. #11
    AButters's Avatar
    Join Date
    Feb 2012
    Location
    Wales
    Posts
    474
    Thank Post
    143
    Thanked 107 Times in 82 Posts
    Rep Power
    42
    I use Make/Model driver model. Seems to be the best. Basically MDT will only install the drivers onto a PC based on its exact make and model.

    There is a good guide here: Scroll down to the Driver Management \ Add drivers part.

    cluberti.com » MDT for the small(er) guys &ndash; Part 3

  13. #12
    DMcCoy's Avatar
    Join Date
    Oct 2005
    Location
    Isle of Wight
    Posts
    3,461
    Thank Post
    10
    Thanked 496 Times in 436 Posts
    Rep Power
    113
    It's the Intel GMA driver isn't it? It's broken and gets removed by the generalise phase.

    They don't seem to care.

  14. #13

    Join Date
    Feb 2012
    Location
    Seattle
    Posts
    1
    Thank Post
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    One thing that has made a huge difference for me is using the actually CAB files for drivers. For Dell you can go here:

    en.community.dell.com/techcenter/enterprise-client/w/wiki/2065.dell-driver-cab-files-for-enterprise-client-os-deployment.aspx

    Download the correct CAB file, import it to MDT and update your media. The correct drivers should be injected automatically.

SHARE:
+ Post New Thread

Similar Threads

  1. So what did I miss?
    By bizzel in forum General Chat
    Replies: 3
    Last Post: 23rd March 2011, 10:50 PM
  2. What did you learn at BETT 2008
    By alexknight in forum BETT 2014
    Replies: 25
    Last Post: 27th January 2008, 01:47 PM
  3. Doc Who Xmas Special - what did you think ?
    By mattx in forum General Chat
    Replies: 18
    Last Post: 27th December 2007, 09:39 PM
  4. What am I missing now?
    By indiegirl in forum ICT KS3 SATS Tests
    Replies: 16
    Last Post: 30th March 2006, 03:40 PM
  5. What am I missing? Printer issues...!!
    By indiegirl in forum Wireless Networks
    Replies: 6
    Last Post: 15th March 2006, 11:56 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
  •