In this post we are going to be covering slides 10-14 from my presentation, the live installation and configuration demo. Let’s get started! For this demo, I will be using two systems, the first is my MDT 2013 server, running Windows Server 2012 R2. The second is my MDT client/target, to which I will be deploying Windows Server 2012 R2 from a volume license ISO. On the MDT server, I will start by downloading the Microsoft Assessment and Deployment Kit (ADK) for Windows 8.1 which can be found here:http://www.microsoft.com/en-us/download/details.aspx?id=39982.
Click Download:
Click Run:
I would always recommend downloading the ADK to a local folder or network share, since these files take a while to download and are commonly used in many Microsoft products, including System Center. Select a local or network path and click Next:
Click Next:
Accept the license agreement:
After many minutes (or even hours), the ~3GB files will finish downloading. When complete, re-launch the ADK setup wizard by executing adksetup.exe from the path specified earlier:
If the installation files are detected, the installer will simply prompt for an installation directory. Click Next:
Click Next:
Accept the license agreement:
Uncheck all features except Deployment Tools, Windows Preinstallation Environment (Windows PE), and User State Migration Tool (USMT). These are the only features required for the MDT Server. Click Install:
After a couple minutes, the installation will finish. Click Close:
Next, we’ll download the MDT 2013 install files from: http://www.microsoft.com/en-us/download/details.aspx?id=40796. Click Download:
Select all files and click Next:
Click Save for each file, putting the files in an MDT folder:
Once each of the five files have been downloaded, launch MicrosoftDeploymentToolkit2013_x64.msi:
Click Next:
Accept the license agreement and click Next:
Click Next:
Click Next:
Click Install:
Click Finish:
On Windows Server 2012 R2, click the Start menu:
As with many newly installed applications, you’ll find the app shortcuts are a bit buried in Windows Server 2012 R2 until you get used to it. From the Start interface, click the Down arrow in the bottom left for all programs:
A new Microsoft Deployment Toolkit section is created. Launch the Deployment Workbench (New):
The first time launched, you’ll see a nice overview of MDT 2013:
Right click Deployment Shares in the left navigation and select New Deployment Share:
Change the deployment share path or leave defaults and click Next:
Change the deployment share name or leave defaults and click Next:
Change the deployment share description or leave defaults and click Next:
Review and uncheck each of the default options and click Next:
Review and click Next:
Click Finish:
Open Computer Management. Expand Local Users and Groups and right click Users to select New User:
A local user account with rights to the MDT share will be very beneficial for deployments. Create a local user, set password never expires, and enter a password that can be safely stored in plain text without much risk (not a super secretive password):
By default the deployment share is created with Everyone Full Control permissions. To review, find the deployment folder, right click and go to the Sharing tab. Click Advanced Sharing:
Click Permissions:
Note Everyone is added by default with Full Control (security is controlled by NTFS permissions on the folder):
On the Security tab of the share, note that Users have Read & Execute, List Folder Contents, and ReadNTFS permissions. This is perfect for our newly created MDT user to access the share during deployments:
Back in the Deployment Workbench, right click the new deployment share and select Properties:
Under the Rules section, drop the following block of options at the end of the [Default] section:
SkipComputerName=YES
SkipDomainMembership=YES
SkipUserData=YES
SkipCapture=YES
DoCapture=NO
SkipLocaleSelection=YES
SkipTaskSequence=NO
SkipTimeZone=YES
SkipApplications=YES
SkipSummary=YES
SkipBDDWelcome=YES
TimeZone=004
TimeZoneName=Pacific Standard Time
After you’re fairly experienced with MDT, you can read up and review all of the CustomSettings.ini options in various documentation articles and blogs online. Once each option has been added, click Edit Bootstrap.iniin the bottom right:
Under the [Default] section, drop the following block of options:
UserID=MDT
UserDomain=WS12R2MDT01
UserPassword=P@ssw0rd01
KeyboardLocale=en-US
SkipBDDWelcome=YES
Close the Notepad document and you will be prompted to save changes:
Click Save:
Click Apply to save changes to CustomSettings.ini for the deployment share:
Click OK:
Next, we’ll import the Operating System images (WIM) for Windows Server 2012 R2. To do this, I will very handily double click to Mount the volume license ISO:
The next drive letter available for my MDT server was E:\ so the installation media is now mounted using that drive:
In the Deployment Workbench, right click Operating System and select Import Operating System:
Select Full set of source files and click Next:
Type E:\ to use the recently mounted ISO. Click Next:
Enter a destination directory name (I typically just clean up the default name that was detected). Click Next:
Click Next:
Upon completion (typically a couple minutes) click Finish:
Typically, I do some cleanup since I won’t need most of the WIM files imported. For now, I’ll delete the three WIM files and leave Server Datacenter. To do so, select each file, right click and select Delete:
I’ll select Completely delete and click Next:
Click Next:
Click Finish:
Next, I’ll rename to clean up the WIM file name to “Windows Server 2012 R2 Datacenter.wim”:
Right click Task Sequence and select New Task Sequence:
Enter DEPLOY-WS2012R2 for the Task sequence ID and a name to be selected using the deployment wizard, “Deploy Windows Server 2012 R2” for example. Click Next:
Select Standard Server Task Sequence from the drop-down and click Next:
Select the Operating System from the list and click Next:
Your choice to enter a product key, or do this later. Click Next:
Enter a name, organization, and home page. Click Next:
Enter a password that you don’t mind having stored in plain text as this is kept within the Unattend.xml file. The administrator password can always be changed post-deployment. Click Next:
Click Next:
Click Finish:
Next, we’ll modify the task sequence to enable Windows Updates. Right click the new task sequence and select Properties:
Under the State Restore section, there are two entries for Windows Update which are both disabled by default. Highlight each of these tasks and click the Options tab:
Uncheck Disable this step to enable the step.
Repeat for the second Windows Update entry:
Uncheck Disable this step and both tasks should now be enabled. This will come in hand later when we start slipping in applications to the task sequence. Click OK to save all changes to the task sequence:
Optionally (and highly recommended), the default Microsoft Solutions Accelerator background can be replaced by using an identically sized and bit depth BMP file in the following location: C:\Program Files\Microsoft Deployment Toolkit\Samples\Background.bmp:
Finally, let’s package everything up to create a LiteTouch ISO file for booting. In the Deployment Workbench, right click the deployment share and select Update Deployment Share:
Leave defaults and click Next:
Click Next:
Upon completion, click Finish:
Once the deployment share has been updated the first time, the LiteTouchPE_x64.iso files are created under the \Boot folder in the deployment share. These ISO files can be used to directly boot physical and virtual machines, or integrated into Windows Deployment Services for PXE booting to deploy MDT images.
For this blog post, I have attached the LiteTouchPE_x64.iso file to a new virtual machine. On first boot, the machine will boot from optical media and start the process:
Using the Bootstrap.ini and CustomSettings.ini options I provided, only a single question must be answered during deployment:
Optionally, two additional lines can be added to the Bootstrap.ini file to skip this screen and automatically deploy a task sequence of your choosing. These options are:
SkipTaskSequence=YES
TaskSequenceID=DEPLOY-WS2012R2
This can be very helpful when creating MDT Media, a topic that I will likely cover in a future blog post.
Upon completion, the wizard will indicate success of failure. Click Finish:
http://blog.itvce.com/2013/10/27/installing-and-configuring-microsoft-deployment-toolkit-mdt-2013-on-windows-server-2012-r2/
