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. However, it is an example only; you can substitute any values you require. For example, different architecture and folder names and locations. Click Start , click Deployment and Imaging Tools. Otherwise, type Deployment and Imaging Tools , and then click Deployment and Imaging Tools from the search results pane.
You will be presented with a Command Prompt window. Boot the client computer to the media. You may need to change the boot order in the client BIOS to do this. When the client boots to the media, your experience will be exactly the same as if you had booted to the network.
Optionally, you can automate the entire installation. To do this, you use two different unattend files: one for the Windows Deployment Services UI screens, and one for the latter phases of Setup. Windows Deployment Services client unattend file.
This file uses the Unattend. It is used to automate the Windows Deployment Services client user interface screens such as entering credentials, choosing an install image, and configuring the disk. Image unattend file. This file can use either the Unattend. It is used to automate the remaining phases of setup for example, offline servicing, Sysprep specialize, and mini-setup. Ensure that you are a member of the Local Administrators group on the Windows Deployment Services server.
USMT is a backup and restore tool that allows you to migrate user state, data, and settings from one installation to another. Note Occasionally, we find that customers are wary of USMT because they believe it requires significant configuration, but, as you will learn below, using USMT is not difficult. In addition to these tools, there are also XML templates that manage which data is migrated.
You can customize the templates, or create new ones, to manage the backup process at a high level of detail. USMT uses the following terms for its templates:. A sample USMT migration file that will exclude. USMT supports capturing data and settings from Windows Vista and later, and restoring the data and settings to Windows 7 and later including Windows 10 in both cases.
It also supports migrating from a bit operating system to a bit operating system, but not the other way around. By default USMT migrates many settings, most of which are related to the user profile but also to Control Panel configurations, file types, and more. The default templates that are used in Windows 10 deployments are MigUser. These two default templates migrate the following data and settings:. Folders from each profile, including those from user profiles as well as shared and public profiles.
Specific file types. USMT templates migrate the following file types:. These are the settings migrated by the default MigUser. Windows Imaging and Configuration Designer Windows ICD is a tool designed to assist with the creation of provisioning packages that can be used to dynamically configure a Windows device PCs, tablets, and phones. This is particularly useful for setting up new devices, without the need for re-imaging the device with a custom image.
For more information, see Windows Imaging and Configuration Designer. Windows SIM is an authoring tool for Unattend. With this tool, you can install and manage product keys throughout the organization. For example, if you want to get information from the VAMT database, you can type:. The key thing to know about Windows PE is that, like the operating system, it needs drivers for at least network and storage devices in each PC.
Luckily Windows PE includes the same drivers as the full Windows 10 operating system, which means much of your hardware will work out of the box. You can also extend Windows RE and add your own tools if needed. Remember that the two main functions you will use are the PXE boot support and multicast. Most of the changes are related to management and increased performance. In most scenarios, the Active Directory integration mode is the best option. WDS also has the capability to manage drivers; however, driver management through MDT and Configuration Manager is more suitable for deployment due to the flexibility offered by both solutions, so you will use them instead.
In most scenarios, those solutions are better than the built-in pre-staging function as they allow greater control and management. This is not required, but each server and client computer must be able to connect to each other to share files, and to resolve all DNS names and Active Directory information for the contoso. Internet connectivity is also required to download OS and application updates. The following generic credentials are used in this guide.
You should replace these credentials as they appear in each procedure with your credentials. Active Directory domain name : contoso. The following OU structure is used in this guide. Instructions are provided below to help you create the required OUs. These steps assume that you have the MDT01 member server running and configured as a domain member server. You might need to temporarily disable IE Enhanced Security Configuration for administrators in order to download files from the Internet to the server.
Be sure that you are viewing file extensions and that you save the file with the. The final result of either method is shown below. When creating a reference image, you need an account for MDT. To create an MDT build account, open an elevated Windows PowerShell prompt on DC01 and enter the following copy and paste the entire command, taking care to notice the scroll bar at the bottom. By default MDT stores the log files locally on the client. In order to capture a reference image, you will need to enable server-side logging and, to do that, you will need to have a folder in which to store the logs.
0コメント