Setting up new scanner machines
New scanner machines have to be setup as follows:
- Log in as local admin not as a privileged user who belongs to the local admin group
- Install Perceptive Content Client
- Plug in scanner
- Install ISIS driver based on the scanner model and OS installed on the machine: http://www.fujitsu.com/global/support/computing/peripheral/scanners/drivers/isis/v21112105001.html
- Install KOFAX VRS driver based on the scanner model and OS installed on the machine: http://www.fujitsu.com/global/support/computing/peripheral/scanners/drivers/sv-5pro.html
- Copy this file to the workstation to which the scanner will be attached.
- Run it to unzip the installation files.
- Run the setup.exe file.
- Register the product. Use any of the values as needed to complete the registration on your workstation
- Test scanner connectivity and KOFAX VRS by opening either KOFAX VC Demo or KOFAX Test Console
- Make sure the scanner can actually scan documents to either of the two tools mentioned above
- Once this the scanner can scan documents, the Imagine team can take over to create capture profiles
- Once the Imagine admin has created capture profiles in this machine: copy inscan.xml and indevice.xml file from the local admin (or from whoever is logged in at the time the capture profiles have been created) to all the users' profiles that will be using this machine or that will be scanning.
- Please see instructions at How to copy Capture Profiles?
Why isn’t my scanner working?
Check the power first. Power off your scanner, and then your computer. Power up your scanner, and then your computer. If the power cycles do not restore your ability to scan, call your technical support for hardware check.
Best practices for scanning performance
Below are best practices developed by Perceptive Software based on experience deploying and supporting CaptureNow in customer environments.
- Allocate at least 2 GB of RAM to the scanning computer. As images are scanned, they are stored in memory, written to the hard drive, and then uploaded to the server. The more memory available to the scanner, the fewer times it has to write those images to the file system.
- If business needs allow, scan in Black and White at 200 dpi. Higher resolution, grayscale and color increase the size of the stored image, which slows down the upload process. However, optimal patchcode recognition occurs at 240 dpi, and optimal OCR results occur at 300 dpi.
- Use a USB 2.0 connection to connect the scanner to the scanning station.
- Verify that the scanning computer is using the latest ISIS drivers for the scanner model.
- If a full antivirus scan is performed regularly on the ImageNow Server computer, exclude the Scanned folder within the user's workpath on the scanning computer from real-time antivirus scanning. If this folder is not excluded, then each page will be examined by the antivirus software during scanning, which can slow down the scanning process.
- The work path for an ImageNow user can be found by clicking Help, then About from the ImageNow Client.
Why are my scanned images of poor quality?
There are several possible reasons.
- First check the resolution settings on your scanner. The recommended resolution for scanning is 150 dpi and Fine for faxing.
- The poor quality of the scan could also be due to the quality of the document you are scanning.
- Finally, check to see if your scanner needs to be serviced. Contact your local IT support for an initial review.
What do I do when a scanner machine is being replaced?
As PCs are replaced by new ones, problems with the scanner, capture profiles, etc. can arise if the appropriate actions are not taken, especially when PCs connected to scanners are being replaced.
(Please note that local IT admin should perform the steps in this section)
1. Before removing the old machine, please make sure to:
- Copy the indevice.xml or inscan.xml files from either C:\Documents and Settings\<<username>>\Application Data\ImageNow on XP, C:\Users\<<username>>\AppData\Roaming\ImageNow on Windows 7 for roaming profiles, or C:\Users\<<username>>\AppData\Local\ImageNow on Windows 7 for local profiles(the local IT administrator knows the specific path) as they will be used after the new machine has been set up. Please see corresponding instructions:How to copy capture profiles.
- Copy Kofax license number (if applicable).
2. Once the new machine has been setup with the ImageNow client:
Click on the installation file and “run as administrator”.Apply Kofax license as needed - Note: If no Kofax license exists, please make sure to fill in the registration window that pops up after the installation and reboot. If this step is not performed, there will be a Kofax watermark on each scanned page.Test that the machine can connect with the scanner and actually scan pages (without using ImageNow).If the scanner successfuly scans pages, without ImageNow, proceeed to copy the indevice.xml and inscan.xml files from step 1.a above. Please see corresponding instructions: How to copy capture profiles. This should bring the capture profiles the user normally applies.The user should log into ImageNow and proceed to use capture profiles. If there are problems, send an email to firstname.lastname@example.org.
- Install the corresponding scanner driver.
- Install the corresponding Kofax VRS version (http://www.kofax.com/support/products/vrs/4.2/downloads.php)
- Please note: the download requires a previously licensed version of VRS 4.0 or 4.1 in order to work. Also note that Kofax might not support VRS version 4.1 anymore.
Note: if after having copied the indevice.xml and inscan.xml files, and especially after the user has logged out of Windows and logged back in, the capture profiles "have disappeared", try changing the ownership of those files; that is, make sure the owner of those files is the actual user and not the local IT admin. For example, in the case below, Peter, the local IT admin, appropriately copied the files; however, every time the user, Cindy, logged out of Windows, those files were overwritten by default files causing the user to "lose" the capture profiles. In this case, all the capture profiles had to be recreated from scratch since we didn't know about the "ownership" issue.