Faronics Insight - Manual (Page 24)

Faronics Insight User Guide
24
|
Installing Faronics Insight
THINCLIENT 001004=Student, Channel=1, Name= THINCLIENT 001004
DEFAULT=Student, Channel=1, Name=Default
The first part of each line (THINCLIENT001001 in this example) is the “Client Name” of that thin
client. Each thin client device has a unique Client Name set by the manufacturer or during
hardware configuration. You can find that name by logging into the device and entering the “SET”
command from a command prompt. Many IT departments will have a list of Client Names for
each thin client device.
The Client Name “DEFAULT” can be used as a default setting. If a Thin Client does not find itself
in the LskTSDat.ini file, it will assume the configuration of the DEFAULT entry (if that entry
exists.)
NOTE: Some Thin Client devices require configuration to set a unique Client Name for the device.
Faronics Insight requires all Thin Client devices to have a unique Client Name. Please check your
Thin Client device's documentation to make sure each device has a unique Client Name.
Following the Client Name is the type of Faronics Insight software to run on that thin client device
(either Student or Teacher.) The next parameter defines which Faronics Insight Channel to use
for that thin client. Generally, all thin client devices in the same classroom will have the same
Channel number.
The last parameter defines the Faronics Insight Display Name. The Student will appear in the
Teacher Console with both the login name and this name. By default, we use the Client Name, but
that can be changed if a more meaningful name is desired.
Multiple Terminal Servers
If you are load balancing (i.e. multiple Terminal Servers serving the same classroom) you must
install Faronics Insight software on all Terminal Servers and then replicate the completed
LskTSDat.ini file to all Terminal Servers. If there are many Terminal Servers load balanced
together, it is possible to configure Faronics Insight to share a common LskTSDat.ini file.
There are two options to install Insight on multiple Terminal Servers that are load balanced:
1) Specify which server each system connects to and use the standard installation.
2) There is also a way to share a ini file for multiple servers. This requires a change in the registry.
To use a remote .ini file, you will need to add the following key to the registry of each Terminal
Server in the server cluster:
HKEY_LOCAL_MACHINE\SOFTWARE\Insight\RemoteIniPath
It needs to be of type REG_SZ and should be the path of the shared ini file. The name of the ini file
will still be set to LskTSDat.ini, but you can now specify a remote location for that file. This
follows the normal “Windows” way of naming the Remote Ini Path.
Here are some examples:
"\\?\UNC\xpprosp3-3\Data
This will specify a remote share “Data” on computer “xpprosp3-3”
C:\Program Files\Insight
This specifies a local file.
Upgrading Insight on Terminal Server
The TerminalServices.msi installs the updated files for both Teacher and Student, so once that
install has completed, both Teacher and Student are updated.