MDT – Perform a stand-alone installation from media [Quick Guide]

6:08 pm January 30, 201715700

I. introduction

in response to the article by Florian “ MDT: create a key USB bootable LiteTouch ” and answer some questions about this deployment technique, I propose a little tutorial on the topic “ how to make installing MDT from stand-alone media (typically a USB) “. ”

The MDT (alias Microsoft Deployment Toolkit ) is a toolbox full of resources (or for some surprises).

Generally, the MDT is associated with deployment through the network and facilities. Sometimes, in the absence of a PXE server, we use a USB key (or a CD / ISO) to ensure the customer (LiteTouch) LTI boot sequence but resources are shared on a server.

In the case where the network becomes a constraint (bandwidth limited, stand-alone deployments in workshop or not), the MDT solution can still help, thanks to the use of the mode “MEDIA”.

II. implementation

I would not stay on the installation and configuration of base of a dot. In other words, I consider that departure model consists of:

  • system Windows 7 x 64 PRO with MDT2013 + ADK8.1up1
  • adding a Windows 7 x 64 PRO under “Operating Systems”

for this demonstration, we need the following 3 features selected in the ADK.

note: I did not choose the ADK10-1607 final “bcdedit” unexplained when generating the ISO image error.

A. preliminary

for this demonstration, we need to at least an operating system available in the MDT console:

B. statement of a sequence of tasks

select the topic “ Task Sequence ” then the menu “ Action…» “New Folder ” or the context menu.

Enter a name such as “ Deploy Media ” possible description for the new folder, and then click 2 times on “ Next ‘ then ‘ Finish “. ”

Select the new folder then the menu “ Action…» “New Task Sequence ” or the context menu.

Enter an ID and a description then click on ‘ Next

choose “ Standard Client Task Sequence ” in the drop-down list and then click on “ Next

select your operating system and then click on” Next “.”

Fill the following forms according to your needs, then click on “ Finish “. ”

I don’t will focus not on the many possible adjustments in the sequence of task, such as the injection of drivers by model, installing application… but you will quickly understand the interest to create subfolders in the MDT and the usefulness of the selection profiles.

Precision : Reminder, MDT records displayed in the MDT console are referenced in XML files (located under Control) and are not visible in the structure of the MDT shared resource files. (Where the importance of always perform your copy, move, rename, or further dismantling only within the console). This tree MDT essentially lets you define selection profiles, which you can check that records the desired elements containers.

C. Definition of a selection profile

this step becomes important as the dot contains a lot of elements such as different systems, applications, package, drivers, etc…

To view and/or report a selection profile, you must expand the console tree until ‘ Advanced configuration… ‘. “Selection profile

for the demonstration, we will create a specific profile to this type of deployment.

Select the topic “ Selection Profiles ” then the menu “ Action…» New Selection Profile “or the context menu.

Enter a name and a possible description for this new profile, then click on “ Next “. ”

For this example, we don’t have any applications, packages, or specific drivers, but you will understand that the use of subfolders in the different headings allows to adjust at best what to keep on the destination media.

Check the desired records, click 2 times on “ Next ” and then on “ Finish “. ”

D. statement by the LTI media

to the media statement, you must expand the console tree until ‘ Advanced configuration… ‘. «Media

select this topic “ Media ” then the menu “ Action…» “New Media ” or the context menu.

Enter a path (Media path), a possible description and select your previously created profile and click 2 times on “ Next “. ”

Note: Do not assign a path or network drive to the location of the media, at the risk of having an error message during the generation of the final ISO image.

Once the completed copy operation, click on ‘ Finish “.”

Select the new “ MEDIA001 ‘ which appears in the details window and then use the menu” Action…» Properties “.»

Tab ‘ General “, you still have to choose a few options, such that uncheck” Generate x 86 boot image ‘, useless in this example.»»» ”

We keep the last option “ Generate a Lite Touch bootable ISO image ” in order to have a media can be used within a virtual machine.

The tab “ Rules “, you will find the now famous “ CustomSettings.ini ” and the file “ Bootstrap.ini “.»»» ”

The content is variable depending on your preferences and the adjustments made. For this demonstration, I propose adding the following under the [Default] section, to automate the different screens of the deployment wizard.

These choices remain of course at your discretion. Simply add a semicolon at the beginning of line to ignore it.


 [Settings] Priority = Default Properties = MyCustomProperty [Default] OSInstall = Y SkipCapture = YES SkipAdminPassword = YES SkipProductKey = YES SkipPackageDisplay = YES SkipBDDWelcome = YES SkipAppsOnUpgrade = YES SkipComputerName = YES SkipDomainMembership = YES SkipUserData = YES SkipComputerBackup = YES SkipLocaleSelection = YES SkipTaskSequence = YES SkipTimeZone = YES SkipApplications = YES SkipBitLocker = YES SkipSummary = YES SkipFinalSummary = NO _SMSTSOrgName = Demo Deploy Media _SMSTSPackageName = current Installation...
OSDComputerName = DEMO-#Right ("%SerialNumber%", 10) # TimeZone = 105 TimeZoneName = Romance Standard Time UILanguage = en - us; KMS Default key for Windows 7 Pro ProductKey = FJ82H-XT6CR-J8D7P-XQJJ2-GPDD4 JoinWorkgroup = WORKGROUP TaskSequenceID = 0001 

otherwise, you will have to validate each of the screens offered during the deployment.

Note: As part of a deployment by media, the file “ Bootstrap.ini ” didn’t usually need to be customized. However, to ensure a few settings you can add the following content:

 [Settings] Priority = Default [Default] SkipBDDWelcome = YES KeyboardLocale = en - us KeyboardLocalePE = 040c:0000040c InputLocale = UILanguage = en - us 040c:0000040c 

for this example, we won’t touch the last tab “ Windows PE “. ” Click on ‘ apply ‘ or ‘ OK “in order to validate these changes.

select again the line “ MEDIA001 “in the details window and then use the menu” Action…» Update Media Content “.»

Manufacturing process, relatively long, will copy the elements selected via the profile to a subfolder “[MediaPath] Content”, then generate the WinPE LiteTouch kernel and finally generate the image. ” ISO (we asked).

Result and content of [MediaPath]

once the build is completed, we can test the result in a virtual machine from the image “ LiteTouchMedia.iso “. ”

If you followed the example in letter, the installation should begin without any intervention on your part

installation runs automatically

then ends without error 😀

to test from USB media , just prepare the key as follows:

  • a prompt command as Administrator
 DISKPART List Disk Select Disk n (where n is USB media) Clean Create Partition Primary Format fs = ntfs quick label = MDT - Media Assign Letter = k: Exit 

  • from Windows Explorer or from a command prompt

copy the entire folder “ Content ” to USB (here “k: “)

III. Case UEFI and WIM above 4 GB

you can see that this kind of deployment is not very complicated to implement. However, I draw your attention to the fact that a custom WIM image can quickly exceed the fateful size of 4 GB. This in fact implies a formatting NTFS USB media (as mentioned earlier).

Off, the formatting of a NTFS boot media is not (always) installation on a PC which supports UEFI-compatible. However, if you format your Flash drive to FAT32 for this type of installation, you will not be able to accommodate the WIM more of 4 GB.

You can either opt for a double partition (FAT32 and NTFS) unless you have a key known as ‘Disc’ and not as ‘removable ‘. CF

on “removable media”, typically the keys USB, Windows does not recognize that the first partition.

So to solve this problem and be able to install a UEFI post from a standard USB and a WIM image larger than 4 GB, there are only 2 options:

  • cut the WIM image files less than 4 GB, (via DISM for example) SWM, and drop them on your USB drive formatted in FAT32. Don’t forget to check that MDT (including the script ZTIApply.wsf) task sequence takes well into this feature. (Officially taken into account from MDT2013 update1)
  • Use the tool “ Rufus ‘, deceptively simple…

you can find Rufus tool here including a ‘portable’ version to keep preciously in your Toolbox 🙂

  • insert your USB then launch”Rufus”
  • choose the option”For UEFI GPT partition Type”in the drop-down list
  • keep the proposed (FAT32) file system
  • click on the button in front of «Create a boot… drive»»» “and select the ISO image ‘LiteTouchMedia.iso’
  • click on the ‘Start’ button, and it’s over 😀

good deployment to all