Install Microsoft Document Imaging 2010

Posted on by admin
  1. Microsoft Office Document Imaging Install
  2. Microsoft Office 2016 Document Imaging

First introduced in Office XP, the Microsoft Office Document Imaging application was later deprecated in Office 2010, as most of its features were integrated in several mainstream applications (such as Word), precluding the need for a separate program to handle its capabilities. After the install you probably want to find Microsoft Office Document Imaging in the start menu, R-click on it, choose More, and Run as Administrator. Once you have the application running with Administrator privileges go to the menu and choose Tools/Options select the Other tab and click on the Reset button to make it the default app for TIF.

Microsoft Office Document Imaging was a feature installed by default in Windows 2003 and earlier. It converted the text in a scanned image to a Word document. Redmond removed it in Office 2010, though, and as of Office 2016, hasn't put it back yet.

The good news is that you can reinstall it on your own—rather than purchase OmniPage or some other relatively expensive commercial optical character recognition (OCR) program. Reinstalling Microsoft Office Document Imaging is relatively painless.

Once you have done so, you can scan the text of a document into Word. Here's how.

of 06

Open Microsoft Office Document Imaging

Click on Start > All Programs >Microsoft Office. You’ll find Document Imaging in that group of applications.

of 06

Start the Scanner

Load the document you want to scan into your scanner and turn the machine on. Under File, choose Scan New Document.

of 06

Choose the Preset

Choose the correct preset for the document you’re scanning.

of 06

Choose Paper Source and Scan

The program’s default is to pull paper from the automated document feeder. If that’s not where you want it to come from, click on Scanner and uncheck that box. Then, click the Scan button to start the scan.

Microsoft Office Document Imaging Install

of 06

Send Text to Word

Once it finishes scanning, click on Tools and select Send Text to Word. A window will open giving you the choice of keeping photos in the Word version.

of 06

Edit the Document in Word

The document will open in Word. OCR isn't perfect, and you’ll probably have some editing to do—but think of all the typing you've saved!

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:

Microsoft Office 2016 Document Imaging

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).

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

Imaging

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

  • Serrano
    goyanks1981 Mar 14, 2013 at 05:09pm

    Thanks for this Rob. This is going to simplify my workstation rollouts even further!

  • Mace
    Chamele0n Mar 14, 2013 at 05:15pm

    Thanks Rob, nice work.

  • Jalapeno
    batsnapper Jun 18, 2013 at 08:48pm

    This works great for viewing and we use MODI as our TIF viewer with DocVue imaging system. This solution was necessary as we migrate Office 2010.

    However, we often use the File / Send To / Recipient as Attachment. It crashes in the install environment described above with Office 2010 Pro 64bit on Win7 64bit. It presents a Switch To. Retry error and just hangs.

  • Pure Capsaicin
    Rob Dunn Jun 18, 2013 at 09:46pm

    Batsnapper - Any time you have an Office component like MODI, etc. you need to have your versions of those components match. Only 32-bit MODI with 32-bit Office, etc. Mister retro coupon code.

  • Pimiento
    xopher.james Mar 4, 2015 at 08:46pm

    I don't know if anyone still follows this post, but when we try the above steps in a Win7 64-bit environment at our office, OCT removes the items that are set as 'Not Available'. Are we missing a step?

  • Pure Capsaicin
    Rob Dunn Mar 4, 2015 at 09:09pm

    Do you already use Sharepoint designer? What other Office apps do you have installed?

  • Pimiento
    xopher.james Mar 4, 2015 at 09:15pm

    No we do not use sharepoint designer, but when we did download it, it did not provide the Admin folder for the OCT. What we are using is the OCT via the MS office folder. What we also have installed are the standard office applications such as, word, powerpoint, excel, outlook etc.

  • Pure Capsaicin
    Rob Dunn Mar 4, 2015 at 09:21pm

    Yep, you have to create the administrative install with the extracted Sharepoint Designer folders and nothing else. As an aside, I just downloaded the designer again, ran the extract command and it created an admin folder no problem (amongst others). Maybe try again? I'm guessing that by using the OCT supplied by Office, it's removing the items that match up in the installer.

  • Pimiento
    xopher.james Mar 4, 2015 at 09:39pm

    We must have overlooked that step. We tried again, but received the following error:

    'The installation of this package failed.'

    Any ideas? Thank you for all your help by the way. Much better than banging my head against the desk!

  • Pimiento
    xopher.james Mar 5, 2015 at 03:03pm

    Solved that part.. we weren't running as admin. Will continue trying to sort this out today. Thanks again for all your help!

  • Pimiento
    xopher.james Mar 5, 2015 at 05:10pm

    OK. I'm told the guy trying to automate it has solved his issue. Thank you!

  • Pure Capsaicin
    Rob Dunn Mar 5, 2015 at 05:14pm

    That's great! I'm glad you got it all sorted out.

  • Jalapeno
    michael menzie Apr 15, 2015 at 02:45pm

    awesome article but could someone help me with a part i do not understand?? the part where it mentions:

    '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.'

    i do not want sharepoint designer to show in add/remove programs but the screenshot in the articl does not specify where to put the lock/hidden attributes. do you do it to them all??? i just need that piece for mine to be perfect

  • Pure Capsaicin
    Rob Dunn Apr 15, 2015 at 02:54pm

    It's an additional setting in the same place as 'Run all from my computer/Run from my computer.' You need to do this for any feature you install so 'Sharepoint Designer' does not show as an installed program.

    I've updated the screenshot.

  • Jalapeno
    michael menzie Apr 15, 2015 at 07:07pm

    hello Rob Dunn,
    sorry for sounding like such an inexpierienced noob but i know where the lock and hidden is i just didn't understand what ones i should set to locked and hidden. so i am guessing by what you are saying is that i should only apply the lock and hiddend to 'Microsoft Office Document Imaging', 'Scanning, OCR, and Indexing Service Filter', and 'help' since those are the ones i enabled and all the 'not available' ones do NOT need the lock and hidden. is that correct??

  • prev
  • 1
  • 2
  • next