Add Driver Packages To Windows Deployment Services
- Add Driver Packages To Windows Deployment Services
- Add Driver Packages To Windows Deployment Services 2012
I am trying to add a driver package to WDS it says that my driver is not signed, corrupt or of the wrong architecture. So I tried to accomplish the process with cmd to see the errors and heres what I found. This is the complete log of the cmd. Also I have added one other driver and it worked. Same issue was here.I found a solution in this page.
What is Windows Deployment Services Server?
Windows Deployment Services (WDS) is a server role that provides a simplified and secure means of remotely deploying Microsoft Operating Systems to computers over the network. For a WDS to install OS on a remote computer, the computer must be PXE-enabled.
In this tutorial, you will learn how to:
- Install and Configure the Windows Deployment Services (WDS) role
- Configure and Manage Boot, Install and Discover images.
If you wish to perform the tasks in this tutorial you need one Windows server. Preferably Windows Server 2016.
Install and Configure the Windows Deployment Services (WDS) role
WDS can be installed as a Transport or Deployment Server, or both. These options are available when installing the role using Server Manager.
Sponsored Content
Transport Server
This option provides a subset of the functionality of Windows Deployment Services. It contains only the core networking parts which you can use to transmit data on a stand-alone server. Transport server uses multicasting for data transmission.
You can also use transport server if you want to have a PXE server that allows clients to PXE boot and download your own custom setup application. You should use this option if you want to use either of these scenarios, but you do not want to incorporate all the components of WDS.
Deployment Server
This option provides the full functionality of Windows Deployment Services. Provides all the options to configure and remotely install Windows operating systems. Deployment Server is dependent on the core parts of Transport Server.
You can install WDS server role via Server Manager or by using Windows PowerShell. After the Windows Deployment Services role is installed, the server has to be configured before it can be used for automated Windows Operating system deployment.
WDS can be configured as a stand-alone or Active Directory-integrated server. In this tutorial, I will show you how to configure Windows Deployment Services as an Active Directory-integrated server .
Important WDS Installation Notes and Requirements
- A Deployment Server requires a DNS and DHCP servers on the network.
- Both Deployment and Transport server requires an NTFS partition for the file store.
- After installation, you must configure WDS either by using WDSUtil.exe or running Windows Deployment Services Configuration wizard.
- You must add at least one boot image and one install image to the image store.
A boot image provides the initial environment you boot a computer to while an install image is the Operating System image.
If you follow this tutorial step-by-step, I will walk you through how to meet the outlined requirements. This tutorial does not include DNS and/or DHCP setup.
For your PXE clients to be able to lease IP addresses, configure your DHCP scope for both DHCP and BOOTP. See image below for details.
How to Install the Windows Deployment Services Role
The steps below will guide you to install Windows Deployment Services (WDS) role:
- Log on to the server and open Server Manager (should launch by default).
- From Server Manager click Manage then select Add Roles and Features.
Sponsored Content
- On the Before you begin screen, click Next.
- Next, select Role-based or feature-based installation and click Next.
- Next, on the Select Destination server page, select the server you wish to install Windows Deployment Services Role.
- On the Server Role page, check the box beside Windows Deployment Services. A page will load asking you to confirm additional features to install. Click Add Features. Then click Next.
- On the Select roles services page, check both Deployment Server and Transport Server. Note that if you check Deployment Server you MUST also check Transport Server. However, you can check Transport Server without checking Deployment Server.
- When you get to the Confirmation page, review your selections then click Install.
To install the Windows Deployment Services role with Windows PowerShell, run the command below:
Configuring Windows Deployment Services
You can configure WDS with the steps below:
- Open Server Manager. Then click Tools and select Windows Deployment Services. The WDS management console opens.
- Expand Servers. Then right-click the WDS server and select Configure Server. The configuration wizard opens.
Sponsored Content
- On the Before You Begin page, read the requirements then click Next.
- Select the integrate with Active Directory option. Click Next.
- Enter a path for your remote installation folder or accept the default.
In a production environment, I strongly recommend having your remote installation folder in a drive other than C.
- Note the information on the Proxy DHCP Server page then click Next.
- Configure settings for the PXE server.
- Finally, wait for the wizard to complete the configuration. Click Finish.
- Start the Windows Deployment Services (WDS) service: Right-click the server, point to All Tasks and click Start.
The above task can also be accomplished by running the following command:
To revert changes made during the server configuration or Initialization, execute the command:
Sponsored Content
Configure and Manage Boot, Install, and Discover Images
After configuring Windows Deployment Services server, the next step is to add the necessary image files. The following images are required:
Boot Images: Boot images are Windows PE images that you boot a client computer into to perform an operating system installation. In most scenarios, you should use the Boot.wim file from the OS installation media.
Install Images: Install images are the operating system images that you deploy to the client computer. You can also use the Install.wim file from the OS installation media.
Discover Images: In some circumstances, A computer might not have PXE-enabled network cards. In this situation, discover images may be created and used to install operating system on those computers.
A discover image may be saved on a media (CD, DVD, or USB drive), and a client computer may then be booted with the media. The discover image on the media locates a Windows Deployment Services server, and the server deploys the install image to the computer.
Discover images are not required to use Windows Deployment Services.
Prepare Boot and Install Images for Windows Deployment Services
- Copy boot.wim from Windows 10 DVD (if you have a Windows 10 ISO, mount it. Boot.wim is located in the sources folder.
To create install.wim from Windows 10 DVD, follow the steps below:
- Open command prompt with administrator privileges (search command prompt, right-click it then select run as administrator)
- Run the command below:
Below is the output of the command. Note the index number of the edition you wish to create install.wim for. I am creating a install.wim file for Windows 10 Pro. Index number is 6.
- To create install.win for Windows 10 pro, execute the command below:
The export process will commence. See image below. When it reaches 100%, the wim file is ready.
Add Boot and Install Images to Windows Deployment Services (WDS)
To add an install image, follow the steps below:
- From Server Manager, open Windows Deployment Services. Expand the Servers Node. Then expand your WDS server name.
- Right-click Install Images then click Add Install Image.
- On the Image Group window, enter a name then click Next.
- Enter path to your install.wim then click Next.
Sponsored Content
- Select the Operating System Image then click Next.
- On the Summary page, click Next. Wait for the image to be added.
- Windows 10 install image is now available in Windows Deployment Services!
You can add multiple Install.wim images. For instance you could have an image for different editions of the same OS. Alternatively, you could add images for different Operating Systems.
The steps below will walk you through adding a boot image.
- From the WDS console, right-click Boot Images and select Add Boot Image.
- Enter the path to your boot.wim file. Click Next.
- Rename the boot image to a more user-friendly name. The image name will be displayed for selection during a PXE-boot.
- On the Summary page, click Next. Then wait for the image to be imported.
- The boot image is now available.
Creating Discover Images
To create a discover image follow the steps below:
- Right-click the boot image you created earlier and select Create Discover Image.
- On the Metadata and Location page, enter all information. For the name of the Windows Deployment Services server, click Browse then use the Active Directory search tool to search for the server. When you finish click Next.
There you have it. If you have any questions or comments, kindly use the “Leave a Reply” form below.
Sponsored Content
Other Helpful Tutorials
Additional Resources and References
How to Make Windows 10 Look Like Windows 7
How to Roll Back Windows 10 Update (3 Methods)
How to Fix Network Discovery If it Keeps Turning Off in Server 2016
How to Install Windows 10 1903 Update Manually
Spotify Web Player Not Working [Fixed]
Remote Desktop Connection an Internal Error Has Occurred [Fixed]
Find My Samsung: Register and Use Samsung Find my Mobile
Windows Powershell vs CMD: Differences and Similarities
Spotify No Longer Supports this Version of Microsoft Edge [Fixed]
Windows 10 Won’t Boot With Black Screen? 3 Ways to Fix It
iPad Won’t Charge? How to Fix It
5 Ways to Restore Your Printer Online If Status is Offline
How to Move Columns to Rows and Rows to Columns in Excel
Dropbox Login: Your Ultimate Guide to Dropbox
How to Use WhatsApp Web from a Browser on Your Computer
How to Fix DISM Error 50 in Windows 10 and Windows Server 2016
2 Easy Options to Repair Windows Server 2016
Windows Server 2016 Won’t Boot After Update? Here are 3 Fixes
4 Quick Fixes for 0xc000021a Stop Error in Windows Server 2016
How to Install and Configure DHCP in Windows Server 2016
Routing and Remote Access in Windows Server 2016 (Part 4): Configure Web Application proxy
Routing and Remote Access in Windows Server 2016 (Part 3): Configure VPN
Routing and Remote Access in Windows Server 2016 (Part 2): Configure NAT
Add Driver Packages To Windows Deployment Services
Routing and Remote Access in Windows Server 2016 (Part 1): Install Remote Access Role
Add Driver Packages To Windows Deployment Services 2012
How to Fix “RDP an Internal Error has Occurred” in Server 2016
RAID 50 vs RAID 10: Benefits and Disadvantages Compared
PowerShell Start-Sleep Command: Syntax, Examples
The Active Directory Domain Services is Currently Unavailable [Fixed]
Windows was Unable to Complete the Format [Fixed]
How to Change Profile Picture on Spotify (from Desktop or Mobile)
Do I need to add my driver packages to my Windows 7 install image in order for them to get deployed when using that install image?
I can't seem to understand if this is necessary based on the documentation. The documentation sort of makes it sound like all I need to do is add it to the driver group and set the filters on the driver group appropriately...
Thank you.
JeffJeff1 Answer
You don’t have to manually add drivers to the install image, simply add them to the WDS drivers node. WDS will use Plug and Play to choose the correct driver to install. You can limit which drivers are available to your images by setting up driver groups and have the entire group installed to the client, or to use filters to define which clients get access to which driver groups.The TechNet article ‘Managing and Deploying Driver Packages’ explains these methods in more detail.
More articles and videos related to deploying Windows can be found on the Deliver and Deploy Windows 7 (and Windows 8) pages of the Springboard Series on TechNet.
Hope this helps,