Windows Deployment Services Getting Started Guide for Windows Server 2012

Windows Deployment Services Getting Started Guide for Windows Server 2012
  • Article
  • 35 minutes to check out

Applies To: Windows Server 2012 R2, Windows Server 2012

This guide includes detailed assistance for how to utilize the Windows Deployment Services function. This guide concentrates on the performance of the total setup of Windows Deployment Services.

Table of Contents

In this guide

Contents

Quick begin list

To get up and running rapidly, carry out the following actions. You can utilize the directions in the rest of this guide to carry out more sophisticated jobs such as producing your own set up images, developing find images, or setting up an ignored setup.

Task Reference
Install Windows Deployment Services. Installing Windows Deployment Services
Configure the server and include the default images (Install.wim and Boot.wim) that are consisted of on the setup media (in the Sources folder). Configuring Windows Deployment Services
Install an os. Installing a set up image

What is Windows Deployment Services?

Windows Deployment Services allows you to release Windows running systems. You can utilize it to establish brand-new computer systems by utilizing a network-based setup. This indicates that you do not need to set up each os straight from setup media, for instance a DVD or USB drive.

What’s brand-new in Windows Deployment Services?

Windows Deployment Services has actually developed as each variation is launched. You can check out the brand-new functions and enhancements in Windows Deployment Services in What’s New in Windows Deployment Services

Who should utilize this guide?

Windows Deployment Services is meant for release professionals who are accountable for the release of Windows running systems. This guide presumes that you have a working understanding of typical desktop implementation innovations, along with networking parts such as Dynamic Host Configuration Protocol (DHCP), Domain Name System (DNS), and Active Directory Domain Services (ADVERTISEMENT DS). The target market are:

  • IT coordinators or experts assessing Windows 7, Windows 8, Windows ® 8.1, Windows Server 2008 R2, Windows Server 2012, and Windows Server ® 2012 R2.
  • Enterprise IT organizers or designers.
  • Deployment experts thinking about releasing images to computer systems.

Benefits of Windows Deployment Services

Windows Deployment Services offers the following advantages:

  • Allows network-based setup of Windows running systems, consisting of Windows 7, Windows 8, Windows 8.1, Windows Server 2008 R2, Windows Server 2012, and Windows Server 2012 R2. It lowers the intricacy and expense when compared to manual setups.
  • Deploys Windows images to computer systems without running systems.
  • Supports combined environments that consist of Windows Vista, Windows 7, Windows 8, Windows 8.1, Windows Server 2008 R2, Windows Server 2012, Windows Server 2012 R2, Windows XP, and Windows Server 2003
  • Uses basic Windows Server setup innovations, consisting of Windows PE,. wim files, and image-based setup.

Installing Windows Deployment Services

Prerequisites for setting up Windows Deployment Services

The following are requirements for installing this function, depending upon whether you pick the default setup (both Deployment Server and Transport Server), or just the Transport Server function service.

Deployment Server and Transport Server

( incorporated with Active Directory)

Transport Server
  • ADVERTISEMENT DS A Windows Deployment Services server should be either a member of an advertisement DS domain or a domain controller for an advertisement DS domain. The advertisement DS domain and forest variations are unimportant; all domain and forest setups support Windows Deployment Services.
  • DHCP You should have a working DHCP server with an active scope on the network due to the fact that Windows Deployment Services utilizes PXE, which depends on DHCP for IP attending to.
  • DNS You should have a working DNS server on the network prior to you can run Windows Deployment Services.
  • NTFS volume The server running Windows Deployment Services needs an NTFS file system volume for the image shop.
  • Credentials To set up the function, you should belong to the Local Administrators group on the server. To initialize the server, you should belong to the Domain Admins group.
The only requirement is that you should belong to the Local Administrators group on the server to set up Transport Server.
Deployment Server and Transport Server

( Standalone mode, no dependence on Active Directory)

Transport Server
  • NTFS volume The server running Windows Deployment Services needs an NTFS file system volume for the image shop.
  • DNS You should have a working DNS server on the network prior to you can run Windows Deployment Services.
  • DHCP You need to have a working DHCP server with an active scope on the network since Windows Deployment Services utilizes PXE, which counts on DHCP for IP dealing with.
  • Credentials To set up the function, you should belong to the Local Administrators group on the server.
The only requirement is that you should belong to the Local Administrators group on the server to set up Transport Server.

Installation Methods

You can set up Windows Deployment Services by utilizing Server Manager, or utilizing Windows PowerShell.

To set up utilizing Server Manager

  1. In Server Manager, click Manage
  2. Click Add functions and functions
  3. Select Role-based or feature-based setup and select the server to release WDS.
  4. On the Select server functions page pick the Windows Deployment Services check box.
  5. Click Next and follow the wizard to conclusion.

During setup, on the Select function services page, the wizard provides the alternative to choose function services to be set up in Windows Deployment Services. You can select to set up the Deployment Server and Transport Server, or leave both functions chosen.

  • Transport Server This alternative supplies a subset of the performance of Windows Deployment Services. It includes just the core networking parts. You can utilize Transport Server to develop multicast namespaces that send information (consisting of running system images) from a standalone server. You can likewise utilize it if you wish to have a PXE server that enables customers to PXE boot and download your own customized setup application. You must utilize this alternative if you wish to utilize either of these circumstances, however you do not wish to integrate all of Windows Deployment Services.
  • Deployment Server This choice supplies the complete performance of Windows Deployment Services, which you can utilize to set up and from another location set up Windows running systems. Keep In Mind that Deployment Server depends on the core parts of Transport Server.
    Note

    When you set up Windows Deployment Services, it will immediately offer the alternative (chosen by default) to set up the Remote Server Administration Tools. You can likewise include this function by utilizing the Add Roles and Features Wizard and inspecting Remote Server Administration Tools on the Select function page.

hh831478.eda3e676 68d6 4a56 90af dd29179cfd9b 28ws.11 29 Windows PowerShell comparable commands

The following Windows PowerShell cmdlet or cmdlets carry out the exact same function as the preceding treatment. Get in each cmdlet on a single line, despite the fact that they might appear word-wrapped throughout numerous lines here due to the fact that of format restraints.

In Windows PowerShell, unlike in the Add Roles and Features Wizard, management tools and snap-ins for a function are not consisted of by default. To consist of management tools as part of a function setup, include the -IncludeManagementTools criterion to the cmdlet. If you are setting up functions and functions on a server that is running a Server Core Installation and you include a function’s management tools to a setup, you are triggered to alter the setup choice to a minimal-shell choice that permits the management tools to run. Otherwise, management tools and snap-ins can not be set up on servers that are running the Server Core Installation alternative of Windows Server.

To set up utilizing Windows PowerShell

  1. Do among the following to open a Windows PowerShell session with raised user rights.
    • On the Windows desktop, right-click Windows PowerShell on the taskbar, and after that click Run as Administrator
    • On the Windows Start page, type any part of the name Windows PowerShell Right-click the faster way for Windows PowerShell when it is shown on the Start page in the Apps results, click Advanced, and after that click Run as Administrator To pin the Windows PowerShell faster way to the Start page, right-click the faster way, and after that click Pin to Start
  2. Type the following, and after that press Enter, where computer_name represents a remote computer system on which you wish to set up Hyper-V. To set up WDS straight from a console session, do not consist of -ComputerName in the command.
     Install-WindowsFeature-- Name WDS -ComputerName  -IncludeManagementTools 
  3. To see a list of offered and set up functions and functions on the regional server, type Get-WindowsFeature and after that press Enter The outcomes of the cmdlet include the command names of functions and functions that have actually been contributed to this computer system.
    Note

    In Windows PowerShell 4.0, there is no requirement to import the Server Manager cmdlet module into the Windows PowerShell session prior to running cmdlets that belong to the module. A module is immediately imported the very first time you run a cmdlet that becomes part of the module. Windows PowerShell cmdlets are not case-sensitive.

  4. When the setup is completed, confirm setup by running Get-WindowsFeature. If you set up WDS from another location, consist of the ComputerName criterion (Get-WindowsFeature– ComputerName <computer_name>) to see a list of functions and functions that are set up on the server.
Note

This will set up both the Deployment Server and the Transport Server functions. The previous command line tool, Servermanagercmd.exe, was deprecated in Windows Server2012 It is advised that you utilize the Windows PowerShell cmdlets.

Install Windows Deployment Services

To set up the Windows Deployment Services function

  1. Sign in to the server as a member of the regional Administrators group.
  2. Server Manager will begin immediately. If it does not instantly begin, click Start , type servermanager.exe, and after that click Server Manager.
  3. Click Manage .
  4. Click Add functions and functions, click Next
  5. On the Before you start page of the Add Roles and Features Wizard, click Next
  6. On the Select setup type page, click Role-based or feature-based setup, and after that click Next
  7. On the Select location server page, choose the proper server, and after that click Next The regional server is picked by default.
  8. On the Select server functions page, scroll down and after that pick the Windows Deployment Services check box. Click Next
  9. Remote Server Administration Tools are needed to handle this function. Select Include management tools (if relevant) Click Add Features Click Next
  10. On the Select functions page, click Next
  11. On the Select function services page, choose the function services to set up for Windows Deployment Services. If you want to set up both the Deployment Server and Transport Server, leave these function services picked. Click Next
  12. On the Confirm setup choices page, click Install
  13. Windows Deployment Services will now be contributed to the server. Setup development will now be highlighted in the Add Roles and Features Wizard.
Note

For an Active Directory incorporated setup, the Deployment Server needs that Active Directory Domain Services, DHCP, and DNS services are offered on your network. Transportation Server does not need any extra functions or services. Both of these services need an NTFS partition for the file shop.

Note

Before you start, you require to set up Windows Deployment Services by running either the Windows Deployment Services Configuration Wizard or WDSUtil.exe. You will likewise require to include a minimum of one boot image and one set up image to the image shop.

Note

To set up Windows running systems from a Windows Deployment Services server, either the customer computer systems should be PXE-enabled, or you need to utilize the current variation of the Windows Pre-Installation Environment (Windows PE). See Windows Assessment and Deployment Kit (ADK) for Windows 8.1 in Additional References

Configuring Windows Deployment Services

After you set up the Windows Deployment Service function, you need to set up the server. When you have actually utilized the guidelines in this area to set up the server, include a boot image, and a set up image, you will be all set to release images. You can utilize the guidelines in the rest of this guide to carry out more innovative jobs like producing your own set up images, developing find images, or setting up an ignored setup.

Prerequisites for setting up Windows Deployment Services

  1. If Windows Deployment Services is incorporated with Active Directory, the server should belong to an Active Directory Domain Services (ADVERTISEMENT DS) domain, or a domain controller for an advertisement DS domain. If Windows Deployment Services is set up in Standalone mode, it can be set up without having a dependence on Active Directory.
  2. There is an active DHCP server on the on Windows Deployment Services utilizes Pre-Execution Environment (PXE), which counts on DHCP for IP dealing with.
  3. There is an active DNS server on the network.
  4. The server has an NTFS file system partition on which to save images.

Steps for setting up Windows Deployment Services for Standalone Server

There are 2 setup alternatives for Windows Deployment Services. It can be set up to incorporate with Active Directory or be set up as a standalone server.

To set up the server function in Standalone mode, utilize the following treatment. See the following area to include images to the server.

To set up Windows Deployment Services in Standalone mode

  1. Log on to the server as a member of the regional Administrators group.
  2. Server Manager will begin immediately. If it does not instantly begin, click Start, type servermanager.exe, and after that click Server Manager
  3. Click Tools, and after that click Windows Deployment Services to release the Windows Deployment Services MMC-snap (or console).
  4. In the left pane of the Windows Deployment Services MMC snap-in, broaden the list of servers.
  5. Right-click the wanted server, click Configure Server
  6. On the Before you start page, click Next
  7. On the Install choices page, pick Standalone server
  8. On the Remote Installation Folder Locations page, select the default course or enter your own course to the remote setup folder. Click Next
  9. On the PXE Server Initial Settings page, select preferred alternative to specify which customer computer systems this server will react to. Click Next This will finish the setup of Windows Deployment Services.
  10. When the setup is finished clear the Add images to server now check box, and after that click Finish
  11. If you wish to customize any of the settings of the server, right-click the server in the MMC-snap in, and click Properties

Now that you have actually set up the server, you will require to include images. These images consist of a boot image (which is the bootable environment that you at first boot the computer system into, and the set up images (which are the real images that you release). For directions, see Steps for including images

Installing Windows Deployment Services incorporated with Active Directory

This area explains setting up Windows Deployment Services incorporated with Active Directory. You might avoid this if you have actually selected to set up Standalone mode, and continue to Steps for including images

Prerequisites for setting up Windows Deployment Services

The following are requirements for installing this function, depending upon whether you select the default setup (both Deployment Server and Transport Server), or just the Transport Server function service.

To set up Windows Deployment Services incorporated with Active Directory, the following requirements are needed.

Deployment Server and Transport Server Transport Server
  • ADVERTISEMENT DS A Windows Deployment Services server need to be either a member of an advertisement DS domain or a domain controller for an advertisement DS domain. The advertisement DS domain and forest variations are unimportant; all domain and forest setups support Windows Deployment Services
  • DHCP. You need to have a working DHCP server with an active scope on the network due to the fact that Windows Deployment Services utilizes PXE, which counts on DHCP for IP dealing with.
  • DNS. You need to have a working DNS server on the network prior to you can run Windows Deployment Services.
  • NTFS volume. The server running Windows Deployment Services needs an NTFS file system volume for the image shop.
  • Credentials. To set up the function, you should belong to the Local Administrators group on the server. To initialize the server, you should belong to the Domain Admins group.
The only requirement is that you should belong to the Local Administrators group on the server to set up Transport Server.

Steps for setting up Windows Deployment Services incorporated with Active Directory

To set up the Windows Deployment Services server function incorporated with Active Directory, utilize the following treatment.

To set up Windows Deployment Services incorporated with Active Directory

  1. Log on to the server as a member of the Domain Administrators group.
  2. Server Manager will begin instantly. If it does not instantly begin, click Start, type servermanager.exe, and after that click Server Manager.
  3. Click Tools, and after that click Windows Deployment Services to introduce the Windows Deployment Services MMC-snap (or console).
  4. In the left pane of the Windows Deployment Services MMC snap-in, broaden the list of servers.
  5. Right-click the wanted server, click Configure Server.
  6. On the Before you start page, click Next.
  7. On the Install choices page, pick Integrated with Active Directory.
  8. On the Remote Installation Folder Locations page, select the default course or enter your own course to the remote setup folder. Click Next.
  9. If your server is running as a DHCP Server, you will see the Proxy DHCP Server page. Select Do not listen on DHCP and DHCPv6 ports and Configure DHCP choices for Proxy DHCP. Click Next.
  10. On the PXE Server Initial Settings page, pick preferred choice to specify which customer computer systems this server will react to. Click Next. This will finish the setup of Windows Deployment Services.
  11. When the setup is finished, click Finish.
  12. If you wish to customize any of the settings of the server, right-click the server in the MMC-snap in, and click Properties.

Now that you have actually set up the server incorporated with Active Directory, you will require to include your images. These images consist of a boot image (which is the bootable environment that you at first boot the computer system into, and the set up images (which are the real images that you release). For guidelines, see the next area, Steps for including images.

Steps for including images

You should include a minimum of one boot image and one set up image prior to you will have the ability to boot to the Windows Deployment Services server and set up an image.

  • Boot images. Boot images are Windows PE images that you boot a customer computer system into to carry out an os setup. In many situations, you ought to utilize the Boot.wim file from the setup media (in the Sources folder). The Boot.wim file consists of Windows PE and the Windows Deployment Services customer.
  • Install images. Set up images are the os images that you release to the customer computer system. You can likewise utilize the Install.wim file from the setup media (in the Sources folder), or you can produce your own set up image by utilizing the actions in Creating customized set up images later on in this guide.

The following guidelines utilize Windows 7 setup media as an example for producing a set up image that can be released with Windows Deployment Services. You can likewise utilize the exact same directions for server setup media.

To include the default images, utilize the following treatments.

To include the default boot image consisted of on the item setup media

  1. In the left pane of the Windows Deployment Services MMC snap-in, right-click the Boot Images node, and after that click Add Boot Image.
  2. Browse to select the default boot image (Boot.wim) on the Windows setup media, situated in the Sources folder.
  3. Click Open, and after that click Next.
  4. On the Image Metadata page, go into the wanted image name and description. Click Next.
Like this post? Please share to your friends:
Leave a Reply

;-) :| :x :twisted: :smile: :shock: :sad: :roll: :razz: :oops: :o :mrgreen: :lol: :idea: :grin: :evil: :cry: :cool: :arrow: :???: :?: :!: