The Modern Compatibility Process to Accelerate Microsoft Office Deployment

1. OSP305 The Modern Compatibility Process to Accelerate Microsoft Office Deployment Curtis Sawin

2. Agenda • Traditional Compatibility Approach Overview • Modern Compatibility Approach Overview • Modern Compatibility Approach Details • When to use Tools?

3. Traditional Compatibility Approach Find Keep Testing Review Test     Keep testing – when finished, deploy Find all documents and applications Review all documents and applications for issues and criticality Test all documents and applications that meet the importance bar Is this cost effective?Are you reducing risk?

4. Traditional Compatibility ApproachBenefits Manage Risks Tools Things Keep Working Predictable ?  Obtain as much data as possible to assess environment IT is tasked with managing the environment, and must deliver Goal is “no surprises” during deployments Heavy use of tools/ automation to provide data

5. Traditional Compatibility ApproachPitfalls Lengthy evaluations Costly Treats docs/apps equally Tools can misguide  = $ 12-18 months of evaluation…before doing any work. Agility is hindered ROI is not evaluated against risk Tools provide technical data, not business data Additional expenses to deploy and obtain value

6. Modern Office Compatibility Process Rationalize Discover Remediate Manage  Business collaboration Don’t over discover Business Impact Large Scale Day 1 requirements On demand Obtain value Future Planning

7. Modern Process Overview Pre- Deployment Post- Deployment Proactive Reactive When do I scan my docs for “issues?”

8. Pre-Deployment Activities What to Do Proactively

9. Discovery – Collecting CriticalApplications Traditional Method Modern Method What I have • Scan/Find all of them (Inventory) • Cross off the ones that don’t meet the bar (Rationalization) • Partner with Business Areas • Track • Ask • Office docs/apps not traditionally IT-managed Does it make sense to create a list of 10 million documents, and then cross off 99.99% of that list? What I need Discovery; Not Inventory Goal: “What do I care about?” “What should be tested?”

10. Discovery – Determining Criticality Make two lines in the sand Apps and Documents I am accountable to keep functioning at all costs Proactive Testing Reactive Testing Apps and Documents I will fix if somebody calls me about them Apps and Documents I will never care about Testing? Why?

11. Discovery – Determining Criticality What makes it critical? http://blogs.msdn.com/b/cjacks/archive/2011/08/10/chris-jackson-s-formula-for-when-to-test-for-application-compatibility.aspx

12. Discovery/RationalizationUsing Tools Risk Goal Challenge Suggestion Automate: “What do I need?” Using technical criteria to derive business value adds “degrees of separation” Using any filtering introduces risk of False positives/negatives Make sure your tool/criteria is closely aligned with business criticality… …or don’t use the tool!

13. Discovery – Example of using Bad Criteria Butter Pecan 9 Toffee 10 Cookies ‘n Cream 5 Pralines ‘n Cream 6 Strawberry 7 Cookie Dough 8 Rum Raisin 1 Vanilla 2 Chocolate 3 Mint Choc Chip 4 Low Fat Vanilla 19 Lemon Sherbet 20 Neapolitan 15 Cherry 16 Nutty Coconut 17 Rainbow Sherbet 18 Peanut Butter Cup 11 Rocky Road 12 Peanut Butter & Chocolate 13 Pistachio 14 Choc Almond 29 No sugar added Choc 30 Nut Crunch 25 Black Walnut 26 Fudge Brownie 27 Banana Nut 28 Choc Fudge 21 Cotton Candy 22 Pink Bubblegum 23 Choc Mousse 24 Blueberry Cheesecake 39 Egg Nog 40 Coffee 35 Choc Marshmallow 36 Apple Cobbler 37 Black Raspberry 38 Caramel Swirl 31 Pineapple Coconut 32 Fudge ripple 33 French Vanilla 34 Orange Pineapple 49 Strawberry Cheesecake 50 Orange Sherbet 45 Pistachio 46 Pumpkin Pie 47 Raspberry Fudge 48 Marble 41 Choc Choc Chip 42 Cotton Candy 43 Cherry Cheesecake 44

14. Discovery – When/How to Use Tools? Recommendations  Do not use Office Planning Migration Manager (OMPM) during discovery Use Office Environment Assessment Tool (OEAT) • OMPM finds document conversionissues, not document issues • Leads to drawing the wrongconclusions • Can be OK in limited scenarios • (more later…) • To discover add-ins/interop apps • To drive your test plan • Uses installation count and usage as criteria

15. Discovery – UsingOEAT • Discovery tool for add-insandappsthat use Office • Executed on desktops/laptops • Under user’s context (add-ins) • With admin rights (interop) • Determinescountof add-ins…not usage • Determines usageof apps

16. OEATHow-to: Identify Your Test Users Run OEAT wizard Determine target computers Execute OEAT on target computers Compile results Partner with business to identify critical add-ins/apps Identify users/computers that have important add-ins/ apps Perform UAT

17. demo Using OEAT to Drive Your Test Plan Curtis Sawin Senior Consultant Microsoft

18. About OMPM OMPM Toolset that can scan, analyze, filter, and convert documents Identifies potential document “conversion” issues Does not help identify if documents will work in Office 2010 Biggest tangible benefit… ...bulk conversion (ofc.exe)

19. OMPM - Common (Mis)Uses OMPM Inventory – “What do I have?” Testing – “Will it work in Office 2010?”

20. Discovery/OMPM Alternatives OMPM • Scan only recently accessed files • Use “SkipOldAccessedFiles” and “OldAccessDate” settings in Offscan.ini • Scan only critical files • Provide additional data (and reassurance) • Use XCOPY.EXE to find recently used docs

21. Augment skilled engineers • Tune for deployment blocking issues only Proactive Testing Activities Smoke Tests Automated Testing User Tests • Quick test pass • Goal: find obvious issues to increase user cooperation rates • “The only test that matters” • Final validation • Supported by remediation engineering

22. Testing - DeterminingCompatibility Goal Compatibility means that an application or a document has: No bugs… …on the platform you want… …which stop you from getting work done An app/document is “Compliant” with the latest version of Office

23. Testing - Determining Compatibility If everything else is broken except the parts that drive the work you do, do you care? How do you prove it’s “compatible”? Who knows how to do your work? Do your work! The people who do the work! Can you afford to?

24. Testing – Creating a Testing Environment Goals: Make it Production-like Make it easy Leverage a Virtual Desktop Infrastructure (VDI) Provision a Virtual UAT environment Facilitates rapid (re)provisioning Provides reach, scale Remove testing barriers

25. Positioning for Post-Deployment Preparing for Reactive Remediation

26. Readying the Safety Net Virtualization as a Mitigation Prepare for Reactive Remediation • Create a virtual package/instance of Office 200x • Get the user immediately productive • Remediate with ‘normal’ priority • Augment your help desk (staff, knowledge) • Position your help desk to deploy safety net • Provide Interactive Guides • Deploy with Office 2010

27. Document Scanning/Conversion DetermineROIfor a document conversion project Can it be cost-justified? Leverage OMPM to identify “low risk” files Will an archival approach suffice? Main benefits Storage savings (~50%) Leverage new features Conversion is not the goal of Deployment

28. OMPM Recommendations OMPM Use for environment optimization; not deployment readiness Bulk-convert low-risk files:“green” or “no issues” filesFilesthat haven’t been modified in 30 daysFiles without macro issues

29. Updating Deprecated Code Will still compile No need to proactively remediate deprecated code But always test! Deprecated code Macros/solutions Position for future upgrades Leverage to identify macro issues Not all “issues” captured by these tools are “impactful” OMPM/OCCI

30. Macro Object Model Differences For more details, check out: http://blogs.technet.com/b/office_resource_kit/archive/2011/09/08/understanding-potentially-impactful-changes-in-the-office-2010-object-model.aspx

31. Key Takeaways Partner with Business areas Pre-Deployment & Post Deployment Tools Compliment Process Prepare the Safety Net Identify deployment enabling tasks and environment optimization tasks Discovery; Not Inventory Tools provide data…not answers. Manage Risk; Don’t avoid risk

32. Related Content

33. Related Resources • Office 365 TechCenter: technet.microsoft.com/Office365 • Office Client TechCenter: technet.microsoft.com/office • Office, Office 365 and SharePoint Demo Area Includes: • Office 365 IT Pro Command Center • Office 365 Data Center Exhibit • Office IT Pro Blog:blogs.technet.com/b/office_resource_kit • Understanding Potentially Impactful OM Changes • Using OMPM Part 1, 2, and 3

34. Related Resources • Office 365 TechCenter: technet.microsoft.com/Office365 • Office Client TechCenter: technet.microsoft.com/office • Office, Office 365 and SharePoint Demo Area Includes: • Office 365 IT Pro Command Center • Office 365 Data Center Exhibit

35. Resources Learning TechNet • Connect. Share. Discuss. • Microsoft Certification & Training Resources http://northamerica.msteched.com www.microsoft.com/learning • Resources for IT Professionals • Resources for Developers http://microsoft.com/technet http://microsoft.com/msdn

36. Complete an evaluation on CommNet and enter to win!

37. MS Tag Scan the Tag to evaluate this session now on myTechEd Mobile

38. © 2012 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.