The Modern Compatibility Process to Accelerate Microsoft Office Deployment Curtis Sawin

OSP305

Agenda

Traditional Compatibility Approach Overview

Modern Compatibility Approach Overview

Modern Compatibility Approach Details

When to use Tools?

Traditional Compatibility Approach

Find Review Keep TestingTest

Find all documents and applications

Review all documents and applications for issues and criticality

Test all documents and applications that meet the importance bar

Keep testing – when finished, deploy

Is this cost effective? Are you reducing risk?

Traditional Compatibility ApproachBenefits

Manage RisksThings Keep

Working ToolsPredictable?

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

Traditional Compatibility ApproachPitfalls

Lengthy evaluations

Treats docs/apps equally Costly

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

$=

Discover Rationalize Remediate

Business collaborationDon’t over discover

Business ImpactLarge Scale

Day 1 requirementsOn demand

Manage

Obtain valueFuture Planning

Modern Office Compatibility Process

Modern Process Overview

Post- Deployment

Pre- Deployment

Proactive

Reactive

When do I scan my docs for “issues?”

Pre-Deployment ActivitiesWhat to Do Proactively

Discovery – Collecting Critical ApplicationsTraditional Method

Scan/Find all of them (Inventory)

Cross off the ones that don’t meet the bar (Rationalization)

Modern Method

Partner with Business Areas

Track

Ask

Office docs/apps not traditionally IT-managedDoes it make sense to create a

list of 10 million documents, and then cross off 99.99% of that list?

Goal: “What do I care about?”

“What should be tested?”

Discovery; Not Inventory

What I have

What I need

Discovery – Determining Criticality

Apps and Documents I am accountable to keep functioning at all costs

Apps and Documents I will fix if somebody calls me about them

Apps and Documents I will never care about

Proactive Testing

Reactive Testing

Testing? Why?

Make two lines in the sand

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

Goal Risk Challenge

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

Suggestion

Make sure your tool/criteria is closely aligned with business criticality…

…or don’t use the tool!

Discovery/RationalizationUsing Tools

Discovery – Example of using Bad CriteriaRum Raisin

1

Vanilla

2

Chocolate

3

Mint Choc Chip

4

Cookies ‘n Cream

5

Pralines ‘n Cream

6

Strawberry

7

Cookie Dough

8

Butter Pecan

9

Toffee

10

Peanut Butter Cup

11

Rocky Road

12

Peanut Butter &

Chocolate13

Pistachio

14

Neapolitan

15

Cherry

16

Nutty Coconut

17

Rainbow Sherbet

18

Low Fat Vanilla

19

Lemon Sherbet

20

Choc Fudge

21

Cotton Candy

22

Pink Bubblegum

23

Choc Mousse

24

Nut Crunch

25

Black Walnut

26

Fudge Brownie

27

Banana Nut

28

Choc Almond

29

No sugar added Choc

30

Caramel Swirl

31

Pineapple Coconut

32

Fudge ripple

33

French Vanilla

34

Coffee

35

Choc Marshmallo

w36

Apple Cobbler

37

Black Raspberry

38

Blueberry Cheesecake

39

Egg Nog

40

Marble

41

Choc Choc Chip42

Cotton Candy

43

Cherry Cheesecake

44

Orange Sherbet

45

Pistachio

46

Pumpkin Pie

47

Raspberry Fudge

48

Orange Pineapple

49

Strawberry Cheesecake

50

Discovery – When/How to Use Tools?

Recommendations

To discover add-ins/interop apps

To drive your test plan

Uses installation count and usage

as criteria

Use Office Environment Assessment Tool (OEAT)

Do not use Office Planning Migration Manager (OMPM) during discovery

• OMPM finds document conversion

issues, not document issues

• Leads to drawing the wrong

conclusions

• Can be OK in limited scenarios

• (more later…)

Discovery – Using OEAT

Discovery tool for add-ins and apps that use Office

Executed on desktops/laptopsUnder user’s context (add-ins)

With admin rights (interop)

Determines count of add-ins…not usage

Determines usage of apps

OEAT How-to: Identify Your Test Users

1. Run OEAT wizard

2. Determine target computers

3. Execute OEAT on target computers

4. Compile results

5. Partner with business to identify critical

add-ins/apps

6. Identify users/computers that have important add-

ins/ apps

7. Perform UAT

demo

Curtis SawinSenior ConsultantMicrosoft

Using OEAT to Drive Your Test Plan

About OMPM

Toolset that can scan, analyze, filter, and convert documents

Identifies potential document “conversion” issuesDoes not help identify if documents will work in Office 2010

Biggest tangible benefit…

...bulk conversion (ofc.exe)

OMPM

OMPM - Common (Mis)Uses

Inventory – “What do I have?”

Testing – “Will it work in Office 2010?”

OMPM

Discovery/OMPM Alternatives

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

OMPM

Proactive Testing Activities

Automated Testing Smoke Tests User Tests

Augment skilled engineersTune for deployment blocking issues only

Quick test passGoal: find obvious issues to increase user cooperation rates

“The only test that matters”Final validationSupported by remediation engineering

Testing - Determining Compatibility

An app/document is “Compliant” with the latest

version of Office

Compatibility means that an application or a document has:

No bugs…

…on the platform you want…

…which stop you from getting work done

Goal

Testing - Determining Compatibility

How do you prove it’s “compatible”?

Who knows how to do your work?

If everything else is broken except the

parts that drive the work you do, do you

care?Do your work! The people who do the work!

Can you afford to?

Testing – Creating a Testing Environment

Provision a Virtual UAT environment

Leverage a Virtual Desktop

Infrastructure (VDI)

Goals: Make it Production-

likeMake it easy

Facilitates rapid (re)provisioning

Provides reach, scale Remove testing barriers

Positioning for Post-Deployment

Preparing for Reactive Remediation

Readying the Safety Net

Virtualization as a Mitigation

Create a virtual package/instance of Office 200x

Get the user immediately productive

Remediate with ‘normal’ priority

Prepare for Reactive Remediation

Augment your help desk (staff, knowledge)

Position your help desk to deploy safety net

Provide Interactive Guides

Deploy with Office 2010

Document Scanning/Conversion

Main benefits

Storage savings (~50%)

Leverage new features

Determine ROI for a document conversion project

Can it be cost-justified?

Leverage OMPM to identify “low risk” files

Will an archival approach suffice?

Conversion is not the goal of Deployment

OMPM Recommendations

Use for environment optimization; not deployment readiness

Bulk-convert low-risk files:“green” or “no issues” filesFiles that haven’t been modified in 30 daysFiles without macro issues

OMPM

Updating Deprecated Code

Deprecated code

Macros/solutions

OMPM/OCCI

Will still compileNo need to proactively remediate deprecated codeBut always test!

Position for future upgrades

Leverage to identify macro issuesNot all “issues” captured by these tools are “impactful”

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

ExcelWord

PowerpointOutlook

Access

0

1000

2000

3000

4000

5000

6000

7000

926

42

9

Summary of Object Model Changes - Cumu-lative

Total Items

Non-Impactful Changes

Potentially Impactful Changes

Key Takeaways

Tools provide data…not answers.

Tools Compliment

Process

Identify deployment enabling tasks and environment optimization tasks

Pre-Deployment &

Post Deployment

Prepare the Safety Net

Partner with Business areas

Discovery; Not Inventory

Manage Risk; Don’t avoid risk

Related ContentCode Title Schedule

OSP221 Microsoft Office 365 for Enterprises 6/11/2012 3:00 PM

OSP321 Active Directory Integration with Microsoft Office 365 6/12/2012 10:15 AM

OSP224 Microsoft Office 365 Management and Deployment 6/12/2012 1:30 PM

OSP223 Microsoft Office 365 for Education 6/12/2012 3:15 PM

OSP303 Supporting Microsoft Office in an Enterprise Environment 6/12/2012 3:15 PM

OSP202 Microsoft Excel: A Web Development Tool? 6/12/2012 5:00 PM

OSP306 Microsoft Office Deployment for the Elite 6/13/2012 10:15 AM

OSP325 To the Cloud, from the Trenches: Best Practices for Migrating to Microsoft Office 365 6/13/2012 1:30 PM

OSP302 Building Integrated Microsoft Office 365, SharePoint Online, and Office Solutions Using BCS and LOB Data 6/13/2012 3:15 PM

OSP323 Microsoft Office 365 Security, Privacy, and Trust 6/13/2012 5:00 PM

OSP324 Microsoft Office 365 Service Reliability and Disaster Recovery 6/14/2012 8:30 AM

OSP304 Optimized Desktop Deployment Jeopardy Live Game Show 6/14/2012 1:00 PM

OSP222 Empowering Small Businesses: Microsoft Office 365 P-Suite 6/14/2012 4:30 PM

Related Resources

Office 365 TechCenter: technet.microsoft.com/Office365

Office Client TechCenter: technet.microsoft.com/officeOffice, Office 365 and SharePoint Demo Area Includes:

Office 365 IT Pro Command CenterOffice 365 Data Center Exhibit

Office IT Pro Blog: blogs.technet.com/b/office_resource_kit

Understanding Potentially Impactful OM ChangesUsing OMPM Part 1, 2, and 3

Related Resources

Office 365 TechCenter: technet.microsoft.com/Office365

Office Client TechCenter: technet.microsoft.com/officeOffice, Office 365 and SharePoint Demo Area Includes:

Office 365 IT Pro Command CenterOffice 365 Data Center Exhibit

Resources

Connect. Share. Discuss.

http://northamerica.msteched.com

Learning

Microsoft Certification & Training Resources

www.microsoft.com/learning

TechNet

Resources for IT Professionals

http://microsoft.com/technet

Resources for Developers

http://microsoft.com/msdn

Complete an evaluation on CommNet and enter to win!

MS Tag

Scan the Tagto evaluate thissession now onmyTechEd Mobile

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