Window Vista Deployment with Microsoft Deployment ToolkitStu FoxMicrosoft New Zealandhttp://blogs.technet.com/stufox

Agenda

MDT OverviewVista Deployment – 5 minute refreshLite Touch Deployment of VistaMDT Integration with Config MgrTroubleshootingSome cool stuff (time permitting)

2

MDT Overview

What’s an MDT?

Not just another TLA

A Solution Accelerator which provides THE tools and processes to deploy Vista

(And XP, Server 2003, Server 2008)

The latest evolution of BDD

BDD 2007

Microsoft Deployment

Microsoft Deployment Toolkit 2008

But What About BDD 2007?

Microsoft Deployment Toolkit 2008 is the continuation of the line, replacing BDD 2007 and Microsoft DeploymentNo further updates to BDD 2007 or Microsoft Deployment are planned

BDD 2007 Update 2 was released to add Windows Vista SP1 support

Microsoft Deployment

Microsoft Deployment

Lite Touch Zero Touchwith SMS 2003

Zero Touchwith Configuration

Manager 2007

• Aligns with ConfigMgr• Simple upgrade from

BDD 2007• Evolutionary

refinements• Adds server support

• Aligns with ConfigMgr

• Simple upgrade from BDD 2007

• Evolutionary refinements

Leverages core deployment tools

• New!• Fully integrated

experience• Single console• Adds server support• Extends and

enhances

Provides process and tool guidance

MDT FeaturesSupport for Vista SP1Support for server deployment

Full support for Windows Server 2003Support for Windows Server 2008, including Server Core installation optionInstall Server Roles – Hyper-V, AD etc

Lite Touch enhancementsSupport for multicast deployments with Windows Server 2008 Windows Deployment ServicesEnhanced disk configuration and NIC configuration capabilitiesShift from builds to task sequences to better align with ConfigMgrSupport for multiple task sequence templates, including those that don’t deploy an operating system

MDT Features

System Center integrationFull support for ConfigMgr 2007 deployments, adding additional capabilities and features

Dynamic user state determination, unknown computer support, offline patching, language packs, etc.

Seamless integration into the ConfigMgr 2007 MMC, with new wizards, actions, and templates

A single console for (almost) all operations

Support for OpsMgr 2007 via a new management pack

Mass Storage Driver HandlingLite Touch enhancement

Designed to make Windows XP and Windows Server 2003 deployment easierTwo separate capabilities

For unattended installs, automate the handling of TEXTMODE driver supportFor image deployments, automate the population of the sysprep.inf [SysprepMassStorage] section for all available mass storage drivers

With Lite Touch, you still need to build a new image to support additional mass storage drivers

No support for injecting mass storage drivers during an XP/2003 image deploymentConfigMgr does provide this support

Miscellaneous New Features

Support for installing updates from a WSUS server

Modified ZTIWindowsUpdates.wsf scriptRequires configuring the WSUSServer variable

Support for creating new boot images in ConfigMgr

New wizard on the Boot Images nodeSupport for additional task sequence conditions in Deployment Workbench

Registry, file, installed software (MSI)Support for OEM scenarios (partial builds)

Windows Vista Deployment – 5 minute refresh

Vista Deployment

Image based installation format (install.wim)

Multiple images, single file, single instanceOffline servicingHardware independent

Windows PE based setupUnattend.xml

Replaces multiple files (unattend.txt, winbom.ini, sysprep.inf, cmdlines.txt)

WAIKSystem Image ManagerImageX

Vista Deployment

Configuration PassesWindowsPEofflineServicingGeneralizeSpecializeauditSystemauditUseroobeSystem

MDT Detail

MDT Requirements

SoftwareWindows AIK 1.1USMT 3.01

InfrastructureDNS, DHCPWindows Deployment ServicesActive Directory

MDT Configuration Files

Bootstrap.iniCustomsettings.iniScriptsTask SequencesUnattend.xml

All stored in the distribution share

The Distribution Share

Distribution – shared as Distribution$$OEM$ApplicationsBootCapturesControlOperating SystemsOut-of-Box DriversPackagesScriptsServicingTools

CustomSettings.ini

Standard INI file containingSectionsPropertiesSettings

[Settings] <- SectionPriority = Default, MACAddress

<Property> = <Setting>Priority is a special property, defines the sequence of sections

[Settings] section is mandatory

CustomSettings.ini

Sections can be applied to groups of computers or individual computers

[DefaultGateway][LocalDataName][Custom Section]

[DefaultGateway]LocalDataName

E.g. [02:00:54:55:4E:01]E.g. [HP]

CustomSection

CustomSettings.ini[DefaultGateway]172.16.0.3=AKL172.16.1.3=AKL172.16.111.3=WLG172.16.112.3=WLG172.16.116.3=CHC172.16.117.3=CHC [AKL]UDShare=\\AKL-AM-FIL-01\MigDataSLShare=\\AKL-AM-FIL-01\LogsPackages1=NYC00010-InstallPackages2=NYC00011-InstallAdministrator1=WOODGROVEBANK\AKL Help Desk Staff [CHC]UDShare=\\CHC-AM-FIL-01\MigDataSLShare=\\CHC-AM-FIL-01\LogsAdministrator1=WOODGROVEBANK\CHC Help Desk Staff

LTI Deployment

Process

BuildCaptureDeploy

Configuring LTI – Build & Capture

Install MDTCreate the distribution shareAdd OS Source FilesAdd Device DriversCreate a Task SequenceCreate a deployment pointConfigure Windows PE optionsUpdate the deployment point

Configuring LTI – Build & Capture

Create LTI Bootable media Or configure WDSStart Reference computer with LTI bootable media/PXE

Configuring LTI - Deploy

Add captured OS imageCreate a task sequenceStart target computer with LTI bootable media/PXE

Demo

MDT Workbench Overview

Demo

MDT Driver Management

Demo

MDT Lite Touch OS Management

Demo

MDT Lite Touch Multicast Deployment

ZTI Deployment

ZTI – Build & Capture

Install MDT on Config Mgr ServerConfigure integrationInstall USMT 3.01Create folders & sharesAdd OS Source FilesAdd Device DriversCreate driver packages

ZTI – Build & Capture (2)

Import a MDT Task SequenceFollow the wizardCustomise the MDT Configuration FilesDistribute packages to DP’sCustomise the task sequenceAdvertise the task sequenceBoot the reference computer with bootable media/PXE

Configuring ZTI - Deploy

Add captured OS imageImport a MDT task sequenceFollow the wizardCustomise the MDT Configuration FilesDistribute packages to DP’sAdvertise the task sequenceStart target computer with LTI bootable media/PXE

Demo

MDT Integration with Configuration Manager

Demo

Task Sequence Deployment

Other Stuff

Creating the MDT Database

Use deployment workbench

The MDT Database

Can configure based on:Site – defined by IP gatewaysMake/model – defined using WMI informationComputer – defined by MAC, asset tag, or SMBIOS UUIDRole – arbitrarily assigned to sites, make/model, and computers

Stores:General settingsApplications to install (list)Administrator members to add (list) Roles to assign (list)

The MDT Database

Contents maintained by the Deployment Workbench MMC snap-in

Initially created by a wizardNew entries added by a wizard

Queries performed by “Gather” step early in the task sequence

Wizard to add the rules to CustomSettings.ini, indicating what to queryGenerally, first value found wins, so order of queries might be important (and computer and collection variables would normally win)Global variables set as a result of the queries

Global variables consumed by the task sequence steps as they execute

Demo Scenario

SiteConfigure a specific area code for all users at a site

Make/modelSpecify a package to install on all Dell Latitude D600 computers

RoleConfigure an “Accounting” role that specifies a list of packages to install on all computers with that role

ComputerAssign the “Accounting” role to a computer

Demo

Creating the MDT Database

Other Cool Stuff

MDT 2008 “Gather” action can query any SQL Server database

Select queries or stored proceduresNamed pipes or TCP/IPIntegrated (Windows) or standard securityColumns returned should match the variable names, or can be remapped

Can also query Web ServicesCan customise Wizard screens (or create your own new ones)

Demo

Querying Another Database

Demo

Customising the Wizard screens

It’s all gone horribly wrong!

Understanding MDT Logs

Each script generates its own log file in the log pathThe log path will change based on the type of deployment and phaseCommon Log Paths:

X:\MININT\SMSOSD\OSDLOGSC:\MININT\SMSOSD\OSDLOGSC:\_SmsTaskSequence\SMSOSD\OSDLOGS

BDD.log contains a summarized view of all other MDT log files

Task Sequencer Logs

SMSTS.log. Created by the Task Sequencer and describes all Task Sequencer transactions. Depending on the deployment scenario, it may reside in %TEMP%, %WINDIR%\System32\ccm\logs, C:\_SmsTaskSequence\Logs, or C:\SMSTSLog.

Operating System LogsWindows Vista

Netsetup.log. Resides in %WINDIR%\Debug; useful when troubleshooting domain join issuesSetupact.log. Resides in %WINDIR%\panther; lists installation actions and is useful when investigating failed installationsSetupapi.dev.log. Resides in %WINDIR%\inf; useful when investigating failed driver installationsSetuperr.log. Resides in %WINDIR%\panther; details errors that occurred during installation

Summary

MDT is THE way to deploy Vista (and XP, and Server 2003, and Server 2008)LTI for when you don’t have Config MgrZTI for when you do (or SMS 2003)

We have only scratched the surface of what you can doDownload Microsoft Deployment Toolkit 2008

http://www.microsoft.com/deployment

Resources

BlogsTeam blog: http://blogs.technet.com/msdeploymentMike Niehaus: http://blogs.technet.com/mniehausDeployment Guys: http://blogs.technet.com/deploymentguys

ToolsMDT Wizard Editor: http://www.codeplex.com/MDTWizardEditor