You can integrate this server with AD, as at this point we are configuring the Windows options, but I prefer a standalone server that responds to all requests and doesn’t need AD pre-staging. There are a few minor changes I like to make to the setup. On the WDS server, launch the configuration wizard and finish up the WDS configuration. The other three options are pretty standard for most DHCP setups. The “Bootfile Name” is the WDS executable that we want the client to run. The “Boot Server Host Name” is the IP address of the WDS server.
#Create a mac image for deployment update#
If you like, you can add a second NIC to this server and have a dedicated network built off it, but personally, I like to be able to build my servers on the main network anyway, so I prefer to update the central DHCP server with the additional WDS DHCP attributes: Now that we have the basic Windows Deployment Services server installed, we need to make some changes to the DHCP pool.
Install-Windowsfeature –name WDS -includemanagementtools Install-WindowsFeature –name Web-server -includemanagementtools This can be done either via the server manager tool, or if you like, the PowerShell approach. The server will need WDS and IIS to be installed.
The installation and configuration have several steps: Setup the WDS Server
#Create a mac image for deployment install#
Taking a clean Windows server, I like to provide a 60GB C: drive for the OS and a 300GB WDS drive for the various WIM files for deployment of Windows and for the Linux install files. There is no reason that others couldn’t be used. I’ll be focusing on those three operating systems as I go through this article. The WDS setup I currently use builds Windows, CentOS and ESXi. Once done, a menu entry is created to allow the Linux PXE boot menu to hand over to Windows for Windows builds, and IIS is used to provide a web interface for downloading the Linux config files. Essentially, the PXE boot loader used by Windows needs to be swapped out for a Linux one. To configure WDS to be able to deploy Windows and Linux systems requires some command line changes. Out of the box, it’s able to deploy Windows VMs, and with a couple of small tweaks, it’s possible to have WDS build Linux and VMware servers, all from a selectable Preboot eXecution Environment (PXE) boot menu. Windows Deployment Services (WDS) is a great addition to the Windows product set.