Converting Windows 10 Media Creation tool to install.wim

When creating media with the Microsoft Windows 10 media creation tool, the USB drive or ISO file will not have install.wim included.  Therefore, you are not able to import an operating system into MDT.  There must be a install.wim in the “sources” in the media.  By default, the media creation tool creates a “install.esd” file.


To convert install.esd into install.wim, you can you use dism.

Open the Deployment and Imaging Tools Environment CMD prompt as admin, and browse to your folder location of install.esd

type:  dism /Get-WimInfo /WimFile:install.esd





We are looking for the index of the version we want to convert.  For example, if you want Windows 10 PRO, use index 1.

then type:  dism /export-image /SourceImageFile:install.esd /SourceIndex:1 /DestinationImageFile:install.wim /Compress:max /CheckIntegrity





This will convert your install.wim file and can now delete install.esd.  This should now import into MDT.

Posted in dism, MDT, MDT 2010, Windows 10 | Tagged , , , | Leave a comment

Remove all Windows 10 Metro Apps, except the Store

As you probably already know, sysprep will usually fail if the Windows 10 store metro style apps aren’t removed.  Most of my customers want these apps removed anyway.  I did have a request today to have all apps removed, but keep the Windows store just in case something wanted to be added in the future.


The normal method of removing the apps also removes the store.  I just tested the following Powershell commands that remove every app, except the store.  This may be useful as it’s difficult to add the store after the fact.


Get-appxprovisionedpackage –online | where-object {$_.packagename –notlike “*store*”} | Remove-AppxProvisionedPackage –online


Get-AppxPackage -AllUsers | where-object {$ –notlike “*store*”} | Remove-AppxPackage

Posted in MDT, MDT 2010, Microsoft Deployment Toolkit, Windows 10 | Tagged , , | Leave a comment

Remove all Windows 10 “Metro” style Apps from Reference Image

Many times Windows 10 sysprep will fail when the built-in Windows 10 apps are present.  The reasons can vary, however most times I just remove them anyway in my reference image.

This will remove most of the junk apps in the Windows 10 start menu, but may not remove the shortcuts themselves.

Use these 2 lines in your reference image task sequence, or run them manually before sysprep.

Get-AppxProvisionedPackage –online | Remove-AppxProvisionedPackage -online

Get-AppxPackage –AllUsers | Remove-AppxPackage


While we’re at it, we may as well remove Candy Crush, Twitter, etc… the Consumer Experience apps.  Add this to your task sequence or just edit the base reference image.

Import this registry entry.

Windows Registry Editor Version 5.00


Posted in MDT, MDT 2010, Powershell, SCCM 2012 | Tagged , , , | Leave a comment

Using WMIC to Find Computer Model for SCCM or MDT

A quick tip that I use quite a bit.  If you like to query WMI to get the computer model for drivers in MDT or SCCM, one little nagging challenge is getting the exact name of the model in WMI.

Here’s a quick command line that you could also script if needed.

From an elevated command prompt, type:

wmic csproduct get name

The result should give you the exact name returned by WMI in your task sequence query. 



 Then, just plug in your model you are targeting into a SCCM task sequence condition.  For example:

SELECT * FROM Win32_ComputerSystem WHERE Model LIKE “%HP Compaq Elite 8300 SFF%”







Posted in MDT, MDT 2010, SCCM 2007, SCCM 2012 | 1 Comment

MDT 2012 New Features – Monitoring

A big complaint of mine and many colleagues was the lack of monitoring in MDT 2010.  You never really knew what the status of a job was if it failed halfway thru. 

MDT 2012 now comes with a moniting section to view the progress of your task sequences. 

You can find monitoring in the bottom of your Deployment Workbench.  By default, this is turned off.  But very easy to turn on.

 mdt monitoring

mdt monitoring2


When you enable MDT 2012 monitoring, two things happen:

From Michael Neihuas Blog at Microsoft

  1. A new service, the “Microsoft Deployment Toolkit Monitor Service” (short name MDT_Monitor), is installed on the computer.  This service receives events from the computers being monitored, tracking each computer and how far it is in the deployment process.  It also provides this tracking data to Deployment Workbench for you, the administrator, to see.
  2. The CustomSettings.ini file is modified to add a new entry specifying the URL (a combination of the host name and port specified in the deployment share settings) to be used for monitoring.  This is how clients know where to send information.  The MDT scripts (through their use of ZTIUtility.vbs) will automatically send events to this URL.

A few other details:

  • The computers will be automatically removed after three days, to keep the database from getting too big.
  • If the monitoring service doesn’t hear from a computer for more than four hours, it considers the machine “unresponsive” – so if you see that status in the Workbench list, that’s why.
  • Every time a deployment task sequence starts, completes, or fails, an event log message will be written by the service.  So if you want to trigger some activity based on these events, you can easily do so.
  • You might think that IIS would be required for the MDT_Monitor service, but it’s not.  It’s leveraging features of the .NET Framework to run a “mini web server” as part of the service itself.
  • You might also think that a SQL database would be required to store the details.  Well, there is one, but you don’t need to install SQL Server to use it.  MDT uses a SQL Compact database; all the files needed are installed as part of MDT (and only used if monitoring is enabled).

Fairly easy to turn this one.  Also don’t need to worry about SQL either.  Just a compact SQL install included in the MDT install files. 


Posted in MDT, MDT 2010 | Leave a comment

Restarting a Hung MDT 2010 or 2012 Task Sequence

I’ve been asked a few times about the easiest way to restart a hung task sequence.  Hung meaning – for some reason the task sequence you kicked off doesn’t complete during or after imaging.  Most cases I see are hung after the image is down on the machine and waiting for the applications to load.   MDT basically tries to start where it leaves off and fail.

You try to reboot off the boot media and you see a message stating you can’t restart the task sequence becuase its waiting for applications to load.

If it’s a chronic problem – this probably isn’t the fix.  This is just for the one-off scenarios for when MDT decides to break.

To stop these errors from re-occuring

  • Boot to the OS
  • Delete these 2 folders from root of C:  _smstasksequence & minint
  • reboot and boot off MDT disk or PXE.  The MDT deployment share should start from scratch.

Also, can do the same thing winthin WinPE

  • diskpart 
  • select disk 0 
  • clean
  • then, restart the deployment
Posted in MDT, MDT 2010 | Leave a comment

MDT 2010 Lite Touch Training Page 3

MDT 2010 Lite Touch Training Page 3

Part 17 – USMT 4.0 Troubleshooting

– Reviewing log files
– Configure USMT 4.0 Log files


Part 18 – Using the MDT 2010 database

– Creating the MDT database
– Add computer entries
– Configuring roles in the database
– Setting location based settings
– Using Make and Model based settings


Part 19 – Extending the MDT 2010 Database

– Create additional tables
– Create additional stored procedures
– Configure MDT to use stored procedures


Part 20 – Extending MDT 2010 with user exits

– Create User Exit scripts
– Configure MDT 2010 to use user exits


Part 21 – Extending MDT 2010 with web services

– Resources for web services in MDT 2010
– Configure MDT 2010 to use web services
– Tools for editing the MDT wizard


Part 22 – Speeding up development time in MDT 2010

– Tips and tricks for speeding up development time
– Create a test environment


Part 23 – Scaling MDT 2010 Lite Touch in a distributed environment

– Recommendations around Linked Deployment Shares
– Configuring bootstrap.ini to connect to local deployment server
– Replicating the deployment share


Part 24 – Troubleshooting – Following a Windows 7 Setup

– The Windows 7 Setup Engine
– Logfiles and troubleshooting
– Debugging


Part 25 – Using Windows System Image Manager (WSIM)

– Create unattend.xml files using WSIM
– Understanding configuration passes


Part 26 – Component Based Servicing (CBS)

– Resources for understanding CBS
– Windows 7 Deployment resources


Part 27 – Windows 7 and Device Drivers

– The Windows 7 Driver Store
– Using pnputil and DISM
– Using Group Policies to control device drivers
– How MDT integrates with the driver store
– Driver signing and ranking


Posted in MDT, MDT 2010, Microsoft Deployment Toolkit | Leave a comment

MDT 2010 Lite Touch Training Page 2

MDT 2010 Lite Touch Training Page 2


Part 8 – ntegrating WDS with MDT 2010

– Adding boot images from MDT to WDS


Part 9- Using Multicast for MDT 2010

– Configuring MDT for Multicast
– The WDS multicast namespace
– Deploying Windows 7 using multicast


Part 10 – Troubleshooting MDT 2010 Lite Touch

– Debugging MDT
– Solving network connection issues
– Verifying storage controller drivers
– Log files


Part 11 – Locating drivers for MDT

– Third party vendor resources and utilities
– Microsoft Catalog site for drivers
– Locating PNPIDs


Part 12 – MDT 2010 Lite Touch Driver Management

– Boot image drivers
– Windows Operating system drivers
– Out-of-box drivers repoistory in MDT 2010 Lite Touch
– Using folders
– Using selection profiles to filter drivers
– Using DriverGroups to filter drivers based on computer make and model


Part 13 – MDT 2010 Lite Touch Drivers Tips and Tricks

– Configuring WinPE Scratchspace
– Dealing with drivers that are applications and,or services


Part 14 – USMT 4.0 in action

– USMT command lines


Part 15 – MDT 2010 Lite Touch – Refresh and Replace scenarios

– Configuring Refresh and Replace in MDT 2010 Lite Touch
– Starting a Refresh Deployment
– Creating a Replace Task Sequence
– Starting a Replace Deployment


Part 16 – Customizing USMT 4.0 migrations

– Customizing profile capture using command line switches
– Customizing data and settings using XML templates
– Create customized templates
– Configure rules in MDT 2010 Lite Touch for USMT 4.0


Posted in MDT, MDT 2010, Microsoft Deployment Toolkit | Leave a comment

MDT Lite Touch in VMWare Workstation for your test lab

So I came across a little but pretty tricky issue when trying to create a new MDT 2010 test lab in VMWare Workstation.

When trying to image up a bare metal VMware XP workstation I came across this error

When you create a new VM and use the XP VMWare profile it defaulted to and AMD PCNet NIC.

None of the MDT Lite Touch boot PE images have the AMD driver.  Took a little digging – but here it is.  AMD PCNet NIC

Import these drivers into your drivers into MDT, update your deployment share, and update the PXE boot image and you are set!

A quick and easy fix – hopefully this helps!  Its been awhile since I’ve had to use this exact setup!


Posted in MDT, MDT 2010, Microsoft Deployment Toolkit, VMWare | Leave a comment

MDT 2010 Videos – Lite Touch Training

All credit to Johan Arwidmark – one of the best!

MDT 2010 Lite Touch Training Page 1

Part 1- Introduction to Windows AIK 2.0

– Creating a custom WinPE image
– Use ImageX to mount the image
– Use DISM to inject a driver
– Show BCDBoot
– Use Windows System Image Manager (WSIM) to edit unattend.xml


Part 2 – Windows Deployment Services (WDS) configuration

– PXE listener and Multicast
– PXE Boot Policy
– Network Configuration


Part 3 – Introduction to MDT 2010 Lite Touch

– Create Deployment Share
– Import Operating System
– Add applications
– Create Task Sequences
– Create boot images
– Test a deployment


Part 4 – Multiple Deployment Shares


– Why we need them
– Lab and Production shares


Part 5 – Creating the MDT Build Lab Share

– Rules configuration
– Configuring the task sequence
– Using the LTI Suspend feature


Part 6 – Creating the MDT Production Share

– Rules configuration
– Configuring the task sequence
– Joining the domain


Part 7 – Introduction to MDT 2010 Rules

– Basic rules (customsettings.ini)
– Using Properties
– Review reference documentation







Posted in MDT, MDT 2010, Microsoft Deployment Toolkit | Tagged , , | Leave a comment