Ms Office Document Imaging 2010 Download

If you have been using Microsoft’s Office Document Imaging and are wondering where it went in Office 2010, you’re not alone. Microsoft has dropped it as of Office 2010, but there is a workaround to install it in Office 2010 by using the Office 2007 version of it. Click Microsoft Office, and then select Microsoft Office Tools. Click Microsoft Office Document Imaging. Method 2: Install MODI with the 2007 Office System media. To use MODI in the 2007 Office System together with Office 2010, follow these steps: 1. Start the 2007 Office System setup process. Review, and then accept the software. Microsoft Office document imaging is used to scan hard copies of documents and import them into your Microsoft Office suite for editing. This feature was always bundled in with the Microsoft Office package from Office XP through to Office 2007, but now for some reason, Microsoft has decided to take it out of the latest version Microsoft Office 2010. Microsoft Office Document Imaging (MODI) is removed. To retrieve the feature, here is a thread for your reference: Retrieve Features that have been deleted for Free - MODI, Picture Manager and ClipArt.

Learning has never been so easy!

MODI (Microsoft Office Document Imaging) was an application that was bundled with Microsoft Office 2003 and 2007. This application allowed you to scan, annotate, perform OCR and re-arrange pages inside of a viewer. Many people used MODI as an important part of their workflow with many other pieces of software (such as EMR document management, for example).

Once Office 2010 was released, Microsoft stopped bundling MODI, and required you to install it from Office 2003/2007 media. If you did not have licensing for these applications, you may not have had the capability of using or installing MODI for your business use.

Fortunately, Microsoft's free Sharepoint Designer 2007 includes MODI as part of its bundle.

Here are the instructions on how to deploy MODI automatically with a Microsoft Installer patch file (.msp) - which you can generate using the setup executable.

6 Steps total

Step 1: Download SharePoint Designer 2007

Find SharePoint Designer 2007 at the following link (note that SharePoint Designer 2010 does NOT include MODI):

http://www.microsoft.com/downloads/en/details.aspx?FamilyID=BAA3AD86-BFC1-4BD4-9812-D9E710D44F42&displaylang=en

Step 2: Extract the files from the downloaded executable to a folder

This download does have the ability for the admin to create a customization file in the Office customization tool (OCT) to install MODI. You will need to download the main .exe; SharePointDesigner.exe, then extract the files with the command line. For example:

ServernameShareNameSharePointDesigner2007_downloadSharePointDesigner.exe /extract:servernamesharename

This will extract the setup.exe, Admin folder, etc. to servernamesharename

Make sure you perform this step with appropriate administrative rights.

Step 3: Open the Office Customization Tool

From the extracted folder location, run the following command to create the customizations in the OCT:

ServernameShareNameSharePointDesigner2007setup.exe /admin

Step 4: Select the custom options for SharePoint Designer (note that you won't actually install the Designer!)

Within the OCT, you would go to Set feature installations state, and make everything 'not available,' except MODI, as in the screenshot here. Changing the OCT settings to hidden and locked, if you do not want users to utilize SharePoint Designer, will hide it from within the Add/Remove Programs.

Step 5: Save your patch file (.msp) to the 'Updates' folder

Save the resultant .msp (file>save) file and save it in the ‘updates’ folder where you extracted the Sharepoint Designer resource files. When you double-click setup.exe the install will use this file to define its installation parameters (no need to call it from the command-line).

Microsoft Office Document Imaging 2010

Step 6: Bonus: unregister name.dll to disable Designer interaction with IE

After the installation of SharePoint Designer, if you are using SharePoint document libraries, it is recommended to unregister the Name.dll for SharePoint Designer (unless you have the actual Designer component installed). Unregistering the Name.dll for SharePoint Designer will address the interaction of Office files stored on a SharePoint document library and having two different versions of Office products (Office 2010 and SharePoint Designer 2007) on the computer.

Published: Mar 14, 2013 · Last Updated: Apr 15, 2015

References

You Asked, We Answered... Where is MODI?

16 Comments