Friday, 12 August 2011

RIS OEM driver update

Check with the OEM to determine whether the supplied network adapter driver is digitally signed. If the drivers from the manufacturer contain a catalog (.cat) file, they are probably properly signed. Drivers signed by Microsoft have been verified and tested to work with Windows. If your driver has not been signed but you still want to use it, make sure to add the following unattended-setup parameter to the .sif file that is located in the RemoteInstall\Setup\Language\Images\Dir_name\I386\Templates folder:
[Unattended]
DriverSigningPolicy = Ignore
Note that if the OEM driver is an update of an included Windows XP driver (for example, if the drivers have the same name), the file must be signed or else Setup uses the included driver instead.

    On the RIS server, copy the OEM-supplied .inf and .sys files for the network adapter to the RemoteInstall\Setup\Language\Images\Dir_name\i386 folder. This allows Setup to use the driver during the text-mode portion of the installation.
    At the same level as the i386 folder on the RIS image, create a $oem$ folder. Use the following structure:
    \$oem$\$1\Drivers\Nic
    Copy the OEM-supplied driver files to this folder. Note the folder in which the .inf file looks for its drivers. Some manufacturers place the .inf file in a folder and copy the driver files from a subfolder. If this is the case, create the same folder structure below the one you created in this step.
    Make the following changes to the .sif file that is used for this image installation:
    [Unattended]
    OemPreinstall = yes

    OemPnpDriversPath = \Drivers\Nic
    Stop and then restart the Remote Installation service (BINLSVC) on the RIS server. To do this, type the   following commands at the command prompt and press ENTER after each command:
    net Stop binlsvc
    net Start binlsvc

No comments: