Windows deployment services

1.Installing WDS #

Installing Windows Deployment Services on Server 2012 R2.

WDS is a Microsoft technology which enables you to install Windows on multiple computers simultaneously in your network. This can help you to deploy any Windows without using CD or DVD on each client machine.

Attended Vs Unattended Installation 

The difference between attended and unattended installation is the required user intervention during installation. Attended installation requires full user intervention while unattended is an automatic installation technology and requires minimal user intervention on client machines.

In this article, I am focusing on unattended installation. Attended installation method requires an answer file which I’ll cover in other article.

Benefits of WDS    

WDS has certain benefits over manual or other deployment methods which are listed below:

  • Saves system administrator time in deploying the operating system

Reduces complexity and cost

  • Transmits the data using multicast functionality which reduces network congestion
  • Allows you to create a reference image of a computer using its Image Capture wizard
  • Allows you to deploy driver packages to client computers along with install images.

Deployment Scenarios

WDS can be deployed in following three scenarios.

1. WDS and Microsoft DHCP are running on same server (especially good for small organizations)

2. WDS and Microsoft DHCP are running on different servers

3. WDS and Non- Microsoft DHCP are running on different servers

Based on the scenario, you may have to change WDS properties in DHCP tab in windows deployment services console.

Prerequisites

  • The Windows Deployment Services server must be a member of an Active Directory Domain Services (AD DS) domain or a domain controller. You may need to ‘Install Active Directory in Windows Server 2012 R2‘.
  • The Domain Name System (DNS) server on the network before you can run Windows Deployment Services. DNS will install with Active directory domain services, but if you have not, read the DNS Installation article ‘Install and Configure DNS in Windows Server 2012 R2‘.
  • For deploying IP address you must have a Dynamic Host Configuration Protocol (DHCP) server with an active scope on the network because Windows Deployment Services uses PXE, which relies on DHCP for IP addressing the clients that want to install OS remotely. Read the topic ‘Install and Configure DHCP Server on Windows Server 2012 R2‘ for DHCP Server.
  • You must have the appropriate credential to install role. It means you must be the member of local admin or domain admin. The hard disk volume must be NTFS.

Installing WDS on Windows Server 2012 R2

WDS or Windows Deployment Services is a server role in Windows Server 2012 R2. You need to install it from server manager by following the wizard. Below are the steps that will help you to get WDS role installed on your machine.

 Open server manager and click “Add roles and features”

http://www.itprotoday.com/sites/windowsitpro.com/files/uploads/2016/03/18/Screenshot%202017-02-11%2008.24.06.png

2. Skip the requirements as these are already listed in our prerequisites section above. Click Next

http://www.itprotoday.com/sites/windowsitpro.com/files/uploads/2016/03/18/Screenshot%202017-02-11%2008.24.50.png

3. Choose the desired destination server from server pool on which you want to install WDS. Click Next

http://www.itprotoday.com/sites/windowsitpro.com/files/uploads/2016/03/18/Screenshot%202017-02-11%2008.25.19.png

4. Choose Windows deployment services from server roles. As soon as you check the box, a new window will appear (as shown in the figure), prompting you to add features which are required for this WDS role. Click “Add Features”

http://www.itprotoday.com/sites/windowsitpro.com/files/uploads/2016/03/18/Screenshot%202017-02-11%2008.25.51.png

Step 6: Click Next

http://www.itprotoday.com/sites/windowsitpro.com/files/uploads/2016/03/18/Screenshot%202017-02-11%2008.26.39.png

Step 7: Leave the default selection(s) and click Next

http://www.itprotoday.com/sites/windowsitpro.com/files/uploads/2016/03/18/Screenshot%202017-02-11%2008.27.27.png

Step 8: Click Next

http://www.itprotoday.com/sites/windowsitpro.com/files/uploads/2016/03/18/Screenshot%202017-02-11%2008.27.57.png

Step 9: Leave the default selections (Deployment and Transport Server) and click Next

http://www.itprotoday.com/sites/windowsitpro.com/files/uploads/2016/03/18/Screenshot%202017-02-11%2008.28.34.png

Step 10: Click Install and wait for installation to finish (It took 5 minutes on my Windows Server 2012 R2 virtual machine)

http://www.itprotoday.com/sites/windowsitpro.com/files/uploads/2016/03/18/Screenshot%202017-02-11%2008.29.08.png

Step 12: Click Close after successful installation

http://www.itprotoday.com/sites/windowsitpro.com/files/uploads/2016/03/18/Screenshot%202017-02-11%2008.29.41.png

2.Configure WDS #

Configuring WDS on Windows Server 2012 R2

When a WDS is installed on your Windows Server 2012 R2 machine, you need to configure it.  These steps will further help you in the configuration of WDS including copying windows installation images from CD or DVD for client machines.

1. Open server manager. Click Tools -> Windows Deployment Services

http://www.itprotoday.com/sites/windowsitpro.com/files/uploads/2016/03/18/Screenshot%202017-02-11%2008.30.18.png

2. Expand Servers. Right-click your WDS server machine and then click “Configure Server”

http://www.itprotoday.com/sites/windowsitpro.com/files/uploads/2016/03/18/Screenshot%202017-02-11%2008.30.46.png

3. Choose “Standalone server” since our machine is not a member of Active Directory Domain Services. Click Next

http://www.itprotoday.com/sites/windowsitpro.com/files/uploads/2016/03/18/Screenshot%202017-02-11%2009.19.32.png

4. Click Next

http://www.itprotoday.com/sites/windowsitpro.com/files/uploads/2016/03/18/Screenshot%202017-02-11%2009.20.13.png

5. Choose the folder (Make sure the folder is created on NTFS partition and the partition should not be system partition) on your machine where you would like to place installation images, PXE boot files, and WDS management tools. Click Next

http://www.itprotoday.com/sites/windowsitpro.com/files/uploads/2016/03/18/Screenshot%202017-02-11%2009.20.46.png

6. Choose “Respond to all client computers (known and unknown)” and click Next. (If you have an active directory in your network, choose to respond only to known client computers and pre-stage client machines using their GUID or mac addresses).

http://www.itprotoday.com/sites/windowsitpro.com/files/uploads/2016/03/18/Screenshot%202017-02-11%2009.21.23.png

Step 7: Wait for configuration to complete and then click Finish

http://www.itprotoday.com/sites/windowsitpro.com/files/uploads/2016/03/18/Screenshot%202017-02-11%2009.22.06.png

Step 8: Now it’s time to add actual windows installation images from CD or DVD for client machines. Click Finish

http://www.itprotoday.com/sites/windowsitpro.com/files/uploads/2016/03/18/Screenshot%202017-02-11%2009.22.49.png

Figure 18

Step 9:  Create an image group where you would like to place your installation images. Click Next (This can take several minutes to complete)

http://www.itprotoday.com/sites/windowsitpro.com/files/uploads/2016/03/18/Screenshot%202017-02-11%2009.23.59.png

Step 10: Wait so that images are copied to WDS server (This can take 10-15 minutes).  When done, click Finish

http://www.itprotoday.com/sites/windowsitpro.com/files/uploads/2016/03/18/Screenshot%202017-02-11%2009.24.31.png

Configuring WDS on Windows Server 2012 R2
When a WDS is installed on your Windows Server 2012 R2 machine, you need to configure it.  These steps will further help you in the configuration of WDS including copying windows installation images from CD or DVD for client machines.

1. Open server manager. Click Tools -> Windows Deployment Services

http://www.itprotoday.com/sites/windowsitpro.com/files/uploads/2016/03/18/Screenshot%202017-02-11%2008.30.18.png

2. Expand Servers. Right-click your WDS server machine and then click “Configure Server”

http://www.itprotoday.com/sites/windowsitpro.com/files/uploads/2016/03/18/Screenshot%202017-02-11%2008.30.46.png

3. Choose “Standalone server” since our machine is not a member of Active Directory Domain Services. Click Next

http://www.itprotoday.com/sites/windowsitpro.com/files/uploads/2016/03/18/Screenshot%202017-02-11%2009.19.32.png

4. Click Next

http://www.itprotoday.com/sites/windowsitpro.com/files/uploads/2016/03/18/Screenshot%202017-02-11%2009.20.13.png

5. Choose the folder (Make sure the folder is created on NTFS partition and the partition should not be system partition) on your machine where you would like to place installation images, PXE boot files, and WDS management tools. Click Next

http://www.itprotoday.com/sites/windowsitpro.com/files/uploads/2016/03/18/Screenshot%202017-02-11%2009.20.46.png

6. Choose “Respond to all client computers (known and unknown)” and click Next. (If you have an active directory in your network, choose to respond only to known client computers and pre-stage client machines using their GUID or mac addresses).

http://www.itprotoday.com/sites/windowsitpro.com/files/uploads/2016/03/18/Screenshot%202017-02-11%2009.21.23.png

Step 7: Wait for configuration to complete and then click Finish

http://www.itprotoday.com/sites/windowsitpro.com/files/uploads/2016/03/18/Screenshot%202017-02-11%2009.22.06.png

Step 8: Now it’s time to add actual windows installation images from CD or DVD for client machines. Click Finish

http://www.itprotoday.com/sites/windowsitpro.com/files/uploads/2016/03/18/Screenshot%202017-02-11%2009.22.49.png

Figure 18

Step 9:  Create an image group where you would like to place your installation images. Click Next (This can take several minutes to complete)

http://www.itprotoday.com/sites/windowsitpro.com/files/uploads/2016/03/18/Screenshot%202017-02-11%2009.23.59.png

Step 10: Wait so that images are copied to WDS server (This can take 10-15 minutes).  When done, click Finish

http://www.itprotoday.com/sites/windowsitpro.com/files/uploads/2016/03/18/Screenshot%202017-02-11%2009.24.31.png

3.WDS adding Images Wim and Boot. #

Add Image To Windows Deployment Services.

We need to add tow types of images in WDS, install.wim and boot.wim. Then install.wimimages are the operating system images that you deploy to the client computer. You can also use the Install.wim file from the installation media (in the \Sources folder of Windows DVD), or you can create your own custom images.

To boot you system through network card, you must add the boot.wim image of the latest Windows Operating System. The Boot.wim images are Windows PE images that you boot a client computer to perform an operating system installation. In most scenarios. Boot.wim image is also located in the Sources folder of Windows DVD.

While you are logon as domain admin or member of administrators group  to WDS Server, go to Server Manage and open Windows deployment services from Tools tab of Server Manger Dashboard.

Add Install Image - Windows Deployment Services

Add Install Image – Windows Deployment Services

Expend the Servers then right click the Install Images  and click Add Install Image.

Create and Image Group for WDS

Create and Image Group for WDS

On the Add Image Wizard page type the name of a group and click Next.

Windows 10 Install Image - Technig

Windows 10 Install Image

On the Image Files page click Browse and select the install.wim image from Windows sources folder and click Open and then click Next. 

Windows Deployment Services Available Images

Windows Deployment Services Available Images

On the Available Images pages select Windows edition, whatever you want and click Next. Here we only have Windows 10 technical preview for enterprise.

Windows Deployment Services Summery Page

Windows Deployment Services Summery page

It will take a few minutes to check the integrity of image’s and adding image. When the image added successfully, just click Finish and see the Clients group that has the image ready for deploying to clients machines.

Deploy Windows 10 with Windows Deployment Services

Deploy Windows 10 with Windows Deployment Services

That is it. You can add as much as Image you want. But now try to add the Boot.wim image the same as Install image. But instead of install.wim image select boot.wim image.

Add Boot Image to boot Clients Machines

Add Boot Image to boot Clients Machines

Now you can deploy and install Windows 10 for your network clients. The next part we will install client operating system through network using WDS.

4.Installing a client with WDS #

Testing the Configuration

We need only single client machine that supports network-based installation of operating system to test this whole configuration.

1. Make sure to change the boot order from BIOS (If you are using physical machine). I am using virtual machine in Hyper-V

http://www.itprotoday.com/sites/windowsitpro.com/files/uploads/2016/03/18/Screenshot%202017-02-11%2009.29.43.png

2. When you boot the machine and it gets an IP lease and WDS information, you can assume your DHCP is working       

http://www.itprotoday.com/sites/windowsitpro.com/files/uploads/2016/03/18/Screenshot%202017-02-11%2009.30.22.png

3. Press F12. Follow the wizard and start the operating system installation as you normally do.

 

5.Indroduction MDT and WDS #

MDT and WDS working together

MDT and WDS Diagram MDT with WDS Diagram Overview

MDT vs WDS

To understand how MDT and WDS work to complement each other it helps to first understand the differences between these two systems.

WDS

Windows Deployment Services (WDS) is a server based technology used for deploying images of Windows operating systems and operates as a server role in Windows Server 2003 SP2, Server 2008, Server 2008R2, Server 2012, and Server 2012R2.  WDS utilizes disk imaging and can perform network based installations of captured images which are typically stored in a .wim format.  Image deployment over the network is accomplished through WDS’s use of the Preboot Execution Environment (PXE) to load a miniature version of Windows known as Windows Preinstallation Environment (PE).

WDS supports the management and deployment of driver packages which allows you to manage a variety of devices and architectures within your environment.  However, it does not support the ability to deploy software or configuration changes during the deployment process.  This necessitates the use of thick images which contain all software, configurations, settings, and updates pre-configured and set in your master image before being captured and deployed.

When operating as the primary deployment solution WDS functions as both a storage repository for the PXE network boot images as well as a repository for the actual operating system images to be installed on the target computer.

MDT

The Microsoft Deployment Toolkit (MDT) is a “solution accelerator” used for designing and creating operating system and application deployment.  It is typically used in concert with the Windows Automated Installation Kit (WAIK) to produce highly customized and automated deployment solutions.

MDT supports a wide variety of deployment methodologies: Zero Touch Installation (ZTI) (Requires integrations with SCCM), Lite Touch Installation (LTI), and User Driven Installation (UDI).  Each of these can be combined with either a thin image deployment or thick image deployment resulting in six available deployment scenarios.

MDT is a task based deployment process that offers unparalleled control over every step of the deployment:

  • Complete management of device drivers – identify the model during deployment and inject only the necessary drivers for that model
  • Run custom scripts
  • Install software
  • Dynamically keep images up to date by adding Windows updates

Due to the dynamic nature that MDT provides it permits the use of a small, clean, thin base image that can be added to during the deployment process based on criteria  you identify ahead of time.  Additionally, because software and settings are added during the active deployment process the need for multiple specialty images is reduced.  You can deploy the same base image to two different areas and through the use of varied task sequences deploy a completely varied set of software packages and settings.

Simplified, WDS can capture thick images of your reference device and deploy that thick image with driver support to various devices within your environment using PXE.  MDT is more of a design tool for creating a highly custom step-by-step deployment sequence.

MDT with WDS

It’s important to note that MDT in and of itself doesn’t have a true deployment system.  You can create a Lite Touch Deployment USB drive with MDT and visit each device independently, but for true deployment capability MDT works best in concert with WDS.  Some people ask the question: WDS is already a complete and standalone OS deployment solution, why not just use it for deployment needs?  The answer is simply customization capabilities.  MDT offers unparalleled customization options during deployment.  We are also moving away from thick images.  Thin images offer numerous advantages to the imaging building process and lifecycle.  So, a combination of MDT’s customization and WDS’s PXE deployment capabilities results in an ideal deployment solution.

MDT and WDS deployment process

To give you some insight into how the two technologies work together I have created the diagram above.

The process begins with the deployment workbench which can be a server or client device typically loaded with the Microsoft Deployment Toolkit (MDT) and the Windows Automated Installation Kit (Windows AIK).  In older versions of the MDT two were required to successfully configure both 64-bit and 32-bit answer files.  Modern versions of the MDT support both 32-bit and 64-bit answer file configuration.  The deployment workbench will be were you setup, configure, and customize the settings on the deployment share. (The deployment share is a storage location located on your network capable of sharing files with devices you wish to deploy to).

Once MDT is setup and configured properly you will go through a finalization process of updating the deployment share.  During this process you will generate boot images.  Dependent on your setup these boot images will be 32-bit and/or 64-bit WinPE boot images that contain the necessary information to access the MDT deployment share.  They will typically contain LAN drivers for the devices in your environment but may also include storage drivers as well.  Once created these boot images will reside on the MDT Deployment share in the following location: \\MDT_Deployment_Share\Share_Location\WDS\Boot.  These boot images can be used to make a deployment CD, deployment USB, or imported into WDS to implement true PXE booting capabilities.

MDT and WDS process flow

The MDT/WDS diagram illustrates the use of the two technologies in a Lite-Touch deployment scenario.  For the purposes of this explanation the WDS server exists as a separate server and is not integrated with the DHCP server.

  1. Client/Server is powered on by tech/admin and F12 PXE boot is initiated.
  2. IP address is supplied by the DHCP server to the client
  3. Client broadcasts a PXE boot request
  4. IP Helper Forwards the PXE broadcast to the WDS server
  5. WDS presents boot image options – tech/admin selects appropriate Lite-Touch boot image – image is sent down to device
  6. The WinPE boot image requests deployment information from the MDT Deployment Share
  7. Tech/Admin utilizes the MDT Task Sequence selection menu and initiates deployment from the MDT Deployment Share for the desired OS

MDT is the star of the show

It’s worth noting that while WDS adds spectacular functionality with PXE booting, MDT is doing the real heavy lifting here.  As soon as the WinPE boot image is downloaded, it immediately accesses the MDT Deployment Share and the remainder of the operation (over 90% – maybe more) is handled via the MDT Deployment Share.  From a bandwidth and performance standpoint, this means that your MDT share should be a lot more powerful than your WDS server.

6.Installing toolkits #

This is how to easily install ADK and MDT in Windows Server 2016 for Windows Deployment. The current version of Microsoft Deployment Toolkit is MDT 2013 update 1. MDT is a solution accelerator for operating system and application deployment. MDT supports deployment client operating systems and server operating system. In this post, we are going to show you how to install and configure MDT and ADK for Windows 10 in Windows Server 2016 which work the same as Windows Server 2012 R2.

The method’s of installation and configuration of all Microsoft Deployment Tool kits are the same. So don’t worry, just download the MDT required components ADK for Windows 10 or for older Windows and start installing.

Download and Install ADK and MDT

The first kit we need to download is the Windows ADK for Windows 10. The second one is the latest update of Microsoft deployment tool kit. Download Microsoft deployment tool kit update 1 files from Microsoft website. Always try to download the latest version of MDT.

  1. Let’s download all components of Windows ADK for Windows 10 and then install it.

Download Windows Assessment and Deployment Kit for Windows 10 Download Windows Assessment and Deployment Kit for Windows 10

2. Select the Download the Windows Assessment and Deployment Kit – Windows 10 for installation on a separate computer and Browns to specify the path then click Next.

Windows Kits Privacy Windows Kits Privacy

3. It’s a test lab so select No and click Next. On the license terms and agreement page click Accept to accept the Windows Kits privacy.

4. It almost 3 and half GB in size. When the download compete successfully, move or copy files to Windows Server 2016 then run the adksetup file to install it.

Windows ADK Downloaded Files Windows ADK Downloaded Files

5. Specify a location or click Next to select the default location. Then on the Windows Kits privacy page select No and on license terms and agreement page Accept.

Specify Location for Windows ADK Specify Location for Windows ADK

6. Now select the features you want to install. Don’t select unnecessary features. Click Next to install it.

Windows Assessment and Deployment Kit Features Windows Assessment and Deployment Kit Features

7. It will take a few minutes to complete. When it finish close the page.

Welcome to the Windows Assessment and Deployment Kit Welcome to the Windows Assessment and Deployment Kit

Now the Windows ADK for Windows 10 is installed successfully in Windows Server 2016. The next step is to install Microsoft Deployment tool kit.

Run the downloaded Microsoft deployment tool kit setup file and click Next.

Welcome to Microsoft Deployment Tool Kit Welcome to Microsoft Deployment Tool Kit

2. Select I accept the terms in the license agreement and click Next.

MDT End User License Agreement MDT End User License Agreement

3. Click Next and do nothings in this page because we need tools and documents.

Documents - Tools and Templates Documents – Tools and Templates

4. For testing lab select I don’t want to join the program at this time and click Next.

Customer Experience Improvement Program Customer Experience Improvement Program

5. Click Install to start the installation. Let the installation will be finish. Finally click Finish to close the page.

Ready to Install Microsoft Deployment Toolkit Ready to Install Microsoft Deployment Toolkit

Yes that’s it. The Microsoft deployment tool kit also installed successfully. If you faced with some errors or problems during the installation, try to search the title on google or comment us through this post.

6. Now go to Windows Server 2016 start menu and run the Deployment Workbench.

Windows Server 2016 Start Menu Windows Server 2016 Start Menu

Here is the Windows deployment Workbench. It is ready for Windows Deployment and Application Deployment.

Windows Deployment Workbench - Install ADK and MDT Windows Deployment Workbench – Install ADK and MDT

Now the Microsoft Deployment Toolkit is ready for configuration and deploying new operating system and Applications.

It’s time to configure the MDT and start deploying Windows 10 with MDT.  So that’s all you need to install ADK and MDT for your Windows Deployment Server in Windows Server.

7.Configure MDT and Deploy #

In this topic

  • Step 1: Configure Active Directory permissions
  • Step 2: Set up the MDT production deployment share
  • Step 3: Add a custom image
  • Step 4: Add an application
  • Step 5: Prepare the drivers repository
  • Step 6: Create the deployment task sequence
  • Step 7: Configure the MDT production deployment share
  • Step 8: Deploy the Windows client image
  • Use offline media to deploy Windows or WDS
  • Unified Extensible Firmware Interface (UEFI)-based deployments

Configure Active Directory permissions

These steps will show you how to configure an Active Directory account with the permissions required to deploy a Windows 8.1 machine to the domain using MDT 2013. These steps assume you have downloaded the sample Set-OUPermissions.ps1 script and copied it to C:\Setup\Scripts on DC01. The account is used for Windows Preinstallation Environment (Windows PE) to connect to MDT01.In order for MDT 2013 to join machines into the contoso.com domain you need to create an account and configure permissions in Active Directory.

  1. On DC, using Active Directory User and Computers, browse to yourdomain / domain / Service Accounts.
  2. Select the Service Accounts organizational unit (OU) and create the MDT_JD account using the following settings:

Name: MDT_JD

  • User logon name: MDT_JD
  • Password: P@ssw0rd
  • User must change password at next logon: Clear
  • User cannot change password: Select
  • Password never expires: Select
  1. In an elevated Windows PowerShell prompt (run as Administrator), run the following commands and press Enter after each command:

Copy

Set-ExecutionPolicy -ExecutionPolicy RemoteSigned –Force

Set-Location C:\Setup\Scripts

.\Set-OUPermissions.ps1 -Account MDT_JD

-TargetOU “OU=Workstations,OU=Computers,OU=Contoso”

  1. The Set-OUPermissions.ps1 script allows the MDT_JD user account permissions to manage computer accounts in the Contoso / Computers OU. Below you find a list of the permissions being granted:
    1. Scope: This object and all descendant objects
  • Create Computer objects
  • Delete Computer objects
  • Scope: Descendant Computer objects
  • Read All Properties
  • Write All Properties
  • Read Permissions
  • Modify Permissions
  • Change Password
  • Reset Password
  • Validated write to DNS host name
  • Validated write to service principal name
  • Create a New MDT Deployment Share

I know you are ready after reading and doing the tasks of the first part, and now continue the step by step guide to MDT. When you are ready to deploy Windows 10 using MDT  in testing lab or production environment, you will first create a new MDT deployment share. Let’s do it step by step.

  1. Open the Deployment Workbench from Microsoft deployment toolkit in Windows server 2016 start menu. Then right click Deployment Share and click New Deployment share.

Create a New Deployment Share Create a New Deployment Share

2. Select the deployment share path, where you want to keep operating system files, applications, drivers and scripts then click Next.

Deployment Share Path Deployment Share Path

Don’t store the MDT deployment share files in system drive in a production environment.

3. For the Share page specify a short and meaningful share name to access it easy and quickly through network then click Next. I have named DepShare. The complete UNC path is \\DC16\Depshare$.

Deployment Share Name

Deployment Share Name

4. On the Descriptive Name page, leave the default MDT Deployment Share or rename it to whatever you want and click Next.

Deployment Descriptive Name

Deployment Descriptive Name

5. On the Options page, select the customize-able options when performing deployment and click Next.

New Deployment Share Options

New Deployment Share Options

6. Read the Summery page and click Next to create the new deployment share.

7. Finally the progress should be done without errors. Otherwise you need to troubleshot the errors. Click Finish on Confirmation page to close the page.

Final and Confirmation Final and Confirmation

The New Deployment share has been created successfully. Now try to add Windows images to deploy Windows 10 using MDT.

Step 2. Import Operating System to MDT

the second step is importing operating system to MDT. Put Windows 10 disc to DVD Rom or mount the Windows 10 Image within Hyper-v virtual machine.

  1. Open MDT Deployment Workbench and expend MDT Deployment Share. Now right click on Operating system and create a New Folder. Specify a name and click Next then click Finishto create the new Windows 10 folder.
  2. Now right click the Windows 10 folder and click Import Operating System.

Deploy Windows 10 using MDT Deploy Windows 10 using MDT

3. Select Full set of sources files on OS Type page and click Next. You can select a customized Windows image or connect to Windows Deployment Services images also.

Operating System Type for MDT Operating System Type for MDT

4. Select the DVD drive and click Next. You can select Windows files from a folder and easy move it with selecting the Move option. So anyway…

Windows 10 Sources

Windows 10 Sources

5. On the Destination page, type a name for the directory where MDT create it for Windows files. When you specified a name click Next.

Destination Directory of Windows 10

Destination Directory of Windows 10

6. On the Summery page read the details and click Next. It will takes a few minutes to import the Windows 10 files to Operating System folder’s of MDT.

7. On the Confirmation page, the Windows 10 should be imported without any errors. If you have faced with any error try to troubleshot it by searching google or comment us the error titles.

Import Operating System Confirmation

Import Operating System Confirmation

Click Finish to close the page and go to step 3, add some application to MDT.

 Deploy Applications using MDT

When you configure your MDT deployment share, you will also add any applications to the new deployment share before creating your task sequence. This section walks you through the process of adding an application to the MDT deployment share using Microsoft Office 2013.

  1. On the Deployment Workbench, Deployment Share, right click Applications and create a New Folder for Microsoft Office 2013.
  2. On the Applications Type page select Application with source files then click Next. Before doing this task you should put the Microsoft Office 2013 to DVD Rom or insert it to Hyper-v virtual machine.

Deploying Applicaitons Using MDT

Deploying Applicaitons Using MDT

3. Write the application details and click Next. Try to fill out the application form with correct software information.

Application details Application details

4. Specify the the source directory of application and click Next. The drive D: is the DVD drive of Office 2013.

Application directory

Application directory

5. On the application Destination page click Next. Leave it with default name or changed it with a related name to the application.

Application Destination

Application Destination

6. On the Command Details page, just type the exact setup name of application setup file with executable extension and click Next.

Application Command Details

Application Command Details

7. On the application Summary page, read the details and click Next to import it.

Application Summery Page

Application Summary Page

8. The importing process should be done successfully with any error. If it issue error? Try different software or fix the problems.

Application Confirmation

Application Confirmation

Finally click Finish to close the page. Now the office has been imported and Windows 10 is also. So the next step will be creating Task sequences.

4. Create a New Task Sequence in MDT

In this section we will explaining you how to create the task sequence used to deploy Windows 10 using MDT.

  1. So right click the Task Sequence and click New Task Sequence. It is better to create a folder for your task sequences.
  2. On the General Settings page type the task sequence id, task sequence name and comments then click Next.

Task Sequence General Settings

Task Sequence General Settings

3. Select the Standard Client Task Sequence from Template page and click Next.

Nov 28, 2017

Standard Client Task Sequence

Standard Client Task Sequence

4. On the Select OS page select the Windows 10 image and click Next. This is the Windows 10 image which previously we had imported from Operating System.

Select Operating System for Task Sequence

Select Operating System for Task Sequence

5. Select Do not specify a product key at this time on Specify Product Key page if you don’t have a product key then click Next.

Windows 10 Product Keys

Windows 10 Product Keys

6. Type to OS settings like name, organization and internet explorer default home page url and click Next.

OS Settings

OS Settings

7. Enter the admin password on the Admin Password page and click Next. This password will be use as administrator user account password. You can set the blank password by selecting Do not specify and Administrator password at this time option. But for security reason you should set a password for local admin.

Windows 10 Admin Password

Windows 10 Admin Password

8. On the Summary page, read the details and click Next to complete the task sequence. Finally click Finish on the Confirmation page to close the window.

Task Sequence Confirmation

Task Sequence Confirmation

Now everything are done and the it is ready to create PE image by updating the deployment share.

5. Update Deployment Share to Create Boot-able PE image

The final steps before deploying Windows 10 using MDT is to update the Deployment Share. This section is going to create Boot-able PE media to boot the client systems in order to deploy Windows 10 using MDT.

  1. So on the Deployment Workbench right click MDT Deployment Share and click Update Deployment Share.
  2. On the Options page select Optimize the boot image updating process and click Next.

Update Deployment Share

Update Deployment Share

2. On the Summary page click Next to apply the update to MDT deployment share. It will take a few minutes, because it will create PE image and preparing the MDT for Windows deployment.

3. Finally the Update Deployment Share will be accomplish successfully. Click Finish to close the update deployment share page.

Update Deployment Share Confirmation

Update Deployment Share Confirmation

Good news, till now everything is going on perfectly and I’m very happy of creating and sharing this long step by step article with you. So hope you would find it helpful.

4. Go to Boot folder in Deployment share directory on E: drive and copy or move the Lite Touch PE to network location or somewhere else.

Light Touch PE Disc

Lite Touch PE Disc

Later we will use the Lite Touch image to boot the new computer and deploy Windows 10 using MDT by the help of this PE image.

Step 6. How to Deploy Windows 10 Using MDT?

Now the deployment server is ready to deploy Windows 10 using MDT and deploy applications. Try to boot a new system where you want to install new operating system.

Here I’m going to test on a new virtual machine by creating new virtual machine in Hyper-v. So you can do both hyper-v or a physical machine.

  1. Boot the new system with Lite Touch PE image. You can boot the physical computer with USB Boot-able or boot through Network.

2. On the Microsoft Deployment Toolkit Wizard page click Run the deployment Wizard to install ad new Operating System.

Run the Deployment Wizard to New Virtual Machine

Run the Deployment Wizard to New Virtual Machine

2. Specify the network address of MDT Deployment Shared folder and click Next then type user, password and domain name.

Remember; the user you enter must have full shared permission and modify NTFS permission to MDT deploymentShare folder on drive E. Otherwise it will not work.

Deployment Share Credentials

Deployment Share Credentials

3. Select the Windows 10 on Task Sequence page and click Next to execute to your new computer.

Task Sequence - Deploy Windows 10 Using MDT

Task Sequence – Deploy Windows 10 Using MDT

4. Type the computer details such as name and join to domain if you want to join it. In this section if you select Join to Workgroup, you will be able to capture an image also. But it’s not related to Windows 10 deployment using MDT. So we will discuss about creating a reference computer and capture image in a separate topic.

Computer Details for Windows 10 Deployment

Computer Details for Windows 10 Deployment

5. On the Move Data and Settings page, select Do not move user data and settings and click Nextto continue.

Move Data and Settings

Move Data and Settings

6. Select Do not restore user data and settings on User Data Restore page and click Next.

7. Enter the Windows product key or select No product key is required and click Next.

Windows Product Key - Deploy Windows 10 Using MDT

Windows Product Key – Deploy Windows 10 Using MDT

8. Select Windows local and time and click Next. Select the correct time zone and language.

Windows 10 Local and Time

Windows 10 Local and Time

9. On the Application page select the applications you want to deploy on this machine at this time and go to the Next page.

Application Deployment using MDT

Application Deployment using MDT

10. Enter the local Administrator password twice and go to Next page.

Local Administrator Password

Local Administrator Password

11. Check everything should be ready to begin on Ready page and click Begin to start deploying Windows 10 using with MDT.

Ready to begin deploy Windows 10 using MDT

Ready to begin deploy Windows 10 using MDT

It will deploy and take too much time. Go to do your other jobs at this time and come back when the deployment task is finished.

12. After finishing deploying Windows, the system will restart and ask to you deploy software. In this section simply accept the terms and agreement of Office 2013 and click continue then click Install Now to begin the installation.

Deploying Office 2013 Using MDT Deploying Office 2013 Using MDT

13. When the Office 2013 installation has finished close all pages and once restart your computer to see the result.

The Final result of Deploy Windows 10 using MDT

The Final result of Deploy Windows 10 using MDT

It’s good to deploy Windows 10 using MDT in order to create master image and then deploy it to other machines. Directly deploying with this method is a time consumer process and is not a good practice for Windows and Application deployment.

Conclusion

The MDT is a perfect toolkit to deploy software and operating system or creating a master image from a reference computer. To get more from MDT for lite touch level, you must combine MDT with WDS to create a flexible Deployment environment and using consistently in your network.

I hope it will help you to create your own deployment lab for your production environment with Windows Deployment Toolkit and can simply deploy Windows 10 using MDT or Windows Deployment Services. If you have any question, feel free to ask you question about Windows and Application deployment.

Help Guide Powered by Documentor
Suggest Edit