Curtis Sawin OSP305 Agenda Traditional Compatibility Approach Overview Modern Compatibility Approach Overview Modern Compatibility Approach Details When to use Tools Traditional Compatibility Approach ID: 491184
Download Presentation The PPT/PDF document "The Modern Compatibility Process to Acce..." is the property of its rightful owner. Permission is granted to download and print the materials on this web site for personal, non-commercial use only, and to display it on your personal computer provided you do not modify the materials and that you retain all copyright notices contained in the materials. By downloading content from our website, you accept the terms of this agreement.
Slide1
The Modern Compatibility Process to Accelerate Microsoft Office Deployment
Curtis Sawin
OSP305Slide2
Agenda
Traditional Compatibility Approach Overview
Modern Compatibility Approach Overview
Modern Compatibility
Approach Details
When to use Tools?Slide3
Traditional Compatibility Approach
Find
Review
Keep Testing
Test
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? Slide4
Traditional Compatibility Approach
Benefits
Manage Risks
Things Keep Working
Tools
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
Slide5
Traditional Compatibility Approach
Pitfalls
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
$
=
Slide6
Discover
Rationalize
Remediate
Business collaboration
Don’t over discover
Business Impact
Large Scale
Day 1 requirements
On demand
Manage
Obtain value
Future Planning
Modern
Office
Compatibility ProcessSlide7
Modern Process Overview
Post-
Deployment
Pre-
Deployment
Proactive
Reactive
When do I scan my docs for “issues?”Slide8
Pre-Deployment Activities
What to Do ProactivelySlide9
Discovery – Collecting Critical
Applications
Traditional 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-managed
Does 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 needSlide10
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 sandSlide11
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
Slide12
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/Rationalization
Using ToolsSlide13
Discovery – Example of using Bad Criteria
Rum 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 & Chocolate
13
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 Marshmallow
36
Apple Cobbler
37
Black Raspberry
38
Blueberry Cheesecake
39
Egg
Nog
40
Marble
41
Choc
Choc
Chip
42
Cotton Candy
43
Cherry Cheesecake
44
Orange Sherbet
45
Pistachio
46
Pumpkin Pie
47
Raspberry Fudge
48
Orange Pineapple
49
Strawberry Cheesecake
50Slide14
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…)
Slide15
Discovery – Using
OEAT
Discovery tool for
add-ins
and
apps that use OfficeExecuted on desktops/laptops
Under user’s context (add-ins)With admin rights (interop)Determines
count
of add-ins…not usageDetermines usage
of appsSlide16
OEAT
How-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/appsIdentify
users/computers that have important add-ins/ apps
Perform UATSlide17
demo
Curtis SawinSenior ConsultantMicrosoft
Using OEAT to Drive Your Test PlanSlide18
About 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 2010Biggest tangible benefit…...bulk conversion (ofc.exe)
OMPMSlide19
OMPM - Common (
Mis
)Uses
Inventory –
“What do I have?”
Testing – “Will it work in Office 2010?”
OMPMSlide20
Discovery/OMPM Alternatives
Scan
only recently accessed
files
Use “
SkipOldAccessedFiles
” and “
OldAccessDate” settings in Offscan.ini
Scan only critical filesProvide additional data (and reassurance)Use XCOPY.EXE to find recently used docs
OMPMSlide21
Proactive Testing
Activities
Automated Testing
Smoke Tests
User Tests
Augment skilled engineers
Tune for deployment blocking issues only
Quick test pass
Goal: find obvious issues to increase user cooperation rates
“The only test that matters”
Final validation
Supported by remediation engineeringSlide22
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
doneGoalSlide23
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?Slide24
Testing – Creating a
Testing Environment
Provision a Virtual UAT environment
Leverage a Virtual Desktop Infrastructure (VDI)
Goals:
Make it Production-like
Make it easy
Facilitates rapid (re)provisioning
Provides reach, scale
Remove testing barriersSlide25
Positioning for Post-Deployment
Preparing for Reactive RemediationSlide26
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
2010Slide27
Document Scanning/Conversion
Main
benefits
Sto
ra
ge 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 DeploymentSlide28
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
OMPMSlide29
Updating Deprecated
Code
Deprecated code
M
acros/solutions
OMPM/OCCI
Will
still
compile
No 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”Slide30
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.aspxSlide31
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 riskSlide32
Related Content
Code
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 PMSlide33
Related Resources
Office 365 TechCenter
: technet.microsoft.com/Office365Office Client TechCenter: technet.microsoft.com/office
Office, Office 365 and SharePoint Demo Area Includes:
Office 365 IT Pro Command Center
Office 365 Data Center
ExhibitOffice IT Pro Blog:
blogs.technet.com/b/office_resource_kitUnderstanding Potentially Impactful OM Changes
Using OMPM Part 1,
2, and 3Slide34
Related Resources
Office 365 TechCenter
: technet.microsoft.com/Office365Office Client TechCenter: technet.microsoft.com/office
Office, Office 365 and SharePoint Demo Area Includes:
Office 365 IT Pro Command Center
Office 365 Data Center ExhibitSlide35
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 Slide36
Complete an evaluation on CommNet and enter to win!Slide37
MS Tag
Scan the Tag
to evaluate this
session now on
myTechEd
MobileSlide38
©
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.Slide39