You can list multiple paths in this key by separating them with a semicolon ; as follows:. Note If the device has already been recognized by the operating system as a known or unknown device, you must remove the device through Device Manager before you run Sysprep or the updated drivers are not installed on startup during mini-Setup. Drivers is a shared folder. The default value is located in the following registry subkey:. Edit the DevicePath key by using Registry Editor so that path where the drivers are located is included in the search path.
Assume that you have completed these steps and new hardware is installed. When a user logs on, Plug and Play locates the new hardware and searches the device paths that you specified to locate the OEM-supplied drivers. Notice that all the rules that apply to signed and unsigned drivers also apply to devices that are installed after Setup. Assume that the OEM-supplied drivers for the new device are not digitally signed and a non-administrator user logs on to the computer after the new hardware is installed.
In this case, the user cannot complete the installation of the device until an administrator logs on to the computer. For Microsoft Windows Unattended setup When you add drivers to unattended Setup, follow these steps. For more information about how to disable this message, click the following article number to view the article in the Microsoft Knowledge Base: How to set the driver signing policy for Windows Unattended Setup Create your distribution share on a server by copying the contents of the Windows installation disc I folder.
Save the answer file. Sysprep setup The steps to add OEM-supplied drivers to a Windows Sysprep Setup resemble the steps in the "Unattended Setup" section, except that you do not have to create the distribution share.
For more information, click the following article numbers to view the articles in the Microsoft Knowledge Base: Non-present SCSI devices appear in Device Manager when you are using Sysprep version 1.
To stop and restart the BINL service, type the following commands at the command prompt, and then press ENTER after each command: net stop "boot information negotiation layer" net start "boot information negotiation layer" Riprep images Riprep and Sysprep share much of the same functionality. If this is the case, you must also follow the procedure that is described in the "RIS Installations" section or use the procedure that described in the following Microsoft Knowledge Base article: How to add third-party OEM network adapters to RIS installations If the image is already created and you want to add OEM-supplied Plug and Play drivers, we recommend that you use RIS to download the image to a computer, follow the steps listed in the previous "Riprep Images" section, and then Riprep the image back to the RIS server.
For more information, click the following article number to view the article in the Microsoft Knowledge Base: Riprep. To do this, follow these steps: Decide whether you want to copy the drivers locally or if you want to store them on a central distribution server. For more information, click the following article number to view the article in the Microsoft Knowledge Base: Non administrator permissions to load and unload device drivers Note If the device has already been recognized by the operating system as a known or unknown device, you must remove the device through Device Manager before you run Sysprep or the updated drivers are installed on startup during mini-setup.
For Windows Server Unattended setup When you add drivers to unattended Setup, follow these steps. For more information about how to disable this message, click the following article number to view the article in the Microsoft Knowledge Base: How to set the driver signing policy for Windows Unattended Setup Create your distribution share on a server by copying the contents of the Windows installation CD-ROM I folder.
For more information, click the following article number to view the article in the Microsoft Knowledge Base: Updated System Preparation tool for Windows Server Service Pack 1 Note If the OEM-supplied drivers are not digitally signed, the mini-wizard postpones the installation of the device until an administrator logs on to the computer.
Existing Windows installations You may have to add new hardware devices to existing Windows-based computers that require OEM-supplied drivers. For more information, click the following article number to view the article in the Microsoft Knowledge Base: Non administrator permissions to load and unload device drivers Note If the device has already been recognized by the operating system as a known or unknown device, you must remove the device by using Device Manager before you run Sysprep or the updated drivers are installed on startup during mini-Setup.
Need more help? Expand your skills. Get new features first. Was this information helpful? Yes No. Thank you! Any more feedback? The more you tell us the more we can help. Can you help us improve? Resolved my issue. Clear instructions. Easy to follow. No jargon. Pictures helped. Didn't match my screen. Incorrect instructions. Too technical. Not enough information. The default Riprep. If one of the OEM-supplied drivers is for the primary network adapter, the RIS server must also have this file available from a typical RIS flat image before the Riprep image is downloaded.
If the image is already created and you want to add OEM-supplied Plug and Play drivers, we recommend that you use RIS to download the image to a computer, follow the steps listed in the previous "Riprep Images" section, and then Riprep the image back to the RIS server.
You may have to add new hardware devices to existing Windows-based computers that require OEM-supplied drivers. Although this process requires that you install the new device, you may want the OEM-supplied drivers to be distributed in a controlled manner or to be centrally located on one server. To do this, follow these steps:. Decide whether you want to copy the drivers locally or if you want to store them on a central distribution server.
If you want to store the drivers locally on the computer's hard disk, you must have a procedure to copy the drivers to the computer. After the distribution method is determined, obtain the path for the device drivers.
The DevicePath key in the local computer's registry has to be updated to reflect the new OEM driver locations. You must have an automated method of remotely updating the registry key.
You can use Regedit files together with logon scripts or with an SMS batch job. Edit the DevicePath key by using Regedt This section, method, or task contains steps that tell you how to modify the registry.
However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base: How to back up and restore the registry in Windows.
After you have completed these steps and new hardware is installed, when a user logs on, Plug and Play locates the new hardware and searches the device paths you specified to locate the OEM-supplied drivers.
If the OEM-supplied drivers for the new device are not digitally signed and a non-administrator user logs on to the computer after the new hardware is installed, the user cannot complete the installation of the device until an administrator logs on to the computer. If the device has already been recognized by the operating system as a known or unknown device, you must remove the device through Device Manager before you run Sysprep or the updated drivers are installed on startup during mini-setup.
You can use Setupmgr. You can find Setupmgr. You can also download the latest files from the Microsoft Web site. You may want to create additional folders in the Drivers subfolder, depending on the hardware that you want to install for example, network adapter, modem, or video. We recommend that you use the latest version of Sysprep that is available for your operating system.
If you do not want the OEM-supplied drivers to remain on the volume after the mini-wizard is complete, you can add the folder structure that you created in the previous step under the Sysprep folder.
The Sysprep folder and its subfolders is automatically removed after Setup is finished. Notice that you do not have to specify the -pnp command-line switch unless there are earlier ISA devices on the target computers. If you use the -pnp command-line switch, a full Plug and Play re-enumeration of all devices is performed, that adds minutes to the Sysprep mini-wizard process.
Also, if you specify an additional mass-storage controller, the -pnp command-line switch may cause some additional hard disk controllers to appear in Device Manager. For example, use the following structure:. You can list multiple paths in this key by separating them with a semicolon ; as follows:. If the device has already been recognized by the operating system as a known or unknown device, you must remove the device through Device Manager before you run Sysprep or the updated drivers are not installed on startup during mini-Setup.
Drivers are a shared folder. Edit the DevicePath key by using Registry Editor so that path where the drivers are located is included in the search path. A network administrator can also preload driver packages on a network server that provides the source for driver packages that are installed on network computers.
When Windows searches for drivers that match a device, Windows will check whether there are preloaded driver packages that match the device. How to configure a Windows installation to preload driver packages is outside the scope of this documentation. After Windows is installed, a driver package can be preloaded in one of the following ways:.
To preload a driver package for a computer network, a network administrator can copy the driver package to a shared directory on a network server and concatenate the path of the shared directory to the DevicePath value entry in the registry of the network computers that have access to the shared directory.
The format of the DevicePath value entry is the following, where each directory path is either a local directory path or a path of a shared directory on a network server where the preloaded driver packages are located:. Specifying network share in DevicePath in a machine with point and print client connection can result in excessive network share access and printing delays.
0コメント