• Article Type: General
• Product: Aleph
• Product Version: 18.01

Description:
[From ALEPH-NA:] Our institutional IT staff would like to install the Aleph client in a network installation. Has anyone succeeded in doing so?

We don't see any way to separate out the configuration files, print history, etc. for each user from the Aleph installation directories, but perhaps some one has figured out a clever way to do this??

Resolution:
Note: There's a "Client Management" document on the Doc Portal ( /Seminars/Olybris Seminar/Client Management) which talks about the network installation.

[From Cindy Fox, at CCLA:]

I have our Aleph clients installed on a Windows server and we use Remote Desktop (RDP) to connect to them. Below are the steps that I use to set everything up.

Install Aleph client on a network drive (example: d:\AL500) - on the "Select Method of Installation" screen, choose "Main Network"

Create Windows user accounts for each user and create their home directories on the server (example: e:\Users\SMITHJ\AL500)

Edit \alephcom\tab\profile.dat and add user information (user account name in first column (SMITHJ) and user's home directory where GUI configuration files will be stored in the second column (e:\Users\SMITHJ\AL500))

To give each user a separate temp location and to avoid sharing problems, create a default alephcom.ini file for each user that only contains the definitions for TempDir in the Main and Print sections (see example below):

[Main]
TempDir=e:\Users\SMITHJ\AL500\temp\Aleph
[Print]
TempDir=e:\Users\SMITHJ\AL500\temp\Aleph

When the user logs into the client and accesses each module, additional directories and files will be stored in their home directory on the server
We still have a few sharing problems that come up sometimes, but basically this setup works pretty well. We use it for our training sessions at our colleges.

• Article last edited: 10/8/2013