To install Windows Deployment Services integrated with Active Directory, the following prerequisites are required. To configure the Windows Deployment Services server role integrated with Active Directory, use the following procedure. On the Install options page, choose Integrated with Active Directory.
Now that you have configured the server integrated with Active Directory, you will need to add your images. For instructions, see the next section, Steps for adding images. You must add at least one boot image and one install image before you will be able to boot to the Windows Deployment Services server and install an image.
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. The Boot. Install images. Install images are the operating system images that you deploy to the client computer. You can also use the Install. The following instructions use Windows 7 installation media as an example for creating an install image that can be deployed with Windows Deployment Services.
You can also use the same instructions for server installation media. Browse to choose the default boot image Boot.
On the Image Metadata page, enter the desired image name and description. After you have at least one boot and one install image on the server, you can deploy an install image. Select the appropriate boot image from the boot menu.
This boot image selection menu will be available only if you have two or more boot images on the server. Click OK. At the Install Windows dialog box, select the operating system you wish to install. If you only have one operating system to install, choose that and click Next.
If prompted at the Where do you want to install Windows page, select the partition you wish to install the operating system on. When you have multiple boot or install images available to client computers, clients will be presented with a boot and an install menu that displays the selection of images to choose from. Windows Deployment Services allows you to set priorities to control the order that both boot and install image listings are presented to clients.
This ability is integrated directly into Windows Deployment Services. Click the Boot Images node. Click Properties. In the Image Properties dialog, on the General tab, enter in your desired priority into the Priority text box. The items that appear first on your install image menu are the ones with the lowest value. Double-click the Install Images node.
You will see your image group or image groups appear as a sub menu item. Right-click your desired image within your image group from the right-hand side of your Windows Deployment Services MMC snap-in. On the Image Properties dialog, in the General tab, enter in your desired priority into the Priority text box.
When you have completed this procedure and you perform a PXE boot on a client computer, a boot or install menu with the menu order you set using priorities will appear. Priorities are pre-populated with a default value that lets you place images higher or lower on the list. The items that appear first on the list are the ones with the lowest value. Optionally, you can create custom install images for Windows 8. To do this, use the instructions in this section to create a capture boot image, prepare a reference computer using Sysprep, and then capture the operating system using the Image Capture Wizard.
When you boot into the capture image, the Image Capture Wizard will start. Note the following points about this wizard:. If you do not run Sysprep on the computer before you boot into the image, you will not see any drives to capture. You must enter a local location to save the new install image; otherwise, you will not be able to capture the image. This location can be a mapped network drive but we recommend that you use a local location to avoid image corruption in the event of a network malfunction.
To create an install image, you must first create a capture image. Capture images are boot images that you boot a client computer into to capture the operating system into a. These images provide an alternative to the command-line utility, ImageX.
Except in advanced scenarios, you can create a capture image by using the Boot. Right-click the image to use it as a capture image. In most cases, you can just use the Boot. Type in your Image Name, Image Description, and the location and file name where you want to save a local copy of the file. You must specify a location in case there is a problem with the network when you deploy the capture image. Enter the location of the Windows Image file that contains the images.
Enter your Image Name and Image Description. After you have created the capture image, follow the instructions in the next section to boot a computer into the capture image and capture the operating system.
Now that you have a capture image, you need to prepare a reference computer and then create the install image. The reference computer can be a computer with a standard Windows installation or a Windows installation that has been configured for your environment. First, you boot a computer which has been prepared with Sysprep into the capture image. Then a wizard creates an install image of the reference computer and saves it as a.
After that, you can deploy the. Create a reference computer install the operating system, applications, and make any other changes that you want. In the boot menu, select the capture boot image that you created in the preceding procedure, and then press ENTER. On the Directory to Capture page, select Volume to capture , enter your Image name and Image description. Referring to Volume to capture , you will see only drives that contain operating systems prepared with Sysprep. If you do not run the command in step 4, you will not see any drives to capture.
Click Browse next to Name and location and browse to a local folder where you want to store the captured install image. Type a name for the image, using the. Note that this location can be a mapped network drive. You must enter a local location to save the new image; otherwise, you will not be able to capture the image. This requirement is enforced to avoid image corruption if there is a network malfunction.
Click Connect. If prompted for credentials, provide a user name and password for an account with permissions to connect to the Windows Deployment Services server. Select your Image Group Name. The wizard will now complete and create a custom installation image and store it in the Windows Deployment Services store.
When this process is complete, you can PXE boot a client computer to install this image. The image will be listed in the installation option. If you have a computer that is not PXE enabled, you can create a discover image and use it to install an operating system on that computer. Otherwise, you can skip this section. The discover image on the media locates a Windows Deployment Services server, and the server deploys the install image to the computer.
You can configure discover images to target a specific Windows Deployment Services server. This means that if you have multiple servers in your environment, you can create a discover image for each one, and then name them based on the name of the server. After you create the discover image, you will need to create media that contains the image. You must create discover images by using the Boot. In the location and file name, click Browse and select the location for storing your discover boot image.
Enter the name of your discover image. Optionally, enter the name of your Windows Deployment Services server that you want to respond when you boot a computer into this image. This following example details how to create media that contains a discovery image. The client computer has a network adapter that does not support Multicast. When you try to run the boot program, the program fails, and you cannot deploy Windows to the client computer.
This issue occurs because an error occurs when WDS tries to disable Multicast. Note This issue occurs only when the network adapter on the client computer does not support Multicast. A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article.
This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix. If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website:.
If you do not see your language, it is because a hotfix is not available for that language. For more information about how to obtain a Windows 7 or Windows Server R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:. The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time DST bias.
Additionally, the dates and the times may change when you perform certain operations on the files. Important Windows 7 hotfixes and Windows Server R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems.
WDS error: Windows cannot install required files. Make sure all files required for installation are available, and restart the installation Ask Question. Asked 8 years, 2 months ago. Active 3 years, 8 months ago. Viewed 21k times. Then the second action Getting files ready for installation ends up displaying the following message: Windows cannot install required files.
Here is the setuperr. Improve this question. HopelessN00b 53k 31 31 gold badges silver badges bronze badges. Brain Brain 1 1 gold badge 3 3 silver badges 10 10 bronze badges. Add a comment. Active Oldest Votes. Unmount and recapture the changes using ImageX. Improve this answer. BE77Y 2, 3 3 gold badges 17 17 silver badges 23 23 bronze badges. This solved my problem!
BT folder from image. Wurms Wurms 21 1 1 bronze badge. Same answer. Kibrom Wendem Kibrom Wendem 1. Sign up or log in Sign up using Google.
0コメント