Windows XP to Windows 7 using P2V Migration

Agenda

• Deploying Local P2V Migration for SA• Retro Mode Scripts• Customize MDT 2010 with Disk2VHD• Windows Virtual PC Shell Integration• Deployment Methods:

USB/DVD/WDS/SCCM OSD

Key Takeaways

• Understanding P2V Migration for SA

• When to use P2V Migration• Tools used for Deployment• Different Deployment Methods

DEMO

Jumpstart Windows XP to 7…Local P2V Migration

Key ingredients ready

MDT an infinitely customizable engine

Disk2VHD to P2V the starting OSWindows Virtual PC RemoteApp Hotfixes for everything

XP SP3 and newerFix for Hardware-Assisted

Virtualization Emulation work had started

Specific Tools Disk2VHD.exe. Sysinternals tool for performing P2V hard disk

conversion KB961742-v3.exe. Update for Windows XP with SP3 to enable

RemoteApp support Windows6.0-KB961741-x86.msu. Update for Windows Vista with

SP1 or later to enable RemoteApp Windows6.1-KB958559-x64.msu. 64-bit Windows Virtual PC for

Windows 7 Windows6.1-KB958559-x86.msu. 32-bit Windows Virtual PC for

Windows 7 Windows6.1-KB977206-x64.msu. 64-bit update to remove the

hardware-assisted virtualization prerequisites for Windows Virtual PC

Windows6.1-KB977206-x86.msu. 32-bit update to remove the hardware-assisted virtualization prerequisites for Windows Virtual PC

Here’s what we wanted to do…

(Then) new Sysinternals

Disk2VHD.exe Converts XP

to a VHD

Windows 7 is Installed with

Applications, User State and Previous

Windows XP + Apps

MDT 2010 or ConfigMgr

Initiates and Runs Fully-Automated

OS Migration Process

What is Sysinternals Disk2VHD?

• Uses Volume Snapshot capabilities introduced in Windows XP/2003

• VHD conversions can be performed online and saved to the same volume

• It’s free and very powerful

Sysinternals Disk2VHDUI for Windows Vista/2008 and newer operating systems

UI for Windows XP and Windows Server 2003

The P2V Process as added to MDT

Prepare Windows for VHD

Conversion

• 0. Validate that Disk2VHD can run (check volume size, determine storage location, check for VSS service health)

• 1. Install RemoteApp Hotfix for Seamless Application Experience

• 2. Add Runonce Commands in the Registry to auto login and execute scripts

Convert Windows XP Machine to a

VHD File

• 3. Run USMT Scanstate

• 4. Run Sysinternals Disk2VHD to convert running Windows OS to a VHD File

• 5. Save output VHD to a protected location (C:\minint folder or off the drive using USMT-like logic).

Install Windows 7 and Virtual PC

• 6. Clean install of Windows 7

• 7. Virtual PC Added to Windows 7 Installation like any hotfix (msu)

• 8. Native applications are installed via the task sequence

Make Windows XP VHD Available on the Windows 7

Host

• 9. Create Virtual Machine Configuration (VMC) File

• 10.(If local admin) Open Virtual Machine so that Integration Components are Installed for USB Support and Applications in Start menu

• 11. Add HTA script to default user profile in order to “Add Old Apps to Start Menu”

Complete Installation and Prepare for User

• 12. Run USMT Loadstate

• 13. Migration complete – first user ready to log in.

• 14. Domain-joined user runs HTA to install integration components and publish apps to start menu

But again there are challenges

1. What happens with licensing and activation?

2. Could we support something with a HAL swap in the process?

3. Could we enhance Disk2VHD and the process to make it more failsafe?

DEMO

• Enabling P2V in MDT and Configuration Manager Task Sequences

• Understanding Scripts for Migration

What happens in Replace Scenarios?

• HTA for Adding Old Applications to Windows 7 Start Menu

• Found in the default profile start menu

When does this make sense?

• “Not for every desktop, but for every organization”

• When we cannot fix or purchase a native working application

• Where a standardized Virtual PC image will not suffice

• For critical users with highly specialized desktops – and everything must return

Comparing Application Compatibility Mitigations…

1 some limited applications do not run in Virtual PC, due to performance requirements or RemoteApp (TS) issues2 standard images cater to global install-base, specialized applications would require custom images3 would require reinstallation of all applicable fixes – some may not be available anymore4 depends on how well the physical PC was managed before conversion5 depends whether VHD needs to leave the machine for computer refresh, high bandwidth for replace scenario

Limitations?

• Windows XP SA/VL media customer has reimaging rights

• VPC only supports VHD captured disks up to 127GB

• Companies may be too slow to replace Windows XP applications with Windows 7 native applications

DEMO

…Back to where we left, are we done?

Announcing…P2V Migration for Software Assurance Just Released

Top Sites and Resources

• Springboard for IT Professionals– http://www.microsoft.com/springboard

• Microsoft Solution Accelerators– http://www.microsoft.com/springboard

Windows 7 Enterprise– http

://www.microsoft.com/windows/enterprise – http://www.microsoft.com/deploynow

Thank YouEmail: aviraj@microsoft.comBlog: http://blogs.technet.com/avirajTwitter: @aviraj111

ResourcesSoftware Application

Developers

http://msdn.microsoft.com/

Infrastructure Professionals

http://technet.microsoft.com/

msdnindia technetindia @msdnindia @technetindia

© 2011 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.