riprep + RIS + OEM drivers problem

[Fencer128]

Hi All,

Here's a quickie for you - I want to deploy a Windows XP riprep image to several thousand clients using a 2003 RIS server. All the clients are PXE bootable (I actually have three different riprep images to encompass all HAL types we use). I use a sysprep.inf file in the c:\sysprep directory of the pc used to compose the riprep image. The sysprep.inf file contains the path to the oem WHQL signed driver files I wish to use:

[Unattended]
OemPnpDriversPath=Drivers\C\I;\Drivers\V\I;Drivers\A\I\845;Drivers\A\I\865;Drivers\A\R;Drivers\L\I\100;Drivers\L\I\1000;Drivers\L\I\XGB

The drivers are located in C:\Drivers\...

I run riprep to copy the image to the RIS server and update the registry with the driver path from the sysprep.inf file. Excepting the NIC driver, no other OEM drivers are installed (native drivers do not exist for the video or audio). We edit the riprep.sif file accordingly to set the product key, language, resolution, etc. outside of what has been set in the image.

When I deploy the image to a client everything is as it should be except for the fact that the OEM drivers are not being used.

The .sys and.inf files for each driver are located in the folders specifed within the path. Not all clients use the same drivers and so those included encompass all circumstances.

I cannot think what I'm missing and would appreciate any help anyone has to offer.

Thanks and I apologise if this is the wrong forum, but it kind of straddles a couple,

Andrew

ps - For reasons of system administration I cannot yet gain complete control over group policy - it's a public sector organisation - hence the need for pre-configured riprep images and not RIS CD installs and group policy.

pps - I realise that network drivers are a seperate issue and I will deal with those accordingly after tackling this problem. I have already copied the .sys and .inf files to the CD install on the RIS server and into the i386 directory of the image as well as restarting the binlsvc service.

 

[mikecel79]

Ok really dumb question but in you sysprep.inf line have you tried this?

OemPnpDriversPath=C:\Drivers\C\I;C:\Drivers\V\I;C:\Drivers\A\I\845;C:\Drivers\A\I\865;C:\Drivers\A\R;C:\Drivers\L\I\100;C:\Drivers\L\I\1000;C:\Drivers\L\I\XGB

or

OemPnpDriversPath=%SYSTEMDRIVE%\Drivers\C\I;%SYSTEMDRIVE%\Drivers\V\I;%SYSTEMDRIVE%\Drivers\A\I\845;%SYSTEMDRIVE%\Drivers\A\I\865;%SYSTEMDRIVE%\Drivers\A\R;%SYSTEMDRIVE%\Drivers\L\I\100;%SYSTEMDRIVE%\Drivers\L\I\1000;%SYSTEMDRIVE%\Drivers\L\I\XGB

I don't use RIS but when I use sysprep and I'm telling it where there are drivers I always do it like this line above.

 

[Fencer128]

Originally posted by: mikecel79
Ok really dumb question but in you sysprep.inf line have you tried this?

OemPnpDriversPath=C:\Drivers\C\I;C:\Drivers\V\I;C:\Drivers\A\I\845;C:\Drivers\A\I\865;C:\Drivers\A\R;C:\Drivers\L\I\100;C:\Drivers\L\I\1000;C:\Drivers\L\I\XGB

or

OemPnpDriversPath=%SYSTEMDRIVE%\Drivers\C\I;%SYSTEMDRIVE%\Drivers\V\I;%SYSTEMDRIVE%\Drivers\A\I\845;%SYSTEMDRIVE%\Drivers\A\I\865;%SYSTEMDRIVE%\Drivers\A\R;%SYSTEMDRIVE%\Drivers\L\I\100;%SYSTEMDRIVE%\Drivers\L\I\1000;%SYSTEMDRIVE%\Drivers\L\I\XGB

I don't use RIS but when I use sysprep and I'm telling it where there are drivers I always do it like this line above.

Hi,

Thanks for the reply. I hadn't tried that as according to MS KB 314479 the %systemdrive% environment variable is autoamatically inserted before each path. As such, I thought this would cause problems.

I will give this a try though it may take a while to test out as I have to recompose the image, add the new sysprep.inf and then reuse ripprep.exe to copy it over to the RIS server.

EDIT: Just checked HKLM\Software\Microsoft\Windows\CurrentVersion\Devicepath key on client built with finished riprep image and the %systemdrive% variable has been correctly placed in front of all entries.

Thanks,

Andrew

 

[Fencer128]

Hi,

I reied the "full path" idea - but no joy.

Any other ideas?

Thanks

Andrew