Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

XP to Windows 7 with MDT


Published on

This is the Windows XP and Office 2003 to Windows 7 and Office 2010 Migration Presentation from the Get On The Bus Tour

Published in: Technology
  • accessibility Books Library allowing access to top content, including thousands of title from favorite author, plus the ability to read or download a huge selection of books for your pc or smartphone within minutes ,Download or read Ebooks here ... ......................................................................................................................... Download FULL PDF EBOOK here { }
    Are you sure you want to  Yes  No
    Your message goes here

XP to Windows 7 with MDT

  1. 1. Deploying An Optimized Windows Desktop<br />Stephen Rose <br />Sr. Community Manager – Windows Commercial <br /><br />
  2. 2. Who Am I?<br />15 years as an IT Pro<br />2 time Microsoft MVP – Setup and Deployment<br />MCSE and MCT since 1997<br />What do I do?<br />The Springboard Series on TechNet<br />Editor of the Springboard Series Insider<br />The Springboard Series on Windows® Team Blog<br />Twitter- @MSSpringboard, @stephenlrose, @thebustour<br />Manager – Windows 7 Forums on TechNet<br />Windows 7 Program Manager for the MVP program<br />Manage the STEP (Springboard Technical Experts Panel)<br />
  3. 3. The Magic of The PiXiE Stick<br />My boss has XP. She needs Windows 7 before she lands.<br />I want to enable my remote workers to migrate to Windows 7 without sending in their laptops.<br />I have 10 machines I want to pilot Windows 7 on.<br />
  4. 4.
  5. 5. Planning for Windows 7 and Office 2010<br />
  6. 6. The Deployment Project…<br />Do I need to invest in test hardware, personnel, and infrastructure?<br />How is this going to impact users and the helpdesk?<br />Do I replace all of my users’ hardware?<br />Testing Process<br />OperationsReadiness<br />InfrastructureRemediation<br />Do my users need to send their hardware to IT or be without their PCs for a day?<br />Do I need to build and maintain an image for each hardware class?<br />ProjectProcess andTeam Guidance<br />Deployment<br />Image Engineering<br />Business Casefor Deployment<br />How do I think about policies, data, and security now?<br />Are my applications going to work?<br />ApplicationManagement<br />Office, too? Does that mean more testing and images?<br />Security<br />Do my techs need to manuallymigrate everyone’s files at their desk or in the lab?<br />OfficeDeployment<br />Migration<br />
  7. 7. …It Depends<br />Windows architecture and deployment tools change for a reason<br />Test?<br />Hardware?<br />Image management?<br />User data migration?<br />Hardware specs and application requirements pretty static for 3+ years<br />Security updates are easier to integrate into the project<br />
  8. 8. …What it Means<br />Refresh existing hardware - don’t wait for hardware replacement<br />Make the process fast and not disruptive for users<br />Test wisely, but don’t expect things to break as often as before<br />That means fewer helpdesk calls than with previous OS deployments <br />
  9. 9. The Migration Process<br />Assess hardware and applications, and plan for the new features or services you want<br />Plan<br />Prepare applications, infrastructure, and images for deployment and migrate users<br />Deliver<br />Expand functionality coverage, transition applications, and manage the desktop environment<br />Operate<br />
  10. 10. Windows Application Compatibility Tools <br />Test & Mitigate<br />Analyze<br />Collect<br />Application Compatibility Toolkit<br />Asset Inventory Service<br />Microsoft Assessment and Planning<br />System Center Family<br />Application Compatibility Toolkit<br />Windows Compatibility Center<br />Compatible Applications List<br />Application Quality Cookbook<br />Application Verifier<br />Application Compatibility Toolkit<br />Application Virtualization<br />Application Quality Cookbook<br />Virtual Legacy Windows OS (MED-V, XP Mode) <br />
  11. 11. Application Compatibility Toolkit (ACT) 5.6<br />Provides tools to inventory applications, hardware, and devices in the production environment<br />Synchronizes collected inventory with current application and hardware compatibility data from Microsoft<br />Includes tools to test and repair individual applications<br />Version 5.6 (release 5/11) adds x64 support for inventory, compatibility fixing, and standard user account issue detection <br />
  12. 12. Application Compatibility Toolkit (ACT) 5.5<br />
  13. 13. Office 2010 Compatibility Toolkit<br />New!Office Environment Assessment Tool<br /> (OEAT)<br />Content<br />Application Compatibility<br />New!Office 2010 CompatibilityInspector Tool<br />Office Migration Planning Manager (OMPM)<br />
  14. 14. App Compat – Office Environment Assessment ToolIdentifying the add-ins & interfacing applications<br />
  15. 15. Office Migration Planning Manager (OMPM)Evaluate, identify, & migrate Office files for OpenXML migration<br />
  16. 16. Control Environment<br />Build Package<br />Define applications and preference<br />Bundle supporting elements, i.e. <br />Add-ins, languages, guides, etc.<br />Office Customization Tool (OCT)<br />Config.xml<br />Enforce system wide policy<br />Control Office application @ a granular level – over 4000 objects<br />Group Policies – Office admin templates<br />Realizing Office 2010 in Your Enterprise<br />Deployment<br />Many methods for delivering install packages (caching, MSI, scripts, SCE/SCCM, virtualization)<br />Deployment method influences degree of control & monitoring<br />Guidance<br />Office Resource Kit (ORK)<br />Security Guide<br />TechNet Community<br />TechNet Resource Centers<br />
  17. 17. Group PolicyOffice admin templates allow IT to control features available for end users<br />
  18. 18. Office Customization ToolBuild deployment packages to fit business requirements<br />
  19. 19. Improved Application Virtualization SupportTighter integration with Microsoft App-V<br />Potential to simplify deployment & management<br />App-V investments improve support of Office 2010*<br />Office 2010 requires App-V 4.6 available in H1 2010<br />App-V requires deployment specific sequencing<br />Features improved with App-V 4.6/Office 2010 include:<br />Outlook:<br />Fast Search using Windows Desktop Search<br />URL Protocol Handlers (Mailto, feeds, webcal(s))<br />Send to Mail integration<br />Enable advanced account configuration<br />SharePoint - Directly open/edit/save hosted documents<br />OneNote - Send to OneNote print driver<br />All - Activation model support<br />*Click to Run offerings leverage App-V<br />
  20. 20. Deployment Benefits of Application Virtualization<br />Faster Delivery of Applications at Deploy Time<br />Immediate Implementation Across Windows Versions<br />Reduced Time for Testing and Packaging<br />Minimize user disruption and speed up migration times with faster application delivery<br />Get to a single OS image more easily with less work to automate application installation and less time needed to deliver applications<br />Get value immediately as you work through your applications for Windows 7 deployment<br />Implement App-V to Windows XP and Windows Vista users before Windows 7 is fully deployed<br />Give users access to new applications before Windows 7 is delivered <br />Reduce testing times with Application Isolation<br />Speed up application packaging for deployment with App-V sequencing<br />Sequence applications for compatibility across Windows versions<br />
  21. 21. Desktop Virtualization and Compatibility Concerns<br />
  22. 22.
  23. 23. Windows Server 2008 R2 + KMS = Office 2010, Windows XP, Vista and 7 Activation<br />What it provides:<br />Better license management<br />Visibility of activations<br />Consistent activation approach for Windows and Office<br />NOT monitored by Microsoft<br />What it requires:<br />Plan for your activation method <br />Key Management Service (KMS)<br />Multiple Activation Key (MAK) <br />
  24. 24. How Is Our Demo Doing?<br />
  25. 25. How Do They Work?...add your ingredients, create a build, and install<br />
  26. 26. Microsoft Deployment Toolkit<br />MDT 2010 Beta Version<br />
  27. 27. Improving the Deployment Core<br />Migration<br />Delivery<br />Imaging<br />So How Does This Help You?<br />Saves time building and updating images<br />These are big files – we can now transfer them quickly<br />Reduce the number of deployment servers<br />Migrate gigabytes of user state in minutes, not hours<br />Deployment Image Servicing and Management<br />Add/Remove Drivers and Packages<br />WIM and VHD Image Management<br />User State Migration Tool<br />Hard-link Migration<br />Offline File Gather<br />Improved user file detection<br />Windows Deployment Services<br />Multicast<br />Multiple Stream Transfer<br />Dynamic Driver Provisioning<br />More installs per day<br />Minimized end user disruption<br />Keep your existing hardware<br />=<br />Solutions to Prepare and Deploy<br />
  28. 28. Files<br />User Accounts<br />Application Settings<br />How Hard-Link Migration works?...index files, create links to each, map links to the right spots<br />Index of Hard-Links -<br />files don’t move<br />Files<br />User Accounts<br />Application Settings<br />
  29. 29. Task-Sequenced Deployment EnginesAutomating the entire migration process<br />System Center Configuration Manager 2007 Zero Touch<br />Microsoft Deployment Toolkit (MDT) Lite Touch<br />Masks the complexity of command line tools<br />Windows OS Image<br />Device Drivers<br />Corporate Domain<br />Applications<br />User Data and Settings<br />User Data and Settings<br />Windows XP or Windows Vista<br />New OS Image Installed<br />Applications Installed<br />Drivers Installed<br />Old OS files deleted<br />Join Domain<br />Apply User State<br />Deployment Task Sequence to Same PC – Fully Automated<br />30-90 Minutes All-Up<br />
  30. 30. Demo of Using Deployment Automation<br />Demo complete? <br />
  31. 31. What Next?<br />
  32. 32.
  33. 33. © 2010 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.<br />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.<br />