[sccm 2012] SCCM has the driver but it not using it

[nicholab]

I have SCCM and it has the driver but it is not installing it and having a functioning network for carrying out the next stage. Also what it the difference between a Driver Packages and Just Drivers?

[Sagima]

Drivers are just all of the drivers - sccm does f all with those as they are although you can categorise them

 

Driver packages are what the drivers need to be (and on a distribution point) put in for sccm to actually use them

[nicholab]

I changed the task sequence to use Apply Driver Package and selected the Driver package for that machine and it now worked. So normally you import the drives and then make them part of a Drive Package?

[Sagima]

You don't have to apply the package like that, although it does make sure the right drivers get installed. As I understand it as long as it has been packaged and popped on a distribution point sccm will find it from the category in the Apply Device Drivers task sequence

[sparkeh]

I changed the task sequence to use Apply Driver Package and selected the Driver package for that machine and it now worked. So normally you import the drives and then make them part of a Drive Package?

Anything you want to distribute (drivers, images, applications etc) need to reside on a distribution point, in a deployment package.

 

So, when you import the driver sccm 'knows' about the driver and the location of the driver files. Then you add it to a package and send it to a distribution point (ie it takes all the driver files, bundles them all up and puts them on a share). During the OSD tasks the device contacts the site server to see if it has the drivers it needs, once located it downloads the relevant packages and applies the drivers.

 

Some people like to create a package per model of PC, some like to package up all similar drivers together.