MDT 2013 (Microsoft Deployment Toolkit 2013) is a fantastic tool for customizing Operating System Deployments and best of all, it’s FREE!
Regardless of your situation, if you’re using Windows at home or at the office you might be able to get a lot of value out of this tool. My first look at it was while studying for my Windows 7 MCSA. What I liked is it brought together a lot of the tools discussed in the study material like WinPE, diskpart, DISM and USMT.
In addition to this, if you are using SCCM in your environment and wish to familiarize yourself with SCCM OSD, there is NO better place to start. In, fact, the Deployment Workbench provided with MDT is almost identical to the Software Library Workspace in SCCM 2012. The only thing you won’t find in MDT is the Software Updates features.
You can download MDT 2013 from here: https://www.microsoft.com/en-us/download/details.aspx?id=40796
But it’s also worth checking the following link just to ensure there hasn’t been a new version of MDT released since this article was posted: http://technet.microsoft.com/en-us/windows/dn475741.aspx
I won’t go through the installation steps for MDT 2013 as it’s pretty straight-forward. MDT 2013 should be installed on your “Tech Computer” or even a server if you desire. Just keep in mind, you will need to create what is called a Deployment Share which will house everything you use for your Operating System deployments: OS Images, Applications, Driver Packages etc. Depending on how far down the rabbit hole you go, this share can grow very large, very quickly.
After MDT is installed, the rest of the Process can be broken down to a few basic steps:
- Install Components
- Create a Deployment Share
- Import your OS Image
- Create and edit a task sequence
- Boot the Task Sequence Media and Deploy the OS
Once you have installed MDT, you’ll want to open the Deployment Workbench. Initially this will be pretty empty because there’s a few components we need to download for MDT first. On the left-hand side of the workbench you’ll find a folder called Information Center. Open this folder and click on Components. At the very least, you’ll need to download the Windows Assessment and Deployment ToolKit (Windows ADK) as this contains the latest (at the time of writing) release version of WinPE. Highlight it and click Download in the lower right of the workbench. For some reason, ADK will not show up as “Installed” like MSXML 6.0 but fear not, it should be there. You may also want to download USMT, even if you’re not planning on saving user states.
Create a Deployment Share
Now that the Deployment Workbench has all the components it needs, it’s time to create a new Deployment Share which as explained above, contains all the files used for our deployments.
Choose where to create your Deployment Share:
Set the name for your deployment share.
Note: If you wish to integrate with WDS the share MUST be named DS$.
You can give your network share a description if you want.
Pick the options you want available for your Lite Touch Deployment.
Complete the wizard and you’ll have your deployment share.
Importing OS Images
Now it’s time to import your OS image(s) you wish to deploy. Either load the install media onto your computer or extract the .iso files to somewhere that MDT can reach them. If you already have a custom WIM file or a WDS Image, you can import those here as well.
Chose the image/installer/media location.
Specify the destination directory, not extremely important but should be something that makes sense to you and is unique in your environment.
Click through to complete the wizard.
Create a Task Sequence
A task sequence can be used in many ways (OSD and even application deployment) as it’s primarily just a sequence of events that you want to complete; however, in this case we’re only using it for OSD.
In the Deployment Workbench, in your Deployment Share right-click on the Task Sequence folder and select New Task Sequence to begin the wizard.
Give your Task Sequence an ID (it can be anything unique), a Name and add comments if you wish.
You have several options for a template but in our case we just want the default, Standard Client Task Sequence.
Enter a product key if you have or need one.
Add your OS Settings next.
You should probably set a local Administrator password here.
Finish and close the wizard.
Edit the Task Sequence
If you have a custom WIM file you may not need to bother modifying anything here. But if you have some applications you want to deploy you can add them to your task sequence here.
If you are performing Driver installation you can add the driver packages to the task sequence here as well.
It’s a good idea to go through the task sequence steps and get familiar with the workflow.
Once your task sequence is ready, you’ll need to update your deployment share. If your changes are minor, you can just update the share. If you are having issues with something or have made a lot of changes, it’s a good idea to for a full regeneration:
Deploying the Operating System
Once the Deployment Share is updated, you’ll find the Lite Touch boot images in the Boot folder of your deployment share. That you can use to boot your target computer or VM.
Now just go through the wizard and fill in the fields. These options will vary depending on what you chose earlier when creating your Deployment Share.
Click begin and sit back and cross your fingers!