Office Compatibility Tools Update 1 zum Download verfügbar

Microsoft stellt für die Office Compatibility Tools; Office Migration Planning Manager, Office Environment Assessment Tool und Office Code Compatibility Inspector im Microsoft Download Center ab sofort das Update 1 zum Download bereit. Einen Überblick über die Neuerungen und Verbesserungen in Office Compatibility Tools Update 1 findet ihr weiter unten.

The Office Compatibility Tools Update 1 delivers important fixes to the tools to improve reliability and performance. The update addresses the existing Office Compatibility tools including: Office Migration Planning Manager (OMPM), Office Environment Assessment Tool (OEAT), & Office Code Compatibility Inspector (OCCI).

Office Environment Assessment Tool herunterladen

Office Environment Assessment Tool Overview

OEAT is a comprehensive scanning tool that helps you assess the compatibility of existing add-ins and applications in your environment. OEAT can identify the following:

  • Office add-ins that are currently installed.
  • Programs that are not registered as add-ins but still interact with Office programs.
  • Information about client computers, such as processor models and types (32-bit or 64-bit), free disk space, Windows version, and Office version.
  • Report: Add-ins assessment—list of third party programs and information about the compatibility of those programs with Microsoft Office 2010.
  • Report: Environmental assessment (potential upgrade issues).

Office Code Compatibility Inspector herunterladen

Office Code Compatibility Inspector Overview

The Office Code Compatibility Inspector for is designed to help update Visual Basic for Applications (VBA) and Visual Studio Tools for Office code so that it is compatible with Office 2010 and Office Pro Plus for Office 365. It consists of four add-ins that load, one add-in per application, in Excel 2010, PowerPoint 2010, Word 2010, and Visual Studio 2008 or Visual Studio 2010.

The Inspector does not correct code; it inspects code, and then comments specific lines of code that reference items in the object model that have been changed, removed, or deprecated. You can then modify the code based on the comments, or use the links that are provided in the comments to view topics on the Web that are pertinent to a particular line of your code.

Office Migration Planning Manager herunterladen

Office Migration Planning Manager Overview

The Office Migration Planning Manager 2010 is a group of tools designed to help administrators during the planning and testing phases of a Microsoft Office 2010 or Office 365 deployment.

Office Migration Planning Manager assists administrators in the discovery and compatibility assessment of existing Office documents for conversion from the binary document formats (.doc, .xls, etc.) to OpenXML formats (.docx, .xlsx, etc.). Additionally, OMPM 2010 adds features to assess macro compatibility with Office 2010 and 64 bit Office compatibility. The toolkit also contains the Office File Converter (OFC), which enables bulk document conversions from binary to OpenXML formats, and a Version Extraction Tool (VET) to extract saved file versions.

The goal of the tool set is to help administrators understand the number and types of Microsoft Office files in their environment and effectively plan for a smooth rollout of the new version of Microsoft Office and conversion of required files to the OpenXML formats. Note it is not necessary nor recommended to convert all existing files when upgrading.

Office Compatibility Tools Update 1 Release Notes

The following table details the key fixes that are delivered with this update.

Office Code Compatibility Inspector Release Notes

Hyperlinks to object model references are broken

  • Some links in the OCCI report and code comments were invalid. These links have been updated to link to Office object model change documentation on MSDN.

The count of potential macro issues differs between the OCCI and OMPM tools.

  • OCCI and OMPM now use the same macro discovery algorithms to provide consistent results in the macro issue identification

Office Environment Assessment Tool Release Notes

Passive mode scanning does not work on some non-English Windows computers

  • OEAT looked for specific security groups that are not present on some non-English computers, causing passive scanning to fail. OEAT no longer relies on English language names of these security groups, making the tool checks language independent.

Compiling OEAT results requires Internet access

  • When compiling report results, OEAT required Internet access to download the latest vendor list. OEAT can now use an existing local vendor file (downloaded from another computer) if the management computer where OEAT is running does not have Internet access. The vendor.xml file must exist in the same folder as the OEAT.exe file when compiling results.

OEAT fails to import scan results due to duplicate names

  • OEAT used MAC addresses to name the scan output file. In some cases, this resulted in duplicate names that caused report compilation to fail. To prevent duplicate scan results, the files are now named using GUIDs.

Offscan.ini ignores invalid parameter values

  • The OMPM file scanner now validates the correctness of parameter values in Offscan.ini as an allowed value. If you enter an invalid value for a parameter, the scanner detects the error and stops the scan instead of ignoring the invalid value. The values are validated according to the documented values for the OMPM file scanner here.

When scanned, Access files are marked as "database too large, not copying. Access properties skipped"

  • The MaxCopyFileSize parameter for Access file scanning was not properly interpreted and lead to failed scans. This issue has been fixed. Note that the scanner configuration file provides the default value as zero. You must adjust this value prior to running the scan. The maximum database size is 2 GB.

A missing OldModifiedDate value in Offscan.ini causes unexpected scan behavior

  • If the OldModifiedDate value in Offscan.ini was blank, the file scanner would use "0/0/0" as the date, leading to unexpected scan results. The value is now validated and the scanner does not run if this value is blank.

Office Migration Planning Manager Release Notes

An invalid value for OldAccessedDate causes the file scanner to crash

  • If alphabetic characters were specified for the OldAccessedDate parameter in the OffScan.ini file, the file scanner would crash. This value is now validated and the scanner does not run if invalid characters are specified.

An invalid path specified for FolderToExclude causes OMPM to not scan

  • If a folder path in FolderToExclude is invalid or inaccessible, the file scanner would hang as the file scanner attempted to retry the path.  The scanner will now continue with additional scanning activity if a folder to exclude is not available or accessible.

If a folder to scan does not exist, the file scanner unexpectedly scans all local drives

  • When a non-existent folder to scan was specified by the FolderToScan parameter of OffScan.ini, the scanner would default to a complete scan of all locally attached drives.  OMPM now ignores a specified scan location if it is not available and continues scanning other locations as specified.

The OMPM macro summary report fails to launch

  • The OMPM compatibility report view for macro summary failed to launch the macro summary report. The macro summary report now launches successfully.

The Office File Converter FoldersToConvert parameter in OFC.ini does not support specifying multiple folders

  • The OFC tool displayed an error if the OFC.ini file defined multiple folders to convert. The update enables the conversion of multiple folders as defined in the configuration file.

The Office File Converter output is truncated when you use the FileFolderList parameter in OFC.ini

  • When using the FileFolderList parameter, the command shell output displayed truncated file paths for any files that could not be converted, This update displays the full file path of all files that could not be converted.

The Office File Converter does not convert all files that are specified by the FileListFolder parameter in OFC.ini

  • When you used the FileListFolder parameter in OFC.ini, only some of the files were converted successfully, and others failed to convert with error "Error: Unknown file type.” This update corrects the parsing to allow the OFC to attempt to convert all files specified by the FileListFolder parameter.

The OMPM report does not display files where access is denied

  • The scan results did not indicate when a file scan failed due to a file access issue. This information is now displayed in the report.

File filters do not filter the macro summary view

  • The OMPM Access report file filter actions were not applied to the macro summary view. This update enables use of the filters with this report view.

OMPM imports fail for some scans

  • Scans results that included non-ASCII characters in the files could cause import errors. The bulk import process has been updated to manage non-ASCII characters.

The OMPM file scanner aborts for null macros

  • The OMPM file scanner would abort when the file contained a macro with a zero-byte size. This update manages this scan condition and enables the scanner to continue processing.

OMPM file details do not include macro VBA counts

  • The OMPM file view did not include data from the macro count when available. As a result, it was not easy to see all information about a single file in the file view. New fields have been added to the file view to enable all file information to be seen in a single view.

The Office File Converter log results are not imported

  • The OFC tool logs failed to import using the importactons.bat script. The log import process has been corrected.

Missing reference is not reported

  • The Access report did not include a proper count of reference objects. The report view has been corrected.

The Last Accessed Date of scanned files are updated in some environments when the /d scan switch is utilized

  • When the OffScan.exe /d scan switch was used, the last accessed dates of scanned files were not supposed to be updated by the file scanner. However, in some environments, this switch was not properly respected, and the last access dates of files were updated unexpectedly. The update enables proper use of the switch to preserve the last access dates of files during a file scan. Note that the scanner must have write permissions to enable the preservation of the last access date property.

The file scanner does not respond to close, logoff, or shutdown events

  • The file scanner did not respond to these events to enable the scanner to be stopped properly. The update responds properly to these events.

Embedded links are not reported

  • Although embedded link data is gathered during the scan, the compatibility reports did not show this information. This update now displays information about embedded links.

The file scanner runs slowly in decentralized scans

  • When the file scanner is run from network share, scan speeds were slower than expected, especially for scanning Excel files. This update improves this performance during the file scanning process for files located on network locations.

Inconsistencies in the OMPM database schema

  • Corrections in the OMPM database schema are delivered in this update to enable proper reporting and align with the documented schema on TechNet.

Office Compatibility Tools Update 1 Upgrade

Upgrading to the new versions of these tools is not supported. You must reinstall each tool to use the Update 1 version of the tools. Prior OMPM file scans or OEAT environment scans are not compatible with the Update 1 versions. You must execute new scans to use the newer versions of the tools.

via Office Compatibility Tools Update 1 Available for Download