Abstract
This Technical Paper deals with the various setups which have to be carried out in
order to make your NetOp School Terminal Server solution a success.
This section contains the topics:
Setup on a Terminal Server
Is NetOp Gateway Required?
Common Setup
NetOp School Functionality
NetOp Gateway Setup
Multiple Terminal Servers
Common Module Setup
Creating a Common Student Setup – Wizard and Tools
Student module – Tools menu
Configuration files (.ndb)
Creating a Common Teacher Setup – Wizard and Tools
Teacher module – Tools menu
Customized Student Setup
Creating different customized Student setups
Applying customized setups to multiple users
Note: This document is the technical backup of the NetOp Whitepaper: NetOp School
in Terminal Server Environments.
Setup on a Terminal Server
Install NetOp School on a terminal server from the terminal server console
Start\Settings\Control Panel\Add/Remove Programs utility.
NetOp School modules running on a terminal server communicate by the NetOp
proprietary Terminal Server communication device.
Is NetOp Gateway Required?
If NetOp School modules running on the terminal server shall communicate only with
NetOp School modules running on the same terminal server, NetOp Gateway is not
required.
If NetOp School modules running on the terminal server shall communicate with NetOp
School modules running on network computers or on other terminal servers on the
network, NetOp Gateway must be installed and set up on the terminal server console.
NetOp® and the red kite are registered trademarks of Danware Data A/S. All other products mentioned in this document
are trademarks of their respective manufactures. Danware Data A/S denies any and all responsibility for damages
caused directly or indirectly as a result of using this document. The content of this document is subject to change without
notice.
Copenhagen October 2006
Page 1 of 7
Common Setup
As a first action after the installation, we strongly recommend that system
administrators create common setups for NetOp Teacher and NetOp Student installed
on a terminal server. The Administrator should start Student and Teacher modules and
walk through the Setup Wizard to create a set of common configuration files (.ndb) for
all Student and Teacher users. If common setups are not created, the first user loading
a NetOp School module on the terminal server will be presented with the Setup Wizard
to set up the module. There will be a high risk of setup problems and errors, and the
opportunity for swift standardization and uniform module protection will be missed. See
below for information on Common and Customized Setup.
NetOp School Functionality
While NetOp School in most respects has the same functionality in a terminal server
environment as in a network environment, some Teacher Commands actions work
differently in a terminal server environment:
All of the commands Log Off, Restart and Shut Down will cause the Student user to
become logged off from the terminal server client session.
Caution: The same commands executed on a Student running on the terminal server
console will execute like in a network setup, affecting the entire terminal server.
NetOp Gateway Setup
NetOp Gateway is a module belonging to the NetOp Remote Control family. It is not
available on the NetOp School CD, but a trial version can be installed from the NetOp
Trial Versions CD. If you urgently need to try out NetOp Gateway, your NetOp supplier
will be happy to help you.
Install NetOp Gateway on a terminal server from the terminal server console
Start\Settings\Control Pane\Add/Remove Programs utility.
To set up communication through the Gateway, select the Tools menu Communication
Profiles command to display this window:
NetOp Net
numbers
Check boxes to enable the Terminal Server communication profile and at least one
communication profile using a networking communication device used on the network
NetOp® and the red kite are registered trademarks of Danware Data A/S. All other products mentioned in this document
are trademarks of their respective manufactures. Danware Data A/S denies any and all responsibility for damages
caused directly or indirectly as a result of using this document. The content of this document is subject to change without
notice.
Copenhagen October 2006
Page 2 of 7
(typically TCP/IP). A NetOp Net number displayed to the right is automatically allocated
to each selected communication profile.
NetOp Net numbers must satisfy these rules:
1. The NetOp Net number allocated to any networking communication profile
using a specific communication device must be the same on all NetOp
Gateways in the network.
2. The NetOp Net number allocated to any Terminal Server communication
profile on any NetOp Gateway must be different from the NetOp Net number
allocated to any communication profile on any NetOp Gateway on the network.
An example: You have three Terminal servers and a Gateway installed on each. On
each Gateway the TCP/IP(UDP) profile share 11 as NetOp Net number. The Terminal
Server profile should use individual numbers like 10, 12 and 13 (but not 11 since that
is occupied by TCP/IP(UDP).
If the automatically allocated NetOp Net numbers do not satisfy these rules, they must
be changed to satisfy the rules. To change the NetOp Net number of a communication
profile, select the communication profile in the pane and click Edit to display a
Communication Profile Edit window with a Gateway Settings section:
The allocated NetOp Net number is displayed in the NetOp Net (10..127): [] field. Edit
the field contents to specify a valid NetOp Net number.
Note: A more detailed explanation of NetOp Gateway setup is available in the NetOp
Gateway documentation.
NetOp Gateway in the Advanced TCP/IP Configuration window by default specifies the
NetOp Remote Control default port number 6502 for communication profiles using the
TCP/IP (UDP) communication device. The Receive Port and Send Port numbers must
be changed into the port numbers used by NetOp School, by default 1971.
NetOp® and the red kite are registered trademarks of Danware Data A/S. All other products mentioned in this document
are trademarks of their respective manufactures. Danware Data A/S denies any and all responsibility for damages
caused directly or indirectly as a result of using this document. The content of this document is subject to change without
notice.
Copenhagen October 2006
Page 3 of 7
If network computers or terminal servers on other subnets shall be reached using
TCP/IP (UDP), their IP addresses or DNS names must be in the IP Broadcast List.
Similar precautions apply to other networking communication devices.
Multiple Terminal Servers
If NetOp School modules running on a terminal server shall communicate with NetOp
School modules running on other terminal servers, add this section to the NETOP.INI
file in the terminal server Windows directory (typically C:\WINNT):
[DTL]
GWRestrictedBroadcast=0
GWAllowFullBroadcast=1
Explanation: By default, communication through two NetOp Gateways across a
network is disabled, as it might in some cases cause a broadcast storm (an
uncontrolled propagation of network traffic). Applying these NETOP.INI settings to
NetOp Gateways running on the console of terminal servers on a network, NetOp
School communication will be routed through the NetOp Gateways without causing a
broadcast storm.
Common Module Setup
Creating a Common Student Setup – Wizard and Tools
To create a Common Student setup, load NetOp Student and run the Setup Wizard to
create an initial Student setup. Required choices are mentioned below.
In the Class name window, specify a name of (one of) the class(es) that shall be used
on Students and Teachers. More can be added later in the Student module under
Tools, menu, Options.
In the Class Management window, select to Identify Student by e.g. Windows login
name. DO NOT select one of the options Computer Name and Computer Name and
\Domain. On a terminal server, the computer name of all Students is the name of the
terminal server computer. These options will give all Students on a terminal server the
same Student Login Name. A running class will not admit a Student with the same
Student Login Name as an already connected Student.
In the Communication Profile window, select Terminal Server.
You may configure other settings of your choice in the Setup Wizard. Click OK to save
and finish.
Student module – Tools menu
In the Tools menu Options window specify more setup details that shall apply to NetOp
Student when loaded by a user for the first time.
On the Options window Class tab, different class connection options are available.
Selecting the option Connect to Class <Class name> requires customized Student
setups if Students on the terminal server shall connect to different classes. See the
section Customized Module Setup below. If all shall connect to the same class, no
further action needs to be taken.
NetOp® and the red kite are registered trademarks of Danware Data A/S. All other products mentioned in this document
are trademarks of their respective manufactures. Danware Data A/S denies any and all responsibility for damages
caused directly or indirectly as a result of using this document. The content of this document is subject to change without
notice.
Copenhagen October 2006
Page 4 of 7
Configuration files (.ndb)
This common Student setup is stored in the configuration files (.ndb) in All Users
directory and by default applies to all Students loaded on the terminal server.
Changes in configuration will apply to all users.
If users running NetOp Student on a terminal server need individual setups, typically
to connect to individual classes, customized Student setups must be created, see the
section below.
Creating a Common Teacher Setup – Wizard and Tools
To create a common Teacher setup, first load NetOp Teacher and run the Setup
Wizard to create an initial Teacher setup. Required choices are mentioned below.
In the Class name window, specify a name of (one of) the class(es) that shall be used
on Students and Teachers. More can be added later in the Teacher module under
Tools, menu, Options.
In the Class Management window, select to identify Students by Student login name or
Windows login name. Selecting Computer Name for use on a terminal server is
meaningless, since the computer name of all Students is the name of the terminal
server computer.
In the Communication Profile window, select Terminal Server.
You may configure other settings of your choice in the Setup Wizard. Click OK to save
and finish.
Teacher module – Tools menu
In the Tools menu Options window, specify more setup details that shall apply to NetOp
Teacher when loaded by a user for the first time.
To facilitate class selection by Teacher users, create all of the classes that shall run on
the terminal server on the Options window Class tab. To prompt Teacher users to
select a class at startup, check the box Always Select Class at Startup.
This common Teacher setup is stored in the configuration files (.ndb) in Teacher
directory under the logged on user profile. To make the common Teacher setup the
default Teacher setup, copy all of the Teacher configuration files to the directory where
NetOp Teacher is installed to overwrite the originally installed Teacher configuration
files.
When loading the first time, the Teacher configuration files residing in the directory
where NetOp Teacher is installed will be copied to the user profile directory.
A Teacher user typically has the option to change the Teacher setup, which will be
stored in the Teacher configuration files in the user profile directory. Note that the
configuration can be protected by a Maintenance Password.
Customized Student Setup
To enable Student users to use, change and save customized configuration per user,
certain precautions need to be taken.
Add this section to the NETOP.INI file in the terminal server Windows directory
(typically C:\WINNT):
[STUDENT]
DataPath=%USERPROFILE%\Application Data\<Student path>
NetOp® and the red kite are registered trademarks of Danware Data A/S. All other products mentioned in this document
are trademarks of their respective manufactures. Danware Data A/S denies any and all responsibility for damages
caused directly or indirectly as a result of using this document. The content of this document is subject to change without
notice.
Copenhagen October 2006
Page 5 of 7
%USERPROFILE% is an environment variable identifying the profile directory of the
terminal server client session user.
<Student path> is the path to the directory where Student user configuration files are
stored, typically Danware Data\NetOp School\Student\.
This will make a Student loaded on the terminal server use the Student user
configuration files in the specified location instead of All Users Student configuration
files.
To create a customized Student setup, first create a common Student setup as
explained in the section above. Once completed, copy all of the Student configuration
files in the All Users directory to the directory where NetOp Student is installed to
overwrite the originally installed Student configuration files. When loading the first time,
the Student configuration files residing in the directory where NetOp Student is installed
will be copied to the user profile directory.
If users are allowed to access the Student configuration, future changes, e.g. new
Class Names added, will now be stored individually only affecting the logged on user.
Note that the configuration can be protected by either a Maintenance Password or by
selecting Stealth Mode to completely hide the Student module.
Creating different customized Student setups
If users are not allowed to change the Student configuration, you may have to create
different customized Student setups from the beginning, e.g. with different Class
options.
Follow the Customized Student Setup procedure as explained above, then copy all of
the Student configuration files in the All Users directory to the individual user profile
directory specified in the NETOP.INI file.
To create multiple customized Student setups, repeat this procedure for each different
customized Student setup.
Applying customized setups to multiple users
To apply a customized Student setup of one user to another user, copy all of the
Student configuration files including subdirectories from one user profile directory to
overwrite the Student configuration files in the other user profile directory.
The customized Student setup can also be applied using a logon script, copying a
certain set of configuration files (.ndb) from a central directory to the user directory,
whenever a user logs on to a session.
In this situation the script should load the Student module after the ndb files were
copied. Thus the Load Student at Windows Startup option should be unchecked.
Who is Danware?
Danware’s core business is to develop and market software products based on the
NetOp core technology – a technology enabling swift, secure and seamless transfer of
screens, sound and data between two or more computers.
The company’s three product areas are Desktop Management, Education and Security.
The core Desktop Management product, NetOp Remote Control, enables remote
control of one or more computers from another computer and can be used across
different system platforms. NetOp School, the Education core product, is a software
NetOp® and the red kite are registered trademarks of Danware Data A/S. All other products mentioned in this document
are trademarks of their respective manufactures. Danware Data A/S denies any and all responsibility for damages
caused directly or indirectly as a result of using this document. The content of this document is subject to change without
notice.
Copenhagen October 2006
Page 6 of 7
application for computer-based classroom teaching in both physical and virtual
classrooms via the Internet or other networks. The Security business products are
NetOp Desktop Firewall and NetOp Netfilter. All are plug ‘n play products offering
extensive functionality, flexibility and user-friendliness.
For more information http//www.netop.com/netop-8.htm
NetOp® and the red kite are registered trademarks of Danware Data A/S. All other products mentioned in this document
are trademarks of their respective manufactures. Danware Data A/S denies any and all responsibility for damages
caused directly or indirectly as a result of using this document. The content of this document is subject to change without
notice.
Copenhagen October 2006
Page 7 of 7