Microsoft Deployment Toolkit Team Blog : Microsoft Deployment

Microsoft Deployment Toolkit 2008 Update 1 is now Available

msdeployment — Fri, 01 Aug 2008 02:21:00 GMT

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

The reference computer does not start Windows PE when you try to perform an image capture operation of a non-U.S. English version of a Windows operating system

msdeployment — Thu, 05 Jun 2008 21:28:00 GMT

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.

Microsoft Deployment Toolkit 2008 Source Code Released

msdeployment — Thu, 01 May 2008 23:05:00 GMT

Source Code for Microsoft Deployment Toolkit 2008 has been released

We have released Microsoft Deployment Toolkit 2008 (build number 4.1.523.0) source code for customers and partners who want to make modifications, enhancements, or bug fixes to MDT’s components. Source Code is current as of the March 2008 release of Microsoft Deployment Toolkit.

Source code for MDT 2008 can be downloaded from Microsoft download center: http://go.microsoft.com/fwlink/?LinkId=117775

How to Receive Support for Microsoft Deployment

msdeployment — Wed, 30 Jan 2008 04:00:00 GMT

We have received a number of emails and questions on how to receive support from Premier Support for Microsoft Deployment. There have been several of you who have been routed to the incorrect support person while trying to receive support for Microsoft Deployment. We apologize for your frustration and inconvenience.

To get routed to the correct support person, follow these instructions. Please note that support for Microsoft Deployment is done on via callback with response times generally ranging between 1 and 4 hours depending on the severity of your issue and the other issues in the queue.

To receive support:

a) Call the support number (1-800-936-3500) http://www.microsoft.com/services/microsoftservices/srv_premier.mspx) or

b) Submit a web incident http://support.microsoft.com/select/default.aspx?target=assistance&c1=508&

c) Clearly state that you have a BDD/MDT issue. (If you talk about deployment they will be routed to a different queue. ).

Thank you and please let us know if you have any problems receiving support in the future.

Microsoft Deployment Technical FAQ

msdeployment — Fri, 25 Jan 2008 23:10:00 GMT

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>

Bug: Applications are not Selected Properly When Set through CustomSettings.ini or through the Database

msdeployment — Sat, 15 Dec 2007 03:50:00 GMT

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!

Workarounds for two bugs in Microsoft Deployment

msdeployment — Thu, 22 Nov 2007 03:04:00 GMT

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"

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 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!

Microsoft Deployment New Feature: Windows Update

msdeployment — Wed, 14 Nov 2007 11:41:00 GMT

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

Microsoft Deployment Quick Start Guide available as a download

msdeployment — Wed, 14 Nov 2007 11:17:00 GMT

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

Microsoft Deployment FAQ

msdeployment — Sat, 03 Nov 2007 02:33:00 GMT

What is Microsoft Deployment?

Microsoft Deployment is the next version of Business Desktop Deployment (BDD) 2007. It unifies the tools and processes required for desktop and server deployment into a common deployment console and collection of guidance. Microsoft Deployment adds new deployment and task sequencing capabilities for desktops and servers using System Center Configuration Manager 2007. Microsoft Deployment also supports Zero Touch Installation of desktop operating systems using Systems Management Server 2003 with the Operating System Deployment Feature Pack. For organizations without software distribution infrastructure, Microsoft Deployment provides a Lite Touch Installation option using the included Deployment Workbench and free tools for disk imaging and deployment.

Microsoft Deployment is available on the Microsoft Download Center and guidance can be read online in the Desktop Deployment and Server Deployment TechCenters on Microsoft TechNet. For more details and links to these destinations and other related content, visit http://www.microsoft.com/deployment.

What applications and operating systems can I deploy using Microsoft Deployment?

Microsoft Deployment will deploy prerelease versions of Windows Server® 2008, Windows Server 2003, Windows® XP SP2, Windows Vista®, and the 2007 Microsoft® Office system using a variety of Microsoft tools and custom scripts. Ongoing updates to the toolset will support released versions of Windows Server 2008.

Can I use Microsoft Deployment to deploy prerelease versions of Windows Server 2008?

Yes. Microsoft Deployment and its Beta predecessor Windows Server Deployment have been part of the Windows Server 2008 Beta programs. Shortly after the official release of Windows Server 2008, an updated version of Microsoft Deployment will provide full support of Windows Server 2008.

Where do I find Microsoft Deployment?

Visit microsoft.com/deployment for all downloads and Microsoft TechNet online resources for Microsoft Deployment. The Microsoft Deployment Toolkit containing both the tools and guidance necessary for automating server and desktop deployment is currently available on the Microsoft Download Center at downloads.microsoft.com, keyword “Microsoft Deployment.”

What new features does Microsoft Deployment contain?

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.

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 Systems Management Server 2003, including dynamic package installation, automatic determination of state store location, computer backup, and database settings.
Added support for online and offline language pack installation.
Added support for offline patching.
Added support for deployment to computers unknown to the System Center Configuration Manager 2007 database.

Lite Touch Installation support for Windows Server 2008:

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

Lite Touch Installation 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 SP2
Server template: Windows Server 2003, pre-release versions of 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.
Windows Update Integration
Enhanced User State Migration

Lite Touch Installation 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.

What is the difference between Microsoft Deployment Lite Touch Installation and Zero Touch Installation?

Microsoft Deployment has been updated from Business Desktop Deployment 2007. As with previous releases, Lite Touch Installation requires a minimum set of tools and assumes that the environment does not have systems management utilities, directory services, or deployment servers in place. The highly automated Zero Touch Installation requires Microsoft System Center Configuration Manager 2007 or Microsoft Systems Management Server 2003 and Microsoft Active Directory® environment for deployment. Microsoft Deployment’s Lite Touch Installation has been updated to share most of the configuration process with Zero Touch Installation. The unified architecture makes it easier to implement both Zero Touch Installation and Lite Touch Installation together if desired, depending on the breadth of tools available in the environment.

What does Microsoft Deployment include?

Microsoft Deployment provides the assets required to deliver Windows Vista and the 2007 Microsoft Office system to the corporate desktop.

Usability

Microsoft Deployment documentation explorer graphical user interface in the Deployment Workbench
Microsoft Deployment Getting Started pages in the Deployment Workbench
Component/tool download and installation status

Included Tools and Related Guidance

Deployment Workbench
Microsoft Application Compatibility Toolkit 5.0
Microsoft User State Migration Tool 3.0.1
Microsoft Windows Enterprise Learning Framework User Kit
Windows Automated Installation Kit (WAIK) User's Guide for Windows Vista
Microsoft Windows Preinstallation Environment 2.0
Stand-alone task sequencer derived from System Center Configuration Manager 2007
Lite Touch wizards
Zero Touch Configuration engine

Technical Solution Guidance

Getting Started Guide
Plan, Build, and Deploy Guide
Volume Activation Guides
Application Management Feature Team Guide
Infrastructure Remediation Feature Team Guide
Security Feature Team Guide
Migration Feature Team Guide
Imaging Engineering Feature Team Guide
Deployment Feature Team Guide
Preparing for Lite Touch Installation Guide
Preparing for Zero Touch Installation Guide
Preparing for System Center Configuration Manager 2007
Release Readiness Feature Team Guide
Operations Readiness Feature Team Guide
Plan, Build, and Deploy Guide for Office Upgrades
Office Deployment Guide
Enterprise Learning Framework User Guide
Test Feature Team Guide

Sample and Job Aid Documents

Sample Deployment Project Plan, featuring a fictitious company archetype named Woodgrove Engineering
Woodgrove Enterprise IT Archetype
Woodgrove Business Case Document
Woodgrove Business Case Presentation
Site Deployment Project Plan
Test Feature Team Guide
Functional Specification
Migration Plan
Pilot Plan
Risk Template Tool
Test Plan
Test Specification
Test Cases Workbook
Training Plan
Vision Scope
Client Build Requirements
Application Knowledge Sheet
Communications Plan
Network and Workstation Hardware Upgrades List
Inventory Template
Assessment Template
Current State Assessment Template
The 20 Commandments of Software Packaging
Macrovision Application Preparation Roadmap
MSI Repackaging and Customization Best Practices Guide
Macrovision Brochure
Office Assessment Template
Office Budget Plan
Office Communications Plan
Office Configuration Plan
Office Current State Assessment Template
Office Distribution Plan
Office File Migration Plan
Office Functional Specification
Office Hardware Upgrades List
Office Inventory Template
Office Management Plan
Office Pilot Plan
Office Project Plan
Office Risk Template Tool
Office Test Plan
Office Training Plan
Office Vision Scope Plan

Which organizations will benefit from Microsoft Deployment?

Microsoft Deployment offers a solution targeted to all corporate customers who have as few as 25 or more networked PCs using Microsoft desktops and/or servers who need a high level of operational excellence and scalability. Microsoft Deployment is especially useful for organizations with varied network and systems management infrastructure. Organizations with low bandwidth or disconnected branch offices or remote users can also benefit from new capabilities in Microsoft Deployment to create stand-alone media-initiated operating system deployments.

Which operating system migrations does Microsoft Deployment provide guidance for?

Microsoft Deployment can be used to manage desktop migrations of Windows 2000 and later operating systems to Windows Vista. Microsoft Deployment also provides functionality for migrating Windows 2000 to Windows XP with Service Pack 2.

Do I need Microsoft Deployment if my organization has System Center Configuration Manager 2007?

System Center Configuration Manager 2007 contains several deployment enhancements compared to Systems Management Server 2003. These enhancements include native support for operating system deployment, an integrated task sequencing engine and support for standalone media-initiated deployment. If your organization has System Center Configuration Manager 2007, Microsoft Deployment provides additional value by delivering deployment project management guidance, extensions to task sequencing capabilities, three additional task sequence templates and enhanced post operating system installation provisioning tasks—including automated role installation for Windows Server 2003 deployment.

How does the workflow process ensure smooth deployment?

The Microsoft Deployment process is based on Microsoft Solutions Framework (MSF). MSF delivers proven practices for planning, building, and deploying a variety of technology solutions. It combines aspects of software design and development plus infrastructure design and deployment into a single project life cycle. With MSF, organizations can achieve the right balance of flexibility while meeting their commitments, as well as achieve speed while minimizing their risks.

Does Microsoft Deployment make it easier for implementers to get to technical content?

Microsoft Deployment contains feature team guides in two sections: guidance for project management and guidance and technical guidance for implementers. The Deployment Workbench MMC application has document navigation features built into the tool.

How does Microsoft Deployment address the biggest obstacles in deployment?

Microsoft conducted extensive research to prioritize the top “deployment blockers” that prevent efficient migration and designed Microsoft Deployment to address these:

· Application compatibility

· Data migration

· Deployment automation

· Disk Imaging

· Post installation configuration and provisioning

Which technologies are being applied in Microsoft Deployment?

Microsoft Deployment is based on deployment tools from Microsoft, as well as custom scripts.

· Hardware and software Inventory—Application Compatibility Analyzer, Microsoft SQL Server™/Microsoft SQL Server™ 2000 Desktop Engine, Microsoft Office Access™

· Application Compatibility Testing and Remediation—Application Compatibility Toolkit 5.0.2, Microsoft Virtual PC 2004

· Core Application Packaging—Office Professional Edition 2007, the Microsoft Office Resource Kit

· Imaging—ImageX, System Image Manager, Microsoft Windows Preinstallation Environment 2.0 (Windows PE 2.0), Sysprep, Deployment Workbench

· Project Management—Microsoft Project 2003

· Application Packaging—Customer choice

· Volume Activation 2.0—New methods of activation

· User Data and Settings—User State Migration Tool 3.0.1

· Deployment Process—Windows PE 2.0, Sysprep, Windows Deployment Services, Microsoft Deployment Deployment Wizard

· BitLocker™ drive encryption support for Lite Touch Install scenarios

Are there technology constraints to Microsoft Deployment?

By design, there are very few. With Microsoft Deployment, Microsoft does not assume that any network management system or specific deployment servers already exist within the organization.

Will desktop users lose all data and settings that they currently have on their computers?

No. Microsoft Deployment provides detailed, best-practice guidance about user state migration for desktops and employs the User State Migration Tool 3.0.1 to migrate the desired settings and attributes to the new desktop.

Does Microsoft Deployment support Windows XP Professional with Service Pack 2 and Windows Server 2003 installations?

Yes. Microsoft Deployment supports Windows XP SP2, Windows Vista, and Windows Server 2003 operating system installations.

How do I get Windows PE 2.0?

Windows PE 2.0 is available as part of the Windows Vista and Windows Server 2008 operating systems (boot.wim). It is also available separately in the Windows Automated Installation Kit (Windows AIK), which includes Windows PE for each platform (ia64, x64, x86) and tools to customize it using Windows System Image Manager and Windows Deployment Services. Microsoft Deployment downloads the Windows AIK from the Deployment Workbench.

What tools are used in the Microsoft Deployment accelerator for imaging?

Microsoft Deployment delivers a feature-rich MMC console, Deployment Workbench, which is built on Windows Vista and Windows Server deployment tools including: ImageX, Windows System Image Manager, Windows PE 2.0, and Windows Deployment Services. Microsoft Deployment also uses Configuration Manager 2007’s stand-alone media initiated operating system deployment feature as well as System Management Server 2003 OS Deployment Feature Pack OS Image package contents and image management.

Does Microsoft Deployment address security policies necessary for desktop and server hardware?

Microsoft Deployment helps companies understand how security policies affect the design of operating system images and also discuss strategies for hardening of desktops and servers. However, Microsoft Deployment is not intended to replace specific security solutions. In parallel with Microsoft Deployment, the Windows Vista Security Guide and Windows Server 2003 Security Guide is available on Microsoft TechNet and from the Microsoft Download Center. Future Deployment accelerator releases will integrate the 2007 Office Security Guide and the Windows Server 2008 Security Guide.

Can Microsoft Deployment be tailored to fit a company’s specific project-management methodology?

Yes. Microsoft Solutions Framework (MSF) is a life-cycle model that addresses a number of disciplines, including project management, so good project-management methodology can be used in conjunction with the solution. The solution can even be adapted to operate within a different life-cycle methodology. Although the phases, tasks, and milestones are specific to MSF, the process is generic. Any analyst with a basic knowledge of MSF and the target methodology should be able to adapt Microsoft Deployment to fit into any project-management methodology.

Who should use Microsoft Deployment and how much does it cost?

Microsoft Deployment is freely available to customers and partners to use in planning and testing their operating system migration and deployment projects for pre-release versions of Windows Server 2008, Windows Server 2003, Windows Vista, Windows XP SP2, and the 2007 Microsoft Office System. More information on Microsoft Deployment and links to downloads and related Microsoft TechNet content can be found at microsoft.com/deployment.