OMPM – Office Migration Planning Manager
“…it is a collection of tools that enables you to prepare an environment for migration to Office 2010.”
|OffScan.exe||Scan Office 97 through Office 2003 files for conversion issues||· Light scan – quickly identifies
· Deep scan – scan document properties
· Macro scan – count potential issues for Microsoft Excel, Word and Powerpoint.
|Microsoft Outlook, Microsoft FrontPage, Microsoft OneNote, and Microsoft InfoPath are not included in either the light or deep scan.|
|Office File Converter (OFC)||Perform bulk conversions||· which enables bulk document conversions from binary to Open XML formats.|
|Version Extraction Tool (VET)||lets you extract multiple saved versions of a single Word 97–2003 document to individual files in Word 2010||·|
|Migration Tool||What tool does?||Scans|
|Office Environment Assessment Tool (OEAT)||· Scans given path for add-ins and applications
· Interact Microsoft Office 97, Microsoft Office 2000, Microsoft Office XP, Microsoft Office 2003
· Scan additional information of host machine
· Reports – environmental assessment, 3rd-party add-ins assessment compatible with Microsoft Office 2010.
|Microsoft Office Code Compatibility Inspector
|· Helps to troubleshoot compatibility issues for VBA Macros and Add-ins
· Individual add-in designed for per add-in per application (Excel, Powerpoint, Word)
· Inspect code to find potential issues
· Reports potential issues line-on-line.
|Office Migration Planning Manager (OMPM)||· Scan bulk applications for Macro issues
· Generate report for issue and compatibility analysis
· Report additional data for office document files and version information
· Seamlessly integrates with SQL Server Express editions and produce logs to track reported issues.
|File / document management|
|Centrally-run scan||to an administrative client computer and use that computer to scan specified network locations.|
|Distributed scan from shared folder||Download to a central file share and use that share to scan all environment client computers.|
|Decentralized scan||Download to each environment client computer for local scanning|
Office 2010 App Compatibility Program to launch (link):
· Office Code Compatibility Inspector (OCCI) – tool indicate if VBA code needs to be updated to work properly in office 2010. more details..
· Office Environment Assessment Tool (OEAT) – identify "add-ins created by third parties, add-ins created by Microsoft and VBA projects,"
· User-created data is preserved when upgrading, including documents, PSTs, templates, macros and other user-created content,"
· Another migration concern is the functionality of Visual Basic for Applications (VBA) projects. End users may have devised their own VBA code to automate certain tasks in Office, and there are a number of reasons
· Office 2010 will be offered for both 32-bit and 64-bit hardware, and migrating from one such version to the other might lead to incompatibilities.
Why VBA Still Makes Sense (link):
· Should I use VBA?
VBA still has a place in this world.
· Is it going to be around in Office 2010?
VBA is included in Office 2010 much as it was in Office 2007. It is indeed supported. You should continue to use VBA where it fits the needs of your business and migrate only if the need arises.
Upgrading Solutions to Office 2010 with Application Compatibility Tools and Guidance (link)
Microsoft Office Code Compatibility Inspector user’s guide (link):
MOCCI – inspects compatibility issues in VBA Macros and add-ins. It does not correct code. It comments specific line of code that reference items in the object model that have been changed or deprecated e.g. Declare statements are commented for 64-bit compatibility.
· Four add-ins – Excel, Word, Powerpoint, VS 2008 (VSTO)
· Runs on per-user or per-document basis.
· Adds comments in code where it finds potential issues
· Displays summary once it is finished with its findings.
· Tool can inspect code for interaction with Outlook but it will not check code for Outlook add-ins.
· It provides summary for Changed, Deprecated, and Redesigned.
Office 2010 application compatibility guide
The application compatibility testing and remediation process for Microsoft Office 2010 deployments identifies compatibility issues and helps you develop plans to fix them. This information is useful primarily to IT professionals who evaluate and mitigate application compatibility issues. Developers who are upgrading Office applications might also find this information useful. After completing the process that is described in this article, administrators and developers will have a better understanding of which add-ins and applications interact with Office and how to migrate them to Office 2010.
Note: In cases where applications cannot be fixed, administrators can use solutions such as Remote Desktop Services (Terminal Services), parallel installations, and the new Microsoft Application Virtualization (App-V) to maintain the previous, compatible Office environment alongside Office 2010.
Office Environment Assessment Tool (OEAT) – new scanning tool for Office 2010 that identifies add-ins that are installed on users’ computers and reports add-in information for Microsoft Office 97, Microsoft Office 2000, Microsoft Office XP, Microsoft Office 2003, and the 2007 Microsoft Office system
ISV Application Compatibility Visibility Program – this program tracks independent software vendors (ISVs) who pledge that their products are compatible with Office 2010. It also submits list and stores information for next use.
Microsoft Office 2010 Code Compatibility Inspector (OCCI) – The Microsoft Office 2010 Code Compatibility Inspector compares existing VBA, Visual Basic .NET, and C# source code for object model API calls that are incompatible with Office 2010.
|Customization type||Information||Assessment tool|
|Automation add-ins (.xll or .wll)||OEAT|
|COM add-in (Windows .dll)|
|Office 97–2003 format VBA add-ins (.dot, .wll, .xla, .xll, .ppa)||OEAT and OCCI|
|Office 2007–2010 format VBA macro-enabled files (.docm, .xlsm, .pptm)||These files contain VBA macro code but are not saved as add-ins.
OEAT will detect macro-enabled Word and Excel files that are stored in the Startup folder or that are loaded as global templates. OEAT will not discover macro-enabled files that are stored in other locations, nor will OEAT discover macro-enabled PowerPoint files in any location.
|OEAT and OCCI|
|Office add-ins created by using Visual Studio||Document-level customizations and Application-level add-ins||OEAT and OCCI|
Planning guide shares the compatibility assessment and redemption process by dividing into phases of planning for compatibility testing, assess the environment, test and remediate compatibility issues. Planning will include further steps to assess, remediation and piloting. Once its planned, an environment assesment should be carried through which will involve to execute and run OEAT, review its output and finalize the remediation plan. Finally, test add-ins using OCCI, Remediate add-ins and applications.
Excel 2010 Object Model Changes Since Earlier Versions: http://msdn.microsoft.com/library/ee836187(office.14).aspx
Outlook: Outlook 2010 Object Model Changes Since Earlier Versions: http://msdn.microsoft.com/library/ee836188(office.14).aspx
Microsoft Office Code Compatibility Inspector user’s guide: http://technet.microsoft.com/en-us/library/ee833946.aspx
Office 2010 application compatibility guide: http://technet.microsoft.com/en-us/library/ee819096.aspx
Upgrading Solutions to Office 2010 with Application Compatibility Tools and Guidance: http://msdn.microsoft.com/en-us/office/ee722033.aspx
Prerequisites for OMPM installtion-
SQL Server 2005 Backward Compatibility & XML Services – Microsoft Core XML Services (MSXML) 6.0: