Automating migration from Windows XP to Windows 8.1Kyle RosenthalTechnical Lead@WindowsPCGuy

Microsoft Virtual Academy

• Describe the components required to migrate from Windows XP to Windows 8.1

• Be able to decide which components and methods suit your migration

• Automation!

Objectives

2

• Deployment components and tools• Deployment decisions• Getting ready for deployment• Automating the deployment

Agenda

• Microsoft Deployment Toolkit• Assessment and Deployment Kit• Windows Deployment Services• System Center Configuration Manager

Deployment components and tools

• MDT 2013 provides a common console with comprehensive tools and guidance for every organizational role—making it the recommended process and toolset to automate large-scale desktop and server deployments.

• Support for LTI deployments and can plug into Configuration Manager

• Migration and deployment of: Windows 8.1 and Windows Server 2012 R2, as well as Windows 7 and Windows 8

Microsoft Deployment Toolkit 2013

• Free download!• ADK contains ACT, Deployment tools (DISM,

SIM, Windows PE, USMT, VAMT, WPT, WAT, WAS) (that’s a bunch of letters!)

• Support for LTI and UDI deployments and can plug into Configuration Manager

Assessment and Deployment Kit

• Updated version of Remote Installation Services

• Available in Windows Server 2008 and above

• New features include multi-cast and anytime join

• Deploy WIM and VHD files• Core delivery method with LTI deployments• Either GUI or command line methods

(WDSUTIL)

Windows Deployment Services

• Configuration Manager allows you to perform tasks such as:

• Deploying operating systems (ZTI)• Deploying software applications• Deploying software updates• Assessing variation from desired

configurations• Taking hardware and software inventory• Remotely administering computers

System Center Configuration Manager

• Deployment methods?• LTI (MDT, WDS)• ZTI (MDT, Configuration Manager)

• Deployment scenarios?• Replace• Upgrade• New Computer

• Migrate user settings?• USMT (version?)• Hard link migration?

• Windows Easy Transfer Wizard

Deployment decisions

• Main automation files:• Winpeshl.ini• Controls whether a customized shell is loaded in Windows PE instead of the default

Command Prompt window• Wpeinit.exe• Command-line tool that initializes Windows PE each time it boots. Wpeinit.exe

specifically installs PnP devices, processes Unattend.xml settings, and loads network resources.

• Unattend.xml• Windows Setup works with an unattended installation answer file to automate

online installations and customizations of Windows. • ZTIGather.xml• This file defines the variables and lists that are declared by MDT for the Gather step

of the Task Sequence • CustomSettings.ini• Holds the properties that are used in MDT deployments

Deployment Automation

• Use MDT to build “gold” images• Use MDT or Configuration Manager to

deploy images• Build in flexibility – use the MDT database• Build up the grocery list for software,

images, drivers and language packs• Deploy only what is needed of the above• Test!

Automation tips

• Deployment components and tools• Deployment decisions• Getting ready for deployment• Automating the deployment

Summary

• Windows ADK http://msdn.microsoft.com/en-us/library/windows/hardware/hh825486.aspx

• MDT 2013 http://technet.microsoft.com/en-US/windows/dn475741.aspx

• System Center Home http://www.microsoft.com/en-us/server-cloud/system-center/default.aspx

• The Deployment Guys http://blogs.technet.com/b/deploymentguys/

• Springboard Series http://technet.microsoft.com/en-au/windows/hh771457.aspx

Useful Links

© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.