Find Find all documents and applications Review Review all documents and applications for issues and criticality Is this cost effective? Test Keep Testing Test all documents and applications that meet the importance.
Download ReportTranscript Find Find all documents and applications Review Review all documents and applications for issues and criticality Is this cost effective? Test Keep Testing Test all documents and applications that meet the importance.
Find Find all documents and applications Review Review all documents and applications for issues and criticality Is this cost effective? Test Keep Testing Test all documents and applications that meet the importance bar Keep testing – when finished, deploy Are you reducing risk? Benefits ? Manage Risks Obtain as much data as possible to assess environment Things Keep Working IT is tasked with managing the environment, and must deliver Predictable Goal is “no surprises” during deployments Tools Heavy use of tools/ automation to provide data Pitfalls $ Lengthy evaluations 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 Costly Additional expenses to deploy and obtain value Modern Discover Rationalize Remediate Manage Business collaboration Don’t over discover Business Impact Large Scale Day 1 requirements On demand Obtain value Future Planning PreDeployment Proactive When do I scan my docs for “issues?” Reactive PostDeployment Critical Traditional Method Modern Method Partner with Business Areas Scan/Find all of them (Inventory) Cross off the ones that don’t meet the bar (Rationalization) Does it make sense to create a list of 10 million documents, and then cross off 99.99% of that list? Goal: Track Ask Office docs/apps not traditionally ITmanaged Discovery; Not Inventory “What do I care about?” “What should be tested?” Criticality Make two lines in the sand Apps and Documents I am accountable to keep functioning at all costs Proactive Testing Apps and Documents I will fix if somebody calls me about them Reactive Testing Apps and Documents I will never care about Testing? Why? 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 Using Tools Goal Automate: “What do I need?” Risk Using technical criteria to derive business value adds “degrees of separation” Challenge 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! Using Bad Criteria Rum Raisin Vanilla Chocolate 1 2 3 Peanut Butter Cup 11 Rocky Road Choc Fudge Cotton Candy 21 22 Caramel Swirl 31 Marble 41 Mint Choc Chip 4 Cookies ‘n Cream 5 Pralines ‘n Cream 6 Strawberry Cookie Dough Butter Pecan Toffee 7 8 9 10 Peanut Butter & Chocolate 13 Pistachio Neapolitan Cherry 14 15 16 Nutty Coconut 17 Rainbow Sherbet 18 Low Fat Vanilla 19 Lemon Sherbet 20 Pink Bubblegum 23 Choc Mousse Nut Crunch Black Walnut Banana Nut Choc Almond 24 25 26 Fudge Brownie 27 28 29 No sugar added Choc 30 Pineapple Coconut 32 Fudge ripple French Vanilla Coffee Apple Cobbler 34 35 Black Raspberry 38 Blueberry Cheesecake 39 Egg Nog 33 Choc Marshmallow 36 Choc Choc Chip 42 Cotton Candy Cherry Cheesecake 44 Orange Sherbet 45 Pistachio Pumpkin Pie 46 47 Raspberry Fudge 48 Orange Pineapple 49 Strawberry Cheesecake 50 12 43 37 40 Tools? Recommendations Use Office Environment Assessment Tool (OEAT) To discover add-ins/interop apps To drive your test plan Uses installation count and usage as criteria 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…) Using OEAT Discovery tool for add-ins and apps that use Office Executed on desktops/laptops Under user’s context (add-ins) With admin rights (interop) Determines count of add-ins…not usage Determines usage of apps OEAT 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 OEAT User’s Guide: http://technet.microsoft.com/en-us/library/ee683865.aspx OMPM convert scan, analyze, filter bulk conversion (Mis)Uses OMPM Alternatives OMPM only recently accessed SkipOldAccessedFiles” and “OldAccessDate” settings in Offscan.ini critical Testing Automated Testing Augment skilled engineers Tune for deployment blocking issues only Smoke Tests Quick test pass Goal: find obvious issues to increase user cooperation rates User Tests “The only test that matters” Final validation Supported by remediation engineering Determining Goal 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 Determining How do you prove it’s “compatible”? Who knows how to do your work? Do your work! The people who do the work! If everything else is broken except the parts that drive the work you do, do you care? Can you afford to? Testing Environment Provision a Virtual UAT environment Facilitates rapid (re)provisioning Leverage a Virtual Desktop Infrastructure (VDI) Goals: Make it Production-like Make it easy Provides reach, scale Remove testing barriers Virtualization as a Mitigation Prepare for Reactive Remediation Create a virtual package/instance of Office 200x Augment your help desk (staff, knowledge) Get the user immediately productive Position your help desk to deploy safety net Remediate with ‘normal’ priority Provide Interactive Guides Deploy with Office 2010 Main benefits Sto 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 Deployment OMPM environment optimization low-risk Bulk Conversion 1. Scan file shares/SharePoint libraries 2. Create OMPM DB 3. Import scan results into OMPM DB 4. Create “low risk” filter 5. Determine estimated storage savings* 6. Export filtered list to XML 7. Identify storage to hold converted files 8. Use OFC.exe/XML to convert files 9. Replace legacy files/Clean up How-to OFC.exe creates a copy of a file, and converts the copy http://blogs.technet.com/b/office_resource_kit/archive/2012/01/09/using-ompm-part-1-identifyingdocument-conversion-candidates-and-estimating-storage-savings.aspx Deprecated Deprecated code Will still compile No need to proactively remediate deprecated code But always test! Macros/solutions Position for future upgrades OMPM/OCCI Leverage to identify macro issues Not all “issues” captured by these tools are “impactful” Summary of Object Model Changes - Cumulative 7000 6000 5000 4000 Total Items 3000 Non-Impactful Changes 2000 Potentially Impactful Changes 1000 9 26 0 Excel Word Powerpoint 4 2 Outlook 9 Access For more details, check out http://blogs.technet.com/b/office_resource_kit/archive/2011/09/08/understandingpotentially-impactful-changes-in-the-office-2010-object-model.aspx Partner with Business areas Discovery; Not Inventory Pre-Deployment & Post Deployment Identify deployment enabling tasks and environment optimization tasks Prepare the Safety Net Manage Risk; Don’t avoid risk Tools Compliment Process Tools provide data…not answers Code Title OSP221 Microsoft Office 365 for Enterprises OSP222 Empowering Small Businesses: Microsoft Office 365 P-Suite OSP305 The Modern Compatibility Process to Accelerate Microsoft Office Deployment OSP224 Microsoft Office 365 Management and Deployment OSP321 Active Directory Integration with Microsoft Office 365 OSP303 Supporting Microsoft Office in an Enterprise Environment OSP302 Building Integrated Microsoft Office 365, SharePoint Online, and Office Solutions Using BCS and LOB Data OSP340 Office Deployment – Notes from the Field OSP323 Microsoft Office 365 Security, Privacy, and Trust OSP324 Microsoft Office 365 Service Reliability and Disaster Recovery OSP350 Office 365 – evaluating, Deploying & Migrating – Notes from the field OSP223 Microsoft Office 365 for Education Schedule 6/26/2012 16:30 6/27/2012 10:15 6/27/2012 12:00 6/27/2012 17:00 6/28/2012 8:30 6/28/2012 12:00 6/28/2012 14:45 6/28/2012 16:30 6/29/2012 8:30 6/29/2012 10:15 6/29/2012 13:00 6/29/2012 14:45 http://europe.msteched.com www.microsoft.com/learning http://microsoft.com/technet http://microsoft.com/msdn http://europe.msteched.com/sessions