WINDOWS2008 WDS Deployment integrated NIC driver solution

Example 1:

As with Remote Installation Services in Server 2003, the basic configuration can be done basically through the wizard, but the following error prompts may eventually occur:

Wdsclient:an error occurred while starting networking:a matching network card driver is not found in this image. Please have your Administrator add the network driver for this machine to the Windows PE image on the Windows Deployment S Ervices server.

In general, an error occurred while starting the network, and no suitable NIC driver was found in the package (Boot.wim).

What we need to do is of course to integrate the NIC driver in the Boot.wim.

The following methods for manually adding drivers are:

Pre-Integration Preparation: (1) equipped with Windows AIK (2) peimg

1, download the required drive.

2, locate the boot image bootwim, which can be found in the system installation CD or exported from the WDS server to the D-Packing directory

3, create a new folder in the directory where Boot.wim is located: Boot

4, execute the command on the computer where Windows AIK is installed: IMAGEX/MOUNTRW d:boot.wim 2 D:boot

5, after successful execution command: Peimg/inf=x:netdriverschipset.inf d:bootwindows, this is to load the driver into the WIM file release directory (/inf=x:netdriverschipset.inf, The equal sign is the path to the INF file in the driver program.

6, after the successful implementation of packaging command: Imagex/unmount/commit d:boot.

Finally, you can import the updated WIM file into the WDS service (directly copy and paste overwrite the original boot.wim).

Note: When you take the windows2008x86 to do the WDS test, you find that the 4th step is modified here

The 1 corresponds to the 1 folders in the Boot.wim file, and 2 is the corresponding 2 folder, the internal structure of the Boot.wim file is this:

During the test found that only import 1 and the NIC driver loaded in, the WDS remote client installation is still unable to find the NIC driver card in the installation has just begun, if the 2 also exported and also load the network card driver, in the test found that the client can be successfully installed. It is best to export here 1 and 2 separately and load the NIC driver separately to make the Boot.wim and then replace it with the WDS server.

Example 2:

If you want to modify Windows PE 2.0, we need to install WAIK. The following is a general process of modification, the path involved in the specific operation of the corresponding changes according to the actual situation.

1. Copy the complete driver and the. wim file of Windows PE 2.0 to a directory

2, and create a directory for temporary storage of Windows PE 2.0 offline files, such as: Pemount

3, find the "Microsoft Windows AIK" program group, click "Windows PE tool command Prompt" into PE CMD line

4, using the ImageX command plus parameters mountrw first load the. wim into the Pemount directory

IMAGEX/MOUNTRW C:winpe2boot.wim 1 C:pemount

5. Use the peimg command to add a third-party driver to Windows PE 2.0, repeat this step if you need to add multiple device drivers.

Peimg/inf=c:winpe2*.inf c:pemountwindows

6. Use the ImageX command plus parameter unmount and commit to write the modifications to the. wim

Imagex/unmount C:pemount/commit

Note: When you take the windows2008x86 to do the WDS test, you find that the 4th step is modified here

The 1 corresponds to the 1 folders in the Boot.wim file, and 2 is the corresponding 2 folder, the internal structure of the Boot.wim file is this:

During the test found that only import 1 and the NIC driver loaded in, the WDS remote client installation is still unable to find the NIC driver card in the installation has just begun, if the 2 also exported and also load the network card driver, in the test found that the client can be successfully installed. It is best to export here 1 and 2 separately and load the NIC driver separately to make the Boot.wim and then replace it with the WDS server.