Difference between revisions of "Active Directory/Documentation/Add Driver To RIS"
Jump to navigation
Jump to search
m |
|||
(8 intermediate revisions by one other user not shown) | |||
Line 3: | Line 3: | ||
# On the RIS server, copy the Windows 2000 .inf and .sys files for the network adapter to the RemoteInstall\Setup\English\Images\<IMAGE>\i386 folder. This allows Setup to use the driver during the text-mode portion of the installation. | # On the RIS server, copy the Windows 2000 .inf and .sys files for the network adapter to the RemoteInstall\Setup\English\Images\<IMAGE>\i386 folder. This allows Setup to use the driver during the text-mode portion of the installation. | ||
# Copy the Windows XP driver files to $oem$\$1\Drivers\Nic. | # Copy the Windows XP driver files to $oem$\$1\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: | + | # 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:<BR> |
− | + | <pre>net Stop binlsvc</pre> | |
− | + | <pre>net Start binlsvc</pre> | |
Stopping and restarting the Remote Installation service is necessary because the Boot Information Negotiation Layer (BINL) needs to read all the new network adapter-related .inf files and create .pnf files in the image. This is a time-consuming task and is performed only when the Remote Installation service starts. | Stopping and restarting the Remote Installation service is necessary because the Boot Information Negotiation Layer (BINL) needs to read all the new network adapter-related .inf files and create .pnf files in the image. This is a time-consuming task and is performed only when the Remote Installation service starts. | ||
+ | |||
+ | '''Note from Brian''': Newer WDS servers have a different service to stop and restart, ''Single Instance Storage Groveler'' | ||
+ | <pre>net Stop groveler</pre> | ||
+ | <pre>net Start groveler</pre> | ||
=SATA Driver= | =SATA Driver= | ||
+ | See [http://h10025.www1.hp.com/ewfrf/wc/document?lc=en&cc=be&dlc=en&product=3204907&lang=en&docname=c00758841#N823 here] | ||
=Other Drivers= | =Other Drivers= | ||
+ | # Download the Windows XP drivers for the device. | ||
+ | # Copy the Windows XP driver files to $oem$\$1\Drivers\<CATEGORY>, where <CATEGORY> is the folder that best describes the device. |
Latest revision as of 09:39, 25 July 2007
NIC Driver
- Download both the Windows 2000 and Windows XP drivers for the NIC.
- On the RIS server, copy the Windows 2000 .inf and .sys files for the network adapter to the RemoteInstall\Setup\English\Images\<IMAGE>\i386 folder. This allows Setup to use the driver during the text-mode portion of the installation.
- Copy the Windows XP driver files to $oem$\$1\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
Stopping and restarting the Remote Installation service is necessary because the Boot Information Negotiation Layer (BINL) needs to read all the new network adapter-related .inf files and create .pnf files in the image. This is a time-consuming task and is performed only when the Remote Installation service starts.
Note from Brian: Newer WDS servers have a different service to stop and restart, Single Instance Storage Groveler
net Stop groveler
net Start groveler
SATA Driver
See here
Other Drivers
- Download the Windows XP drivers for the device.
- Copy the Windows XP driver files to $oem$\$1\Drivers\<CATEGORY>, where <CATEGORY> is the folder that best describes the device.