TECHNIG
Gateway for IT Experts and Tech Geeks

How to Deploy Windows 10 Using MDT in Windows Server 2016?

Deploy Windows 10 Using MDT and WDS, Create an MDT Task Sequence and Configure WDS

This is the second part of Microsoft deployment toolkit article to deploy Windows 10 using MDT. To simply understand the tasks in this article, you need to read the first part “How to Install ADK and MDT in Windows Server 2016?“. Also as a network admin, you should already know about Microsoft Deployment toolkits and Windows deployment. So I assume you have read the first part of deploy Windows 10 using MDT which talk about installing ADK and MDT in Windows Server 2016.

For this Windows deployment lab, I’m using Hyper-v, Windows Server 2016, and Windows 10 to deploy Windows 10 using MDT. The MDT is installed on Windows Server beside Active directory and DHCP Server. You can install MDT separately on a Windows client or Server.

Step 1. 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 a 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 specifies a short and meaningful share name to access it easily and quickly through the 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 Summary page and click Next to create the new deployment share.

7. Finally, the progress should be done without errors. Otherwise, you need to troubleshoot the errors. Click Finish on the 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 Finish to 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 a 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 easily 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 Summary page read the details and click Next. It will take a few minutes to import the Windows 10 files to Operating System folder 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 troubleshoot 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.

Step 3. 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 Application 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 source directory of the 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 issues an 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.

Step 4. Create a New Task Sequence in MDT

In this section, we will explain to 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.

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 homepage 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 used as administrator user account password. You can set the blank password by selecting Do not specify an 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 is done and it is ready to create PE image by updating the deployment share.

Step 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 prepare the MDT for Windows deployment.

3. Finally, the Update Deployment Share will be accomplished 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 with 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 a 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 with 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 the new operating system.

Here I’m going to test on a new virtual machine by creating a 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 deployment share 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 a 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 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 Next to 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 the Ready page and click Begin to start deploying Windows 10 using with MDT.

Ready to begin deploy Windows 10 using MDT
Ready to begin deploying 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 the master image and then deploy it to other machines. Directly deploying with this method is a time-consuming 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 your question about Windows and Application Deployment.


Related Search Queries:

Deploy Windows 10 using MDT and WDS
Deploy Windows 10 using MDT and WDS
MDT download
Sysprep and capture windows 10
How to deploy Windows 10 image over the network
Capture windows 10 image MDT
Deploy windows 10 WDS
Windows 10 ADK

 

10 Comments
  1. Faiz Orz says

    This works great, thanks for your step by step guide for MDT.

    1. Shais says

      Thanks for appreciation dear Faiz

      This was took me a whole night to write and published. So I hope it would be helpful for beginners who are new in Windows deployment with Microsoft deployment toolkit.

  2. karar says

    hello sir, I am glad and thankful of you for making this article but one question I have is that while we deploy windows 10 with mdt at when we specify the network path of file then we enter our username password, it gives us error that that (Invalid credentials: The network path was not found) how can I solve it?

    1. Shais says

      Your welcome dear Karar
      The error Invalid credentials is issued when you don’t enter the correct user and password. But for path was not found error, you should specify the correct path.
      For instance if you have a share folder (DeploymentShare) on you DC computer, must set the network address \\dc\deploymentshare$.

      Remember: you computers must be at the same network when you are using a virtual Lab such as VMWare or Hyper-v.
      Assign IP address for computers manually or using DHCP server.

  3. karar says

    Thanks for your assist, I found some problems and solved it, the problems were with DHCP authorize, no ip address and restart.My problem was solved and I am thankful hope to get new articles soon aswel.

  4. Hussein says

    I was searching for the MDT tutorial on the web many days. Thank you.

  5. Will says

    Sorry for being an idiot! This is new and a learning curve for me.
    I have followed the instructions above but how do I get a laptop to boot to the lite touch pe on our network?

    I am not sure what network location you exactly mean?

    Thanks

    1. Shais says

      Hi Will,

      Use a Bootable USB or write the Lite touch image to a DVD then boot the Laptop with.

  6. aravind says

    Thanks for the post It was very helpful

    . After the deployment when the system restarts Its stuck at ctrl+alt+del screen, It wont auto login.

    Regards

  7. Joe says

    Hi, I am all the way to booting the Lite Touch image. However, it is stuck on the Windows logo – I am using VirtualBox VM as the machine.

    Can you please tell me what I am doing wrong?

    Thanks

Leave A Reply

Your email address will not be published.