RIS 2k and OEM drivers.

  • Thread starter Thread starter Michael law
  • Start date Start date
M

Michael law

Hi

I am trying to deploy 2kpro via ris with oem drivers
added. I have followed the technet/kb articles about
creating a $oem$/$1/drivers folder and putting the oem
drivers into it. i have also put the $oem$ folder in the
same folder at i386 on the 2kpro image. I have edited
the .sif file to add oempreinstall=yes and oemdrivers
= "driver\vid etc". I also had a problem with the intel
pro 1000 drivers but sorted that out without a hitch.

the problem i have is that the ris install takes place
over the network but NO OEM drivers are autodetected BUT
the drivers folder is coppied over to the root with the
oem drivers in it. It appears that although the drivers
are going over, the install isnt adding the autodetect
driver folder into the reg to add another place to search
for pnp drivers instead of the normal winnt\inf.

Any ideas .. i didnt have much hair left before i got less
now :)
 
Are you adding the "DriverSigningPolicy = ignore" to your answer file?
Maybe the drivers are not signed.

After you added the drivers, did you open this directory:

RemoteInstall\Setup\%language\Images\%dir_name%\i386

List view by details and sort by file type. Delete all the PNF (Precompiled
Setup Information). They will be rebuilt by RIS after you restart the BINL
service or restart the box.
 
hi folks

am helping out a couple of friends in sunny saudi arabia. they have
just imported a new ris-2k /mf piece of harware from italy - costing a
fair amount of money. tested it, got it working etc, put it on
demonstration for a new client. hey presto, it died, with an error
message: a/d subsystem, check hardware drive and installation.

i know this sounds like a reinstallation etc. but is there any
workaround? the support is italian and very slow.

and help here much appreciated.

paul
 
Back
Top