This is provided ‘AS IS’ with no warranties, and confers no rights. Use of included samples are subject to the terms specified at Microsoft
Installing Microsoft Deployment Toolkit 2012 Beta 2
To Install MDT 2012 Beta 2, you need to install the .NET Framework 3.5 (SP1 or Higher). Since we are installing MDT 2012 Beta 2 on a Windows Server 2008 R2 Server, we can add the .NET Framework using the ServerManager.
You must have used ServerManager to add roles / features / role services several times. Let’s use PowerShell to install the .NET Framework Feature.
First, we will import the module for ServerManager and then use the Get-WindowsFeature to determine the name of feature as understood by PowerShell
Add the feature by using the Add-WindowsFeature Cmdlet.
As you see below, the installation was successful and it does not require a reboot.
We can verify the same using the ServerManager GUI as shown below:
Once we have the .NET Framework installed, we then have to install the Windows Automated Installation Kit (Windows AIK) for Windows 7 and server 2008 R2
Download the ISO for Windows AIK (http://www.microsoft.com/download/en/details.aspx?id=5188) and mount it on the VM or simply burn it into a DVD.
When you mount it, it autoruns and launches the Welcome Splash Screen as shown below:
Click on the Windows AIK Setup to start the installation.
Accept the License Terms, and Click Next.
We will accept the default path for the installation Directory and click Next.
Click Next to start the installation.
Now that we have all our prerequisites installed, its time to install MDT 2012 Beta 2. You can download the Beta version from http://www.microsoft.com/mdt
Double Click on the MicrosoftDeploymentToolkit2012_x64.msi file. Click Run on the Open File-Security Warning.
On the Welcome to Microsoft Deployment Toolkit 2012 Beta Setup Wizard, click Next.
Accept the License Agreement and Click Next, you may want to print the License Agreement and read it before bed time. J
Click Next on the Custom Setup Page.
Click Next on the Ready to Install Page to start the installation.
Once MDT 2012 Beta 2 is installed, Click Start -> Expand Microsoft Deployment Toolkit folder and select Deployment Workbench (Your playground for MDT)
The Deployment Workbench is based on the typical MMC version 3.0 Console and greets you with the new features in MDT 2012 Beta 2 and its predeccessor MDT 2012 Beta 1.
If you take a look at the Components Directory, you will notice that you can download the Windows Automated Installation Kit from the MDT console itself. You can install MDT 2012 prior to installing the WAIK toolkit but you won’t be able to set up the Deployment Share without having WAIK installed.
In my next blog post, we will see how to configure MDT 2012 Beta 2 Deployment Share. Stay tuned.
Happy Reading and a very Happy Thanks Giving
MDT has a fundamental flaw, no one seems to notice! When you want to capture an image of existing Windows 7, capture task fails becuase WinPE tries to copy it to the 100 MB system reserved partition!
Many of the tasks are redundant, not quite intuitive!!
A very poorly written codes I must add.
A connection to the deployment share could not be made.
MDT Deploy Windows 7 - Domain Join Failed
Deployed computers generate random names
There is not enough space on the disk error
Invalid Credentials error: Even if you enter correct id, password, with or without domain prefix
Access denied when running LiteTouch.VBS to Sysprep and Capture W7
Uploading Image to WDS failed
WDS Multicast not working
Agreed! I have wasted weeks trying resolve MDT Errors! One after another!
Don't agree. I have installed MDT successfully at many customer sites and everytime without the errors above. Maybe i am doing something wrong... :)
And, don't mean to be churlish here, but most of the errors linked above are solved in the thread with helpful guidance on how to configure MDT, Task Sequences, UnattendXMLs, and so on, correctly.
Another point is you can capture an image after removing a system reserved partition. If i want to capture an image, i use a reference machine. and as it is a reference machine i would build a machine on a virtual platform, and remove this partition. I think thats pretty reasonable and not exactly a fundamental flaw.
And another thing... it is still essentially free isn't it?
I would consider a major feature that fails right out of the box on pretty much every computer you would attempt to use it on a fundamental flaw. WDS/MDT is absolutely full of problems.
I've been using MDT for almost 3 years now. Can't complain Metachemical. I've deployed it in small and enterprise environments without a problem. Not deployments of PC's (that's a given) but actual deployment servers. This tool is a breeze and easy to use. There is a TON of stuff on the web to help anyone learn how to configure this thing. To be honest, when I use it with PXE and WDS the installation of the tool is done in 15 minutes and I'm ready to push images without a problem.