Jump to content


KeithDib

OSD deployment driver issues

Recommended Posts

Hi

 

I have set up OSD but I am having trouble with drivers

 

The image deploys OK, and the TS runs fine, but post install drivers will not work. My "Apply Device Driver" section of my TS seems to run (it downloads the drivers and says applying) but once the TS has finished the drivers are not installed.

 

HELPPPPPP

 

PS, I created the image from a sysprep'd machine with a PE boot disk to take image.

 

:)

 

Keith

Share this post


Link to post
Share on other sites

Are you using a WMI query to determine the drivers that get installed?

 

At the moment no..

 

I have set up driver packages, NIC..Audio etc etc, I have included these in the TS, I have also tried the TS auto Apply drivers but this created folders in the root of C: and put the driver files here in, but seems to do nothing with them

Share this post


Link to post
Share on other sites

Recommend to use WMI query and if possible have individual driver packages for your models with the appropriate WMI query attached....I tried the auto apply drivers initially but found myself in similar situations, move to WMI query with individual packages and all good now!

Share this post


Link to post
Share on other sites

Recommend to use WMI query and if possible have individual driver packages for your models with the appropriate WMI query attached....I tried the auto apply drivers initially but found myself in similar situations, move to WMI query with individual packages and all good now!

 

Thanks Rocket Man.

 

I will change set up to use "Model" based driver packages and WMI query for this. What stage during the TS do you think its best to deploy this driver package?

Share this post


Link to post
Share on other sites

Disable the default apply driver task that comes with the creation of the task sequence and add the new driver package task with WMI query in or around the same location after apply OS but definitely before setup configuration manager client task!

Share this post


Link to post
Share on other sites

Does it stop at the driver package at OSD time or bypass it swiftly?

 

What is your WMI query syntax?

 

 

I have not created an XP image before, so sorry if this is a dumb question..

 

Neither have I used SCCM for XP........as you know it is a different sysprep process. I am fairly sure there is a section here on the Windows Noob site that covers XP, it may be in the SCCM 2007 guides!

 

Rocket Man

Share this post


Link to post
Share on other sites

No, is does the correct things when running the driver package. Says 'downloading' then 'installing' takes as long to do this as the rest of the TS.

 

Once the image deployment has finished and sysprep ran the system boots and these are folders in the root of C for each driver, numbered sequentially.

 

I have tried with and without the WMI query, to test this and it makes no difference

Share this post


Link to post
Share on other sites

Hi,

 

i would recommend you to use a virtual machine (vmware player 5 is good enough) for the build and capture process. The only drivers you will need are the network and storage drivers from the vmware tools.

Never apply any other drivers to your base image. This is part of the deployment sequence, where you will use the wmi queries to create a dynamic deployment.

You also need to create a new sysprep package for XP from this cab file.

For the capture use sources with SP3 already included.

 

Just by the way. Do not capture your images twice. Use an operating system installer in your task sequence and not a finished image.

Share this post


Link to post
Share on other sites

Theoratically you can capture a image over and over again. Install software, run sysprerp and capture it again. But it's not recommended.

So back to your problem and my silly question: are your drivers XP drivers, and have you chosen a matching storage driver and model in the apply driver package step? Also make sure that you tick the unsigned driver checkbox there.

Share this post


Link to post
Share on other sites

Peter33

 

The drivers were ripped/backed up from the same unit running XP before I started the process, also we have used the same drivers on other systems, so yes they are XP and tested

 

And, yes. Unsigned is ticked, although again I have checked this both ticked and not ticked.

 

As I say, the drivers copy to the target machine (as their all in a folder once imaged) but the system (or sysprep) does not seem to be installing them

Share this post


Link to post
Share on other sites

The drivers were ripped/backed up from the same unit running XP before I started the process

 

OK, rather download the drivers from the manufacturer site and create a new driver package. Some drivers even might require a regular installation package.

Share this post


Link to post
Share on other sites

Can I ask why you are installing drivers in a Build & Capture?

 

Are you using a VM for this process?

 

I would not apply drivers at a build and capture TS, I would only apply drivers on a build TS.

 

You should try just a build and capture without drivers in any way. Then with the captured image create a new TS and then apply your driver package with WMI query!!

 

It is a waste of an image the way you are trying at moment due to the fact if it was successful with the drivers, then you would only be able to deploy this build & capture image with drivers out to the same model of machine.........if you try and deploy it out to different model then you could get errors including maybe BSOD due to driver incompatibility due to the fact the drivers are hardcoded in the image.....

 

This is the beauty of WMI queries and driver packages......you can basically use a standard image without any modifications and deploy it to any model, aslong as you have the appropriate driver packages attached with WMI queries to suit (and this can be as many as you like on the one TS).

 

Rocket

Share this post


Link to post
Share on other sites

I would just create a new driver package with the drivers from the manufacturer, even if your drivers are working on this one machine you got them from. Just start with the network and storage drivers, This does'nt take long.

Alos check the dism.log and enable the checkbox to only install compatible drivers.

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...


×
×
  • Create New...