Adding new drivers to a RIS-image

[?ystein Folkvord]

Hi!

I've just set up a Windows 2003 server as a ris-server to install a
lot of clients with XP PRO and a complete office installation.

Everything worked fine until i ran into problems with a NIC not
supported by the image. Following the instructions from the
NIC-supplier I was able to get the image installed, but when the
client boots after install the network connection fails, as the driver
is not pressent.

The image is located at

d:\RemoteInstall\Setup\Norwegian\Images\WINXP_SELECTCD

where I have the two directories

i386
$oem$

the structure for the $oem$ directory is:

D:\RemoteInstall\Setup\Norwegian\Images\WINXP_SELECTCD\$OEM$\$1\Drivers\network

My ristndrd.sif contains the following settings in the [unattended]
section:

[Unattended]
UnattendMode=FullUnattended
DriverSigningPolicy = Ignore
OEMPreinstall=Yes
OEMPnPDriversPath = drivers\display;drivers\network
FileSystem = LeaveAlone
ExtendOEMPartition = 0
TargetPath = \WINDOWS
OemSkipEula = yes
InstallFilesPath = "\\%SERVERNAME%\RemInst\%INSTALLPATH%\%MACHINETYPE%"
LegacyNIC = 1


After what I've read in the documentation from microsoft I was
convinced that the files beneath $oem$\$1 should be located at
C:\Drivers\network on my client after the install, and that XP should
be able to find the driver due to the PnpDriversPath, but that is
unfortenatly not happening. Is my assumptation about this wrong ?

Does anyone have any tips on how I can solve or debug this further ?


Thanks in advance,
Oystein

 

[Rex Dieter]

My ristndrd.sif contains the following settings in the [unattended]
section:

[Unattended]
UnattendMode=FullUnattended
DriverSigningPolicy = Ignore
OEMPreinstall=Yes
OEMPnPDriversPath = drivers\display;drivers\network

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Make that
OEMPnPDriversPath = \drivers\display;\drivers\network
and try again.

-- Rex

 

[?ystein Folkvord]

Make that

OEMPnPDriversPath = \drivers\display;\drivers\network
and try again.

Oops!

I've corrected the typo - thanks for pointing that out to me.

I've started a new install after correcting the typo and restarting
the
Remote Install service. I still have problems finding the driver after
the client install. Furthermore, after what I've found in the docs
from Microsoft, I would have expected to find the
driver on the client under C:\drivers, a long with the other
directories
under $oem$\$1\drivers on the server. I thought the files in these
directories would be copied on to the client no matter what. Is this
assumptation incorrect ?


Oeystein