The Microsoft Deployment Toolkit (MDT) 2008 was recently released. It is the update to BDD 2007 and adds a great deal of functionality to SCCM 2007 Operating System Deployment.
Be sure you check out the following related blogs:
Microsoft Deployment Toolkit Team Blog
Michael Niehaus has been working on BDD/MDT Developer since its inception.
New features excerpt from the release notes:
========================================
New Features
The following list highlights the many new features that have been included in this release of Microsoft Deployment Toolkit:
· Deployment Workbench:
· To better align with System Center Configuration Manager, Deployment Workbench has been modified to create and use task sequences instead of builds.
· Support for multiple task sequence templates has been added. Included with this release of MDT are sample templates. Among them are a client template for Windows Vista and Windows XP, a server template for Windows Server 2008 and Windows Server 2003, a Replace scenario template, and a custom template that can be used to build task sequences that perform tasks in addition to the deployment of operating systems.
· System Center Configuration Manager support, with the following features:
· MDT 2008 supports System Center Configuration Manager deployments for Windows Vista, Windows XP, and Windows Server 2003.
· MDT 2008 functionality is completely integrated into the System Center Configuration Manager server. Deployment Workbench is not used with System Center Configuration Manager operations, except when configuring the Deployment Workbench database (DWDB).
· Ability to quick-start System Center Configuration Manager operating system deployments using one wizard to create either operating system packages or operating system installation packages, a Windows User State Migration Tool (USMT) package, a System Preparation Tool (Sysprep) package, a customized boot image, or an MDT 2008 custom settings package (using CustomSettings.ini, Unattend.xml, Unattend.txt, or Sysprep.inf).
· Manage deployment settings directly in Configuration Manager Console.
· Dynamically determine whether user state is backed up locally or to the state management point.
· System Center Configuration Manager uses the CustomSettings.ini file and DWDB to determine the list of packages that will be installed on the target computer. When this list of packages is determined, System Center Configuration Manager performs the required installations.
· A new wizard for creating the boot image is available on the Boot Images node.
· LTI deployment:
· Deployment team members have the option of configuring disks and network adapters as deployment tasks in LTI deployments.
· Functionality has been designed to work like System Center Configuration Manager to ease migration from LTI and Microsoft Systems Management Server 2003 to System Center Configuration Manager.
· LTI can use Windows Deployment Services multicast transmission when performing LTI deployments of operating system images from Windows Server 2008 servers.
· MDT 2008 supports LTI deployment for Windows Server 2008 and Windows Vista with SP1.
· Support to optionally back up the existing drive C on new computers, in addition to support for backing up and reformatting the old computer in Replace scenarios.
· Software updates:
· Support for detecting, downloading, and installing software updates that are available through the Microsoft Updates Web site or intranet servers running Windows Server Update Services (WSUS).
· Web service calls:
· Web services can be invoked as part of the rules processing performed by MDT 2008, using new rules that can be defined in CustomSettings.ini.
· Windows Server roles:
· Support for the installation and, in some cases, configuration of Windows Server roles. These roles include Active Directory® directory service Domain Services (AD DS), Dynamic Host Configuration Protocol (DHCP), Domain Name Service (DNS), Microsoft Internet Information Services (IIS), Windows Server 2003 Terminal Services, Windows Deployment Services, and Windows Internet Naming Service (WINS).
· Package groups:
· Added PackageGroup functionality. Package groups help separate packages during installation. For instance, when you have multiple operating systems to deploy and they use different packages or require different levels of patches or different languages, you can assign packages to different groups. You then assign the group to a particular operating system during deployment or you can select a package group for a task sequence. A PackageGroup can be assigned using the PackageGroup variable in CustomSettings.ini.
· Distribution Share Wizard:
· The installation and configuration process for MDT 2008 has changed from BDD 2007. In MDT 2008, Windows Installer does not create a distribution share. Team members instead need to use Deployment Workbench to create the distribution share before adding the operating system source, applications, and so on.
· There is now support for side-by-side installation of MDT 2008 and BDD 2007 installed on the same computer.
· There is now support for upgrading a BDD 2007 distribution share to MDT 2008.
========================================
The SCCM integration adds additional functionality directly into the ConfigMgr Console and minimizes package creation steps that must be taken prior the creation of your first task sequence. You can even avoid manually creating your Operating System Deployment Packages and let MDT 2008 do it for you.
If you are upgrading from a prior version of BDD, check out the following posts from Michael Niehaus:
Upgrading to Microsoft Deployment Toolkit (MDT) 2008 - Zero Touch with ConfigMgr 2007
Upgrading to Microsoft Deployment Toolkit (MDT) 2008 - Zero Touch with SMS 2003
Also note that this release of MDT supports Windows AIK versions 1.0 and 1.1. Windows AIK 1.1 was released with Windows Vista and is required to deploy Windows Vista with SP1 and Windows Server 2008.
To get AIK 1.1, go to the following link:
Automated Installation Kit (AIK) for Windows Vista SP1 and Windows Server 2008
