Jeff Alexander IT Pro Evangelist Microsoft Australia

8:30-9:00Registration 9:00-9:15 Welcome and Introductions 9:15-10:30 Application Compatibility Strategy Windows 7 IE 6 Roadmap to IE 8 Office :30-10:45 Break 10:45-12:20 Remediation Strategies ACT App-V MED-V Office 2010: OMPM, OEAT, OCI Partner Offerings 12:30 – 13:00 Final Q&A and close

Application Requirements Affect Remediation Techniques

Recoding an Application When source code is available for an application, it is advisable to have it fixed Determine how and when to engage with development teams Third-party buy-a-new-one fix Managing costs Acquisition process

Shims allow Windows to Change Behavior Define standards for when to use this technique: Vendor no longer in business Internal applications Support negotiable  Shimming applications can be outsourced

ApplicationApplicationWindowsWindows Shim DLL ImportFunctionImportFunctionExportFunctionExportFunction ImportFunctionImportFunction

Microsoft Application Compatibility Toolkit Shims

Application Virtualization Microsoft App-V Machine Virtualization MED-V Presentation Virtualization Terminal Services Citrix

Applications Operating System Hardware What it does Creates a package of a single application Eliminates software installation What it is good for Resolve conflicts between applications Simplify application delivery and testing What it does Creates a package with a full OS What it is good for Resolve incompatibility between applications and a new OS Run two environments on a single PC (e.g. corporate and personal) ®

Microsoft Application Virtualization and Microsoft Enterprise Desktop Virtualization

Tools Microsoft Assessment and Planning Toolkit (MAP) Office Migration Planning Manager (OMPM) Office Environment Assessment Tool (OEAT) Office 2010 Code Compatibility Inspector (OCCI) Office Compatibility Pack for Word, Excel and PowerPoint Compatibility Checker Office 2010 Application Compatibility Center on TechNet Content Application Compatibility Analysis and Remediation Guide for Office 2010 Developer References

*NEW Office Code Compatibility Inspector (OCCI) Remediation of macro and VBA compatibility issues Inspect code within files flagged by OMPM to expedite remediation of code compatibility issues. *UPDATED Office Migration and Planning Manager (OMPM) Assess your Office filesScan files for fidelity, macro, and VBA compatibility *NEW Office Environment Assessment Tool (OEAT) Assess the environment Reports installed, add-ins, and anything interfacing with Office. Reports compatibility.

System Readiness Inventory Office Applications Assess hardware & operating system readiness Suggests key upgrades Summary proposal of 2010 readiness System Readiness Inventory Office Applications Assess hardware & operating system readiness Suggests key upgrades Summary proposal of 2010 readiness Application Compatibility Identify interfacing add-ins and interfaces Tag known compatible apps Mitigate VBA and macro code Application Compatibility Identify interfacing add-ins and interfaces Tag known compatible apps Mitigate VBA and macro code File Readiness Scan & identify potential format deltas Identify potential macro issues Migrate Office files to Microsoft Office Open XML formats File Readiness Scan & identify potential format deltas Identify potential macro issues Migrate Office files to Microsoft Office Open XML formats Microsoft Assessment Planning Toolkit (MAP) Office Environment Assessment Tool (OEAT) Office Compatibility Code Inspector (OCCI) Office Migration Planning Manager (OMPM)

MAP Organization Network 1.Assesses the organization environment using an agentless inventory tool 2.Recommends the right technologies 3.Creates proposition and detailed reports with links to Office 2010 Compatibility tools (OEAT, OCCI, OMPM) and content MAP Tool User Compatible hardware? Compatible systems? Installed Office applications? Compatible hardware? Compatible systems? Installed Office applications?

 Microsoft Assessment and Planning (MAP) Toolkit Features –Discovers clients, servers and applications –Conducts migration and virtualization assessments –Auto-generates reports and proposals –Use in small or large businesses  MAP reports for migration to Office 2010 –Microsoft Office 2010 Assessment Report –Microsoft Office 2010 Summary Proposal

 Currently installed applications and installation environment  Add-ins currently in use by Office clients  Programs that are not registered as add-ins but still interact with Office programs  Environmental assessment (potential upgrade issues)  Add-ins assessment—A list of third-party programs and information about the program’s compatibility with Office 2010.

 Office Environment Assessment Tool (OEAT) identifies the following: –Currently installed applications and installation environment –Programs that are registered as add-ins but still interact with Office programs  Reports –Summary Report –Microsoft Office Addins –Addins Not Shipped With Office

 Set of tools that provides detailed information regarding potential file format and document compatibility issues, and enables bulk file conversion to Open XML documents: –OMPM File Scanner (offscan.exe) scans files for conversion issues. –Database creation and import tools –Access-based reporting tool –Office File Converter (OFC) converts files in bulk to the Open XML file format. –Version Extraction Tool (VET) extracts the contents of a file in Word 2003 and earlier versions and then saves that content to multiple different files.  Macro scanning reports issues found, and optionally provides comments with links to possible resolution.  X64 migration scanner scans macros and add-ins for 64-bit compatibility. NEW

 Office Migration Planning Manager (OMPM) prepares an environment for migration to Office 2010  Components of OMPM –OMPM File Scanner –Import utilities –Access-based reporting solution –Office File Converter (OFC) –Version Extraction Tool (VET)

1.Run the file scanner 2.Import the files into the OMPM database 3.Use OMPM reports to prepare reports from the data in the OMPM database 4.Based on the report analysis, perform any of the following: –Use the Office Code Compatibility Inspector tool –Use the Office File Convertor –Use the Version Extraction Tool

OEAT and OMPM

Troubleshooting tool for VBA code. Integrates into Office VBA and VSTO. Performs a simple text search for known properties and methods in the Office COM that have changed. Option to comment or mark those areas in the code where text search has identified a possible COM match. Summary of total lines of code scanned as well as total lines identified as potential candidates for COM changes A detailed report, with module name, line number, and links to remediation for each issue found with possibly a red or yellow flag for impact guidance. The tool also has the ability to report on known compatibility of an add-in based on interaction with a web service provided by Microsoft.

OCI

 Feature-function change  Independent software vendor applications  Add-in compatibility  Maintenance and migration of macros  Maintenance and migration of scripts  Document fidelity

 Enables Word, Excel, and PowerPoint 2000, XP and 2003 to open, edit, and save Office Open XML file formats  Some new features of Office 2010 may not be compatible with prior Office releases  Open, edit, and save documents, workbooks, and presentations in the Open XML file formats which were introduced to Microsoft Office Word, Excel, and PowerPoint beginning with Office  Can be installed for Office 2000, XP and 2003 users to enable them open, edit, and save the new Office file formats in Word, Excel, and PowerPoint. Office Compatibility Pack Office Compatibility Checker Detect features that are not recognized by earlier versions of Office Built-into Word 2010, Excel 2010, PowerPoint 2010 Enabled when the following actions are performed in Office Save one of the Office Open XML file formats to an Office file format -Launch Check Compatibility from the Check for Issues menu in the Backstage view

Planning Know what people are using with application metering Determine application standards Delivering App-V for deployment and updates Operating Track Application Usage Update and Re-deploy Applications Quickly Allocate License Costs Based on Usage and Need MOF = Microsoft Operations Framework

* Microsoft proprietary interviews of 32 customers OMPMOEATCompatibility Inspector

Important to start planning early Windows 7 and Office 2010 resources and tools are available Leverage Technet and SA benefits to get started: Technet “Springboard” Jumpstart POC download 31Microsoft Confidential

 Compatibility Center at  Windows 7 – Springboard: us/windows/default.aspxhttp://technet.microsoft.com/en- us/windows/default.aspx  Understanding Application Compatibility : us/library/ee449431(WS.10).aspxhttp://technet.microsoft.com/en- us/library/ee449431(WS.10).aspx  Office 2010 Application Compatibility (Technet) :  MED-V: –MED-V Information –MED-V Team Blog Provides valuable information on top issues facing customers with MED-V  IE8: –The Internet Explorer 8 Deployment Guide contains topics updated with our latest deployment guidance for Internet Explorer 8.Internet Explorer 8 Deployment Guide –Additional background and troubleshooting resources at IE8 Tech Center at Also find application migration resources at IE8  POC Jumpstart : 819E-12EF &displaylang=en 819E-12EF &displaylang=en 32Microsoft Confidential

33Microsoft Confidential

© 2010 Microsoft Corporation. All rights reserved. This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.

 The independent software vendor (ISV) name  Product name and versions  32-bit or 64-bit compatibility  Link to the ISV’s Web site providing authoritative information about the application or add-in compatibility with Office 2010  Community feedback for products listed as compatible but experiencing issues

 Application Compatibility Analysis and Remediation Guide for Office 2010 –Guide to an environmental assessment, and assists customers with identifying areas of Office that could be of concern for them –Excel, PowerPoint, Word, Outlook, and Access –Will include a list of known issues by product that may present problems to migration, and possible workarounds, alternatives, and solutions (remediation) –Will include top Office migration changes that will affect migration of add-ins, templates, and macros  Roundtripping of documents through 2003 and 2007 SP2 information  Non-professional MSDN.com developers articles for migrating macros and VBA solutions –Excel macro migration –Access macro or run-time migration –Outlook migration –Word migration

 COM changes since Office 2000  Documentation and guidance for developing Office 2010-based solutions –Access 2010 Developer Reference –Excel 2010 Developer Reference –Outlook 2010 Developer Reference –PowerPoint 2010 Developer Reference –Project 2010 Developer Reference –Publisher 2010 Developer Reference –Visio 2010 Automation Reference –Visio 2010 ShapeSheet Reference –Word 2010 Developer Reference  Office 2010 Developer References in.hxs format, as opposed to.chm

OEAT ISV Add-ins OMPM Macro, VBA code TemplatesDocuments OCCI Macro VBA code VSTO code Application Add-in Automation Add-in TEST Macro VBA code VSTO codeTemplates Application Add- in Automation Add- in

–User Settings and Preferences –Group Policies –Custom Installation settings –Feature States –File Formats –Dependencies (Macros etc.) –Add-Ins and Components –Security Settings Setup Structure Localization considerations Office customization Office Activation Enterprise Deployment tool consideration