Uploaded byStephen Rose
Deploying An Optimized Desktop - XP to 7 With P2V
The document discusses various options for migrating from Windows XP to Windows 7, including: 1. Upgrading sequentially from XP to Vista to Windows 7 using setup.exe, which risks applications breaking and hardware issues. 2. Doing a manual migration and install from DVD, which is slow and tedious. 3. Drive cloning based on a reference Windows 7 install, which is fast but requires managing many images. 4. Automated migration tools that move applications, drivers and user data, which is the best option but requires upfront work to package applications and manage drivers.
More Related Content
Similar to Deploying An Optimized Desktop - XP to 7 With P2V
Deploying An Optimized Desktop - XP to 7 With P2V
- 2. Before we start….somegood reference content • Your Building aLiteTouch Bootable USB Image Questions Answered! • Your Adding Office 2010 to MDT 2010 Environment Questions Answered! • Improving Your Image: Sector-Based, File-Based, and Sysprep - What Makes the Most Sense? • Part1:TermsandWindowsToolsPrimer • Part2:TheProsandCons. • Part3:Deploy-timeBuildAutomationandRecommendations • NEW -Manually Performing P2V Migration for Software Assurance http://windowsteamblog.com/windows/b/springboard/
- 3. The Myth There IsNo Way to Upgrade a Windows XP Computer to Windows 7
- 4. Channel Web Network(CRN) did this in February 2009 http://www.crn.com/software/214502800 WAIT A SECOND!!!
- 5. So how dopeople move from Windows XP to Windows 7 then?
- 6. If You StillUse Any Of These…It’s Time To Update! 6 Sector Based Imaging
- 7. Options 1 -Windows XP-to- WindowsVista-to- Windows7 using setup.exe 2- Manual migration and install from DVD 3- Drive Cloning based on a Reference Windows 7 Install 4- Automated migration with applications and drivers
- 8. But I UseOne Of These Other Leading Brands… Desktop Environment Type / Image and Build Type Traditional Thick Sector- Based Images with Limited Install-time Customization File-based Images with Build Automation for User and Hardware Customization Thick File-based Images used like Traditional Sector- Based Images with Limited Install-Time Customization Thick local client environment with user and region-specific applications, local user state and variance in hardware No Yes No Completely homogeneous environment for all users (no local user state, one language, draconian hardware standardization) – either physical or hosted Yes No Yes Thin client hardware environment with main user desktop environment hosted in the datacenter Yes Yes Yes Datacenter-hosted user-specific desktop environments No Yes No OEM Computer Manufacturing Process Yes No Yes Any Combination of the Environment Types Listed in This Column No Yes No
- 9. The Magic ofThe PiXiE Stick My boss has XP. She needs Windows 7 before she lands. I have 10 machines I want to pilot Windows 7 on. I want to enable my remote workers to migrate to Windows 7 without sending in their laptops.
- 10. Here’s The BestPart…. MDT 2010 Windows Deployment Server (WDS)
- 11.
- 12. P2V Migration forSA Customers P2V Migration will convert a user’s existing Windows XP environment to a virtual hard disk then automates the delivery of an updated and personalized Windows 7 operating system containing a virtual machine with the user’s previous Windows environment, applications and Web browser.
- 13. Planning for Windows7 and Office 2010
- 14. The Deployment Project… TestingProcess Infrastructure Remediation Image Engineering Application Management MigrationOffice Deployment Security Deployment Operations Readiness Project Process and Team Guidance Business Case for Deployment Do I need to invest in test hardware, personnel, and infrastructure? Do I replace all of my users’ hardware? Do I need to build and maintain an image for each hardware class? Are my applications going to work? Do my techs need to manually migrate everyone’s files at their desk or in the lab? Office, too? Does that mean more testing and images? How do I think about policies, data, and security now? Do my users need to send their hardware to IT or be without their PCs for a day? How is this going to impact users and the helpdesk?
- 15. …It Depends • Windowsarchitecture and deployment tools change for a reason • Test? • Hardware? • Image management? • User data migration? • Hardware specs and application requirements pretty static for 3+ years • Security updates are easier to integrate into the project
- 16. …What it Means •Refresh existing hardware- don’t wait for hardware replacement • Make the process fast and not disruptive for users • Test wisely, but don’t expect things to break as often as before • That means fewer helpdesk calls than with previous OS deployments
- 17.
- 18. Windows Application CompatibilityTools Application Compatibility Toolkit Asset Inventory Service Microsoft Assessment and Planning System Center Family Application Compatibility Toolkit Windows Compatibility Center Compatible Applications List Application Quality Cookbook Application Verifier Application Compatibility Toolkit Application Virtualization Application Quality Cookbook Virtual Legacy Windows OS (MED-V, XP Mode) Test & Mitigate AnalyzeCollect
- 19. Application Compatibility Toolkit(ACT) 5.6 Provides tools to inventory applications, hardware, and devices in the production environment Synchronizes collected inventory with current application and hardware compatibility data from Microsoft Includes tools to test and repair individual applications Version 5.6 has x64 support for inventory, compatibility fixing, and standard user account issue detection
- 20.
- 21. Office 2010 CompatibilityToolkit Application Compatibility
- 22. App Compat –Office Environment Assessment Tool Identifying the add-ins & interfacing applications
- 23. Office Migration PlanningManager (OMPM) Evaluate, identify, & migrate Office files for OpenXML migration
- 24. Group Policy Office admintemplates allow IT to control features available for end users
- 25. Office Customization Tool Builddeployment packages to fit business requirements
- 26. Windows Server 2008R2 + KMS = Office 2010, Windows XP, Vista and 7 Activation • What it provides: • Better license management • Visibility of activations • Consistent activation approach for Windows and Office • NOT monitored by Microsoft • What it requires: • Plan for your activation method • KeyManagementService (KMS) • Multiple ActivationKey(MAK)
- 27. How Is OurDemo Doing?
- 28. How Do TheyWork? ...add your ingredients, create a build, and install Microsoft Deployment Toolkit 2010 or System Center Configuration Manager 2007 Operating Systems Applications Drivers
- 29.
- 30. Improving the DeploymentCore MigrationDeliveryImaging Deployment Image Servicing and Management Add/Remove Drivers and Packages WIM and VHD Image Management User State Migration Tool Hard-link Migration Offline File Gather Improved user file detection Windows Deployment Services Multicast Multiple Stream Transfer Dynamic Driver Provisioning Solutions to Prepare and Deploy So How Does This Help You? Saves time building and updating images These are big files – we can now transfer them quickly Reduce the number of deployment servers Migrate gigabytes of user state in minutes, not hours More installs per day Minimized end user disruption Keep your existing hardware =
- 31. Application Settings Files User Accounts How Hard-Link Migrationworks? ...index files, create links to each, map links to the right spots Index of Hard-Links - files don’t move Application Settings Files User Accounts
- 32. demo Is Our DemoComplete?
- 33. Results Pros and Consof Each Method Method XP-to-Vista-to- Windows7 using setup.exe Manual migration and install from DVD Drive Cloning based on a Reference Windows 7 Install Automated migration with applications and drivers Pros • Applications migrate • If you can find the media, it’s an easy user experience • Easy to figure out • You know what you’re getting • Makes you look busy to your boss • Easy to duplicate hard drive • Fast installation via file copy or apply • Seems to work • Everyone is doing it, even OEMs • Speed • One build works for all hardware • Data moves in the process • You know which apps are installed Cons • OMG, where do I start? • Applications break • Hardware breaks • Sloooooowwww • Makes IT guys feel dirty attempting it • Slooooowwww • Clicking “next” fatigue • Lots of images to manage • User data migration can take hours • Building it can be tricky for the first time • Apps need to be packaged • Drivers need to be added/managed
- 34. So there isa double-standard for the word “upgrade” between IT pros and consumers? WAIT!!!
- 35.