Most Viewed FAQs
Which version of the LFConnector is right for me?
Can the LFConnector use Windows Active Directory to authenticate against the Laserfiche repository without creating Laserfiche users?
What IP address do I use to Activate a Serial Number for the LFConnector?
I'm getting the message "The serial number for this device is invalid for this version of LFConnector", or "This device is not licensed to run this version of the LFConnector", what can I do?
I have both the eCopy SSOP and Laserfiche software on my Windows XP laptop in order to perform LFConnector demos. Each location I visit usually yields a different TCP/IP address on my wireless card, which in turn impacts my LFConnector serial number activation. What can I do?
Newest FAQs
I'm getting the message "The licensing manager was not properly initialized" after scanning documents on Windows Server 2012. What can I do?
What multi-function devices (MFDs) can be used in conjunction with the LFConnector?
Show/Hide Left Bar

Frequently Asked Questions

19180 Views, Last Updated 8/1/2007
Can the LFConnector use Windows Active Directory to authenticate against the Laserfiche repository without creating Laserfiche users?

Yes!  This feature is supported by using the Session Logon feature of eCopy ShareScan OP v4.x.  For more information about Session Logon, please see the FAQ entitled How can I take advantage of the new Session Logon feature of eCopy ShareScan OP v4.x.

Alternatively, if you are running v2.1.2 or v2.2.2 of the LFConnector, you can specify default credentials to authenticate to Laserfiche.  These credentials can use either Laserfiche or Windows authentication.  For more information on this feature, please see the FAQ entitled Can I force the LFConnector to use the same user credentials for all scan sessions.

If you are not running eCopy ShareScan OP v4.x, or if you are not running one of the above mentioned versions of the LFConnector, a user is required to authenticate against the Laserfiche repository using a Username and Password.  The Username is always a Laserfiche user account.  The Password will be either:

  • The Laserfiche user account's password, or
  • The Windows account password (only if the Laserfiche admininistrator has associated a Windows account to this Laserfiche user's account).

Note:  Should the Laserfiche administrator choose to name each of the Laserfiche user accounts so that that they match  the name of each user's Windows account, then this will allow users to only remember one Username.

Here are some more Frequently Asked Questions related to the one you selected.

Operation
Why can't I OCR documents using the LFConnector v1.0.1?
Does the LFConnector use a Laserfiche license?
What is the best way to obtain support for my Software Connections' product?
What would prevent a user from successfully navigating to a desired folder or document in the LFConnector?
What would prevent a document from "showing up" in the Laserfiche repository even though the user selected that destination in the LFConnector and (apparently) scanned successfully to it?
What are the criteria for performing a basic "Search"?
Is there an advanced "Search" syntax?
What causes an LFConnector error message stating "Unknown image format, or the format is not allowed"?
Can the LFConnector use Windows Active Directory to authenticate against the Laserfiche repository without creating Laserfiche users?
What multi-function devices (MFDs) can be used in conjunction with the LFConnector?
I have both the eCopy SSOP and Laserfiche software on my Windows XP laptop in order to perform LFConnector demos. Each location I visit usually yields a different TCP/IP address on my wireless card, which in turn impacts my LFConnector serial number activation. What can I do?
How can I take advantage of the new Session Logon feature of eCopy ShareScan OP v4.x?
Can I force the LFConnector to use the same user credentials for all scan sessions?
Does the LFConnector support tokens?
I'm getting the message "The licensing manager was not properly initialized" after scanning documents on Windows Server 2012. What can I do?