Microsoft Deployment Toolkit 2010 Update 1 - Now Available!

If you’re making the move to Windows 7, Windows Server 2008 R2, and/or Office 2010, you need tools and guidance to help you through the process. Microsoft Deployment Toolkit (MDT) 2010, a free Solution Accelerator, is designed to fill that need.

The latest MDT 2010 Update 1 release, now available for download, offers something for everyone:

For System Center Configuration Manager 2007 customers:

• New “User Driven Installation” deployment method. An easy-to-use UDI Wizard allows users to initiate and customize an OS deployment on their PCs that’s tailored to their individual needs.
• Support for Configuration Manager R3 “Prestaged Media.” For those deploying Windows 7 and Office 2010 along with new PCs, a custom OS image can easily be loaded in the factory and then customized once deployed.

For Lite Touch Installation:

• Support for Office 2010. Easily configure Office 2010 installation and deployment settings through the Deployment Workbench and integration with the Office Customization Tool.
• Improved driver importing. All drivers are inspected during the import process to accurately determine what platforms they really support, avoiding common inaccuracies that can cause deployment issues.

For all existing customers:

• A smooth and simple upgrade process. Installing MDT 2010 Update 1 will preserve your existing MDT configuration, with simple wizards to upgrade existing deployment shares and Configuration Manager installations.
• Many small enhancements and bug fixes. Made in direct response to feedback received from customers and partners all around the world, MDT 2010 Update 1 is an indispensible upgrade for those currently using MDT (as well as a great starting point for those just starting).
• Continued support for older products. MDT 2010 Update 1 still supports deployment of Windows XP, Windows Server 2003, Windows Vista, Windows Server 2008, and Office 2007, for those customers who need to be able to support these products during the deployment of Windows 7 and Office 2010.

Next Steps

• Download MDT 2010 Update 1 from the Microsoft Download Center.
• Learn more about MDT 2010 by visiting the MDT site on TechNet.
• Get the latest news by visiting Microsoft Deployment Toolkit Team Blog.
• Ask questions, post answers, and share your insights in the MDT Forum.

We are going to be featured on the Technet Radio podcast and we want to know what you would like us to talk about!  Now is your chance to get your deployment questions answered or here us talk about a topic that you have always wondered about.

Feel free to leave your topics as comments or email us through the link.

Thanks!

Announcing Microsoft Deployment Toolkit 2008 – now Windows Vista SP1-Ready!

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. Download MDT 2008 or the updated BDD 2007 today. For more information, go to http://www.microsoft.com/deployment or contact a Desktop Deployment Planning Services specialist.

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

We've received a number of questions over the past few days on the best way to upgrade from MDT 2008 to MDT 2008 Update 1 without losing any settings.  The most common problem that has been seen is that the Deployment Points are no longer present after installing MDT 2008 Update 1.  The following instructions will allow you to upgrade and maintain all of your existing settings:

1.  Before installing MDT 2008 Update make a backup of the Deploy.XML file.  The file is located by default in C:\Program Files\Microsoft Deployment Toolkit\Control

2.  Install the MDT 2008 Update 1 MSI

3.  Launch the Deployment Workbench and right click on Distribution Share and choose Create distribution share directory

4.  A wizard will then be presented.  Choose Upgrade an existing distribution share and type or browse to the path of your existing distribution share.  Check the check box to Backup existing scripts and configuration files and click on Finish (the files will be backed up to the Distribution\Backup folder)

5.  Close the Deployment Workbench and restore the Deploy.xml that was backed up earler to C:\Program Files\Microsoft Deployment Toolkit\Control, overwriting the existing file

6.  Launch the Deployment Workbench, navigate to the Deployment Points and your Deployment Points should now be visible.

7.  Right click on each Deployment Point and choose Update.  This will update all of the Windows PE images with the correct version of the scripts

8.  If you are using WDS, you will now need to replace your boot image in WDS with the updated Lite Touch WIM file

The latest version of the Microsoft Deployment Toolkit, MDT 2010, is currently being developed.  This new version, which is due to be released shortly after the Windows 7 release, will offer:

• Support for Windows 7 and Windows Server 2008 R2.
• Deployment Workbench and script architecture improvements.
• Documentation improvements.

The first beta release will be made available in the coming weeks.  Please sign up for at the Connect website to be notified as soon as it is available, if you haven’t already done so.  To sign up, follow these simple steps:

1. Access http://connect.microsoft.com.
2. Sign on using any valid Live ID.
3. From the Connection Directory, find the “Solution Accelerators” connection.
4. Apply for the “Microsoft Deployment Toolkit” program.  Approval is automatic.

We look forward to receiving your feedback on this new MDT 2010 version and encourage you to use the Connect site for that feedback.

If you have suggestions, comments, or concerns about MDT 2008 (the current release), please submit that through the Connect site as well.

Open Beta for MDT 2010—Join Now

Microsoft Deployment Toolkit 2010

Deploy Windows 7 beta with Microsoft Deployment Toolkit 2010. Join the beta at http://connect.microsoft.com.  Follow the instructions on this blog post to get connected to the Beta: http://blogs.technet.com/msdeployment/archive/2008/12/03/a-new-version-is-coming-soon.aspx

MDT 2010 is the next version of Microsoft Deployment Toolkit, a solution accelerator for operating system and application deployment. New features like flexible driver management, optimized transaction processing, and access to distribution shares from any location simplify deployment and make your job easier. Deploy faster and easier with MDT 2010. Join the beta now.

Tell us what you think! Join the beta and send us your honest feedback. We appreciate your input.

Microsoft Deployment Toolkit is the fourth generation deployment accelerator from Microsoft. It is the recommended process and toolset to automate desktop and server deployment. MDT benefits you by providing:

· Detailed guidance and job aids for every organized role involved with large-scale deployment projects.

• Unified tools and processes required for desktop and server deployment in a common deployment console and collection of guidance.
• Reduced deployment time, standardized desktop and server images, along with improved security and ongoing configuration management. 

New Functionality

• Support for deploying Windows 7, Windows Server 2008 R2 in addition to deploying Windows Vista SP1, Windows Server 2008, Windows XP SP3, and Windows 2003 SP2
• Hard Link Migrations using USMT 4 for Refresh scenarios which will dramatically reduce your user state backup and restore time
• Integration of the new Windows AIK 2.0 Beta toolset such as DISM and BCDBOOT, and Windows PE 3.0

Join the Beta

Additional infrastructure deployment tools are available as beta releases on the Connect Web site. They are open beta downloads. See below for instructions on how to access the Connect Web site.

To join the Microsoft Deployment Toolkit 2010 Beta, follow these steps:

1. Visit the Microsoft Deployment Toolkit Beta at http://connect.microsoft.com.

2. Sign in using a valid Windows Live ID to continue to the Invitations page.

3. Scroll down to Microsoft Deployment Connection.

If you have not previously registered with Microsoft Connect, you might be required to register before continuing with the invitation process.

If the link in step 1 does not work for you, copy the link and paste it into the Web browser address bar.

Related Resources

Check out other Solution Accelerators! Visit the SAT page on TechNet, http://www.microsoft.com/solutionaccelerators, for additional information.

We appreciate your comments and feedback, please send mail to satfdbk@microsoft.com

There have been reports of a problem when running Refresh, Replace, Sysprep and Capture, and Custom task sequences with MDT 2010.  When running those scenarios an error message is displayed after completing the wizard that states “A connection to the distribution share could not be made”.  When looking at the log files the error states: ‘Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed.”

This problem seems to occur most often when logged onto the client machine as one user and entering different credentials into the deployment wizard or customsettings.ini.

We have developed a fix for this problem.  To fix the problem you should edit the ztiutility.vbs file in the deployment share under the scripts folder.  Open the file in notepad and replace the following code in the MapNetworkDriveEX function:

Case Else

' Case &h800704C3 ' Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed.

' Case &h8007052E ' Logon failure: unknown user name or bad password.

' There was a some kind of fatal error.

If ErrDesc <> "" then

             MapNetworkDriveEx = ErrDesc

Else

             MapNetworkDriveEx = "Unable to map UNC Path " & sShare & " :" & "( 0x" & hex(HasError) & " ) "

End if

oLogging.CreateEntry MapNetworkDriveEx & "", iLogType

Exit function

End select

With this code:

Case Else

Err.Clear

On Error Resume Next

oNetwork.MapNetworkDrive  chr(sDrive)&":", sShare, False

HasError = err.number

ErrDesc = err.Description

On Error Goto 0

If Err.Number <> 0 Then

' There was a some kind of fatal error.

             If ErrDesc <> "" then

                                        MapNetworkDriveEx = ErrDesc

             Else

                                        MapNetworkDriveEx = "Unable to map UNC Path " & sShare & " :" & "( 0x" & hex(HasError) & " ) "

             End if

             oLogging.CreateEntry MapNetworkDriveEx & "", iLogType

                           Exit function

Else

      Exit Function

End If                   

End select

We thank you very much for your feedback and assistance in helping us fix this problem.  We are currently working on a KB article that decribes these steps and will update once that KB article is available

The next version of the Microsoft Deployment Toolkit—version 2012— is now available for beta download. To participate, register for MDT 2012 Beta 1 at Microsoft Connect.

Microsoft Deployment Toolkit (MDT) 2012 Beta 1 rides the next wave of System Center releases with support for System Center Configuration Manager 2012. For Lite Touch installations, MDT 2012 improves the overall client-side user experience, while also providing behind-the-scenes enhancements for partitioning, UEFI, and user state migration. These features, combined with many small enhancements, bug fixes, and a smooth and simple upgrade process, make MDT 2012 Beta 1 more reliable and flexible than ever.

Key Benefits:

• Fully leverages the capabilities provided by System Center Configuration Manager 2012 for OS deployment.
• Improved Lite Touch user experience and functionality.
• A smooth and simple upgrade process for all existing MDT users.

Tell the MDT team what you think! To participate in the MDT 2012 Beta 1 program, download and test the tool in your environment and then provide timely feedback and suggestions to our development team. MDT 2012 Beta 1 runs through August 2011. Please submit your feedback through Connect and direct any support questions you may have to satfdbk@microsoft.com. Thank you for taking the time to help us improve the MDT product feature and functions. Your time and assistance are much appreciated.

Next steps:

· Join MDT 2012 Beta 1 and tell the MDT team what you think!

· Help spread the word—share the beta invitation link with your friends.

· Send your comments to the MDT Team.

· Learn more about the MDT.

Get the latest tips from Microsoft Solution Accelerators—in 140 characters or less! Follow us on Twitter: @MSSolutionAccel.

Microsoft Deployment has been released for a little over three months and we now have had enough questions and support calls come in to generate a FAQ.  You might want to bookmark this post because we plan on updating this list as additional questions are asked.

Lite Touch Installation

Q:  Is it possible to change the text IT Organization in the task sequence dialog box?

A: Yes!  You can set the variable _SMSTSORGNAME in the custom settings.ini to match the text you want to use.  For example to set the text to Microsoft Corporation, add the following line to your customsettings.ini:

_SMSTSORGNAME = Microsoft Corporation

Q:  What is the purpose of each of the task sequence templates?

A: In BDD 2007 we supported only the installation of a client Operating System and did not technically support using task sequences for anything other than deploying an Operating System.  With Microsoft Deployment we now support deploying server Operating Systems as well as running customized task sequences that can perform any number of operations.  Here is a list of the templates we provide and their purpose:

• Standard Client Task Sequence - Task sequence used for deploying client Operating Systems such as Windows XP or Windows Vista
• Standard Server Task Sequence - Task sequence used for deploying server Operating Systems such as Windows Server 2003 or Windows Server 2008
• Standard Client Replace Task Sequence - This task sequence is designed to be run on the machine that is being replaced.  This task sequence should be initiated within the client Operating System and will perform a User State Migration, Boot into Windows PE, optionally perform a full system backup, and optionally securely wipe the disk
• Custom Task Sequence - This task sequence is used as a template to install Applications.  This task sequence can be customized to perform any additional actions that you would like to add

Q:  For the Client Replace task sequence, how do I make the task sequence wipe the disk?

A:  Set the variable WipeDisk = TRUE in the customsettings.ini

Q:  In BDD 2007 I modified ztidiskpart.txt to create partitions.  How do I do this in Microsoft Deployment?

A:  Microsoft deployment does not use the ztidiskpart.txt file to create the partitions.  Now, this disks are configured run time based on the task sequence parameters in the Format and Partition Disk step.  This step allows you to create multiple partitions across several disks.  If you do not want a partition formatted you can create your own custom script that calls diskpart /s and provide your own diskpart.xt file

Q:  When trying to add a custom Vista WIM to the workbench, I receive the following error:
Error during wizard processing
An unexpected error occurred while processing the wizard results.
Collection was modified; enumeration operation may not execute.

A:  There is a hotfix available that will fix this problem.  See the following KB article for more information and to retrieve the hotfix:

http://support.microsoft.com/kb/941595

Zero Touch Installation with ConfigMgr 2007

Q:  How do I use the media hook capabilities in Microsoft Deployment to deploy to unknown computers?

A: Michael Niehaus has a great blog entry and screencast on how to set up and configure this feature: http://blogs.technet.com/mniehaus/archive/2008/01/19/microsoft-deployment-configmgr-boot-media-unknown-computers-web-services.aspx

Q:  How do I configure my task sequence to capture a reference image?

A:  In the standard client task sequence there are a series of steps at the end of the task sequence that prepare the system for imaging, reboot to Windows PE, and then captures an image of the computer.  To enable these steps the following variable should be set in the customsettings.ini, Microsoft Deployment Database, ConfigMgr variables, or task sequence variables:

DoCapture = YES

Q:  Do I need to use the Microsoft Deployment database with ConfigMgr 2007?

A:  It depends.  We have made Microsoft Deployment flexible enough for you to use the Microsoft Deployment Database, customsettings.ini, ConfigMgr 2007 Task Sequence variables, Web Services, or Collection or Computer variables.  If you already have a populated database from using BDD 2007, you have the ability to use that database in conjunction with Microsoft Deployment and ConfigMgr by customizing the customsettings.ini to make the database connection.  If you choose to use the Microsoft Deployment database (or any other database) then you will need to use the Import Microsoft Deployment Task sequence to create a custom Windows PE image that includes ADO support

Q:  What is install updates offline and how do I use it?

A:  Install Updates offline is a step that can be added to the task sequence that will install Vista and Windows Server 2008 patches to the Operating System prior to the Operating System booting for the first time.  To use this step in the task sequence, you first need to create an updates package inside of ConfigMgr: http://technet.microsoft.com/en-us/library/bb680701.aspx.  After creating your updates package you need to add the Install Updates Offline step in the task sequence in the PostInstall section immediately prior to the Configure step

Zero Touch Installation with SMS 2003 OSD

Q:  Is it possible to change the text IT Organization in the task sequence dialog box?

A:  Yes!  Due to how the task sequencing engine works with SMS 2003 OSD, the process is slightly different than for Lite Touch. 

Create a variables.dat file in your package source and distribute it to your SMS 2003 Distribution Points.  The contents of that variables.dat file should be the following:

<?xml version="1.0"?>

<MediaVarList Version="4.00.5345.0000"><var name=”_SMSTSORGNAME”>My CorpName</var></MediaVarList>

That is a really long title to a recent KB article that has been posted about an issue with MDT 2008.  You can get the full details here: http://support.microsoft.com/?id=952573

Note the Applies To section should state Microsoft Deployment Toolkit 2008.

If you missed the announcement, MDT 2012 was released last week.  At that point, the Download Center was updated so that the main MDT download is now MDT 2012.  But we understand that some of you may still have a need to download MDT 2010 Update 1.  The MDT Archive download center page, at http://www.microsoft.com/en-us/download/details.aspx?id=2932, now has those files.  Note that MDT 2010 Update 1 will only be supported until April 2013, and that previous versions are no longer supported.

One of the new tasks and scripts in the Microsoft Deployment Lite Touch Task sequence is called Windows Update.  This task is disabled in the default task sequence for the Client Template.  The task runs a script called ztiwindowsupdate.wsf.  One item to note is that the current version of this script requires client access to the Internet and also does not support proxy authentication.  However if you meet those requirements, there are some really nice advantages of using this action.  Here is a brief description of what actions this script performs. 

This script will install and download updates from Windows Update http://windowsupdate.microsoft.com  and Microsoft Update http://update.microsoft.com/microsoftupdate over the Internet using the Windows Update Agent API http://msdn2.microsoft.com/en-us/library/Aa387099.aspx. By default this feature is disabled in each Task Sequence, it must be manually enabled to run, and each computer must have a connection via proxy to the Internet.  This script was designed to run on Windows XP, 2003, Vista, and should be compatible with Windows Server 2008 when released.

Most companies will already have established teams and infrastructures in place to patch newly deployed machines on the corporate network. This involves tracking the latest set of patches, drivers and updates available for each desktop configuration and determining which updates should be downloaded and installed for each configuration. If your company already has an established process, this script should not be necessary. For those teams who do not have established processes, yet wish to ensure that their images are updated when deployed, this script was designed to fill that need.

Microsoft Windows Update will automatically scan your machine and download a wide range of updates:

·         Windows Service Packs (for Windows XP, Windows 2003)

·         Many 3^rd party Drivers have been placed on Windows Update, and will be automatically installed

·         Enhanced features for Windows Vista Ultimate

·         And the latest QFE (Quick Fix Engineering) patches for your System.

·         And more!

Tip Many hardware manufacturers have placed their drivers up on Windows Update. This means for those drivers you will no longer need to maintain these drivers in your “Out of Box Drivers” directory. You can experiment by removing drivers from your distribution share to see which ones are available on Windows Update. Note that if the drivers are not included with Windows by default you should not remove “Networking” or “Storage” drivers, as the OS will require these drivers to boot and connect to windows update over the internet.

Microsoft Update will automatically scan your machine and download a wide range of updates:

·         Updates for Microsoft Office

·         Updates for Exchange Server and SQL Server

·         Updates for Visual Studio

·         Some 3^rd party (non-Microsoft) applications

·         And more!

ZTIWindowsUpdate.wsf is run multiple times during the deployment of an OS during the state restore phase. First it is run after the OS has started for the first time. This ensures that the latest updates and service packs are installed prior to installation of any applications that might require dependencies. This can include the latest version of the .NET Framework, for example. ZTIWindowsUpdate.wsf is also run after the installation of applications allowing Microsoft Update to ensure that the latest application service packs and updates have been applied. For example Microsoft Update can ensure that the latest updates are applied to Microsoft Office 2003 or 2007.

It is possible that during installation of one or more components, Windows Update might need to reboot. This script is designed to automatically reboot and resume again if the Windows Update API requires it. If this script is run and determines that the machine is fully up to date, it will exit and continue, however if after 7 unsuccessful attempts to update the machine, the script still requires a reboot, ZTIWindowsUpdate.wsf will log an error.

Installation Processing

During runtime, ZTIWindowsUpdate.wsf will perform the following:

·         Will ensure that the latest version of the Windows Update API is installed on the machine.

·         Will ensure that the latest version of the Microsoft Update binaries are installed on the machine.

·         Will search the local machine using the default query: "IsInstalled = 0 and IsHidden = 0". Meaning that it will search for all updates that apply to the local machine that are not already installed, and may or may not be normally hidden.

·         For each update found, there will be an associated ID and a KBArticle

o   The ID will be in the GUID format, example: “67da2176-5c57-4614-a514-33abbdd51f67”

o   The KBArticle will be a numerical value: “987654”

·         The script will compare the ID and the associated KBArticle against a list of known exclusions:

o   WUMU_ExcludeKB – A list of KBArticles to exclude. Any Update with a KBArticle found in this list will not be installed.

o   WUMU_ExcludeID – A list of ID’s to exclude. Any Update with an ID found in this list will not be installed.

o   In addition, any update that requires user input will be excluded, and not installed.

·         All updates that require a EULA to be approved are approved. Be sure to manually read and check each EULA before running this script in a production enviornment.

·         Each update is written to the log with the string “INSTALL” or “SKIP” if the update has been approved for installation, along with the Update ID, a short description of the update, and the KB article.

·         Then each update is downloaded and installed in batches.

·         A number of reboots may be required to continue installation.

Note  Internet Explorer 7.0 requires User Interaction, so it is not installed by ZTIWindowsUpdate.wsf

Note By default you should include 925471 in your KB exclude list to prevent Windows Vista Ultimate from installing extra language packs.

Customization

During the typical lifecycle of the ZTIWindowsUpdate.wsf tool, you will want to periodically review the list of updates being installed by the ZTIWindowsUpdate.wsf tool to verify that each update meets your teams needs and expectations. All updates are logged and recorded in the ZTIWindowsUpdate.log file generated during deployment. Each update should indicate if it was “INSTALLED”, or if the script “SKIP”’ed installation of the update, the Update ID, the name, and the KB article associated with each update. If you come across an update that you wish to exclude, you can add that entry to your CustomSettings.ini file (for Lite Touch Installations).

For example, if you wish to exclude the installation of Windows Vista Langauge Packs, you would look up the line in the ZTIWindowsUpdate.log showing where the update was identified and installed, and select either the ID, or if present, the KB article number. In this case the KBArticle number for the Language Pack is 925471. Your Custom Settings would then contain the lines:

WUMU_ExcludeKB1=925471

Yesterday we released Microsoft Deployment RC1 on the Microsoft Connect Site (http://connect.microsoft.com/).  Many of you have already started testing and providing feedback (thank you!).  There are two issues that have been uncovered this morning with the RC1 release.  An error will occur when running Configure ConfigMgr Integraion or Configure WDS PXE Filter.  The error occurs because two files were not properly signed in the release.  We will be releasing an updated build and updated files within the next 24 hours.

 If you would like to work around the issue.  You can follow the following steps:

1. Click on Start, All Programs, Accessories, Command Prompt, and then select  Run as administrator
2. You may see the screen grey and a 'User Account Control' dialog box appear. If this happens, click Continue so that the command prompt starts.

Obtain a copy of sn.exe. Sn.exe installed with Visual Studio 2005, and the .NET Framework 2.0 SDK, and therefore it may already be on the computer. If it is not on the computer, then download .NET Framework 2.0 SDK to obtain it. The x86 version of the Software development kit can be downloaded from http://www.microsoft.com/downloads/details.aspx?FamilyID=FE6F2099-B7B4-4F47-A244-C96D69C35DEC. The x64 version of the SDK can be downloaded from http://www.microsoft.com/downloads/details.aspx?FamilyId=1AEF6FCE-6E06-4B66-AFE4-9AAD3C835D3D<

Download Microsoft Deployment RC1 from Microsoft Connect Today!

Microsoft Deployment is the next version of Business Desktop Deployment (BDD) 2007. The current generation of automated deployment tools from Microsoft is increasingly unified; the same tools, utilities and products in many cases offer support and functionality for desktop and server deployment tasks. Following the trend of unified tools, the Business Desktop Deployment team has incorporated new functionality and guidance to support automated server deployment in addition to desktop deployment capabilities. This expanded feature set, with its guidance and ability to automate installation of Windows client and server operating systems – as well as applications – has effectively outgrown the current name, Business Desktop Deployment.

Microsoft Deployment unifies the tools and processes required for desktop and server deployment into a common deployment console and collection of guidance. Microsoft Deployment adds integration with recently released Microsoft deployment technologies to create a single path for image creation and deployment, including:

·         System Center Configuration Manager 2007 Operating System Deployment

·         Windows Automated Installation Kit

·         Windows Deployment Services with new multicast technology

·         Application Compatibility Toolkit 5.0

·         User State Migration Tool 3.0.1

·         2007 Office system

·         Windows Server 2008 Server Manager for automated server role definition

Enhanced Program on Microsoft Connect

This release candidate also offers an enhanced Microsoft Connect portal including technical frequently asked questions, deployment tips and tricks, a recommended 10-step program for new users to quickly get acquainted with deployment accelerators, customer-ready Solution Accelerator informational materials, and deployment-related conference presentations.

Microsoft Deployment combines the guidance and toolset from previous releases of Business Desktop Deployment and Beta releases of Windows Server Deployment. This release continues to support Zero Touch Installation (ZTI) of desktop operating systems using Systems Management Server (SMS) 2003 with the Operating System Deployment Feature Pack and adds new deployment and task sequencing capabilities for desktops and servers using System Center Configuration Manager 2007. Microsoft Deployment also continues to provide Lite Touch Installation (LTI) support without infrastructure requirements and adds capabilities for Windows Server 2003 and pre-release versions of Windows Server 2008.

New Features in Microsoft Deployment RC1

Microsoft System Center Configuration Manager 2007 support, with the following features:

·         Full support for Windows Vista, Windows XP, and Windows Server 2003 deployments with Microsoft Deployment and Configuration Manager 2007.

·         Complete integration into the Configuration Manager 2007 admin console and task sequencing capabilities.

o    Quick start Configuration Manager 2007 operating system deployments using one wizard to create needed task sequences and packages.

o    Extension of the Configuration Manager 2007 task sequencing capabilities with new actions.

·         Feature parity with BDD 2007 and SMS 2003, including dynamic package installation, automatic determination of state store location, computer backup, and database settings.

·         Installation support for computers unknown to the Configuration Manager 2007 database

·         Added support for offline patching

·         Support for offline and online language pack installation

·         Deployment monitoring:

o    Updated Management Pack for System Center Operations Manager 2007

Lite Touch Installation (LTI) support for Windows Server 2008:

·         Support for deploying Windows Server 2008 Beta 3 and potentially RC1 (to be verified after RC1 release), including support for Server Core installation options. 

·         Automated server role definition using Server Manager

Lite Touch Installation (LTI) enhancements:

·         Enhanced disk and network interface cards (NICs) configuration options, including support for static TCP/IP configuration.

·         Design changes to ease the migration from LTI to Configuration Manager 2007.

·         Support for multiple task sequence templates. New sample templates include:

o    Client template: Windows Vista, Windows XP

o    Server template: Windows Server 2003, Windows Server 2008

o    Replace scenario template

·         Ability to invoke web service calls

o    Support for web service calls from rules

o    Web services can be invoked as part of the rules processing performed by Microsoft Deployment, using new rules that can be defined in CustomSettings.ini.

·         Support for BDD 2007 upgrade or side-by-side installation with Microsoft Deployment.

Lite Touch Installation (LTI) multicast support:

·         Deployment Workbench supports multicast transmission of operating system images when performing LTI deployments from Windows Server 2008 servers that are running Windows Deployment Services.

Microsoft Deployment is available as an open beta download in the Microsoft Deployment Connection Program on Microsoft Connect.

To join the Microsoft Deployment program, click here.

If you are already participating in the program, click here to access the download page.

If you have not previously registered with Microsoft Connect, you might be required to register before you continue with the invitation process.

Desktop Deployment Center on Microsoft TechNet

System Center Configuration Manager on Microsoft TechNet

System Center Configuration Manager evaluation software on Microsoft TechNet

Windows Server 2008 on Microsoft TechNet

We are pleased to announce the release of our first update to Microsoft Deployment Toolkit 2008  (MDT 2008).  We have added two major features:  OEM preload scenarios for Lite Touch Installation and Zero Touch Installation with System Center Configuration Manager 2007 and a new management pack for System Center Operations Manager 2007 SP1.  Minor updates include bug fixes and design changes to override driver platforms as well as the ability to inject all drivers into Windows PE. 

Get MDT 2008 Update 1 and the new Quick Start Guides from the Download Center. All of the latest documentation can be found within  updated and  searchable help files.  However, if you would like a full collection of the Word documents, download it here.

Add these great deployment blogs to your list of resources: these experts are always sharing their latest knowledge around deployment.  MS Deployment, Deployment Guys, Michael Niehaus

A bug has been discovered in Microsoft Deployment where the Application List is not populating correctly if the Applications are pre-defined in the customsettings.ini or in the admin database. 

To work around this bug a small change is needed in the wizard.hta.  Line 731 in the script currently reads like this:

ElseIf oEnvironment.Item(strName & "1") <> "" then

However to fix it, modify it to read like the following:

ElseIf oEnvironment.Item(strName & "001") <> ""  then

Thanks to all of you who have brought this to our attention!

Due to changes in System Center Configuration Manager 2012 RC2, we do not support using MDT 2012 Beta 2 with the RC2 release.  A subsequent MDT 2012 RC1 release will be made available later this quarter that will fully support System Center Configuration Manager 2012 RC2.

If you have been using MDT 2012 Beta 2 and haven’t yet provided your feedback, there is still a short amount of time to get that feedback to us.  Log into http://connect.microsoft.com today!

Deploy Windows 7 and Office 2010 quickly and reliably—while boosting user satisfaction.

If you’re making the move to Windows 7 and Office 2010, you need tools and guidance to help deploy Windows and Office quickly—and do it right the first time.  Microsoft Deployment Toolkit (MDT) 2010 Update 1 Beta includes new features like Office 2010 support, the ability for users to initiate and customize their own deployments using Configuration Manager, key enhancements in driver support, and much more.

Microsoft Deployment Toolkit 2010 Update 1 Beta – Benefits

The MDT 2010 Update 1 Beta provides organizations with the following benefits:

·         Save time and money deploying Office 2010: Customers can now use MDT 2010’s comprehensive tools and guidance to efficiently manage large-scale deployments of Microsoft Office 2010.

·         Respond more effectively to user needs: MDT 2010 Update 1 includes a “User-Driven Installation” (UDI) deployment method that leverages Configuration Manager. An easy-to-use UDI Wizard allows users to initiate and customize an OS deployment on their PC that’s tailored to their individual needs.

·         More reliable driver installation: MDT 2010 Update 1 boosts the reliability of the driver installation process by detecting each driver’s true supported platforms.

These features, combined with many bug fixes and other improvements, make MDT 2010 Update 1 more reliable and flexible than ever.

Next Steps

·         Join the MDT Update 1 Beta. (Live ID required.)

·         Learn more about MDT 2010 by visiting the MDT site on TechNet.

·         Ask questions, post answers, and share your insights in the MDT Forum.

We are pleased to announce the release of MDT 2010 available for download here. 

MDT 2010 has been in planning and development for a little over a year and is our largest release to date with over 70% of our code changing since MDT 2008.  MDT 2010 has also been tested throughout our Beta and Release Candidate versions by well over 10,000 IT professionals around the world.  We appreciate all of the feedback you have given and without your help this release would not have been possible.

Michael Niehaus did a great series of blog posts on most of the new features of MDT 2010.  You can review those posts here: http://blogs.technet.com/mniehaus/search.aspx?q=MDT+2010+New+Feature&p=1

Please make sure you review the release notes for instructions on how to upgrade from MDT 2008 or one of the beta releases of MDT 2010.

THANK YOU EVERYONE FOR MAKING THIS RELEASE POSSIBLE!

If you are looking for a quick overview of how to set up the Microsoft Deployment environment, the Quick Start Guide is now available for download directly.  Based on feedback from the community, this guide offeres the walkthrough step by step instructions on how to set up Microsoft Deployment in a Lite Touch environment.

 The document can be downloaded directly from here

One thing that amazes me about this community is the number of early adopters and the incredible amount of feedback that we receive on our products.  We thank you very much for testing, implementing, and providing your feedback.  We released Microsoft Deployment almost two weeks ago and we have already seen two relatively minor bugs surface through the public newsgroups.  The following information describes these two bugs and how you can overcome them in your environment.

ZTITatoo.wsf

For those of you who may not know what ztitatoo does, this script adds entries into WMI on the client machine in order to track version information of your deployments so you can run WMI queries or SMS Reports to see some or all of the following properties:

• Deployment Method
• Deployment Type
• Deployment Timestamp
• Task Sequence ID
• Task Sequence Name
• Task Sequence Version
• OSD Package ID
• OSD Program Name
• OSD Advertisement ID

Unfortunately the ztitatoo.wsf script was not fully updated to match our new name so there are some bugs inside of the script that point to registry entries that were used with BDD 2007.

To work around this bug, go to c:\program files\Microsoft Deployment Toolkit\templates\Distribution\scripts folder and edit the ztitatoo.wsf file.  After saving the file in your templates folder make sure you copy the updated ztitattoo.wsf file to your distribution$\scripts directory.

Replace the following lines:

'//----------------------------------------------------------------------------
'//  Record the deployment details
'//----------------------------------------------------------------------------

oShell.RegWrite "HKEY_LOCAL_MACHINE\Software\Microsoft\BDD 2007\Deployment Method", oEnvironment.Item("DeploymentMethod"), "REG_SZ"
oShell.RegWrite "HKEY_LOCAL_MACHINE\Software\Microsoft\BDD 2007\Deployment Type", oEnvironment.Item("DeploymentType"), "REG_SZ"

Set oDate = CreateObject("WbemScripting.SWbemDateTime")
oDate.SetVarDate(Now())
oShell.RegWrite "HKEY_LOCAL_MACHINE\Software\Microsoft\BDD 2007\Deployment Timestamp", oDate.Value, "REG_SZ"

'//----------------------------------------------------------------------------
'//  If this is Lite Touch, populate the task sequence details
'//----------------------------------------------------------------------------

oShell.RegWrite "HKEY_LOCAL_MACHINE\Software\Microsoft\BDD 2007\Task Sequence ID", oEnvironment.Item("TaskSequenceID"), "REG_SZ"
oShell.RegWrite "HKEY_LOCAL_MACHINE\Software\Microsoft\BDD 2007\Task Sequence Name", oEnvironment.Item("TaskSequenceName"), "REG_SZ"
oShell.RegWrite "HKEY_LOCAL_MACHINE\Software\Microsoft\BDD 2007\Task Sequence Version", oEnvironment.Item("TaskSequenceVersion"), "REG_SZ"

'//----------------------------------------------------------------------------
'//  If this is OSD, populate the package ID and program name
'//----------------------------------------------------------------------------

If oEnvironment.Item("OSDPACKAGEID") <> "" then

    sValue = oEnvironment.Item("OSDSITECODE") & ":" & oEnvironment.Item("OSDPACKAGEID")   
    oShell.RegWrite "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\CM_DSLID", sValue, "REG_SZ"

    oShell.RegWrite "HKEY_LOCAL_MACHINE\Software\Microsoft\BDD 2007\OSD Package ID", oEnvironment.Item("OSDPACKAGEID")
    oShell.RegWrite "HKEY_LOCAL_MACHINE\Software\Microsoft\BDD 2007\OSD Program Name", oEnvironment.Item("OSDPROGRAMID")
    oShell.RegWrite "HKEY_LOCAL_MACHINE\Software\Microsoft\BDD 2007\OSD Advertisement ID", oEnvironment.Item("OSDADVERTID")

End if

Replace with this code:

'//----------------------------------------------------------------------------
'//  Record the deployment details
'//----------------------------------------------------------------------------

oShell.RegWrite "HKEY_LOCAL_MACHINE\Software\Microsoft\Deployment 4\Deployment Method", oEnvironment.Item("DeploymentMethod"), "REG_SZ"
oShell.RegWrite "HKEY_LOCAL_MACHINE\Software\Microsoft\Deployment 4\Deployment Type", oEnvironment.Item("DeploymentType"), "REG_SZ"

Set oDate = CreateObject("WbemScripting.SWbemDateTime")
oDate.SetVarDate(Now())
oShell.RegWrite "HKEY_LOCAL_MACHINE\Software\Microsoft\Deployment 4\Deployment Timestamp", oDate.Value, "REG_SZ"

'//----------------------------------------------------------------------------
'//  If this is Lite Touch, populate the task sequence details
'//----------------------------------------------------------------------------

oShell.RegWrite "HKEY_LOCAL_MACHINE\Software\Microsoft\Deployment 4\Task Sequence ID", oEnvironment.Item("TaskSequenceID"), "REG_SZ"
oShell.RegWrite "HKEY_LOCAL_MACHINE\Software\Microsoft\Deployment 4\Task Sequence Name", oEnvironment.Item("TaskSequenceName"), "REG_SZ"
oShell.RegWrite "HKEY_LOCAL_MACHINE\Software\Microsoft\Deployment 4\Task Sequence Version", oEnvironment.Item("TaskSequenceVersion"), "REG_SZ"

'//----------------------------------------------------------------------------
'//  If this is OSD, populate the package ID and program name
'//----------------------------------------------------------------------------

If oEnvironment.Item("OSDPACKAGEID") <> "" then

    sValue = oEnvironment.Item("OSDSITECODE") & ":" & oEnvironment.Item("OSDPACKAGEID")   
    oShell.RegWrite "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\CM_DSLID", sValue, "REG_SZ"

    oShell.RegWrite "HKEY_LOCAL_MACHINE\Software\Microsoft\Deployment 4\OSD Package ID", oEnvironment.Item("OSDPACKAGEID")
    oShell.RegWrite "HKEY_LOCAL_MACHINE\Software\Microsoft\Deployment 4\OSD Program Name", oEnvironment.Item("OSDPROGRAMID")
    oShell.RegWrite "HKEY_LOCAL_MACHINE\Software\Microsoft\Deployment 4\OSD Advertisement ID", oEnvironment.Item("OSDADVERTID")

End if

Set Diskpart Bios Compatibility Mode Task

You might have noticed that we have included a task item in our templates for Standard Client and Standard Server Lite Touch Task sequences called Set Diskpart BIOS Compatibility Mode.  This task is designed to fix the Windows PE Uberbug that is described in the following KB articles:

http://support.microsoft.com/?id=931760
http://support.microsoft.com/?id=931761

This task is disabled by default.  If you have enabled the task you have probably noticed that the task sequence fails and examining the smsts.log file shows that an "Access is denied" error occurred when running the ztisetvariable.wsf script.  The actual error message is really Incorrect Function but that does not help you solve the problem.

The problem or bug is actually within the client.xml and server.xml files that serve as templates for our Standard Client and Standard Server task sequences.

Inside of the client and server.xml files in c:\program files\Microsoft
Deployment Toolkit\templates folder, modify the following section:

Change this:
      <step type="SMS_TaskSequence_SetVariableAction" name="Set Diskpart
BIOS Compatibility Mode" description="" disable="true"
runIn="WinPEandFullOS" successCodeList="0">
        <action>cscript.exe "%SCRIPTROOT%\ZTISetVariable.wsf"</action>
        <defaultVarList>
           <variable name="VariableName" property="VariableName"
hidden="true">OSDDiskpartBiosCompatibilityMode</variable>
           <variable name="VariableValue" property="VariableValue"
hidden="true">TRUE</variable>
         </defaultVarList>
      </step>

To this:
      <step type="SMS_TaskSequence_SetVariableAction" name="Set Diskpart
BIOS Compatibility Mode" description="" disable="true"
runIn="WinPEandFullOS" successCodeList="0">
        <action>cscript.exe "%SCRIPTROOT%\ZTISetVariable.wsf"</action>
        <defaultVarList>
           <variable name="VariableName"
property="VariableName">OSDDiskpartBiosCompatibilityMode</variable>
           <variable name="VariableValue"
property="VariableValue">TRUE</variable>
         </defaultVarList>
      </step>

Essentially you are just removing the hidden="true" from the XML file.  Once
you save the XML files just delete your task sequence from the workbench and recreate it.

Again thank you very much for finding these issues and please keep the feedback coming!

Deployment 4 is the code name for the next version of Business Desktop Deployment (BDD) 2007 and unifies the tools and processes required for desktop and server deployment into a common deployment console and collection of guidance. For the thousands of IT professionals already trained on BDD 2007, Deployment 4 requires minimal extra training to perform large-scale Windows Server 2008 and Windows Server 2003 deployments, while offering a further enhanced desktop deployment experience. Deployment 4 adds integration with recently released Microsoft deployment technologies to create a single path for image creation and deployment, including:

System Center Configuration Manager 2007 Operating System Deployment Windows Automated Installation Kit Windows Deployment Services with new multicast technology Application Compatibility Toolkit 5.0 User State Migration Tool 3.0.1 Windows Server 2008 Server Manager for automated server role definition (coming soon) Enhanced Beta Program on Microsoft Connect

This Beta release also offers an enhanced Microsoft Connect portal including technical frequently asked questions, deployment tips and tricks, a recommended 10-step program for new users to quickly get acquainted with deployment accelerators, customer-ready Solution Accelerator informational materials, and deployment-related conference presentations.

Accelerator Description

Deployment 4 Beta 3 combines the guidance and toolset from previous releases of Business Desktop Deployment and Beta releases of Windows Server Deployment. This release continues to support Zero Touch Installation (ZTI) of desktop operating systems using Systems Management Server (SMS) 2003 with the Operating System Deployment Feature Pack and adds new deployment and task sequencing capabilities for desktops and servers using System Center Configuration Manager 2007. Deployment 4 also continues to provide Lite Touch Installation (LTI) support without infrastructure requirements and adds capabilities for Windows Server 2003 and pre-release versions of Windows Server 2008.

New features in Deployment 4 Beta 3

Microsoft System Center Configuration Manager 2007 support, with the following features:

Full support for Windows Vista, Windows XP, and Windows Server 2003 deployments with Deployment 4 and Configuration Manager 2007.

Complete integration into the Configuration Manager 2007 admin console and task sequencing capabilities.

Quick start Configuration Manager 2007 operating system deployments using one wizard to create needed task sequences and packages.

Extends the Configuration Manager 2007 task sequencing capabilities with new actions.

Feature parity with BDD 2007 and SMS 2003, including dynamic package installation, automatic determination of state store location, computer backup, database settings.

Lite Touch Installation (LTI) support for Windows Server 2008:

Support for deploying Windows Server 2008 Beta 3 and potentially RC0 (to be verified after RC0 release), including support for Server Core installation options. (Windows Server 2008 TAP customers only.) Lite Touch Installation (LTI) enhancements:

Enhanced disk and network interface cards (NICs) configuration options, including support for static TCP/IP configuration.

Design changes to ease the migration from LTI to Configuration Manager 2007.

Support for multiple task sequence templates. New sample templates include:

Client template: Windows Vista, Windows XP Server template: Windows Server 2003, Windows Server 2008 Replace scenario template Ability to invoke web service calls Support for web service calls from rules

Web services can be invoked as part of the rules processing performed by Deployment 4, using new rules that can be defined in CustomSettings.ini.

Support for side-by-side installation with Deployment 4 and BDD 2007 installed on the same machine.

Lite Touch Installation (LTI) multicast support:

Deployment Workbench supports multicast transmission of operating system images when performing LTI deployments from Windows Server 2008 servers that are running Windows Deployment Services.

Where to Find Deployment 4 Beta 3

Deployment 4 Beta 3 is part of the Windows Server 2008 Beta and TAP Programs. It is also available as an open beta download.

To join Deployment 4 beta 3 program, follow these steps:

Visit the Microsoft Connect Web site (http://connect.microsoft.com).

Click Invitations on the Connect menu.

You will need to sign in using a valid Windows Live ID before you can continue to the Invitations page.

Enter your Invitation ID in the box. Your invitation ID is: BDDP-QMYH-VWTH Click Go.

If you have not previously registered with Microsoft Connect, you might be required to register before you continue with the invitation process.

To download Deployment 4, click Download Now.

(If this link does not work for you, copy the full link and paste it into the Web browser address bar.)

Thanks for your participation.

Deployment 4 Team

Microsoft