Welcome  |  Sign in
Skip Navigation Links
Office System Suites and Programs TechCenter
Click to Rate and Give Feedback
TechNet
TechNet Library
Office
Office System
 Introduction
Introduction to OMPM

The Office Migration Planning Manager (OMPM) is a collection of tools that enables you to prepare for migration to the Microsoft 2007 Office system. OMPM checks for, and reports on, file properties to help you analyze your environment. You can download OMPM from 2007 Microsoft Office System Migration Guidance: Microsoft Office Migration Planning Manager (http://go.microsoft.com/fwlink?linkid=75727).

For the most part, documents created in Office 2003 and earlier open and behave the same way in the 2007 Office release. However, there might be instances where files require manual intervention or analysis to ensure consistent behavior. For example, a custom solution built in Microsoft Excel 2003 might require modification because it relies on legacy Office features that are no longer supported in Excel 2007.

OMPM includes the following features:

  • The OMPM File Scanner (offscan.exe), a command-line tool that scans files for conversion issues. You can easily deploy this tool using an automated software deployment technology, such as SMS, or a login script. The OMPM File Scanner stores the scan results in XML log files on each computer that it scans. The OMPM File Scanner performs two types of scans:

    • A light scan that quickly identifies the Office documents on a user’s computer or network file system.

    • A deep scan that you can perform on Office documents to gather document properties that provide indicators of potential conversion issues.

  • A set of utilities that automate the creation of a new database (either SQL Server 2000, SQL Server 2005, or SQL Express) and import the XML log files generated by the OMPM File Scanner.

  • A Microsoft Access 2007–based reporting solution that provides different reports for your analysis and enables you to define file sets for automated processing.

  • The Office File Converter (OFC) that allows you to convert specific files to the new 2007 Office release file formats in bulk.

  • The Version Extraction Tool (VET) that allows you to extract saved versions of a file in Word 2003 (or earlier) to different files.

OMPM contents

OMPM is contained in a self-extracting executable file, MigrationPlanningManager.exe. OMPM Components are contained in redistributable subfolders:

  • Scan: The folder containing the OMPM File Scanner.

  • Report: The folder containing OMPM Reports. To export file lists from OMPM Reports, the database folder and related components must also be available.

  • Database: The folder containing scripts to provision and populate the OMPM database.

  • Tools: The folder containing tools such as the Office File Converter and Version Extraction Tool.

Installing OMPM

To install OMPM, type the following at a command prompt:

MigrationPlanningManager /extract:c:\ompm

For help with OMPM, type the following at a command prompt:

MigrationPlanningManager /?

OMPM requirements

The following lists the requirements for running OMPM, both for the client systems that it scans and the administrator system from which it runs.

Client system requirements

The OMPM File Scanner requires the following programs on the computers that it scans:

  • Windows NT 4.0, Windows 2000 SP4, Windows XP SP2, or Windows 2003 SP1

  • Internet Explorer 5.0 or higher

The following system components must exist on all computers running the OMPM File Scanner. If these files do not exist, install the files with a separate distribution job before you run the OMPM File Scanner.

  • Data Access Objects 3.5 or higher (dao350.dll/dao360.dll). These files are included in Microsoft Access 97, Microsoft Windows 98, Microsoft Windows NT® 4.0 Option Pack, and Windows NT 4.0 Service Pack 4.

  • Microsoft Scripting Runtime (sccrun.dll). This file is included in Microsoft Access 2000, Windows NT 4.0 Option Pack, Windows NT 4.0 Service Pack 5, and Microsoft Windows Scripting Host.

  • Visual C Runtime (msvcrt.dll).

  • Kernel32.dll.

  • Msjet40.dll.

  • Crypt32.dll.

  • Ole32.dll.

  • Oleaut32.dll.

  • User32.dll.

  • Advapi.dll.

  • Msvcrt.dll.

All computers that contain files to convert are required by the Office File Converter (OFC) to install the Microsoft Office Compatibility Pack. For more information, see Deploying the Microsoft Office Compatibility Pack.

The Version Extraction Tool (VET) requires installation of Microsoft .NET Framework Version 2.0 Redistributable Package (x86) (http://go.microsoft.com/fwlink/?LinkId=81886) and Microsoft Word 2003.

Administrator system requirements

The administrator running OMPM requires the following:

Computer and operating system

  • A computer running Windows XP SP2 or Windows Server 2003 to use the database provisioning and data import tools in OMPM.

  • Optional: A computer running Windows XP to create a self-extracting package with IExpress 2.0.

    NoteNote:

    Use IExpress 2.0 to create a self-extracting package. Do not use a self-installing package.

Database software

  • SQL Server 2000 or SQL Server 2005 (recommended). SQL Server 2005 is recommended for enterprises working with large amounts of data. SQL Server 2005 provides enhanced database management and reports. The database should have a minimum of 4 GB available free disk space.

  • Microsoft SQL Server 2005 Express Edition. This free, redistributable version of SQL Server 2005 is ideal for client applications that require an embedded database. You can use SQL Server 2005 Express Edition, instead of SQL Server 2005, for smaller-scale data collection. The database should have a minimum of 2 GB available free disk space. SQL Server 2005 Express Edition is available as a free download at SQL Server 2005 Express Edition (http://go.microsoft.com/fwlink/?LinkId=95582&clcid=0x409).

Database tools and utilities

  • Both SQL Server 2005 and SQL Server 2005 Express Edition include several command line utilities, such as Osql.exe and Bcp.exe. These must be available on the client computer from which the provisioning and import tools are run.

  • SQLXML 3.0 SP3. SQLXML enables XML support for your SQL Server 2005 database. This module allows XML files that are collected by the OMPM File Scanner to be imported efficiently into a database server. SQLXML is a free download available at SQLXML 3.0 Service Pack 3 (SP3) (http://go.microsoft.com/fwlink?linkid=52919).

NoteNote:

We recommend using the English editions of SQL Server 2005 or SQL Server 2005 Express Edition to use OMPM. While there are no known issues involving international editions, only the English edition is supported for these tools at this time.

File share

A file share is required to stage the XML log files collected by the OMPM File Scanner before the log files are imported into the database. The file share should have a minimum of 1 GB available space. Any account that is operating the import scripts requires read/write/create access to the file share.

NoteNote:

For performance reasons, it is optimal to have the import tools, log file share, and database on the same server. If this is not possible, the log file share and the database server should be on the same subnet to reduce network traffic.

Other

  • OMPM Reports requires the installation of Microsoft Access 2007 on the client computer from which the data will be examined. To export file lists from OMPM Reports, SQL Server Express or SQL Server and SQLXML 3.0 SP3 must be installed on the computer that runs OMPM Reports.

  • To perform a deep scan with the OMPM File Scanner, Access 2002 or later must also be installed on the computer that runs the OMPM File Scanner.

    NoteNote:

    Other than the requirement listed above, the OMPM File Scanner does not require the installation of any version of Office on any computer it scans.

  • For scanning document storage systems such as Microsoft SharePoint Services, the OMPM File Scanner requires the Web-based Distributed Authoring and Versioning (WebDAV) interface. For more information about WebDAV, see About WebDAV (IIS 6.0) (http://go.microsoft.com/fwlink/?LinkID=81698). This is the only version of WebDAV that is supported for OMPM.

    NoteNote:

    Use either the Windows Vista WebDAV client or a third-party WebDAV client for document libraries that are SSL-enabled. If you use the WebDAV client from previous versions of Windows, the scan of the document library fails.

How the OMPM File Scanner works

The OMPM File Scanner gathers information about the computer and recursively scans the designated path for Office files. The OMPM File Scanner then records the results in an XML log file to the designated destination path.

The OMPM File Scanner performs the following tasks in a single scan:

  • Scans the computer for Office files within the folder structure defined by the SourcePath specified in the configuration file offscan.ini.

  • Scans the computer for properties such as operating system, memory, and language ID.

  • Scans for file property information such as file name, path, size, format, created date, modified date, and file owner.

  • If this is a deep scan, scans for compatibility issues.

  • Writes an XML log file to the destination path for each file that contains compatibility issues.

  • Adds the XML log files to a series of CAB files for later transfer to a SQL Server.

  • Logs failures to the XML log files.

NoteNote:

The OMPM File Scanner does not change file properties, except possibly Last Accessed Date.

NoteNote:

The OMPM File Scanner does not transmit data to Microsoft Corporation.

Log and CAB files generated by the OMPM File Scanner

On each computer that it scans, the OMPM File Scanner writes an XML log file to the destination folder that you specified in the accompanying offscan.ini file. This initial log file contains both scan and computer details. After this, the OMPM File Scanner creates an XML log file for each additional Office file that it scans. The filename for each log file is in the form of a GUID, with a prefix indicating the type of log file.

The OMPM File Scanner creates four unique types of log files to record properties about the computer scanned, file scanned, scan summary, and errors. The following table shows a typical set of log files.

File Name Description

Scan_{40D1300A-F0BE-4D68-ADBF-36C78EE030A1}.xml

Scan log (one per scan)

File_{F575D370-1E7A-486E-9FC6-4BB83C7770DD}.xml

File properties log (one per unique file scanned)

Sum_{75C5A590-A789-4B16-A2EB-E3934BCB01B1}.xml

Summary log

Err_{61CF0E6F-71E1-4878-9E9F-C1D35EBA3506}.xml

Error log (one per unique error occurrence)

The individual log files are compressed into CAB files to make transport to the SQL Server database more efficient. To maximize disk space on the computer that is scanned, after OMPM File Scanner writes 10,000 log files, adds the log files to a CAB file, and then deletes the log files. Each CAB file contains up to 10,000 log files. When a CAB file reaches 10,000 log files, OMPM File Scanner creates a new CAB file for the next 10,000 files.

CAB files use the file name from the ScanID GUID, with an index number appended. Three CAB files generated on the same computer might generate names such as the following:

  • Computer1 {2FA87EDF-4393-4BCF-8829-8776F82DEDD5}00001.cab

  • Computer1 {2FA87EDF-4393-4BCF-8829-8776F82DEDD5}00002.cab

  • Computer1 {2FA87EDF-4393-4BCF-8829-8776F82DEDD5}00003.cab

Creating CAB files can be detrimental to performance if log files are saved across a network. Use the setting CABlogs=1 in the Offscan.ini file to disable the creation of CAB files.

Files scanned by the OMPM File Scanner

The following table shows the file types that are scanned by the OMPM File Scanner, along with file types that are included in the light scan only.

Microsoft Office program Light and deep scan file types Light scan only

Access

  • .mdb

  • .mde

  • .mdz

  • .adp

  • .ade

  • .mdt

  • .mda

  • .accda

  • .accdb

  • .accdr

  • .accdu

  • .accde

  • .accdt

  • .accdc

Excel

  • .xls

  • .xlt

  • .xla

  • .xlm

  • .xlw

  • .htm

  • .html

  • .mhtml

  • .mht

  • .xlc

  • .wk1

  • .wk3

  • .wk4

  • .wj1

  • .wj2

  • .wj3

  • .fj3

  • .fmt

  • .fm3

  • .all

  • .wks

  • .wq1

  • .dbf

PowerPoint

  • .ppt

  • .pot

  • .pps

  • .ppa

Project

  • .mpp

  • .mpt

Publisher

.pub

Visio

  • .vsd,

  • .vss

  • .vst

  • .vdx

  • .vtx

  • .vsx

Word

  • .doc

  • .dot

  • .wiz

Files from Microsoft Office Outlook, Microsoft Office FrontPage, Microsoft Office OneNote, and Microsoft Office InfoPath are not included in either the light or deep scan.

NoteNote:

The OMPM File Scanner does not scan documents that are password-protected or IRM-protected. In addition, the OMPM File Scanner does not scan embedded objects within documents, but does report that the document contains embedded objects.

Download this book

This topic is included in the following downloadable book for easier reading and printing:

See the full list of available books at Office Resource Kit information.

Tags What's this?: Add a tag
Community Content   What is Community Content?
Add new content RSS  Annotations
Processing
© 2008 Microsoft Corporation. All rights reserved. Terms of Use  |  Trademarks  |  Privacy Statement
Page view tracker