Follow / Friend Us
Still using OMPM? Give Office Telemetry Dashboard a try!
To celebrate the release of the Office Migration Planning Manager (OMPM) for Office 2010, I will be creating a series of blog posts that describe OMPM installation, basic and advanced usage, Q&A, and any other topics that come up. Do you have OMPM (or Office Environment Assessment Tool [OEAT]) questions that you’d like to see answered in this blog? Please leave your ideas in the Comments of this blog post for future consideration.
For this first post, I’ll walk you through a basic installation of OMPM using SQL Express 2008 R2 as the database back end. I’ll also scan my laptop to assess my old Office files and go over some of the initial scan results.
Let’s get started!
1. For this walk-through, I will be using the Access reporting tool to view the OMPM scan data. Therefore, make sure that you have Access 2007 or later installed on the computer where you install OMPM.
2. Download and install OMPM from the Download Center. The download process extracts the OMPM files to a folder of your choice. I will be using C:\OMPM for this walk-through.
3. Install SQL Server 2008 R2 SP2 - Express Edition. You can choose either the 32-bit or 64-bit edition. Remember which edition you install so that you can choose the same edition for the components you install in Steps 5 and 6.
4. The setup process for SQL Server 2008 R2 SP2 Express takes a while to download and extract files. Accept the various prompts and wait for the opening page of SQL Express 2008 R2, called the SQL Server Installation Center, to appear after extraction is complete. Then, follow these steps:
a. In the SQL Server Installation Center, click New installation or add features to an existing installation.
b. In the SQL Server 2008 R2 Setup wizard, read the license terms and accept them, and then click Next.
c. On the Feature Selection page, accept the defaults (all checkboxes selected). Click Next.
d. On the Instance Configuration page, create a named instance called OMPM. Click Next.
e. On the Server Configuration page, accept default service accounts. Click Next.
f. On the Database Engine Configuration page, accept the default authentication mode (Windows authentication mode). Your user account will be shown as a SQL Server administrator. Click Next.
g. On the Error Reporting page, click the check box if you want to send error reports to Microsoft. Otherwise, just click Next.
h. Wait for the installation process to finish, and then close the wizard and the SQL Server Installation Center.
5. Install the 2005 Backward Compatibility Pack from the December 2008 Feature Pack for Microsoft SQL Server 2005. (Select the SQLServer2005_BC package from the long list of downloads according to the correct bitness, either SQLServer2005_BC.msi or SQLServer2005_BC_x64.msi). Accept the defaults for all options.
6. Install the Microsoft SQLXML 4.0 SP1 pack. Accept the defaults for all options.
Now that you have the SQL components installed, you are ready to create a database for storing OMPM results. Take the following steps:
1. In an Administrator command prompt window, navigate to the folder where you installed OMPM, and then open the Database folder.
2. Type the following command to create a database called ompmdb for the ompm SQL instance: createdb.bat .\ompm ompmdbWhen you execute the command successfully, you will see the following results in the command prompt window: C:\OMPM\Database>createdb.bat .\ompm ompmdbMicrosoft Office Migration Planning Manager version 2.0Database Provisioning ToolCopyright (c) 2010 Microsoft Corporation. All Rights Reserved.Database 'ompmdb' was created successfully.If you are running the command prompt without administrator privileges, the command will fail.
You are now ready to configure OMPM settings in the Offscan.ini file, which is located in the Scan folder where you installed OMPM. Navigate to the Scan folder and double-click Offscan.ini to edit it. I’m only going to change a handful of settings for this walk-through, but I will also point out some new settings in case you want to experiment. You can find more information about each setting in Offscan.ini in the OMPM Technical Reference.
Note: If you have permissions issues when trying to save Offscan.ini, add yourself to the permissions list for the OMPM folder and let me know via this blog if you encounter this issue.
The table below shows various parameters in Offscan.ini that I will use in this walk-through. Any parameter in bold indicates that I’ve changed the default.
;Run ID is a unique ID for this distribution of the scan.
Each time you run a scan, you must increment this number, otherwise the scan won’t start. When you view your OMPM scan results by using the Access report viewer, you can view all runs or a selected run.
;Description can be used to describe any extra info about the Run. I.E. Month/Year
Description="ORK team blog OMPM scan."
The description also appears in the OMPM Access report viewer. I highly recommend that you use a unique description for each run.
;SkipOldAccessedFiles: if set to 1, offscan will skip files with a Last Accessed Date less than OldAccessedDate
;if set to 0, offscan will not skip old files based on Last Accessed Date
;OldAccessedDate: files with a Last Accessed Date before OldAccessedDate will be skipped if SkipOldAccessedFiles=1.
; Date format should be “YYYY/MM/DD”
;SkipOldModifiedFiles: if set to 1, offscan will skip files with a Modified Date less than OldModifiedDate
;if set to 0, offscan will not skip old files based on Modified Date
;OldModifiedDate: files with a Last Modified Date before OldModifiedDate will be skipped if SkipOldModifiedFiles=1.
;Date format should be “YYYY/MM/DD”
OMPM 2010 now offers a way to limit scanning to only files that have been modified or accessed within a specified date period. These settings are not enabled by default, but we recommend enabling them to keep the scan results manageable. Work with your business groups to determine if scanning every old file is necessary, or if you can limit the scan (and eventual conversion) to files that have been accessed or modified after a specified date.
For this walk-through, I’m not going to skip files by accessed or modified date because I want to ensure that I get a variety of scan results.
;ScanMacros: if set to 1, offscan will attempt to scan macros in scanned filetypes for API or Object Model compatibility issues.
;if set to 0, offscan will not attempt to scan macros for API or Object Model issues
ScanMacros is another new setting for OMPM 2010. For this walk-through, I’m going to enable macro scanning (the default is 0-disabled).
;ScanMacrosX64:if set to 1, offscan will attempt to scan macros in scanned filetypes for x64 compatibility issues
; if set to 0, offscan will not attempt to scan macros for x64 compatibility issues
ScanMacrosX64 is another new setting for OMPM 2010. For this walk-through, I’m going to enable X64 macro scanning (the default is 0-disabled).
I’m going to scan my remote laptop’s C drive. You can specify multiple clients to scan here.
After you’ve completed and saved your offscan.ini edits, it’s time to execute a scan.
1. In an Administrator command prompt window, navigate to the Scan folder and type the following command:offscan.exe
2. You can watch the progress as each file is scanned. Most files are scanned quickly, but some can take a few seconds to complete. When the scan is complete, you’ll see the final lines of output, which are similar to this:
Start: 2010-08-04 12:33:59End: 2010-08-04 13:01:18Seconds: 2068Total number of files scanned: 133770Total number xml logs created: 5253Scan Complete
After the scan completes, your next step is to import the scan into the SQL database.
1. At an Administrator command prompt window, navigate to the Database folder, and then type the following command:ImportScans.bat .\ompm ompmdb c:\ompm\scandata
2. Wait while the scan data is imported into the SQL database.
Now you are ready to use the OMPM Access Report Viewer. Follow these steps:
1. Navigate to the c:\ompm\report folder and double-click the ompm.accdr file. (Update: A new version of ompm.accdr is available here.)
2. In the Microsoft Access Security Notice dialog box, click Open.
3. On the Welcome to the Office Migration Planning Manager screen, enter the following information:Server: .\ompmDatabase: ompmdb
4. Click Connect. You’ll see new links appear at the bottom of the page, like this:
5. Click Office 2010 Compatibility, which takes you to the Overview tab of the report viewer:
6. Click the Issue Summary tab to view a summary of the scan results. Depending on your scan results, you’ll see issues that are classified as Green, Red, and Yellow.
7. Now let’s view the Scanned files tab to take a closer look at the red and yellow issues.
8. Click the DOWN ARROW next to the Max Level column to filter the list to show only red and yellow issues. (FYI, if you don’t have any Red issues, they won’t appear in this list.)
9. In the filtered list, click the file name link to view more details about the issues detected during the scan. Here is one example of a PowerPoint file that has both red and yellow issues:
I’ll wrap up this first blog post here to give you time to experiment on your own. For my next post, I’ll review the results from macro scanning.