Because after capturing, I want to use WDS (Windows Deployment Service) through Server 2008 R2 to deploy the windows and Linux images on new systems. I don't want to use any third party applications to capture the Linux image as it is a requirement. Please help. Those wim's would need to added to the boot images section in WDS (I only use the x64 but depends on whether you are using x64 or x86 version of your images). These wim's give WDS the info of where each MDT deploymentshare is located. And depending on the type of changes you make in the deploymentshares, you may need to right click the shares How to import the boot image. Supply the correct drivers in MDT: Update the Deployment Share. Go to Windows Deployment Services, Boot Images. Go to Add Boot Image (LiteTouchPE_x64.wim) if Lite Touch Windows PE x64 is not already present in WDS: If Lite Touch Windows PE (x64) is already in WDS Boot Images, right click on the image and choose To add a driver to a boot image using the WDS MMC follow these steps: Navigate to the boot images folder and right-click on the boot image to add the driver. Select Add Driver Packages to Image… and click Next. Modify the filters if required and click Search for Packages. Choose the driver to add and click Next. The goal here is to make sure your WDS server is no longer sending the Microsoft bootfile to your PXE-booting clients. So we add Syslinux, which we can customize. This will give us the option to forward it back to your Windows boot images on your WDS (or provided by MDT) or your Linux images, which will be offered via the NFS-protocol. Changing Legacy BIOS Boot Order (Generation One Virtual Machine) To Achieve this we need to log onto the WDS/MDT server and open an Administrative Command Prompt Shell Window. Now open File Explorer and navigate to where you have your WDS RemoteInstall Folder located, inside the root open the TMP Folder and look for a file starting with x86x64. There is an install.wim (the actual Windows installation files) and the other is the boot.wim used to boot the client device. For the differences between Capture image, Discover image, Install and Boot images (Windows PE). Note: During the configuration of Windows Deployment Services (WDS), we did not add the images, this was left on purpose to Windows Deployment Services (WDS) is a really interesting tool from Microsoft. It allows an administrator to remotely deploy Windows operating systems to machines booting from a network adapter. On how to add images to WDS and configure Multicast transmission via the GUI and WDSUTIL, see the following link. See the following guide on how to set… WDS PXE boot is not affected by this change. You can still use WDS to PXE boot devices with custom boot images, but you cannot use boot.wim as the boot image and run Windows Setup in WDS mode. You can still run Windows Setup from a network share. Workflows that use a custom boot.wim, such as MDT or Configuration Manager are not affected by this Configuring multiple boot images on WDS. 1. For my WDS server I installed Windows XP to Windows 10. Including all the server variations as well. Each disk comes with a boot.wim file. Is there any reason I need to load all these boot.wim files in to WDS or can I just use one Windows boot.wim file? windows windows-server-2012-r2 boot pxe-boot wds. The command specifies that Windows Deployment Services does not verify the source image file before it adds it to the image store. Example 2: Import a boot imag