Share this page : facebooktwitterlinkedinmailfacebooktwitterlinkedinmail

Before get touching with MDT, you should know how does WDS works, because MDT must work together with WDS. See this article here: frankfu.click/microsoft/windows-2012/deploying-windows-services.html

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.

Following image illustrate how do they work together:

 

Note that the specific version of the software (MDT, ADK, Windows) must match with each other.

Example:

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:

MDT-1026

Change the deployment share name or leave defaults and click Next:

MDT-1027

Change the deployment share description or leave defaults and click Next:

MDT-1028

Review and uncheck each of the default options and click Next:

MDT-1029

Review and click Next:

MDT-1030

Click Finish:

MDT-1031

Open Computer Management. Expand Local Users and Groups and right click Users to select New User:

MDT-1039

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):

MDT-1040

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:

MDT-1041

Click Permissions:

MDT-1042

Note Everyone is added by default with Full Control (security is controlled by NTFS permissions on the folder):

MDT-1043

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:

MDT-1044

Back in the Deployment Workbench, right click the new deployment share and select Properties:

MDT-1033

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=255
TimeZoneName=A.U.S. Eastern 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:

MDT-1034

Under the [Default] section, drop the following block of options:

UserID=MDT
UserDomain=WS12R2MDT01
[email protected]
KeyboardLocale=en-US
SkipBDDWelcome=YES

Close the Notepad document and you will be prompted to save changes:

MDT-1035

Click Save:

MDT-1036

Click Apply to save changes to CustomSettings.ini for the deployment share:

MDT-1037

Click OK:

MDT-1038

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:

MDT-1045

The next drive letter available for my MDT server was E:\ so the installation media is now mounted using that drive:

MDT-1046

In the Deployment Workbench, right click Operating System and select Import Operating System:

MDT-1047

Select Full set of source files and click Next:

MDT-1048

Type E:\ to use the recently mounted ISO. Click Next:

MDT-1049

Enter a destination directory name (I typically just clean up the default name that was detected). Click Next:

MDT-1050

Click Next:

MDT-1051

Upon completion (typically a couple minutes) click Finish:

MDT-1052

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:

MDT-1053

I’ll select Completely delete and click Next:

MDT-1054

Click Next:

MDT-1055

Click Finish:

MDT-1056

Next, I’ll rename to clean up the WIM file name to “Windows Server 2012 R2 Datacenter.wim”:

MDT-1057

Right click Task Sequence and select New Task Sequence:

MDT-1058

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:

MDT-1059

Select Standard Server Task Sequence from the drop-down and click Next:

MDT-1060

Select the Operating System from the list and click Next:

MDT-1061

Your choice to enter a product key, or do this later. Click Next:

MDT-1062

Enter a name, organization, and home page. Click Next:

MDT-1063

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:

MDT-1065

Click Next:

MDT-1066

Click Finish:

MDT-1067

Next, we’ll modify the task sequence to enable Windows Updates. Right click the new task sequence and select Properties:

MDT-1068

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:

MDT-1069

Uncheck Disable this step to enable the step.

MDT-1070

Repeat for the second Windows Update entry:

MDT-1071

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:

MDT-1072

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:

  1. Right Click on the Deployment share and select properties
  2. Click the Windows PE x86 Settings Tab (Or 64 Bit tab depending on what you are changing)
  3. Under Windows PE Customizations, you should see a Custom background bitmap file box. Browse to your image (C:\Program Files\Microsoft Deployment Toolkit\Samples\Background.bmp) you want to use
  4. Hit Apply and then OK

MDT-1073

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:

Time zone and time zone name: https://blog.brankovucinec.com/2014/10/20/microsoft-time-zone-index-values/

 

 

 

Applications deployment