Microsoft Deployment Toolkit 2013 Update 1 Has Arrived!

 

We had to wait a couple of week (since the launch of Windows 10), but it’s finally there : MDT 2013 Update 1!

At the moment (August 19th) it’s not yet available at http://microsoft.com/deployment

image

 

……… but Aaron has put a nice blogpost together over at the /MSDeployment Blog.

 

“The Microsoft Deployment Toolkit (MDT) 2013 Update 1 is now available on the Microsoft Download Center. This update requires the Windows Assessment and Deployment Kit (ADK) for Windows 10, available on the Microsoft Hardware Dev Center. (Scroll to the bottom of the page to the section, “Customize, assess, and deploy Windows on your hardware.” The page also includes other Windows kits; remember for deployment you only need the Windows ADK for Windows 10.)

Significant changes in MDT 2013 Update 1:

  • Support for the Windows Assessment and Deployment Kit (ADK) for Windows 10
  • Support for deployment and upgrade of Windows 10
  • Support for integration with System Center 2012 R2 Configuration Manager SP1 with the Windows 10 ADK (see this post on the Configuration Manager Team blog for more information on using the Windows 10 ADK with Configuration Manager)

Here is a more detailed list of some specific changes in this release:

  • Support for new Enterprise LTSB and Education editions of Windows 10
  • Support for modern app (.appx) dependencies and bundles
  • Improved support for split image files (.swm)
  • Switched to using DISM for imaging processes (instead of deprecated ImageX)
  • Deployment Workbench revisions for deprecated content
  • Enhanced accessibility within the Deployment Workbench
  • Revised lists of time zones, regions and languages in the Deployment Wizard
  • Removed Start menu shortcut for “Remove PXE Filter”
  • Several MVP recommended fixes for Windows Updates, password handling, and PowerShell cmdlets
  • Added missing OOBE settings to Unattend.xml
  • Unattend.xml default screen resolution changed to allow for automatic scaling
  • Updated task sequence binaries from System Center 2012 R2 Configuration Manager SP1
  • New GetMajorMinorVersion function for integer comparison of Windows version numbers

We are still working to update the MDT documentation on TechNet, so in the short-term will use this blog to share any additional necessary information regarding this release.”

 

 

 

https://www.microsoft.com/en-us/download/details.aspx?id=48595

Deploying Windows Server 2008 R2 (non-VL) with MDT 2012 & Windows ADK

Just a few weeks ago Microsoft has released MDT 2012 Update 1, with full support for Windows Server 2012 and Windows 8. Microsoft did also release the Windows Assessment and Deployment Kit (ADK) for Windows 8, the replacement for the good old WAIK. With the RTM of Window Server 2012 I decided to upgrade my Deployment environment to the latest version. When I did some initial deployments of Windows 8 and Windows Server 2012 everything worked just fine, but when I tried to deploy Windows Server 2008 R2 (non-VL version) or Windows 7, I ran into a small problem.

The Issue
Just after the deployment I had to enter the Product Key.

image

At first I thought I made a mistake during the built proces, but after I asked a question at the Microsoft Deployment Toolkit Forum. Because the first responses suggested that there was something wrong with my Deployment Share. After some suggestions and a start from scratch (the first time I imported and upgraded the ‘old’ deployment shares), also not importing the ‘old’ deployment shares, the answer came from Michael Niehaus:

“MDT 2012 Update 1 switched from using SETUP.EXE to instead use ImageX to apply the image.  As a result, if you use retail or OEM media, you’ll get a prompt because the product.ini file isn’t being read any more (SETUP.EXE did that, ImageX doesn’t).

Fortunately the fix is pretty simple:  Look up the correct setup (generic) key in the product.ini file on your media and specify it in the unattend.xml (second location).  After you do that, it won’t prompt any more.

This won’t happen with volume license media.”

So that’s probably why the people who responded earlier didn’t have the same issue, they were (probably) using volume license media!

 

The Solution
So, to fix the issue had to specify the (generic) product key (from the product.ini in the Sources folder)

image

image

Open the unattend.xml (in the correct Control  Task Sequence folder) and enter the product key at the second   start-tag.

image

Now you can just restart the Task Sequence and you won’t be asked for a product key during the deployment!

Just a few weeks ago Microsoft has released MDT 2012 Update 1, with full support for Windows Server 2012 and Windows 8. Microsoft did also release the Windows Assessment and Deployment Kit (ADK) for Windows 8, the replacement for the good old WAIK. With the RTM of Window Server 2012 I decided to upgrade my Deployment environment to the latest version. When I did some initial deployments of Windows 8 and Windows Server 2012 everything worked just fine, but when I tried to deploy Windows Server 2008 R2 (non-VL version) or Windows 7, I ran into a small problem.

The Issue
Just after the deployment I had to enter the Product Key.

image

At first I thought I made a mistake during the built proces, but after I asked a question at the Microsoft Deployment Toolkit Forum. Because the first responses suggested that there was something wrong with my Deployment Share. After some suggestions and a start from scratch (the first time I imported and upgraded the ‘old’ deployment shares), also not importing the ‘old’ deployment shares, the answer came from Michael Niehaus:

“MDT 2012 Update 1 switched from using SETUP.EXE to instead use ImageX to apply the image.  As a result, if you use retail or OEM media, you’ll get a prompt because the product.ini file isn’t being read any more (SETUP.EXE did that, ImageX doesn’t).

Fortunately the fix is pretty simple:  Look up the correct setup (generic) key in the product.ini file on your media and specify it in the unattend.xml (second location).  After you do that, it won’t prompt any more.

This won’t happen with volume license media.”

So that’s probably also the people who responded earlier didn’t have the same issue, they were using volume license media!

 

The Solution
So, to fix the issue had to specify the (generic) product key (from the product.ini in the Sources folder)

image

image

Open the unattend.xml (in the correct Control  Task Sequence folder) and enter the product key at the second   start-tag.

image

Now you can just restart the Task Sequence and you won’t be asked for a product key during the deployment!

Deploying Windows 8 Release Preview with MDT 2012 Update 1 (Beta)

Today Microsoft has released the beta version of MDT 2012 Update 1. You can upgrade the following versions of MDT with the MDT 2012 Update 1 Beta :

  • MDT 2008 Update 1
  • MDT 2010
  • MDT 2010 Update 1
  • MDT 2012

After you installed MDT 2012 Update 1, you should upgrade your deployment share. You should also read the Release Notes where you can find some more tips about this new version.

Some of the new features :

  • Support for using the DaRT 8 Beta with the Windows 8 Release Preview version of the Assessment and Deployment Kit (ADK).
  • New “Build Your Own Pages” support for User-Driven Installation (UDI), enabling IT pros to create new wizard panes using simple drag-and-drop operations – no coding required.
  • Integration with System Center Orchestrator, enabling task sequences to invoke Orchestrator runbooks at any point in the deployment process.
  • Completely reworked “Roles and Features” logic, supporting both installation and removal, as well as providing a new Lite Touch wizard pane for selecting roles and features to install at deploy time.
  • Support for PowerShell 3.0 to make it easier to run PowerShell scripts inside task sequences on Windows 8, Windows Server 2012, and Windows PE 4.0.
  • Simple monitoring functionality for Configuration Manager task sequences, leveraging the monitoring capabilities provided initially in MDT 2012 for Lite Touch deployments.
  • Improved “boot from VHD” deployment capabilities, supporting both bare metal and refresh deployment

Instead of the Windows AIK (for Windows 7), you can now use the Windows ADK to deploy Windows 8 Release Preview and Windows 7. When installing Windows 7 using Setup.exe with Windows PE 4.0 from the Windows ADK, two error dialog boxes are displayed while still in Windows PE. The dialog boxes do not affect the deployment, but you must click OK in each of them before the deployment process will continue.

I created a small (7 minute) video of a default Windows 8 Release Preview deployment with the new version of MDT. Please leave a comment if you like it.
http://youtu.be/kMAuXzuztY0

Upgrade Microsoft Deployment Toolkit 2012 RC to MDT 2012 RTM

image

It’s quite simple to upgrade your Release Candidate version of MDT 2012 to the RTM version…. just follow the following steps.

  1. Shutdown the (current version of the) Deployment Workbench
  2. Start MicrosoftDeploymentToolkit2012_x64.msi (or the x86 version)
  3. Click Next
  4. Accept the License Agreement and click Next
  5. Keep the default installation path and click Next
  6. Click Install
  7. Wait for the installation to finish succesfully and click Finish.
  8. Open the Deployment Workbench
  9. Right click your Deployment share and select Upgrade Deployment Share
    image
  10. Click Next
  11. MDT will now update the Deployment Share
    image
  12. Click Finish to complete the upgrade!

That’s all…have fun deploying!

P2V Windows XP and Deploy Windows 7

In my previous post I showed how you can configure the P2V Migration Add-on. In this post I would like to show you how the created task sequence can be started to P2V the Windows XP installation, followed by the installation of Windows 7. When that is finished the Windows XP VHD is configured to run as a virtual machine inside the just installed Windows 7 client.

08

Continue reading “P2V Windows XP and Deploy Windows 7” »

P2V Migration with MDT 2010

With the Microsoft Deployment Toolkit it was a piece of cake to deploy your machine with Windows XP, Windows 7 or even Windows Server 2008 R2. From now on it is also possible, with a MDT 2010 Add-on, to P2V your existing Windows XP, Windows Vista and even Windows 7 machine. Only (for now) the 32-bit version of these operating systems can be P2V’d. A virtualized version of the operating system can be used as a virtual machine inside your 32-bit or 64-bit Windows 7 machine.

The P2V Migration add-on is still in the beta stage right now, but because this add-on can be another positive vibe to (finally) migrate to Windows 7 I really would like to share it with you.

Continue reading “P2V Migration with MDT 2010” »

WDS + MDT = GDS

The last few months I’ve been working on several project where deploying the Windows Desktop was a task I was responsible for. Of course there are several (Microsoft) solutions to deploy desktops, but the combination of Windows Deployment Services in combination with Microsoft Deployment Toolkit is by far my favorite!

Some of my colleagues only use System Center Configuration Manager when they talk about deployment, but the WDS+MDT combination is free of charge (oke, you have to pay for the Windows license, but you can install WDS as a feature and MDT is free) and for the non-enterprise environments I think it’s a really Good Deployment Solution (GSD)!

Like every IT Pro I like to investigate new solutions and try new products. Because I would like have a flexible environment, I started to use MDT 2010 to deploy my test environments.

In the following blog posts I would like to show you how easy it is to create your own deployment environment and how you can deploy desktops and servers (incl. AD, DNS, etc.). I will also show you how you can capture an installed machine to a WIM image and also deploy that image.

At the moment I’m not sure how many blog posts I will create, but if you want me to explain a certain part of MDT please leave a comment below! Part one will be online somewhere next week and in that post I’ll explain how you can configure your machine so you will be able to deploy a Windows 7 Desktop.

ps. I won’t explain how you have to install Windows Server 2008 R2, the WDS role or MDT 2010 itself. So please visit microsoft.com/deployment if you want to install MDT 2010.

Tech-Ed IT Pro 2008 : Windows 7 Client Deployment en MDT 2010 (Dag 2)

TechEd-Logo

Aangezien Deployment een van mijn specialisaties is moest ik natuurlijk naar de sessie over Windows 7 Client Deployment.

Gelukkig hoor ik gelijk dat alles wat in gang is gezet voor het deployen van Windows Vista (MDT 2008, System Center Configuration Manager) gewoon hetzelfde blijft met het deployen van Windows 7.

MDT 2008 & MDT 2010
Op dit moment kun je de Pre-Beta van Windows 7 niet ‘default’  deploymen met de Microsoft Deployment Toolkit 2008. Gelukkig is het met een paar eenvoudige aanpassingen in een paar configuratiebestanden van MDT 2008 wel mogelijk!

Jeremy kondigt aan dat bij de beta-release van Windows 7 er tevens een beta beschikbaar zal zijn van de nieuwe versie van de Microsoft Deployment Toolkit : MDT 2010. Naar alle waarschijnlijkheid zullen deze beta’s begin 2009 beschikbaar komen.

MDT 2008 and BDD 2007 are now Windows Vista SP1 and Windows Server 2008-Ready

Source : Microsoft Deployment Blog 

Windows Vista Service Pack 1 was Released to Web via Windows Update and Download Center this Tuesday and we know there are a lot of companies waiting to deploy it into production. You may be familiar with the Business Desktop Deployment (BDD) tools from the past and the latest version, dubbed Microsoft Deployment Toolkit (MDT) which was released in November. We changed the name from BDD because you can now build images and deploy desktops and servers (including Windows Server 2008) with the same toolkit and we thought MDT better reflected that functionality. Today we’re excited to announce the release of Microsoft Deployment Toolkit 2008!  MDT makes imaging and deployment much easier with its new checklist and wizard-driven user interface. At the same time it continues to provide lots of great in-depth guidance for managing your deployment projects end-to-end, as well as quickstart guides if you want to quickly dive into the tools. If you are among the more than 350,000 people still using BDD 2007, we didn’t forget about you. An update for BDD 2007 to support SP1 imaging and deployment is also available today.

Both these tools can save you lots of time in planning and building out a standard desktop experience all the way to rolling OS images out into production.

In addition to Service Pack 1 support for Windows Vista, MDT 2008 also has the following  new features:

  • Full support for Windows Server 2008
  • Additional Actions including Configure DHCP, Authorize DHCP, Configure DNS, and Configure ADDS
  • New scripts that will automate the installation of Mass Storage Drivers for Windows XP and Windows 2003 Systems
  • Ability to use a WSUS server for the Windows Update script
  • Improved performance for the PXE Filter for System Center Configuration Manager unknown computer support
  • Improved documentation including a new Quick Start Guide for System Center Configuration Manager and a guide for implementing the Management Pack for System Center Operations Manager

Download Microsoft Deployment Toolkit 2008
Download Updated Business Desktop Deployment 2007
Click here for more information about Microsoft Deployment