Window Vista Deployment with Microsoft Deployment Toolkit

1. Window Vista Deployment with Microsoft Deployment Toolkit • Stu Fox • Microsoft New Zealand • http://blogs.technet.com/stufox

2. Agenda • MDT Overview • Vista Deployment – 5 minute refresh • Lite Touch Deployment of Vista • MDT Integration with Config Mgr • Troubleshooting • Some cool stuff (time permitting) 2

3. MDT Overview

4. 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

5. But What About BDD 2007? • Microsoft Deployment Toolkit 2008 is the continuation of the line, replacing BDD 2007 and Microsoft Deployment • No further updates to BDD 2007 or Microsoft Deployment are planned • BDD 2007 Update 2 was released to add Windows Vista SP1 support

6. Microsoft Deployment • Aligns with ConfigMgr • Simple upgrade from BDD 2007 • Evolutionary refinements • Aligns with ConfigMgr • Simple upgrade from BDD 2007 • Evolutionary refinements • Adds server support • New! • Fully integrated experience • Single console • Adds server support • Extends and enhances

7. MDT Features • Support for Vista SP1 • Support for server deployment • Full support for Windows Server 2003 • Support for Windows Server 2008, including Server Core installation option • Install Server Roles – Hyper-V, AD etc • Lite Touch enhancements • Support for multicast deployments with Windows Server 2008 Windows Deployment Services • Enhanced disk configuration and NIC configuration capabilities • Shift from builds to task sequences to better align with ConfigMgr • Support for multiple task sequence templates, including those that don’t deploy an operating system

8. MDT Features • System Center integration • Full 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

9. Mass Storage Driver HandlingLite Touch enhancement • Designed to make Windows XP and Windows Server 2003 deployment easier • Two separate capabilities • For unattended installs, automate the handling of TEXTMODE driver support • For 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 deployment • ConfigMgr does provide this support

10. Miscellaneous New Features • Support for installing updates from a WSUS server • Modified ZTIWindowsUpdates.wsf script • Requires configuring the WSUSServer variable • Support for creating new boot images in ConfigMgr • New wizard on the Boot Images node • Support for additional task sequence conditions in Deployment Workbench • Registry, file, installed software (MSI) • Support for OEM scenarios (partial builds)

11. Windows Vista Deployment – 5 minute refresh

12. Vista Deployment • Image based installation format (install.wim) • Multiple images, single file, single instance • Offline servicing • Hardware independent • Windows PE based setup • Unattend.xml • Replaces multiple files (unattend.txt, winbom.ini, sysprep.inf, cmdlines.txt) • WAIK • System Image Manager • ImageX

13. Vista Deployment • Configuration Passes • WindowsPE • offlineServicing • Generalize • Specialize • auditSystem • auditUser • oobeSystem

14. MDT Detail

15. MDT Requirements • Software • Windows AIK 1.1 • USMT 3.01 • Infrastructure • DNS, DHCP • Windows Deployment Services • Active Directory

16. MDT Configuration Files • Bootstrap.ini • Customsettings.ini • Scripts • Task Sequences • Unattend.xml • All stored in the distribution share

17. The Distribution Share • Distribution – shared as Distribution$ • $OEM$ • Applications • Boot • Captures • Control • Operating Systems • Out-of-Box Drivers • Packages • Scripts • Servicing • Tools

18. CustomSettings.ini • Standard INI file containing • Sections • Properties • Settings • [Settings] <- Section • Priority = Default, MACAddress • <Property> = <Setting> • Priority is a special property, defines the sequence of sections • [Settings] section is mandatory

19. 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

20. CustomSettings.ini [DefaultGateway] 172.16.0.3=AKL 172.16.1.3=AKL 172.16.111.3=WLG 172.16.112.3=WLG 172.16.116.3=CHC 172.16.117.3=CHC [AKL] UDShare=\\AKL-AM-FIL-01\MigData SLShare=\\AKL-AM-FIL-01\Logs Packages1=NYC00010-Install Packages2=NYC00011-Install Administrator1=WOODGROVEBANK\AKL Help Desk Staff [CHC] UDShare=\\CHC-AM-FIL-01\MigData SLShare=\\CHC-AM-FIL-01\Logs Administrator1=WOODGROVEBANK\CHC Help Desk Staff

21. LTI Deployment

22. Process • Build • Capture • Deploy

23. Configuring LTI – Build & Capture • Install MDT • Create the distribution share • Add OS Source Files • Add Device Drivers • Create a Task Sequence • Create a deployment point • Configure Windows PE options • Update the deployment point

24. Configuring LTI – Build & Capture • Create LTI Bootable media • Or configure WDS • Start Reference computer with LTI bootable media/PXE

25. Configuring LTI - Deploy • Add captured OS image • Create a task sequence • Start target computer with LTI bootable media/PXE

26. Demo MDT Workbench Overview

27. Demo MDT Driver Management

28. Demo MDT Lite Touch OS Management

29. Demo MDT Lite Touch Multicast Deployment

30. ZTI Deployment

31. ZTI – Build & Capture • Install MDT on Config Mgr Server • Configure integration • Install USMT 3.01 • Create folders & shares • Add OS Source Files • Add Device Drivers • Create driver packages

32. ZTI – Build & Capture (2) • Import a MDT Task Sequence • Follow the wizard • Customise the MDT Configuration Files • Distribute packages to DP’s • Customise the task sequence • Advertise the task sequence • Boot the reference computer with bootable media/PXE

33. Configuring ZTI - Deploy • Add captured OS image • Import a MDT task sequence • Follow the wizard • Customise the MDT Configuration Files • Distribute packages to DP’s • Advertise the task sequence • Start target computer with LTI bootable media/PXE

34. Demo MDT Integration with Configuration Manager

35. Demo Task Sequence Deployment

36. Other Stuff

37. Creating the MDT Database • Use deployment workbench

38. The MDT Database • Can configure based on: • Site – defined by IP gateways • Make/model – defined using WMI information • Computer – defined by MAC, asset tag, or SMBIOS UUID • Role – arbitrarily assigned to sites, make/model, and computers • Stores: • General settings • Applications to install (list) • Administrator members to add (list) • Roles to assign (list)

39. The MDT Database • Contents maintained by the Deployment Workbench MMC snap-in • Initially created by a wizard • New 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 query • Generally, 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

40. Demo Scenario • Site • Configure a specific area code for all users at a site • Make/model • Specify a package to install on all Dell Latitude D600 computers • Role • Configure an “Accounting” role that specifies a list of packages to install on all computers with that role • Computer • Assign the “Accounting” role to a computer

41. Demo Creating the MDT Database

42. Other Cool Stuff • MDT 2008 “Gather” action can query any SQL Server database • Select queries or stored procedures • Named pipes or TCP/IP • Integrated (Windows) or standard security • Columns returned should match the variable names, or can be remapped • Can also query Web Services • Can customise Wizard screens (or create your own new ones)

43. Demo Querying Another Database

44. Demo Customising the Wizard screens

45. It’s all gone horribly wrong!

46. Understanding MDT Logs • Each script generates its own log file in the log path • The log path will change based on the type of deployment and phase • Common Log Paths: • X:\MININT\SMSOSD\OSDLOGS • C:\MININT\SMSOSD\OSDLOGS • C:\_SmsTaskSequence\SMSOSD\OSDLOGS • BDD.log contains a summarized view of all other MDT log files

47. 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.

48. Operating System Logs • Windows Vista • Netsetup.log. Resides in %WinDir%\Debug; useful when troubleshooting domain join issues • Setupact.log. Resides in %WinDir%\panther; lists installation actions and is useful when investigating failed installations • Setupapi.dev.log. Resides in %WinDir%\inf; useful when investigating failed driver installations • Setuperr.log. Resides in %WinDir%\panther; details errors that occurred during installation

49. Summary • MDT is THE way to deploy Vista (and XP, and Server 2003, and Server 2008) • LTI for when you don’t have Config Mgr • ZTI for when you do (or SMS 2003) • We have only scratched the surface of what you can do • Download Microsoft Deployment Toolkit 2008 • http://www.microsoft.com/deployment

50. Resources • Blogs • Team blog: http://blogs.technet.com/msdeployment • Mike Niehaus: http://blogs.technet.com/mniehaus • Deployment Guys: http://blogs.technet.com/deploymentguys • Tools • MDT Wizard Editor: http://www.codeplex.com/MDTWizardEditor