The LINCC Aleph v.20 client may be installed beginning April 19, 2010, in advance of the LINCC system upgrade. However, you cannot use or log in to the v.20 client until the full LINCC system is upgraded on May 30, 2010.
General Installation Information
Review the instructions and information provided in this document before installing the LINCC Aleph v.20 client.
Service Desk Assistance
Contact the FLVC Help Desk at (877) 506-2210 or email@example.com with any questions, or to request installation assistance.
Before Installing the LINCC Production Client
The following materials are required before installing the LINCC production client.
- Installing the LINCC v.20 Client (this document).
- Downloading the LINCC v.20 Client, instructions available from CCLA’s Library Staff Resources web page.
- LINCC Aleph v.20 client software (LINCC_20.1.r1_XXX.exe, where XXX is the three-letter institution code), available by download from the CCLA client web page at https://client.lincc.net. A CD will be provided upon request.
- Java Runtime Environment (JRE) software is required by the Aleph v.20 client and is available for download at http://www.java.com.
Concurrent Client Versions
The current version of LINCC (Aleph v.19) can reside on the same workstation as v.20 and does not need to be uninstalled before use of v.20; however, the two versions cannot connect to one another or share data. CCLA will notify colleges when it is appropriate to uninstall LINCC Aleph v.19 and instructions will be available from CCLA’s Library Staff Resources web page.
LINCC Client Encryption
Encryption is automatically enabled during installation of the LINCC client. No manual intervention is required.
Florida Virtual campus (FLVC) distributes the LINCC client software under the terms of a contract with Ex Libris (USA) to provide an automated library system to Florida’s community colleges. The client contains proprietary vendor software licensed for use by authorized staff at Florida community colleges to perform LINCC library management system functions, and may be installed only on library staff workstations approved for such use by the community college’s designated FLVC Administrative Contact. The client software may not be installed on any workstation that is accessible to the public.
LINCC Client Permissions in Windows XP and Vista
User accounts with full local administrative rights to the workstation should have no problems running the LINCC classroom client. However, user accounts that are not given local administrative rights may experience problems. In this case, the file system privileges for the C:\LINCC_20.1.r1_XXX folder (where XXX is the three-letter institution code) will need to be changed to allow users Full Control of the directory and all subdirectories within it. Full Control permissions will also need to be given to temporary directories that are used by the client (C:\temp and C:\temp\Aleph). For more information, refer to Setting LINCC Client Permissions in Windows XP and Vista, available from CCLA’s Library Staff Resources web page.
The LINCC client will initiate a connection to the CCLA server much like a web browser initiates a connection to a web site. The LINCC client will use non-standard ports when accessing the server; however, it will not function as a server or receive requests for a connection initiated from a remote host. If the firewall at the local institution is set to block the necessary outgoing ports, the LINCC client will not work.
The LINCC client depends on non-standard ports to access servers at CCLA. Production, training, and practice clients require access to different outgoing ports. These ports may need to be opened manually depending on local security policies.
Ports used for client functionality:
- Production client: 6600, 66XX (where XX is the first two digits of the library agency code) to lms.lincc.net
- Practice client: 6600, 6626 to trainlms.lincc.net
Installing the LINCC Production Client
Use the following steps to install the LINCC production client. All default settings should be retained during the installation process.
**Important** Any customizations made to the current version of the LINCC client (Aleph v.19) must also be made to the Aleph v.20 client. For example, if the print.ini file in Aleph v.19 was modified to enable special features for spine label printing, the print.ini file in Aleph v.20 must be modified to enable the same features.
To install the LINCC production client:
Download the setup file LINCC_20.1.r1_XXX.exe from the CCLA client web page. A valid LINCC user name and password are required. For additional instructions, refer to Downloading the LINCC v.20 Production Client, available from CCLA’s Library Staff Resources web page.
- After the files have been extracted, the Welcome screen will appear. Click Next.
- On the Select Method of Installation screen, select Stand-alone, and then click Next.
- On the Select Installation Type screen, select Typical, and then click Next.
- On the Select Destination Directory screen, verify that the installation directory is C:\LINCC_20.1.r1_XXX (where XXX is the three-letter institution code), and then click Next.
- On the Select the Program Manager Group screen, verify that the default program manager group is LINCC_20.1.r1_ XXX (where XXX is the three-letter institution code). If the default setting is not correct, select the appropriate program group from the list. Click Next.
- On the Run Version Check screen, verify that the Version check on starting application check box is selected, and then click Next.
- On the Ready to Install screen, click Next. The LINCC production client installation program will run automatically and an installation progress window will appear.
- A prompt will appear when the installation is complete. Click OK.
- A window displaying the contents of the installation will appear. Close the window.
- To open the LINCC production client from the desktop, click Start, point to Programs, point to LINCC_20.1.r1_XXX (where XXX is the three-letter institution code), and then select a module from the list. Note: You may only log in to the LINCC v.20 client after the full LINCC system is upgraded on May 30, 2010.
Logging In to LINCC
A LINCC user name and password are required each time the LINCC client is accessed. Note: You may only log in to the LINCC v.20 client after the full LINCC system is upgraded on May 30, 2010.
To log in to LINCC:
- On the desktop, click Start, point to Programs, point to LINCC_20.1.r1_XXX (where XXX is the three-letter institution code), and then select a module.
- When prompted to log in, enter a valid LINCC user name and password in the appropriate fields and click OK.
Once logged in to any module, all other modules can be accessed on the ALEPH menu by pointing to Switch Application and clicking the appropriate module in the list. Modules can also be accessed by clicking a module icon in the Application toolbar at the lower right portion of the screen.
Troubleshooting Login Errors
Errors will appear if an incorrect user name or password is entered or if network access is blocked. Use the following chart to identify and resolve common login errors. If the error persists, contact the FLVC Help Desk for assistance.
Error / Message
Cannot log in (no error message).
Forgotten username or password.
Contact the Service Desk to obtain the correct username and password.
“Password failed to read reply.”
Incorrect username or password entered.
Click “OK” on error message box and reenter the username and password. Call the Service Desk if the problem continues.
“Password not verified on connectable host.”
Client cannot make a connection to the host.
Check with local IT staff to insure that appropriate outgoing ports have been opened through the local firewall. Call the Service Desk if the problem cannot be resolved at the local level.
Setting the Workstation ID
A Workstation ID, specific to each sublibrary, is necessary to loan and return books in the LINCC client. A list of Workstation IDs is provided on the following pages.
To set the Workstation ID:
- Log in to any module of the LINCC client. Right-click the key icon at the lower right portion of the screen.
- On the menu that appears, click Set Workstation Identifier.
- When prompted, enter the appropriate Workstation ID in the Enter New Station ID field. Click OK.
LINCC Workstation ID Codes
College / Campus
Brevard Community College
Central Florida College
Daytona State College
Edison State College
Florida Keys Community College
Florida State College at Jacksonville
Gulf Coast Community College
Hillsborough Community College
Indian River State College
St. Lucie West
Lake City Community College
Lake-Sumter Community College
Miami Dade College
North Florida Community College
Northwest Florida State College
Palm Beach Community College
Palm Beach Gardens
Pasco-Hernando Community College
Pensacola Jr. College
Polk State College
St. Johns River Community College
St. Petersburg College
St. Petersburg Gibbs
Health Education Center
Santa Fe College
Seminole Community College
Sanford Career Center
South Florida Community College
State College of Florida, Manatee-Sarasota
Tallahassee Community College
Valencia Community College
| || || || || || |