Scan to Network App Release Notes History

Release Notes

• Fix for Scan To Network inter-operation with Background and Idle Screen.

• Fix for XML file not saved when you scan a document after you delete the profile template in Barcode Discovery app

For more information on installation and configuration instructions, see the Lexmark Scan to Network Guide and the Scan to Network Premium Administrator's Guide provided with the application. Adobe Acrobat Reader is required to view these guides.

Back to top

Overview

This Readme file pertains to the current release of the LEXMARK SCAN TO NETWORK application.

Lexmark Scan to Network is an embedded solution that can be installed on printers that support the Lexmark Embedded Solutions Framework (eSF) v4.x or v3.x. Scan to Network enables users to scan documents to a network, with network destinations chosen by the administrator.

Scan to Network:

• Eliminates time spent transferring scanned files from a computer to a network drive

• Reduces the steps used to store scanned documents on a file share

• Simplifies the process of archiving scanned files

• Enables a destination to be configured to determine the actual network location via an LDAP lookup

NOTE:

This unlicensed version of Scan to Network is fully functional and includes basic scan settings. A premium version of Scan to Network is available in the Lexmark Virtual Solution Center. Scan to Network Premium offers advanced features such as custom prompt creation and bar code scanning.

Scan to Network Premium requires a license. To obtain a license, go to

and click the "Contact Lexmark" link at the bottom of the page.

Associated files

The following files and publications are included in the release.

a. Application files

• scanToNet_e4_s2-4.8.11.fls The Scan to Network application for eSF v4.x printers with 7- and 10-inch displays

• scanToNet_e4_s3-4.8.11.fls The Scan to Network application for eSF v4.x printers with 4.3-inch displays

• scanToNet_e3_s2-4.8.11.fls The Scan to Network application for eSF v3.x printers

b. Other files

• scanToNet_e4_s2_desc-4.8.11.xml The solution descriptor file for eSF v4.x printers with 7- and 10-inch displays

• scanToNet_e4_s3_desc-4.8.11.xml The solution descriptor file for eSF v4.x printers with 4.3-inch displays

• scanToNet_e3_s2_desc-4.8.11.xml The solution descriptor file for eSF v3.x printers

• LicenseServer.exe The network license manager

c. Publications

• Lexmark_ScanToNetwork_AdminGuide.pdf The Administrator's Guide

• Lexmark_ScanToNetwork_UserGuide.pdf The User's Guide

• Readme.txt (This file)

Requirements

a. A printer that supports eSF v4.x or v3.x applications

Supported eSF v4.x printers include:

• CX410 Required firmware level: LW40.GM4.P436 or later

• CX510 Required firmware level: LW40.GM7.P436 or later

• MX410, MX51xRequired firmware level: LW40.SB4.P436 or later

• MX61x Required firmware level: LW40.SB7.P436 or later

• MX6500e Required firmware level: LW40.JD.P436 or later

• MX71x Required firmware level: LW40.TU.P436 or later

• MX81x Required firmware level: LW40.TU.P436 or later

• MX91x Required firmware level: LF.MG.P053 or later

Supported eSF v3.x printers include:

• X54x Required firmware level: LHS40.VK.P440 or later

• X74x Required firmware level: LHS40.NY.P440 or later

• X79x Required firmware level: LHS40.MR.P440 or later

• X92x Required firmware level: LHS40.HK.P440 or later

• X95x Required firmware level: LHS40.TQ.P440 or later

• 6500e Required firmware level: LHS40.JR.P440 or later

b. Memory: The printer must have 256MB of RAM.

c. Protocols

Scan to Network uses the following protocols.

• 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 printer use this protocol when authenticating using Directory Services such as Microsoft Active Directory.

NOTE:

Other protocols may also be supported.

d. Ports

Scan to Network uses the following ports.

• 137

• 138

• 139

• 445

• 9100

• 9400

Limitations and compatibility of the release

Common issues

a. This release of Scan to Network supports importing a maximum of 25 destinations (without custom images) through Markvision Enterprise (MVE). If custom images are used, then less than 25 destinations can be imported through MVE. In addition, even if 25 destinations are imported successfully, MVE may show a "Failed to import Scan to Network Folder config file" message.

b. 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 multipage file formats (PDF, XPS, and multipage TIFF) than for single-page formats (JPEG and single-page TIFF).

If preview is disabled and the job is cancelled after the scan is complete (that is when the "Scan the Next Page" or "Finish the Job" prompts are shown), then the application starts writing the images as it starts receiving data from the scanner. This action occurs immediately after "Scan It" is clicked. The files are saved on the network share, regardless of their format.

Whether or not these files can be opened or used depends on the file type. JPEG files can be opened, but PDF, single-page TIFF, multipage TIFF, and XPS files cannot be opened.

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

d. Supported operating systems for destinations:

NOTE:

All Microsoft Windows operating systems listed below are 32-bit unless otherwise noted.

Shared drive

• Mac OS X v10.9 to v10.11

• Windows Server 2012 R2 (64-bit)

• Windows 10

• Windows 8 (32- and 64-bit)

• Windows 8 Pro (32- and 64-bit)

• Windows 8 Enterprise (32- and 64-bit)

• Windows 7 Ultimate (32- and 64-bit)

• Windows 7 Home Basic

• Windows Vista Ultimate

• Windows Server 2008

• Windows Server 2008 R2 (64-bit)

NOTE:

Windows 8 shares are only automatically supported on eSF v4.x printers. However, eSF v3.x printers can support Windows 8 shares if updated with a special version of firmware. To acquire this firmware, contact technical support.

For eSF v3.x devices:

• X54x: LHS23.VK.P278 or later

• X74x: LHSC3.NY.P278 or later

• X79x: LHS23.MR.P278 or later

• X92x: LHS23.HK.P278 or later

• X95x: LHS23.TQ.P278 or later

• 6500e: LHS.JR.P278 or later

FTP

• Mac OS X v10.9 to v10.11

• Novell Open Enterprise Server Linux SUSE 9

• Red Hat Linux Enterprise Edition

• Solaris 10

• Windows Server 2012 R2 (64-bit)

• Windows 7 Ultimate and Ultimate 64-bit

• Windows 7 Home Basic

• Windows Vista Ultimate

• Windows Server 2008

• Windows Server 2008 R2 (64-bit)

e. 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 can keep an idle connection open. This issue 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 "OK," a "Scan Failed" message appears along with an "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," then 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.

f. If the file to which the scan data is being written is already in use by another application or user, then the network save operation fails. The application shows this message: "The scan cannot be completed using this file name. The file is currently being used by another program."

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

g. If the administrator selects "Start in user directory," then the application attempts 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 applicable to the user, then turn off "Start in user directory."

h. On a Windows FTP server, if the value returned by the LDAP server for the path attribute is the same as the user name, then an issue similar to the one documented in section 4.g occurs. The user is automatically placed in the "username" directory, and the attempts to connect to the FTP server by the application fail because it will not be able to find the "username" directory.

i. If the length of a custom file name is between 241 and 255 characters, then the scanned image is saved successfully in the destination, but it cannot be opened or previewed.

This issue occurs only on Windows devices.

If the file name exceeds the limit of 255 characters, then an error message and a "Scan Failed" message are shown.

j. If a destination prompts a user to enter a PDF image file name and the user types Greek, Hungarian, Czech, or Russian characters, then the PDF file cannot be opened in Adobe Reader 7.x. The file can be opened in Adobe Reader 8.x.

k. When the printer DNS server address is different from the destination server DNS server address and/or the printer is in a domain / work group while the destination server is in a work group, then the application may fail to connect to the destination server using only the host name. If the destination server is in a domain, then providing the fully qualified host name followed by the share name may facilitate a successful connection with the destination.

For example, if "myhost.domain.com" is the fully qualified server name and "myshare" is a shared folder, and “\\myhost.domain.com\myshare” is typed in the Address field, then Scan to Network should be able to connect to the destination successfully.

l. The application does not support combining the Secure PDF file format with the PDF/A version.

If the file format is set to Secure PDF and the version is set to PDF/A, PDF 1.2, or PDF 1.3, then the printer ignores the Secure PDF file format. The document is scanned as a regular PDF. For eSF v3.x printers, the user is informed of the compatibility issue before the scan starts and prompted to continue or cancel the scan.

m. A scanned PDF file accessed from a destination may have garbage characters in its Document Properties window, or the Document Properties window may not open. This is due to the PDF file format and PDF version compatibility issues described previously.

n. Choosing color and 300 dpi for large paper sizes (such as A3 and Ledger) may result in insufficient memory to complete the job. It is recommended that the option for color is set to "Off" for large paper sizes.

o. The Address field can contain up to 256 characters.

Issues for eSF v4.x and v3.x printers

a. If you intend to use OCR or Compressed PDF output, then the printer must have 512MB of RAM. However, 1GB of RAM is recommended for optimal performance.

b. If OCR features are enabled, then only 300 dpi scan quality is available.

c. The application supports up to 100 profiles, but if there are too many profiles, then you may encounter slow performance. It is recommended that you create only up to 80 profiles.

Issues for eSF v3.x printers

a. The scan does not start when the printer Start button is pressed from the destination Summary screen.

b. The "Scan Edge to Edge" and "Edge Erase" settings can be used simultaneously even though they are incompatible with each other.

Release notes

• Fix on lost scanned jobs when scanning several sets of a multipage document

• Fix on random and intermittent missing scan files

• Properly display destination path in the print confirmation page

• Properly sort folders

• Fix incorrect number of pages in XML log files when blank page removal and scan preview is enabled

• Fix DDU and other import/export UCF issues

• For more information on installation and configuration instructions, see the Lexmark Scan to Network Guide and the Scan to Network Premium Administrator's Guide provided with the application.

• Adobe Acrobat Reader is required to view these guides.

Back to top

Overview

This Readme file pertains to the current release of the LEXMARK SCAN TO NETWORK application.

Lexmark Scan to Network is an embedded solution that can be installed on printers that support the Lexmark Embedded Solutions Framework (eSF) v4.x, v3.x, or v2.x. Scan to Network enables users to scan documents to a network, with network destinations chosen by the administrator.

Scan to Network:

• Eliminates time spent transferring scanned files from a PC to a network drive.

• Reduces the steps used to store scanned documents on a file share.

• Simplifies the process of archiving scanned files.

• Enables a destination to be configured to determine the actual network location via an LDAP lookup.

NOTE:

This unlicensed version of Scan to Network is fully functional and includes basic scan settings. A premium version of Scan to Network is available in the Lexmark Virtual Solution Center. Scan to Network Premium offers advanced features such as custom prompt creation and bar code scanning.

Scan to Network Premium requires a license. To obtain a license, go to www.lexmark.com and click the "Contact Lexmark" link at the bottom of the screen.

Associated files

The following files and publications are included in the release:

a. Application Files

• scanToNet_e4_s2-4.1.23.fls The Scan to Network application for eSF v4.x printers with 7- and 10-inch control panels

• scanToNet_e4_s3-4.1.23.fls The Scan to Network application for eSF v4.x printers with 4.3-inch control panels

• scanToNet_e3_s2-4.1.23.fls The Scan to Network application for eSF v3.x printers

• scanToNet_e2_s2-4.1.23.fls The Scan to Network application for eSF v2.x printers

b. Other Files

• scanToNet_e4_s2_desc-4.1.23.xml The solution descriptor file for eSF v4.x printers with 7- and 10-inch control panels

• scanToNet_e4_s3_desc-4.1.23.xml The solution descriptor file for eSF v4.x printers with 4.3-inch control panels

• scanToNet_e3_s2_desc-4.1.23.xml The solution descriptor file for eSF v3.x printers

• scanToNet_e2_s2_desc-4.1.23.xml The solution descriptor file for eSF v2.x printers

• LicenseServer.exe The network license manager

c. Publications

• Lexmark_ScanToNetwork_AdminGuide.pdf The Administrator's Guide

• Lexmark_ScanToNetwork_UserGuide.pdf The User's Guide

• Readme.txt (this file)

Requirements

a. A printer that supports eSF v4.x, v3.x, or v2.x applications.

Supported eSF v4.x printers include:

• CX410 Required firmware level: LW30.GM4.P328 or later.

• CX510 Required firmware level: LW30.GM7.P328 or later.

• MX51x, MX410 Required firmware level: LW30.SB4.P328 or later.

• MX61x Required firmware level: LW30.SB7.P328 or later.

• MX6500e Required firmware level: LW30.JD.P328 or later.

• MX71x Required firmware level: LW30.TU.P328 or later.

• MX81x Required firmware level: LW30.TU.P328 or later.

Supported eSF v3.x printers include:

• X54x Required firmware level: LHS30.VK.P303 or later.

• X74x Required firmware level: LHS30.NY.P303 or later.

• X79x Required firmware level: LHS30.MR.P303 or later.

• X92x Required firmware level: LHS30.HK.P303 or later.

• X95x Required firmware level: LHS30.TQ.P303 or later.

• 6500e Required firmware level: LHS30.JR.P303 or later.

Supported eSF v2.x printers include:

• X46x Required firmware level: LR.BS.P631 or later.

• X65x Required firmware level: LR.MN.P631a or later.

• X73x Required firmware level: LR.FL.P631 or later.

• X86x Required firmware level: LP.SP.P631 or later.

b. Memory: The printer must have 256MB of RAM.

c. Protocols

Scan to Network uses the following protocols:

• 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 printer use this protocol when authenticating using Directory Services such as Microsoft Active Directory.

NOTE:

Other protocols may also be supported.

d. Ports

Scan to Network uses the following ports:

• 137

• 138

• 139

• 445

• 9100

• 9400

Limitations and compatibility of the release

Common Issues

a. This release Of Scan to Network 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 Network Folder config file" message.

b. 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 (JPEG and single-page TIFF).

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 or not these files can be opened or used depends on the file type. JPEG files can be opened, but PDF, single-page TIFF, multi-page TIFF, and XPS files cannot be opened.

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

d. Supported operating systems for destinations:

NOTE:

All Microsoft Windows operating systems listed below are 32-bit unless otherwise noted.

Share drive

• Mac OS X v10.6-v10.9

• Windows 8 (32- and 64-bit)

• Windows 8 Pro (32- and 64-bit)

• Windows 8 Enterprise (32- and 64-bit)

• Windows 7 Ultimate (32- and 64-bit)

• Windows 7 Home Basic

• Windows Vista Ultimate

• Windows Server 2008

• Windows Server 2008 R2 64 Bit

• Windows Server 2003 Standard Edition SP1

• Windows Server 2003 Standard Edition R2

• Windows XP Professional SP2

• Windows XP Home

• Windows 2000 Professional SP4

• Windows 2000 SP4

NOTE:

Windows 8 shares are only automatically supported on eSF v4.x printers. However, eSF v2.x and v3.x printers can support Windows 8 shares if updated with a special version of firmware. Contact technical support to acquire this firmware.

For eSF v2.x devices:

• X46x: LR.BS.P645 or later

• X65x: LR.MN.P647 or later

• X73x: LR.FL.P646 or later

• X86x: LP.SP.P642 or later

For eSF v3.x devices:

• X54x: LHS23.VK.P278 or later

• X74x: LHSC3.NY.P278 or later

• X79x: LHS23.MR.P278 or later

• X92x: LHS23.HK.P278 or later

• X95x: LHS23.TQ.P278 or later

• 6500e: LHS.JR.P278 or later

FTP

• Mac OS X v10.6-v10.9

• Novell OES Linux SuSE 9

• Redhat Linux Enterprise Edition

• Sun Solaris 10

• Windows 7 Ultimate and Ultimate 64-bit

• Windows 7 Home Basic

• Windows Vista Ultimate

• Windows Server 2008

• Windows Server 2008 R2 64-bit

• Windows Server 2003 Standard Edition SP1

• Windows Server 2003 Standard Edition R2

• Windows XP Professional SP2

• Windows XP Home

• Windows 2000 Professional SP4

• Windows 2000 SP4

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

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

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

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

h. On a Windows FTP server, if the value returned by the LDAP server for the path attribute is the same as the username, an issue similar to the one documented in 5.g above occurs. The user is automatically placed in the "username" directory (see 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.

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

j. If a destination uses a string prompt to ask users to enter a PDF image filename and a user enters Greek, Hungarian, Czech, or Russian characters in the filename prompt, the PDF file cannot be opened in Adobe Reader 7.x. The file can be opened in Adobe Reader 8.x.

k. When the printer's DNS server address is different from the destination server's DNS server address and/or the printer is in a domain/workgroup while the destination server is in a workgroup, the application may fail to connect to the destination server using only the hostname. If the destination server is in a domain, providing the fully-qualified hostname followed by the share name may facilitate a successful connection with the destination.

For example, if "myhost.domain.com" is the fully-qualified server name and "myshare" is a shared folder, if "\\myhost.domain.com\myshare" is entered in the "Address" field, Scan to Network should be able to connect to the destination successfully.

l. The application does not support combining the Secure PDF file format with the PDF/A version.

If the file format is set to Secure PDF and the version is set to PDF/A, PDF 1.2, or PDF 1.3, the printer will ignore the Secure PDF file format. The document will be scanned as a regular PDF. On eSF v2.x printers, this occurs automatically. On eSF v3.x printers, the user will be informed of the compatibility issue before the scan starts and will be prompted to continue or cancel the scan.

m. A scanned PDF file accessed from a destination may have garbage characters in its Document Properties window or the Document Properties window may not open. This is due to the PDF file format and PDF version compatibility issues described above.

Issues for eSF v4.x and v3.x Printers

a. If you intend to use OCR or Compressed PDF output, the printer must have 512MB of RAM. However, 1GB of RAM is recommended for optimal performance.

b. If OCR features are enabled, only 300 DPI scan quality is available.

c. If OCR features are enabled, only the output file type specified in the OCR settings is honored. However, the scan settings summary still displays a file type, even though it will be ignored.

Issues for eSF v3.x Printers

a. The scan does not start when the printer Start button is pressed button is pressed from the destination Summary screen.

b. The Scan Edge to Edge and Edge Erase settings can be used simultaneously even though they are incompatible with one another.

Issues for eSF v2.x Printers

a. LDAP referrals are not supported.

Release notes

• Updated the Summary screen and EWS to show only the scanning features controlled by OCR when OCR is enabled.

• Fixed a bug that was causing overwrites of the first page when Page Break is enabled.

For further installation and configuration instructions, please see the Lexmark Scan to Network and Scan to Network Premium Administrator's Guide provided with the application. Adobe Acrobat Reader is required to view this guide.

Back to top

Lexmark Scan to Network is an embedded solution that can be installed on multifunction printers (MFPs) that support the Lexmark Embedded Solutions Framework (eSF) v2.x or v3.x. Scan to Network enables users to scan documents to a network, with network destinations chosen by the administrator.

Scan to Network:

• Eliminates time spent transferring scanned files from a PC to a network drive.

• Reduces the steps used to store scanned documents on a file share.

• Simplifies the process of archiving scanned files.

• Enables a destination to be configured to determine the actual network location via an LDAP lookup.

NOTE:

This unlicensed version of Scan to Network is fully functional and includes basic scan settings. A premium version of Scan to Network is available in the Lexmark Virtual Solution Center. Scan to Network Premium offers advanced features such as custom prompt creation and bar code scanning.

Scan to Network Premium requires a license. To obtain a license, go to

and click the "Contact Lexmark" link at the bottom of the screen.

Requirements

1. A printer that supports eSF v2.x or v3.x applications.

2. Device memory requirements: A minimum of 256 MB RAM.



3. Protocols

• 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 may also be supported.

4. Ports

Scan to Network uses the following ports.

• 137

• 138

• 139

• 445

• 9100

• 9400

Package contents

The following files and publications are included in Scan to Network v3.5.0.

1. scanToNet-fw2-3.5.0.fls - Scan to Network application for eSF v2.x MFPs



2. scanToNet-fw3-3.5.0.fls - Scan to Network application for eSF v3.x MFPs



3. scanToNet-fw2_3.5.0_desc.xml - The solution descriptor file



4. LicenseServer.exe - The network license manager



5. Lexmark_ScanToNetwork_AdminGuide.pdf - Administrator's Guide



6. Lexmark_ScanToNetwork_UserGuide.pdf - User's Guide



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

Language-specific files for this application can be found in a sub-directory named for each supported language.

Limitations and compatibility of the release

1. MAXIMUM NUMBER OF IMPORTED DESTINATIONS WITH MARKVISION PROFESSIONAL

This release Of Scan to Classroom 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 Classroom 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). 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 or not 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.

3. CONFIGURATION FILE COMPATIBILITY

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

4. 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 7 Home Basic

• 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 XP Home

• 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 7 Home Basic

• 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 XP Home

• Microsoft Windows 2000 Professional SP4

• Microsoft Windows 2000 SP4

• Redhat Linux Enterprise Edition

• Sun Solaris 10

• Novell OES Linux SuSE 9

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

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

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

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

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

On a Windows FTP server, if the value returned by the LDAP server for the path attribute is the same as the username, an issue similar to the one documented in 6.g above occurs. The user is automatically placed in the "username" directory (see 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.

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

10. START BUTTON DOES NOT INITIATE SCANNING

On eSF v3.0 MFPs, the scan does not start when the MFP Start button is pressed from the destination Summary screen.

11. SCAN EDGE TO EDGE AND EDGE ERASE CAN BE USED SIMULTANEOUSLY

On eSF v3.0 MFPs, the "Scan Edge to Edge" and "Edge Erase" settings can be used simultaneously even though they are incompatible with one another.

12. PDF FILES WITH NON-ENGLISH CHARACTERS IN FILENAME CANNOT BE OPENED

If a destination uses a string prompt to ask users to enter a PDF image filename and a user enters Greek, Hungarian, Czech, or Russian characters in the filename prompt, the PDF file cannot be opened in Adobe Reader 7.x. The file can be opened in Adobe Reader 8.x.

13. USING FULLY-QUALIFIED HOSTNAMES WHEN CONNECTING TO DESTINATIONS

When the printer's DNS server address is different from the destination server's DNS server address and/or the printer is in a domain/workgroup while the destination server is in a workgroup, the application may fail to connect to the destination server using only the hostname. If the destination server is in a domain, providing the fully-qualified hostname followed by the share name may facilitate a successful connection with the destination.

For example, if "myhost.domain.com" is the fully-qualified server name and "myshare" is a shared folder, if "\\myhost.domain.com\myshare" is entered in the "Address" field, Scan to Network should be able to connect to the destination successfully.

14. SECURE PDF FILE FORMAT + PDF/A VERSION NOT SUPPORTED

The application does not support combining the Secure PDF file format with the PDF/A version.

If the file format is set to Secure PDF and the version is set to PDF/A, PDF 1.2, or PDF 1.3, the MFP will ignore the Secure PDF file format. The document will be scanned as a regular PDF. On eSF v2.0 MFPs, this occurs automatically. On eSF v3.0 MFPs, the user will be informed of the compatibility issue before the scan starts and will be prompted to continue or cancel the scan.

15. PDF DOCUMENT PROPERTIES WINDOW ISSUES

A scanned PDF file accessed from a destination may have garbage characters in its Document Properties window or the Document Properties window may not open. This is due to the PDF file format and PDF version compatibility issues described above.

Installation details

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

Scan to Network

'

Administrator's Guide (AdminGuide.pdf) provided with the application. Adobe Acrobat Reader is required to view this guide.

Back to top

---

Older Versions:

Version	Changes or Fixes
Version 3.3.15 Beta Cert via PE	Bug fix on 3.3.14
Version 3.3.14 BETA Cert via PE	Fixed not remembering the "LDAP Userid Attribute" value set on the EWS which resulted in unsuccessful LDAP lookup.
Version 3.3.13 Release Cert via PE	Same as 3.3.12
Version 3.3.12 BETA Cert via PE	Increased memory reserve from 105 MB to 130 MB tofix SNF Premium advanced imaging features failing at higher DPI.
Version 3.3.8 BETA Cert via PE	LDAP Debugging enabled. Released on Sep 30, 2011.
Version 3.3.6 Release Cert via PE	BlankPageRemoval fixes Thread synchronization fixes (resulting in app running faster) “Multiple TIF file” configuration fixes
Version 3.3.5 BETA Cert via PE	Increased up front memory reserve from 40 MB in build_fw2.xml to 105 MB. Implements SMB Client

Back to top

---

LEGACY ID: FA823