CD installation

  • For the CD media please run the setup.exe program located under the CD’s D:\setup.exe.

Zipped installation set

  • The zipped installation set is available from either:

Provided by an EzeScan consultant

OR

Downloaded from the EzeScan website (https://www.EzeScan.com.au)

https://www.ezescan.com.au/downloads/software-downloads/ezescan-installers/ezescan-full-installation

Downloads > Software Downloads > EzeScan Installers

  • Save the zipped installation set to a suitable location on the PC being used
  • Right click properties on the zip file and check if the file is blocked. If so, click unblock and apply and ok.

            

  • Unzip the file and run the setup.exe program
 

 

Installation wizard

This will launch the EzeScan installer. The main installation screen displays:

EzeScan Setup Wizard screen

  • Select Next to continue.
  • The License Agreement screen displays:

You must agree to the license agreement before proceeding

  • If you agree to the License Agreement, Select the I Accept Checkbox
  • Select Next to continue.
  • The Choose Destination Location screen displays:

Ensure the “Create a shortcut” box is ticked before clicking Next

Select Next to accept the default installation directory of C:\Program Files (x86)\Outback Imaging\EzeScan. (If required: Tick to create a shortcut on the desktop)

Click Install button

  • Click Install to begin the installation
  • The next screen displays while the software is loaded onto the workstation:

 

Installing EzeScan progress screen

Installation completed screen

  • Click Finish to close the setup wizard.

The administrator can then log off and allow the operator to login and use EzeScan.

Direct link to FAQ

The below details how to configure an EzeScan Job or Route to use MicroSoft Office 365.

EzeScan 4.3.197 (Version 4 platform) or 5.0.28 (Version 5 platform) or above is required.

Firstly an App Registration is to be performed in the Azure Portal. This is to allow EzeScan to be able to connect to the mailbox to download email items.

Note: A registration by default will allow access to all mailboxes. Upon completion of the registration follow this link to restrict access to the mailbox (or mailboxes) that EzeScan require.

Perform App Registration

FAQ142-2.png

 

The administrator would choose the account type (this needs to be noted for EzeScan configuration later). We would recommend using Single Tenant.

FAQ142-3.png

The redirect URI needs to be configured. We recommend http://localhost (this needs to be noted for EzeScan configuration later)

FAQ142-10.png

The client secret needs to be created this needs to be noted for EzeScan configuration later.
Please note: When creating the secret, we require the secret value, not the secret ID. This needs to be copied upon creation as it can’t be retrieved again. If in error, delete and create a new secret.
 

FAQ142-5.png

 

The API permissions to be configured.

FAQ142-6.png

Select Microsoft Graph

FAQ142-7.png

 

Select Application permissions and choose:

  • Mail.ReadWrite
  • User.Read.All

FAQ142-8.png

Configured permissions

FAQ142-9.png

Once all this is completed the EzeScan configuration can be performed.

The following information needs to be noted to be passed on to whoever is responsible for configuring in EzeScan:

  • Tenant ID (If Single-Tenant ID)
  • Client ID
  • Client Secret (It is a good idea to internally document when this secrect will expire so you can update EzeScan in the future with the next one generated).
  • Redirect URI (should be http://localhost)

If possible. The Azure administrator can approve the registration. Otherwise it will be performed later in the EzeScan connection.

EzeScan Configuration

The next step is to configure EzeScan to connect to the mailbox.

This step will also require an Azure Administrator to grant consent to the new app registration (if not yet approved).

Note: If an Azure administrator is not configuring EzeScan, the person configuring EzeScan will provide a URL link for the Azure administrator to approve.

- Load EzeScan as an administrator

- Select Admin -> Jobs -> Import Tab or Admin -> Routing Import Tab

Functionality is added as Import Folder “Import Sources” as shown at right and is applicable to both an EzeScan Client and EzeScan Server configurations

Note: Previously you may have a IMAP Import Profile, and may be migrating to Office 365. Unitck the IMAP profile (for now) and click and plus icon to add a new connection

FAQ142-1.png

Click the plus icon to add a new connection and select Microsoft Office 365 outlook from the pull down list.

Change the OAuth Registration to Custom

Change the OAuth Registration Type to Single Tenant 

Set the Authorisation Type to Client Credentials

O365Settings.png

 

- Complete the Tenant ID, Client ID, Secret and Redirect URI (from the registration process).

- Then click on the ... for the admin consent. A web page will display asking for approval.

FAQ142-12.png

FAQ142-13.png

Once the wizard above has been completed this screen may return an error

This page isn’t working

localhost didn’t send any data.

ERR_EMPTY_RESPONSE

Close the tab and the connection has been completed.

The operator can then configure the rest of the Import Documents Settings below.

 

FAQ142-14.png

Note: If migrating from IMAP to Office 365, you can flick between the profiles to note the previous settings and then apply to the newly created Office 365 connection.

When complete you can leave the IMAP settings unticked or remove that profile completely.

 

For more information about this connection method please see the below Microsoft links which provide more information:

https://docs.microsoft.com/en-us/graph/auth-register-app-v2

https://docs.microsoft.com/en-us/azure/active-directory/develop/quickstart-configure-app-access-web-apis

https://docs.microsoft.com/en-us/graph/auth-limit-mailbox-access (we recommend this link for restricting the app registration to the mailboxes only required for EzeScan use)

Direct link to FAQ

If you look at the scanned image and you have an unwanted solid band/slice of black pixels on the top, bottom, left or right sides of the mage then this FAQ is for you.

Here's our top tips to help you troubleshoot and fix your problem.

1. If the black edges are on the left and right sides of the image, your paper width is most likely set to be larger than the physical width of the paper. Either:

   a. Make sure the scanner input tray guides are locked in the centered position and that images are not being skewed due to loose guide positioning.

   b. Make sure the paper orientation (portrait/landscape) in the scanner settings is set to match the physical page orientation in the scanner in-tray.

   c. Make sure the paper size (e.g. A4, Letter, Legal, A3) in the scanner settings matches the paper size of the physical pages being scanned.

   d. If an exact match for the paper size does not exist, then use a custom paper size and set the paper height and width settings to exactly match the physical page size.

   e. If the scanner supports 'Auto' paper size, try turning that on to see if it fixes your problem.

   f. If the has a  separate 'Auto crop' option try turning that on to see if it fixes your problem.

2. If you have black edge on the bottom of the image you need to check:

   a. The paper height setting is set incorrectly. Use the correct paper size for the height of the pages being scanned.

   b. The paper height setting is set incorrectly. Use a custom paper size and set the height setting to match the height of the pages being scanned.

3. If you have a black edge only on the leading edge of the scanned image (i.e top edge in most cases) then check:

   a. The upper paper feed rollers for wear and tear. If the pick roller/first roller is too slow to start scanning the page, the lamp turns on and starts producing a slice of black pixels until the white paper actually moves over the lamp. This is caused by worn rollers in the scanner throat. Try replacing the main drive rollers which are easily replaced consumable parts. They are usually the top rollers when you open the scanner throat.

   b. The lower rollers for wear or tear. Also on Kodak Alaris i2900,i3000, i4000 and i5000 series scanners if the brake roller is too hard or seized completely it can slow down the picking up of the paper, and cause the same issue as 3a above. Try replacing the brake roller on the lower section of the scanner throat.

  c. Feed and brake rollers are consumable parts meant to be purchased as needed and replaced by the customer. These rollers only last somewhere between 100,000 to 250,000 pages scanned. Many have visible tread pattern that wear's out muck like the tread wears out on a bald car tire/tyre. They are the biggest cause of scanner mis-feed problem and paper jams.

4. Most issues are fixed by going through troubleshooting steps 1a-1f, 2a-2b and 3a-3c. If you still have a problem there are some issues to consider.

a. Sometimes the scanner vendors driver settings for paper sizing and auto paper sizing have quirky issues during scanning. Paper sizes end up wrong or things get cropped off that you don't expect to and nothing seems to fix them. The first thing to try is download the latest scanner driver (with TWAIN support) and install it on the PC. Then retest to see if the problem is fixed. In most instances these will help solve some of your issues.

b. If you get to here and your images are still wrong. Create a new scan job and try carefully setting it up one step at a time. After each change of setting is made, make sure the whether the problem is fixed, still occurring or has gotten worse.

c. In rare circumstances the transistors in the main scanner drive circuits are blown or are defective, so that the scanning is no longer fully synchronized with the image capture system. We have  only seen this twice in 15 years and we are dealing with 1000's of scanners.

We hope you found these tips useful. Please check out FAQ 126 if you are having a problem with small thin vertical lines appearing on your scanned images.

 

 

 

 

Direct link to FAQ

1. This depends on which version of EzeScan Desktop software you are using:

   EzeScan Desktop V5.0 and higher 

       Yes - The 64 bit version of EzeScan Desktop v 5.0 supports only 64 bit TWAIN drivers

       No -  The 32 bit version of EzeScan Desktop v 5.0 supports only 32 bit TWAIN drivers

   EzeScan Desktop v4.3 (Now superseded)

       No - EzeScan Desktop v4.3 is available as 32 bit only. It only supports using 32 bit TWAIN drivers.

2. The second consideration is how old your scanner is?

      As a rough guide:

      Scanner models introduced new to the market before 2013 are likely to only include 32 bit TWAIN drivers.

      Scanner models introduced new to the market between 2014 and 2018 will include 32 bit TWAIN drivers, and some may include 64 bit TWAIN drivers as well.

      Scanner models introduced new to the market from 2019 to now will most likely include both 32 bit TWAIN drivers and 64 bit TWAIN drivers.

      Scanners sold from around 2013 to 2019 seem to have the most issues when trying to install and use 64 bit TWAIN drivers. Many scanner vendors seem to allude to 64 bit support , but in reality they didn't include 64 bit TWAIN drivers in their software installers. They just added support for Windows 64 bit Operating Systems (i.e. they still wanted you to use a 32 bit scanning application with a 32 bit TWAIN driver on the 64 bit Operating System). It's interesting to note that Kodak Alaris did release updated TWAIN 64 drivers for its older i3000, i4000 and i5000 model scanners, Whereas Canon did not release TWAIN 64 drivers for its DR-G1100/1130 range. It's really up to the scanner manufacturer whether they do this or not.

3. We've worked out some quick and easy ways to check if the scanner vendors 64 bit installer package is actually installing a TWAIN 64 bit driver onto your computer.

    a. The simplest way is to check if a 64 bit TWAIN driver file was added by the Scanner manufactures software installer into the c:\windows\twain_64 directory. There has to a be driver file for that model or series of scanner located in this directory for it to work with any 64 bit version of scanning software (like the 64 bit version of EzeScan Desktop V5.0). If there is no driver file for the scanner in the c:\windows\twain_64 directory then the scanner will not appear in 64 bit version of EzeScan Desktop v5.0 when you browse TWAIN Sources for available scanners.

b. Google search on-line for a download link for the TWAIN org's twack64 bit test application. Find a download link that you trust, download and install the program and run it. Then use the Twack64 app's 'Select Scanner' option to browse a list of installed 64 bit TWAIN scanner drivers. If you can see your scanner model/series in the list of available TWAIN Sources, then you know that  the Scanner Manufacturer's software installer has supplied and installed 64 bit TWAIN drivers. The scanner should now also be browse-able as a TWAIN Source in the 64 bit  version of EzeScan Desktop v5.0.

c. If your scanner does not show up in Twack64 list of available 64 bit TWAIN scanner sources then the either you've installed the wrong TWAIN driver installer package from the Scanner vendor website, or the scanner was never released with 64 bit TWAIN driver support. Scanner manufacturers of old scanners that are not providing 64 bit TWAIN drivers by now, will most likely never provide a new driver update to support 64 bit TWAIN. So realistically you have will have 2 options:

    1. Use your old scanner with a 32 bit scanning application that will use the 32 bit TWAIN drivers. You could then use your licensed copy of the 32 bit version of EzeScan Desktop v5.0 to work with the scanners 32 bit TWAIN driver.

    2. Upgrade your scanner to a model that includes TWAIN 64 bit drivers. You could then use your licensed copy of the 64 bit version of EzeScan Desktop v5.0 to work with the scanners 64 bit TWAIN driver.

We hope you found this information useful.

 

 

 

 

Direct link to FAQ

None of our products or solutions use any implementations of Java.

EzeScan can confirm that:

  • There is no Log4j vulnerability in our EzeScan Desktop or EzeScan Server program applications.
  • There is no Log4j vulnerability in our EzeScan WebApps applications.
  • There is currently no Log4j vulnerability in our implementation of EzeScan Cloud  on the AWS platform.

Customers do not need to patch or upgrade our software to rectify any Log4j vulnerability.

Direct link to FAQ

Pages