Lexmark 'Scan to EMR' Solution v3.2.0 Readme

2. MFP device memory requirements: A minimum of 256 MB RAM



3. The MFP must have a hard drive installed.



4. Protocols required to function, to include:

• Common Internet File System (CIFS): A dialect of the Server Message Block (SMB) protocol. Destinations that use Windows Shares employ this protocol.
• File Transfer Protocol (FTP): Destinations that use FTP Shares employ this protocol.
• Lightweight Directory Access Protocol (LDAP): The application and the MFP use this protocol when authenticating using Directory Services such as Microsoft Active Directory.

NOTE: Other protocols also may be supported.

5. Open ports

• 137
• 138
• 139
• 9100
• 9400

6. This application requires an electronic license. To obtain a license, go to www.lexmark.com and click the "Contact Lexmark" link at the bottom of the screen.

Package Contents

The following files and publications are included in Scan to EMR v3.2.0.

1. ScanToNet-3.2.0.fls – Scan to EMR solution



2. ScanToNet-3.2.0_desc.xml – Solution descriptor file



3. LicenseServer.exe – Network license manager



4. Administrator_Guide.pdf – Administrator's Guide



5. User_Guide.pdf – User's Reference Guide



6. Readme.txt – (this file) Language-specific files for this application can be found in a sub- directory named for each supported language.

Limitations and compatibility of this release

1. MAXIMUM NUMBER OF IMPORTED DESTINATIONS WITH MARKVISION PROFESSIONAL

This release of Scan to EMR supports importing a maximum of 25 destinations (without custom images) through MarkVision Professional (MVP). If custom images are used, less than 25 destinations can be imported through MVP. In addition, even if 25 destinations are imported successfully, MVP may display a "Failed to import Scan to EMR Folder config. file" message.

2. SAVED FILE BEHAVIOR WHEN SCAN IS CANCELLED

A scan job can be cancelled in one of two ways: during the scan or after the scan is complete but the job has not been accepted. For each of these scenarios, the application may behave differently for "multi-page" file formats (PDF, XPS, and multi-page TIFF) than for "single-page" formats (JPG and single-page TIFF).

3. If preview is disabled and the job is cancelled after the scan is complete (i.e., when the "Scan the Next Page" or "Finish the Job" screen is displayed), the application will start writing the images as it starts receiving data from the scanner. This occurs immediately after "Scan It" is clicked. Therefore, the files will be saved on the network share, regardless of their format. Whether these files can be opened or used depends on the file type. JPG files can be opened, but PDF, single-page TIFF, multi-page TIFF, and XPS files cannot be opened.

4. CONFIGURATION FILE COMPATIBILITY

Configuration files from this release are not compatible with those of earlier versions of Scan to EMR. However, exported configuration files from Scan to EMR v2.0.7 and higher can be imported into this version.

5. SUPPORTED OPERATING SYSTEMS FOR DESTINATIONS

NOTE: All Microsoft Windows operating systems listed below are 32-bit unless otherwise noted. Share drive

• Microsoft Windows Vista Ultimate Edition
• Microsoft Windows 7 Ultimate
• Microsoft Windows 7 Ultimate 64 Bit
• Microsoft Windows Server Professional 2008
• Microsoft Windows Server 2008 64 Bit
• Microsoft Windows Server 2003 Standard Edition SP1
• Microsoft Windows Server 2003 Standard Edition R2
• Microsoft Windows XP Professional SP2
• Microsoft Windows 2000 Professional SP4
• Microsoft Windows 2000 SP4

FTP

• Microsoft Windows Vista Ultimate Edition
• Microsoft Windows 7 Ultimate
• Microsoft Windows 7 Ultimate 64 Bit
• Microsoft Windows Server Professional 2008
• Microsoft Windows Server 2008 64 Bit
• Microsoft Windows Server 2003 Standard Edition SP1
• Microsoft Windows Server 2003 Standard Edition R2
• Microsoft Windows XP Professional SP2
• Microsoft Windows 2000 Professional SP4
• Microsoft Windows 2000 SP4
• Redhat Linux Enterprise Edition
• Sun Solaris 10 Novell OES Linux SuSE 9

6. The following Microsoft Windows Server 2003 configurations are supported.

• Standalone Distributed File System (DFS)
• Domain-based DFS
• Domain-based DFS with one-child domain used for authentication

7. CONNECTION DROPPED BEFORE SCAN DATA IS SENT

The amount of time before the application begins to send the scan data to an FTP server may exceed the amount of time the server will keep an idle connection open. This results in the connection being dropped before the scan data is sent. The application shows an "application error has occurred" message.

When the user selects the "OK" button, a "Scan Failed" confirmation screen appears along with another "application error has occurred" message that has three options: "Yes, to same destination," "Yes, to a different destination," and "No." If the user selects "No," the application returns to the home screen.

This issue can be resolved by having the network (FTP server) administrator increase the idle session timeout for the FTP passive mode.

8. NETWORK SAVE FAILS IF FILE IS ALREADY IN USE

If the file to which the scan data is being written is already in use by another application or user, the network save operation will fail. The application shows a "The scan cannot be completed using this filename. The file is currently being used by another program" message.

When the user selects the "OK" button, a "Scan Failed" confirmation screen appears along with another "The scan cannot be completed using this filename. The file is currently being used by another program" message that has three options: "Yes, to same destination," "Yes, to a different destination," and "No." If the user selects "No," the application returns to the home screen.

9. "START IN USER DIRECTORY" BEHAVIOR

If the administrator selects the "Start in user directory" option, the application will attempt to store the scanned file in a subdirectory with the same name as the user ID. Some file systems may automatically place the user in the "user" directory, so the application may create yet another subdirectory named for the user. If this behavior is noted and is not desirable, turn off the "Start in user directory" option.

10. "START IN USER DIRECTORY" BEHAVIOR WITH LDAP PATH ATTRIBUTE SET

On a Windows FTP server, if the value returned by the LDAP server or the path attribute is the same as the username, an issue similar to the one documented in 9 above occurs. The user is automatically placed in the "username" directory (see 9 above), and the application's attempts to connect to the FTP server will fail because it will not be able to find the "username" directory.

11. SAVED FILES WITH LONG CUSTOM FILENAMES CANNOT BE OPENED

If the length of a custom filename is between 241 and 255 characters, the scanned image will be saved successfully in the destination, but it cannot be opened or previewed. This issue occurs only on Windows machines. If the filename exceeds the limit of 255 characters, an error message and a "Scan Failed" confirmation are displayed .

Installation details

For further installation and configuration instructions, please see the Lexmark '

Scan to EMR'

LEGACY ID: FA818