2. Mark Aslett Microsoft maslett@microsoft.com Introduction to Application Compatibility

3. Why do we need to consider Application Compatibility? Application Compatibility Windows 7 brings… Enhanced security Reliability improvements Some existing features updated New features are introduced But… Some features removed Tighter control over application execution

4. Getting Started with Application Compatibility Planning for Application Compatibility Understand some the tools that are available Introduction to Application Compatibility Toolkit tools Session Objectives

5. Don’t underestimate the work ahead… But it’s NOT an impossible challenge Where To Start? Start with a Vision and Scope Have a clear goals for the upgrade project Define you application management strategy Get support from your organization and find a project sponsor

6. Planning the Project

7. User Manual Test Application Compatibility Project Plan Start Automated Analysis Assessment Initial Budget ACT Inventory Refine Budget Rationalize Refine Budget Detailed Automated Analysis App Install Green? Install Manual Test App Run Green? Remediate Runtime Manual Test Ready To Deploy Finish Yes No

8. Use your organizations tool of choice if you trust the data… or consider Microsoft ACT Application Auditing Collect Application Details Division or organization Role Usage But don’t try and collect every last piece of information

9. Filter applications early and inexpensively Analyze Audit Information Start Remove Duplicates Remove Multiple Versions Remove Hardware Apps Remove Obvious Noise Involve Business Owners Finish

10. Categorize Applications Prioritize Applications Business Critical – Money is lost without these Important – The business cannot run for long without them Nice to have – Having them will keep people happy Unimportant – Should they still be in the list? Use Categories to drive remediation behavior Business Critical - Unbounded by time Important – 16 hours? Nice to have – 8 hours? Unimportant – 0 hours!

11. Application Compatibility Tools

12. Which one tool solves all your compatibility problems? Application Compatibility Tools App-V MED-V ACT 5.6 XP Mode Static Analysis Tools Disable UAC VDI Remote Desktop Shims

13. Just causes a lot of prompts and should be turned off? User Account Control UAC is an aid to running all users as a Standard User Helps compatibility issues with file and registry virtualization Disabling UAC turns off Internet Explorer Protected Mode Protected Mode causes IE to run in a restricted context Low integrity level prevents malicious code making system changes

14. Microsoft App-V Application Virtualization Does NOT isolate applications from the OS Isolates applications from one another Possible to shim sequenced applications Other benefits New licensing and application deployment options Key part of a bigger virtualization vision

15. Microsoft Enterprise Desktop Virtualization MED-V Machine virtualization solution Application actually run on a Windows XP OS User sees only the application window Centrally managed Part of the Microsoft Desktop Optimization Pack Small businesses can use XP Mode Compelling IE6 application compatibility story Seamless redirection of the browser

16. Strengths of ACT 5.6 Inventory tool Application runtime analysis Compatibility agent data is useful when used at the right time Shim creation and management Standard User Analyzer Microsoft ACT 5.6

17. User Manual Test ACT and the Project Plan Start Automated Analysis Assessment Initial Budget ACT Inventory Refine Budget Rationalize Refine Budget Detailed Automated Analysis App Install Green? Install Manual Test App Run Green? Remediate Runtime Manual Test Ready To Deploy Finish Yes No

18. A number of tools available from partners Run offline against applications so can test 1000’s of rules Can run detailed analysis against application installation processes Can be powerful tools in the hands of expert engineers Not a replacement for skilled individuals Can be used to provide an early assessment of a large number of applications Static Analysis

19. User Manual Test Static Analysis and the Project Plan Start Automated Analysis Assessment Initial Budget ACT Inventory Refine Budget Rationalize Refine Budget Detailed Automated Analysis App Install Green? Install Manual Test App Run Green? Remediate Runtime Manual Test Ready To Deploy Finish Yes No

20. Fixing Broken Applications

21. Does my application need to be supported? How Do I Fix My Apps? Vendor update required Run in MED-V Access through Remote Desktop Services Fix it in house? Redevelop the application Add missing component to OS image Correct hardcoded paths Create and deploy custom Shim database

22. Remediation Strategy for Failed Apps Start App Support Needed Yes No Upgrade from vendor Patch Available Yes App Is Required Offline Run from remote desktop No Requires IE6 or XP Yes Deploy MED-V In House App Yes No Re- develop Yes Create a Shim Deploy Application

23. What is Application Compatibility Testing? Testing Compatibility Fixes An application that is compatible will meet the following criteria: Has no bugs… on the target platform… that prevent the application being used for its business purpose What’s then end goal? or

24. Application Shims

25. Fixing Applications - Shims How Shims Work ApplicationApplication WindowsWindows Import Function ShimmedFunctionShimmedFunction ExportFunctionExportFunction Shim DLL

26. Great for the following bugs When to Use Shims Incorrect Windows version checks Writing to HKCR at runtime Unnecessary checks for “Is User an Admin?” Writing to WRP-protected keys and files Windows thinks the application is an installer Some file/registry redirections

27. Demo Standard User Analyzer and Shims

28. Treat Application Compatibility as you would any other project Communicate with the business and users Plan, audit and rationalize early on Use the right tools at the right time and don’t rely on a single tool Stay focused on the end goal, don’t try and fix everything Key Takeaways

29. © 2008 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.