[mdt] What did i miss?

[Little-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?

[witch]

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.

[Little-Miss]

Ooohh, ok..

[plexer]

What display drivers are they?

 

Ben

[simpsonj]

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:

 

[simpsonj]

Though re-reading your original post, it looks like you've already done what I've posted! Apologies...

[SYNACK]

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

   
       
           true
       
   
   

 

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.

[DrPerceptron]

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.

[SYNACK]

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.

[scottpowers82]

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

[PotNoodleTech]

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 – Part 3

[DMcCoy]

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.

[icanpressbuttons]

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.