Windows 7 and Office 2010 migration using only what you already have and free tools

1. Windows 7 and Office 2010 migration using only what you already have and free tools Karim Cammoun & Lionel Cau Sogeti Suisse – Microsoft Infrastucture Transformation (MIT) Team Rue du Rhône 65, 1204 GENEVE karim.cammoun@sogeti.com, lionel.cau@sogeti.com

2. Agenda • Surfing on the Win7 wave & typical concerns 5‘ • Windows 7 migration tasks and tools 35‘ • Software and hardware inventory • Application compatibility • Application packaging • Image creation • Data backup and restore • Image deployment • Applications deployment • Integration • Office 2010 migration tasks and tools 10‘ • Office document scanning • Office document conversion • Office suite installation • Other migration tasks and tools 5‘ • Project management • Testing • Training • Conclusion 5‘

3. Surfing on the Win7 wave

4. 66% of all businesses already expect to migrate Forrester, October 2009

5. Within 12 months, Windows 7 will become the new standard Forrester, October 2009

6. ChangeBase Between 20 to 40% of software used by enterprises are ready for Windows 7, but the majority of applications (between 60 to 80%) may need some changes to run reliably on Windows 7 Gartner Research migration costs could be $1 035 to $1 930 per user to move from Windows XP to Windows 7, and $339 to $510 per user to move from Windows Vista to Windows 7 The typical organization requires 12 to 18 months waiting, testing, and planning before it can start deploying a new client OS. There is a lot of work to be done in preparation, and delays in getting started will only result in added costs later Market views on Windows 7 migration

7. Typicalconcerns

8. A Windows 7 migration is an infrastructure evolution looking for new features and better supportability What is the best methodology to adopt ? Several sub projects have to be handled : Hardware – required configuration, drivers availability... Administration and operating tools – inventory, patch management ... Local applications – compatibility, integration ... Office 2010 – documents and macro compatibility... any new application + communication, training, security, ... Concerns of CTOs about migration while keeping in mind all risksand impact on business activities

9. Concerns of CIOs about migration • Control • Planning using automation for reliable and predictable results • End to end automated solution • Impact of incompatibilities are minimized • Scalable solution for mass migration with minimum efforts • Business Impact • Minimum network bandwidth utilization • Least downtime for users during migration • Customised plan optimized for minimum deployment time frame • Cost • Optimized for cost, quality & scalability • No huge storage required • Factory based approach with Global Delivery Model • User Data • Minimum or no interference with user data • Avoid User data move

10. Downgrade rights for Windows 7 Professional, Ultimate and Enterprise Windows 7 Professional and Ultimate can always downgrade to Vista can downgrade to XP Professional if before Windows 7 SP1 and before 22nd of April 2011. can downgrade to XP Professional if enrolled in SA coverage Dates to remember Windows 7 release date: 22.10.2009 double-downgrade limit : 22.04.2011 Windows 7 and downgrades

11. Windows 7 migration tasks and tools

12. Weneed to know the following: Which systems are you running What are the characteristics of your systems and are they compatible with Windows 7 and Office 2010 requirements (RAM, CPU, HDD free, graphic card, network, devices) What compatibility level do you have today What compatibility level are you looking for ? What are the systems you will have to upgrade How much will it cost to reach this level Hardware inventory

13. Weneed to know the following: Which binaries belong to which applications What versions of which applications we have What levels of vendor support are provided for the application versions we have Do you already have an inventory that you like? Can you run agents on production machines? Do you know all of the applications that matter? Office? Web? Application inventory

14. Budgeting How many applications do I have? How much is it going to cost to fix them? Rationalization What business problem does this software solve? Who needs this software to do their jobs? How many users depend on this software? Testing Which operating system does this software work on? What other applications are installed on the computer? Who is a subject matter expert on the software? Deployment Where, and by whom, is the software being used? Application inventory objectives

15. Use your existing tool There's really no significant difference between standard tools As soon as youcan export data in Excel format, that'sjust fine Use othertools Microsoft AIS but thisis an online solution and is part of the MDOP pack (not free) Microsoft assessment and planning toolkitismuchbetter and free ! Perform your inventory

16. Integrated Automated Toolkit for migration planning from desktops to servers Agent-less inventory of clients, servers, applications, devices and roles Technology migration and readiness assessment and proposal generation Multi-Product Planning and Assessment Tool Hardware and device compatibility for Windows 7, Windows Server 2008 andthe 2010 Microsoft Office System Server Virtualization candidates for consolidation with Hyper-V and Microsoft Virtual Server 2005 R2 Microsoft SQL Servers Inventory Microsoft Online Services survey-based assessment Desktop Security Assessment and Forefront/NAP Readiness Power management and savings Infrastructure assessment for environment to leverage Microsoft Application Virtualization Microsoft Assessment and Planning Toolkit

17. When should you consider using ACT? When you don’t have an inventory When you have an inventory, but it doesn’t tell you all you want for your compatibility project When you calculate: ACT collection costs + automated and manual matching costs less than Current inventory + manual matching costs Application Compatibility Toolkit 5.5

18. Application compatibility experience

19. Main toolis the Application Compatibility Manager Agent-based solution (unlike MAP) Runs a service, uploads XML results to a file share Data is processed into a SQL Server database for analysis Report Online communities Othertools Setup Analysis Tool Standard User Analyser Application Compatibility Administrator (Shims) How does ACT 5.5 Work?

20. ACT Data Collection Architecture Data Collection Packages Application Compatibility Manager Inventory Collector UAC Evaluator Windows Evaluator Desktop Topology Log Collection Service ACT Database

21. Runtime evaluation: you have to run the bad code to find the issue Because it is runtime evaluation, fidelity of issue detection is very high However, some issues may already be mitigated by operating system features, such as file and registry virtualization Because they are performance-optimized (not a forensic analysis), they don’t detect everything On an application-by-application basis, they tend to do no better than chance at determining if an application, as a whole, works or does not work Be cautious in your investments in compatibility evaluators Many customers overspend for data that isn’t as valuable as they hope Strengths and Weaknesses of Compatibility Evaluators

22. Interface with software asset management: existing inventory Interface with software deployment: any additional agents deployed Interface with software manufacturers Interface with your packaging services provider (if any) Interface with end users: issues with software inventory agents Interface with project and IT management: status updates and the final report Remove redundant software immediatly The application inventory may provide youwith the visibility you need into your application portfolio to make decisions about what will be tested and supported and what should be migrated, upgraded, or standardized ACT results must be completed

23. Demonstration ACT 5.5

24. Free mitigation tools Registry virtualisation Compatibility mode XP mode Schims Application mitigation

25. Schims are created using the ACT "Compatibility Administrator " Creating these shims is actually a complex process so it should be treated as a nearly last resort and you should clearly define standards for when you’ll use this process Define standards for when to use this technique: Vendor no longer in business Internal applications Support negotiable Shims allow Windows to change behavior

26. Unfortunately Microsoft is not providingany free tools to create .msi files There's no real third party free tool widely accepted for this You will have to rely on what you already have or acquire standard solutions (AdminStudio, InstallShield, Package Studio, WinInstall) or outsourceyour packaging activities, whichmakeseven more sense if youdecided to virtualize part of your applications Applications packaging

27. ImageX a command-line tool that works with Windows image (.wim) files capture, modify, and apply images for deployment ability to mount an image to a directory, where you can browse, copy, paste, and edit the files from a classic file-management tool .wim files works at the file level, contain one or more volume images for a Windows operating system a volume image represents the captured volume or partition of a Windows operating system reduced image size due to "single instancing" non-destructive image application Sysprep isstillneeded of course you must run sysprep with the /generalize option, even if the computer has the same hardware configuration Image creation: ImageX and Sysprep

28. User State Migration Tool (USMT) 4.0 isrequired to support Windows 7 deployments safely migrates user accounts, operating system and application settings Two components ScanState scan the source computer, collect the files and settings and create a store copies files into a temporary location and then into the migration store LoadState migrates the files and settings, one at a time, from the store to a temporary location on the destination computer transfers the file to the correct location, deletes the temporary copy, and begins migrating the next file New featuresfrom USMT 3.0 Local group migration Hard-link migration Support for shadow copy Data backup and restore

29. Store user state locally (hardlink) or on Share or SMP? Retention of user state Full Backups for VIP scenario deployments What users to migrate? Domain / Local Logged in past XX days What files and settings to migrate? User Profile Exclusions – mp3 files, iso, vhd Application-based user settings – link with Application lifecycle management Define USMT requirements

30. As a rollback plan, it is often desirable to perform a full backup of the existing system Valid solutions are capture the existing system as a WIM file use your full backup third party solution Or, there's a free sysinternals utility for capturing the HDD as a vhd file: disk2vhd this capture will be treated as user's data Microsoft Virtual PC 2007 is included in the master and preconfigured An icon on the all users' Windows 7 desktop will be proposed to start the previous system as a VM Performing a backup of the previous system

31. Windows PE version 3.0 a minimal operating system designed to prepare a computer for Windows installation based on the Windows 7 kernel running in protected mode included as a part of the Windows AIK version 2.0 isrequired to deploy Windows 7 used to start a computer with no operating system (a bare-metal system partition and format hard drives copy disk images or initiate Windows Setup from a network share Deployment Image Servicing and Management (DISM) servicing offline image mounting and unmounting WIM files customizing Windows PE boot images replaces many of the tools in previous versions of the Windows AIK (Pkgmgr.exe, Intlcfg.exe and PEimg.exe) Windows PE and DISM

32. Windows Deployment Services typically, you do not use ImageX for deployment WDS hosts boot images for Pre-Boot Execution Environment (PXE) WDS enables companies to remotely administer and deploy .wim files WDS replaces the Remote Operating System Installation (RIS) deployment technology WDS\Transport Server with Multicasting (2008 Only) can image 1000’s of machines with minimal impact on the network Image deployment: WDS

33. Microsoft DeploymentToolkit Unifies the tools and processes required for desktop and server deployment into a common deployment console and collection of guidance Allows script based deployment and capture of images Logic based driver injection, application deployment and patching For Windows Server 2008 Roles can be installed and configured Centralized management of deployment points, images, task sequences, applications and drivers GUI front end that drives WAIK and underlying scripts Image deployment: MDT

34. Light Touch or ZeroTouch ? NO !

35. As Microsoft says it'sverycomplex to use SCCMwithout MDT in a Win7 migration MDT ismandatory to manage heterogenous or multilanguageenvironments migrations Zero Touch without SCCM just import a list of machines within the MDT database or simply insert this information in the customsettings.ini file MDT: powerful, proven, supported & free

36. Demonstration MDT 2010

37. Facts Applications can be deployed by MDT following the image deployment process However, this is not a replacement of an Enterprise Software Distribution tool Deploying .MSI files by means of AD onlyis not a viable option Unfortunately, there's no real free valid ESD alternative As a consequence You will have to rely on yourexisting solution If youdon't have one, thisshouldbe the opportunity to select one But, your ESD solution selectioncriteriasshouldreally not bebased on Windows 7 deploymentfeatures and should focus on pure operationalfeatures (inventory, patch management, remote control, software distribution, ...) Why ? Because, as we'veseenpreviously, deploying Windows 7 canbeentirely made in a fullyautomatedwayusingonly free, official and supported Microsoft tools Application deployment

38. Integration can be considered at multiple levels AD integration: automated in MDT Naming conventions, standard drivers, local passwordsrules: custom settings in MDT Security integration: GPOs and security agents included in the master image Operationalenvironment: ESD agent included in the master image Applications corporate portfolio: eitherincluded in the image, deployed by MDT or bemeans of the ESD agent Integration

39. Office 2010 migration tasks and tools

40. Concerns and tools are the same as with Office 2007 (User interface, Document compatibility, Macros) Most of migration risks are classic to Office suite migration projects… macros compatibility, document version changes, embedded security,... But a few of them are really specific document compatibility: OpenXML format toolbars, custom menu security Office 2010 is a projet within the migration project

41. Comprehensive environment scanning tool part of the App Compat kit on TechNet Currently installed applications and installation environment Add-ins currently in use by Office clients Programs that are not registered as add-ins but still interact with Office programs Environmental assessment (potential upgrade issues) Add-ins assessment - list of 3d party programs and information about the program’s compatibility with Office 2010 Office Environment Assessment Tool (OEAT)

42. This tool will integrate into Office VBA and VS Use information collected from OM differences and perform a simple text search (likely candidate search) for known properties and methods in the Office OM that changed It will give the user the option to comment/mark those areas in the code where text search has identified a possible OM match Summary of total lines of code scanned as well as total lines identified as potential candidates for OM changes A detailed report, with module name, line number, and links to remediation for each issue found with possibly a red/yellow flag for impact guidance Scans Declare statements for 64-bit compatibility Office 2010 Compatibility Inspector Tool (OCIT)

43. OMPM provides scanning and reporting tools Command-line execution Can scan network shares, WebDav shares, and client systems Aggregates scan results in a SQL Server or SQL Server Express database Indicates potential compatibility issues IF legacy documents are converted to the 2007 XML format Bulk conversion of the documents Scan macro code for 32-bit versus64-bit compatibility Discovery of Office Documents using the Office Migration Planning Manager (OMPM) File Server Migration PlanningManager Desktop SharePoint Server

44. Office documents compatibility experience

45. The conversion canbehandled manually (let users to perform conversion attheir pace and set a deadline) automatically (bulk conversion but with limitations) We developed specific tools to fill gaps of Microsoft conversion tools Templates conversion Old documents deletion after successful conversion (optional) Run incremental conversion (no double conversion) Embedded pictures conversion Detailed logging for trouble shooting Office document conversion

46. Config.XML compared to Customization Files (MSP for OCT) Office suite installation

47. Other migration tasks and tools

48. Microsoft tools are not free Microsoft Project Professional is a standard Excel stays its first concurrent solution Microsoft Project Server is certainly a very good solution to manage all your projects portfolio and lifecycle but it requires a certain level of maturity at the IT department level Most common free tool is Open Workbench Project management

49. Testing is necessary at the image level at the application level at the final result level(final result = a Win7 machine with everything active: applications, agents, security, GPOs... ) Testing • Unfortunately, desktop testing is not as mature as application development testing for historical reasons • Testing tends to be a manual process with simple tests cases & checklists. Results are manually consolidated inducing too much effort and errors • Putting in place simple test procedures and tools is always worthwhile • One classic free testingtool (not for automated tests but for creating tests cases & test plans, collecting tests results and to track test issues): Test Link

50. Training could be handled typically with training courses However, as an alternative and often a complement, it is common to propose to users an intranet online training training guides communications and support a reference for users after the migration itself A classic free tool for creating simple knowledge sharing sites: Mind On Site Training