syspreping pcs display driver disappears

[sted]

ive been using sysprep and wds to fire images at laptops in a school. Ive tried it with 2 different laptops (1 hp 1 acer) but both have intel video drivers. Sysprep works ok (im just running it manually and ticking generalize) and all drivers except the video card are fine but it seems to uninstall the video drivers while its sysprepping the laptop.

 

Im pretty sure its something im doing wrong but cant think what it is (display driver is signed as far as i remember) and it is more annoying than a serious problem but any suggestions are welcome

[SYNACK]

It is an expected behaviour as when it generalises it rips out all of the machine specific drivers (most of the time ) if you are using the MDT the solution is as simple as adding the driver packages to the distribution point and it will pick them up automaticly. If not you will have to either setup the driverpath in the image to a specific location and add the drivers here or add them to a $OEM$ folder in the image (you'll have to check this method out as I have not done it this way).

[farmerste]

I found recently that a driver extracted from a running machine using Smart driver backup portable version ,did not get removed during sysprep.

i took the intel video driver off a working machine and then as I recreated a new image I found it hadn't been stripped after sysprep. this was intel HD graphics v9.17.10.3347 ( win7 to win 7 obviously)

 

hope this might help someone out.

[IAMCloud_Curt]

If you are using WDS you can inject the display drivers using the GUI or the Windows Deployment toolkit. Here is the guide I use, always works.

 

PeteNetLive - KB0000218 - Adding / Injecting Drivers into Windows PE 3.0

[Oaktech]

If you are using WDS you can inject the display drivers using the GUI or the Windows Deployment toolkit. Here is the guide I use, always works.

 

PeteNetLive - KB0000218 - Adding / Injecting Drivers into Windows PE 3.0

 

That's never worked for me - the mount prompt always fails with a catalogue error.

 

The way I've got around it in WDS is to import the driver package into WDS, create a driver group and set the appropriate filters for the machine I want to target. I can go into more detail if you think the approach might work for you.

[LeMarchand]

The way I've got around it in WDS is to import the driver package into WDS, create a driver group and set the appropriate filters for the machine I want to target. I can go into more detail if you think the approach might work for you.

 

That's the way I do it, too (apart from the filtering, which I probably should do).

[Don__1]

Have you set PersistAllDeviceInstalls in the sysprep answer file?

[PyROm]

I use DriverStore Explorer [RAPR] - Home which is a simple program for inserting drivers into the driver store.

[cooka]

This is very common when syspreping. You can use an unattended answer file when using sysprep that will keep all drivers - I have it if you could like it. just drop me a pm. I would then insert the driver into your build process just to make sure