Applies To: Windows Server 2012 R2, Windows Server 2012
Insert the Windows Server 2012 R2 DVD-ROM or bootable USB and turn on your computer. You should see a message informing you that Windows is copying temporary files; if not, you should access the BIOS setup program included with your computer and modify the boot sequence so that the computer boots from the DVD or USB. These features and functionalities in Windows Server 2012 R2 have either been removed from the product in the current release or are planned for potential removal in subsequent releases (“deprecated”). Common Management Tasks and Navigation in Windows Windows Server 2012 R2 and Windows Server 2012 feature the new Modern user interface. This videos contains the step by step installation of Windows Server 2012. How to install Windows Server 2012 R2 Domain Controller (Step By Step guide) - Duration: 30:20.
This guide contains step-by-step guidance for how to use the Windows Deployment Services role. This guide focuses on the functionality of the complete installation of Windows Deployment Services.
In this guide
Contents
Quick start checklist
To get up and running quickly, perform the following steps. Then you can use the instructions in the rest of this guide to perform more advanced tasks such as creating your own install images, creating discover images, or configuring an unattended installation.
What is Windows Deployment Services?
Windows Deployment Services enables you to deploy Windows operating systems. You can use it to set up new computers by using a network-based installation. This means that you do not have to install each operating system directly from installation media, for example a DVD or USB drive.
What’s new in Windows Deployment Services?
Windows Deployment Services has evolved as each version is released. You can read about the new features and improvements in Windows Deployment Services in What’s New in Windows Deployment Services.
Who should use this guide?
Windows Deployment Services is intended for deployment specialists who are responsible for the deployment of Windows operating systems. This guide assumes that you have a working knowledge of common desktop deployment technologies, as well as networking components such as Dynamic Host Configuration Protocol (DHCP), Domain Name System (DNS), and Active Directory Domain Services (AD DS). The target audiences are:
Benefits of Windows Deployment Services
Windows Deployment Services provides the following benefits:
Installing Windows Deployment ServicesPrerequisites for installing Windows Deployment Services
The following are requirements for installing this role, depending on whether you choose the default installation (both Deployment Server and Transport Server), or only the Transport Server role service.
Installation Methods
You can install Windows Deployment Services by using Server Manager, or using Windows PowerShell.
To install using Server Manager
During installation, on the Select role services page, the wizard presents the option to select role services to be installed in Windows Deployment Services. You can choose to install the Deployment Server and Transport Server, or leave both roles selected.
Windows PowerShell equivalent commands
The following Windows PowerShell cmdlet or cmdlets perform the same function as the preceding procedure. Enter each cmdlet on a single line, even though they may appear word-wrapped across several lines here because of formatting constraints.
In Windows PowerShell, unlike in the Add Roles and Features Wizard, management tools and snap-ins for a role are not included by default. To include management tools as part of a role installation, add the -IncludeManagementTools parameter to the cmdlet. If you are installing roles and features on a server that is running a Server Core Installation and you add a role’s management tools to an installation, you are prompted to change the installation option to a minimal-shell option that allows the management tools to run. Otherwise, management tools and snap-ins cannot be installed on servers that are running the Server Core Installation option of Windows Server.
To install using Windows PowerShell
Note
This will install both the Deployment Server and the Transport Server roles. The previous command line tool, Servermanagercmd.exe, was deprecated in Windows Server 2012. It is recommended that you use the Windows PowerShell cmdlets.
Install Windows Deployment ServicesTo install the Windows Deployment Services role
Note
For an Active Directory integrated installation, the Deployment Server requires that Active Directory Domain Services, DHCP, and DNS services are available on your network. Transport Server does not require any additional roles or services. Both of these services require an NTFS partition for the file store.
Note
Before you begin, you need to configure Windows Deployment Services by running either the Windows Deployment Services Configuration Wizard or WDSUtil.exe. You will also need to add at least one boot image and one install image to the image store.
Note
To install Windows operating systems from a Windows Deployment Services server, either the client computers must be PXE-enabled, or you must use the latest version of the Windows Pre-Installation Environment (Windows PE). See Windows Assessment and Deployment Kit (ADK) for Windows 8.1in Additional References.
Configuring Windows Deployment Services
After you install the Windows Deployment Service role, you must configure the server. Once you have used the instructions in this section to configure the server, add a boot image, and an install image, you will be ready to deploy images. Then, you can use the instructions in the rest of this guide to perform more advanced tasks like creating your own install images, creating discover images, or configuring an unattended installation.
Prerequisites for configuring Windows Deployment Services
Steps for configuring Windows Deployment Services for Standalone Server
There are two configuration options for Windows Deployment Services. It can be configured to integrate with Active Directory or be configured as a standalone server.
To configure the server role in Standalone mode, use the following procedure. Then see the following section to add images to the server.
To configure Windows Deployment Services in Standalone mode
Now that you have configured the server, you will need to add images. These images include a boot image (which is the bootable environment that you initially boot the computer into, and the install images (which are the actual images that you deploy). For instructions, see Steps for adding images.
Installing Windows Deployment Services integrated with Active Directory
This section describes installing Windows Deployment Services integrated with Active Directory. You may skip this if you have chosen to install Standalone mode, and proceed to Steps for adding images.
Prerequisites for installing Windows Deployment Services
The following are requirements for installing this role, depending on whether you choose the default installation (both Deployment Server and Transport Server), or only the Transport Server role service.
To install Windows Deployment Services integrated with Active Directory, the following prerequisites are required.
Steps for configuring Windows Deployment Services integrated with Active Directory
To configure the Windows Deployment Services server role integrated with Active Directory, use the following procedure.
Windows Server 2012 R2 Setup GuideTo configure Windows Deployment Services integrated with Active Directory
Now that you have configured the server integrated with Active Directory, you will need to add your images. These images include a boot image (which is the bootable environment that you initially boot the computer into, and the install images (which are the actual images that you deploy). For instructions, see the next section, Steps for adding images.
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.
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.
To add the default images, use the following procedures.
To add the default boot image included on the product installation media
Repeat this procedure to add any additional boot images.
Installing an install image
After you have at least one boot and one install image on the server, you can deploy an install image.
Prerequisites for installing an install image
Steps for installing an install image
To perform a PXE boot on a computer to install an image, use the following procedure.
To install an operating system
Boot Image and Install Image Priorities
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.
Steps for configuring the boot menuTo configure menu order for boot images
To configure menu order for install images
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. (if those images apply to that computer).
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.
Creating custom install images
Optionally, you can create custom install images for Windows 8.1, Windows 8, and Windows 7. 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.
Prerequisites for creating custom install images
Known issues when creating custom install images
When you boot into the capture image, the Image Capture Wizard will start. Note the following points about this wizard:
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.
Steps for creating a capture image
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 .wim file. You can also create media (a CD, DVD, USB drive, or other type of media) that contains a capture image, and then boot a computer from the media. These images provide an alternative to the command-line utility, ImageX.exe. Except in advanced scenarios, you can create a capture image by using the Boot.wim file from the Windows installation media.
To create a capture image
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.
Steps for creating an install image
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 .wim file. After that, you can deploy the .wim file to a computer.
To create a custom install image
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.
Creating discover images
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. When you create a discover image and save it to media (a CD, DVD, USB flash drive, or other type of media), you can then boot a computer to the media.
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.
Prerequisites for creating discover images
Windows Server 2012 After Installation GuideSteps for creating discover images
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.wim file from your Windows installation media.
To create a discover image
Use the following procedure to create media that contains the 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.
To create media that contains the discover image
Performing an unattended installation
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.
Prerequisites for performing an unattended installation
Steps for performing an unattended installation
To automate the installation, create the appropriate unattend file depending on whether you are configuring the Windows Deployment Services screens or Windows Setup. We recommend that you use Windows System Image Manager (included as part of the Windows Assessment and Deployment Kit) to author the unattend files. The Windows System Image Manager (Windows SIM) creates and manages unattended Windows Setup answer files in a graphical user interface (GUI).
You will then need to copy the unattend file to the appropriate location, and assign it for use. You can assign it at the server level or the client level. The server level assignment can further be broken down by architecture, enabling you to have different settings for x86-based and x64-based clients. Assignment at the client level overrides the server-level settings.
To associate a client unattend file by architecture
To associate an image unattend file
Creating a multicast transmission
Multicast transmissions enable you to deploy an image to a large number of client computers without overburdening the network. When you create a multicast transmission, the image is sent over the network only once, which can drastically reduce the amount of network bandwidth that is used. Note that data is transferred only if clients request data.
If no clients are connected (that is, if the transmission is idle), data will not be sent over the network. For information about using multicast functionality with Transport Server, see Using Transport Server.
Prerequisites for creating a multicast transmission
Steps for creating a multicast transmission
To enable multicasting for an image, you must create a multicast transmission for it. You have two options for creating a transmission:
There are two types of multicast transmissions:
Steps for configuring transmissions
After a transmission has been created, you can perform the following actions:
Steps for configuring clients in a transmission
After you have created the transmission, client computers can join it by selecting the image in the Windows Deployment Services client installation screens. Client computers can also join a transmission by using Wdsmcast.exe, a command-line tool included in the Windows Assessment and Deployment Kit (ADK). You will find command line tool from the C:Program Files (x86)Windows Kits8.0Assessment and Deployment KitDeployment Toolsx86wdsmcast folder.
When there are clients in a transmission, you can do any of the following:
Additional ReferencesUnderstanding the Windows Assessment and Deployment Kit (ADK) for Windows 8.1
Download the Windows Assessment and Deployment Kit for Windows 8.1.
Features available in the Windows Assessment and Deployment Kit (ADK) include:
Application Compatibility Toolkit (ACT)
The Application Compatibility Toolkit (ACT) helps IT Professionals understand potential application compatibility issues by identifying which applications are or are not compatible with the new versions of the Windows operating system. ACT helps to lower costs for application compatibility evaluation by providing an accurate inventory of the applications in your organization. ACT helps you to deploy Windows more quickly by helping to prioritize, test, and detect compatibility issues with your apps. By using ACT, you can become involved in the ACT Community and share your risk assessment with other ACT users. You can also test your web applications and web sites for compatibility with new releases of Internet Explorer. For more information, see Application Compatibility Toolkit.
Deployment Tools
Deployment tools enable you to customize, manage, and deploy Windows images. Deployment tools can be used to automate Windows deployments, removing the need for user interaction during Windows setup. Tools included with this feature are Deployment Imaging Servicing and Management (DISM) command line tool, DISM PowerShell cmdlets, DISM API, Windows System Image Manager (Windows SIM), and OSCDIMG. For more information, see Deployment and Imaging Tools Technical Reference.
User State Migration Tool (USMT)
USMT is a scriptable command line tool that IT Professionals can use to migrate user data from a previous Windows installation to a new Windows installation. By using USMT, you can create a customized migration framework that copies the user data you select and excludes any data that does not need to be migrated. Tools included with the feature are ScanState, Loadstate, and USMTUtils command line tools. For more information, see User State Migration Tool Technical Reference.
Volume Activation Management Tool (VAMT)
Windows 2012 Server Installation Guide 2017
The Volume Activation Management Tool (VAMT) enables IT professionals to automate and centrally manage the activation of Windows, Windows Server, Windows ThinPC, Windows POSReady 7, select add-on product keys, and Office for computers in their organization. VAMT can manage volume activation using retail keys (or single activation keys), multiple activation keys (MAKs), or Windows Key Management Service (KMS) keys. For more information, see Volume Activation Management Tool Technical Reference.
Windows Performance Toolkit (WPT)
Windows Performance Toolkit includes tools to record system events and analyze performance data in a graphical user interface. Tools available in this toolkit include Windows Performance Recorder, Windows Performance Analyzer, and Xperf.
Windows Assessment Toolkit
Tools to discover and run assessments on a single computer. Assessments are tasks that simulate user activity and examine the state of the computer. Assessments produce metrics for various aspects of the system, and provide recommendations for making improvements.
Windows Assessment Services
Tools to remotely manage settings, computers, images, and assessments in a lab environment where Windows Assessment Services is installed. This application can run on any computer with access to the server that is running Windows Assessment Services.
Windows Preinstallation Environment (Windows PE)
Minimal operating system designed to prepare a computer for installation and servicing of Windows.
-->
Applies To: Windows Server 2012, Windows Server 2012 R2
Use the articles in this section to learn how to install and deploy Windows Server 2012 R2 and Windows Server 2012.
Windows Server 2012 R2
Windows Server 2012
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |