THIS PROGRAM IS PROVIDED "AS
IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING,
BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
PARTICULAR PURPOSE.

LICENSOR MAKES NO WARRANTIES OR
REPRESENTATIONS, EXPRESS OR IMPLIED, ORAL OR WRITTEN, REGARDING THE PROGRAM OR
DOCUMENTATION AND HEREBY EXPRESSLY DISCLAIMS ALL OTHER EXPRESS OR IMPLIED
WARRANTIES, INCLUDING MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
LICENSOR DOES NOT WARRANT THE PROGRAM WILL MEET YOUR REQUIREMENTS OR THAT ITS
OPERATION WILL BE UNINTERRUPTED OR ERROR FREE.

IN NO EVENT WILL GEORGIA SOFTWORKS
BE LIABLE TO YOU FOR ANY DAMAGES, INCLUDING ANY LOST PROFITS, LOST SAVINGS OR
OTHER INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY
TO USE SUCH PROGRAMS.

COPYING:

WHILE YOU ARE PERMITTED TO MAKE
BACKUP COPIES OF THE SOFTWARE FOR YOU OWN USE AND PROTECTION, YOU ARE NOT
PERMITTED TO MAKE COPIES FOR THE USE OF ANYONE ELSE.

LICENSE:

YOU ARE LICENSED FOR A SPECIFIC
NUMBER OF CONCURRENT OR SIMULTANEOUS CONNECTIONS TO A SINGLE WINDOWS 7/8/10/NT/XP/VISTA/2000/2003/2008/R2/2012/R2/2016
SYSTEM. THE NUMBER IS SPECIFIED IN YOUR PURCHASE AGREEMENT. ANY ATTEMPT TO
INCREASE THE NUMBER OF SIMULTANEOUS OR CONCURRENT CONNECTIONS EITHER
INTENTIONAL OR UNINTENTIONAL IS IN VIOLATION OF THIS AGREEMENT. THE GEORGIA
SOFTWORKS WINDOWS 7/8/10/NT/XP/VISTA/2000/2003/2008/R2/2012/R2/2016 TELNET
SERVER SOFTWARE MAY BE INSTALLED ON A SINGLE WINDOWS 7/8/10/NT/XP/VISTA/2000/2003/2008/R2/2012/R2/2016
SYSTEM.

Thank you for purchasing the Georgia SoftWorks Universal
Terminal Server Software for Windows. You will be pleased with the performance
and robustness provided with this product. Ease of use will be a significant
time saver when using the Georgia SoftWorks Universal Terminal Server software.
Complicated keyboard sequences are not required to map to the actual keys you
want to send. The GSW UTS was developed to meet a need in the market that
allows users to operate in a fast, reliable and uncomplicated fashion.

Windows is transformed into a truly multi-user environment
with the GSW UTS software. Remote administration, full support for DOS Legacy
applications, superior user control, Session Monitoring/Shadowing and
Data Stream Encryption will allow you to utilize Windows as never before. True
Client Side printing is also available for a Windows Telnet/SSH Server for the
first time with the Georgia SoftWorks Universal Terminal Server. Session Saver
and Pass-through printing are excellent features for RF hand held terminal
applications.

RF Terminal environments will perform exceptionally well
with the GSW UTS due to a rich set of standard features such as Session Saver,
Pass-through printing, Automatic Logon, logon scripting, configurable timers
and other features optimized specifically for RF terminal access.

GSW Team Services provides your mobile device users a
breakthrough in telnet/SSH technology that shatters all prior usability and
efficiency standards by allowing for unprecedented user collaboration and cutting
the costs of hardware. Team Services empowers the mobile device users to share
resources, transfer, swap, share and recover mobile device sessions from the
mobile device!

The GSW Mobile and Desktop clients are voice enabled to
provide support to Vangard Voice Systems AccuSpeech® Mobile
technology.

With IPv6 support you are ready for migration to IPv6
addresses with your network. Operation is available in IPv6, IPv4 or mixed.

SAPConsole environments will enjoy the ease of operation
with the GSW UTS as well as specialized SAPConsole features that include mobile
printing, Session Monitoring and a streamlined interface with the GSW Rocket
Terminal Engine[1]. Special Bell
processing has been improved to provide to sound the bell even after Session
Saver reconnects.

The
Georgia SoftWorks Universal Terminal Server offers industrial quality Windows
Telnet or SSH Services designed and built for the most demanding industrial and
commercial applications.

The
GSW Universal Terminal Server is the core software that provides the
performance, reliability, consistency and powerful features required for
demanding industrial and commercial applications. The GSW UTS is highly
optimized and modular in design to integrate with protocol interfaces allowing
access with remote clients. The standard protocol interface for the GSW UTS is
the Telnet Interface; however an optional SSH interface (GSW SSH Shield) is
available. The SSH interface also has a Federal Information Processing Standards
Publication (FIPS) 140-2 compliant option available for purchase.

When
the GSW UTS is coupled with the GSW Telnet Interface software the resulting
package is the GSW Telnet Server. When the GSW UTS is coupled with the GSW SSH
Interface software the resulting package is the GSW SSH Server. The mechanism
to couple the GSW SSH Interface is to obtain and install the GSW Telnet Server
and then install the GSW SSH Shield. The installation of the GSW SSH Shield
disconnects the Telnet Interface and installs the SSH Interface software
resulting in the GSW SSH Server.

The
features described in the User’s Guide apply to all interfaces offered unless
specifically noted.

The
GSW UTS and Client software is the fastest and most robust Telnet/SSH Server
for Windows on the market. Full support for DOS Legacy applications including
DOS character mode graphics, function keys, mouse and special characters allows
you to work in a local mode when at a remote location.

The
GSW UTS provides a level of robustness that is a cut above the competition. Industrialquality orphaned
session detection and elimination including NTVDM's and attempted
graceful termination of DOS legacy applications upon link and client PC
failures are features pioneered by the GSW UTS software for Windows.

Logon
Scripting
provides system administrators with unmatched control over user connections.
One function of Logon Scripting allows the user to automatically enter
specific applications upon connection. Logon Scripting can also restrict
the user to only execute a specific application. Logon Scripting can do
much more (see page 205)!

The GSW UTS Server is
the software installed on your Windows computer. This software is responsible
for establishing connections and spawning agent processes that manage
each SSH2/Telnet session. The Georgia SoftWorks Universal Terminal Server
software enforces the number of allowed simultaneous sessions.

A SSH2/Telnet session is created each time a connection is established. A connection is
established when a user logs on to the Windows system using a SSH2/Telnet Client. For each session that is created the GSW UTS software spawns an agent
process. The agent process is responsible for managing and communicating
with the user session. Screen optimizations are performed by the agent process
to facilitate faster data transfers. The capability of a configurable server
side heartbeat timer exists for use by the agent process to help identify
link or remote PC failures. In addition the configurable server side
inactivity timer exists to help identify abandoned sessions so that they
can be properly terminated and made available to other users.

The Georgia SoftWorks
Windows SSH2/Telnet clients are proprietary software that run on remote PCs and
Pocket PC class devices and utilizes advanced features offered in the GSW UTS
server software. The advanced features are propriety extensions that enable a
wide range of functionality including mouse operation, enhanced printing
methods, automatic update of client software and much more! Well-designed
optimizations are included that enable the GSW Server software for Windows to
be the fastest SSH2/Telnet software available on the market.

The client software
contains a configurable heartbeat timer that notifies the agent process of its
presence. This mechanism helps to identify link or remote PC failures.It is
recommended that the Georgia SoftWorks Client software be used although it is
not required. The Georgia SoftWorks Windows Telnet Server is RFC 854 compliant
which allows any 3rd Party Telnet Client to be used. The GSW SSH Server allows
connections from any third party SSH compliant client.

The Georgia SoftWorks Windows
clients offer the Enhanced printing method as a component of True Client Side
Printing (Page 213). This allows users to print to their local printer even
when connected across the Internet or RAS.

The Hostname or IP
address is displayed in the title bar of the Georgia SoftWorks Windows Clients
to provide an easy method of identifying to which host you are connected.Many
command line parameters are provided to enhance the convenience and power of
the client. Please see page 72 for detailed descriptions of these parameters.

The GSW Windows SSH2/Telnet Clients automatically update to the appropriate version for the GSW UTS Server
when connected[2].

The GSW clients are
available on a wide variety of operating system platforms ranging from Windows to Pocket PC 2002/2003. See the table on page 27 for a detailed list of GSW Windows clients
available for each platform.

For Android customers,
GSW ConnectBot is a GSW Android Client product that can be purchased seperately.

The Georgia SoftWorks Universal Terminal Server is the core server software module that provides
the reliability, consistency, robustness and powerful features that has
distinguished GSW Server Products. The design of the GSW UTS facilitates
integration of protocol and application interfaces producing industrial quality
server products.

The protocol and
application interfaces available for the GSW UTS are the GSW Telnet Interface
and the GSW SSH Interface. The GSW UTS is not sold as a standalone product. The
standard protocol interface provided is the GSW Telnet Interface.

Protocol Interfaces
other than the telnet interface require an application interface installer to
add the interface to the GSW UTS. The application interface installer for SSH
is the GSW SSH Shield. When the SSH application interface installer installs
the SSH Interface the Telnet Interface is disabled.

The GSW SSH Server is
obtained by purchasing the GSW Telnet Server and the GSW SSH Shield. The GSW
Telnet Server provides the GSW UTS and the SSH Shield is the application and
interface installer for the GSW SSH interface.

First the GSW Telnet
Server is installed. Next the GSW SSH Shield is installed. Again the installation
is quick and easy.

NOTE: When the SSH
Interface is installed the GSW Telnet Interface is un-installed. This is done
for security reasons as many view telnet as unsecured and thus should not be
available to malicious third parties.

Installation is simple
and quick. The same installation program installs the server software and the
client software. The installation software will prompt you for a full or
client only installation if on a Windows system and automatically install client software if on a Windows 95/98 system.

As 64-bit computing
rapidly progresses towards mainstream computing, Georgia SoftWorks provides a
64-bit edition of the GSW UTS Telnet Server named the Georgia SoftWorks UTS x64[3].
This edition is for 64-bit editions of Microsoft operating systems (Windows 7/8/10/VISTA/2008/R2/2012/R2/2016
and Windows XP/2000/2003). The GSW UTS x64 provides all the performance
benefits and addressing capabilities expected when running on 64-bit platforms.
Additionally extraordinary high session counts can be attained with the GSW UTS
when running on 64-bit platforms.

The GSW UTS 32-bit
edition runs on 64-bit platforms as well as on 32-bit platforms. When running a
GSW UTS 32-bit version on a 64-bit platform significant performance benefits
are also realized.

If the application that
you are accessing via the UTS is a 64-bit application then use the UTS x64.

When using the GSW
Directed Terminal Input Output (DTIO) Engine, it is recommended to use the same
platform edition of the GSW DTIO and GSW UTS. For example use the GSW DTIO x64
with the UTS x64.

Both the GSW UTS and
GSW UTS x64 editions are included on the CD when purchased. Simply navigate to
the corresponding folder to run the setup program. If the software is a
downloaded rather than using a CD then be sure to download the desired
edition.

The GSW UTS 32-bit
edition installs trouble free on either platform. The GSW UTS x64 will install
only on a 64-bit platform. If you accidentally try to install the GSW UTS x64
on a 32-bit platform you will be alerted and setup will exit.

Run the setup.exe
program. The procedure is the same for both the GSW UTS and UTS x64, but be
sure to use the setup.exe corresponding to the platform. The UTS x64 is
identified on the setup screen as pictured below.

If
you are installing the GSW UTS 32-bit edition then the text x64 will be omitted
in the dialog above.

2. The Installation
options screen is displayed. The choices are Full Install or Install Client
Only software. For Windows systems that you want to install clients to
connect select Full Install using the Radio Buttons. The Full Install installs
the Server Software and the Client software. Click Continue.

3. A screen is
displayed indicating the directory that the Georgia SoftWorks Telnet Server
will be installed. The default is C:\gs_uts. You may change the installation
directory at this time. Note: If you install on a drive other than the
system drive and have NTFS (on the installation drive) then you must make sure
that the system has full permissions to get to the installation directory and
subdirectories. Click Continue.

Please view the
readme.txt file as it may contain late breaking information about the telnet
server that has not yet made it into the user guide. Release notes are also
contained in the ReadMe file. NOTE: TCP/IP must be installed and
operational. TCP/IP comes as part of Windows.

This
information indicates that the GSW UTS is installed and running. The version is
also displayed and will indicate if the 64-bit edition is installed. The GSW SSH
Server (SSH Shield) is also installed.

The
installation status also indicates that the Georgia SoftWorks RF Directed
Terminal Input/output (DTIO) Engine is not installed. This item will only be
checked as installed and running if it was purchased and installed. GSW RF DTIO
boosts performance and can increase the number of sessions that an application
can handle in many environments. Please visit GSW website for more information
on the RF DTIO Engine.

Note: If you are
performing a fresh install of the 30-day trial copy, you do not need to
register the software. Skip the registration steps.

Note: For UTS
versions 7.51 and older, do not use Remote Desktop or Windows Terminal Server
to perform software registration.

Two options exist for
registering the license for the GSW UTS Server software. The first option is a
Floating License (hardware key) that can be installed on a USB or Parallel port
on the server. The registration instructions for the Floating license are
below. The second option is a software method that is sent to GSW using the
GSTicket system. Instructions for the software registration are on page 23.

Georgia SoftWorks
offers an optional Floating License for customers that require the
flexibility to rapidly move the telnet server from one machine to another. If
you did not purchase the Floating License - skip this section and go to the
machine specific license on page 23.

With the Floating
License No registration is required for the telnet server to operate.

Common scenarios where
the Floating License is useful include:

·Laboratory usage in a development or test environment
where the telnet server is required for short periods of time on any particular
machine and then moved to a new machine.

·Backup Servers in a production environment. Typically additional
telnet servers are purchased for backup systems. However with a Floating
License the Hardware Key can be quickly moved from the primary machine to the
backup without any other registration requirements.

·Environments where a failed server must be replaced or rebuilt
and immediately restored to operation with full telnet capability.

The Georgia SoftWorks
floating license is a hardware key that can be ordered for a USB Port or a
Parallel port.

The Parallel Port Floating License connects to a female
parallel port on the server and does not impact functionality of the port for
other uses. It acts pass though allowing normal connections to the other side
of the key.

The SSH2/Telnet server will recognize the presence of the key and activate the software for the
correct number of sessions and the proper date for which free version upgrades
can be obtained. It does not matter which parallel or USB port on the server
the Hardware Key is installed, as all ports will be scanned for the
installation of the key.

The Floating License
currently is installed using the manufacturer SafeNet, previously Aladdin of
the hardware key setup program. It is described below. The name of the hardware
key is HASP4 and you will see it displayed in the setup screens. The best
drivers for the HASP4 are the HASP HL drivers.

Note:
If you are using a USB Floating License on a Windows NT system - run the
file aksnt4usb.exe prior to the following steps.

1.Copy the files from the Floating License folder (hardkey) on the provided
CD to the hard drive on your server.

2.Run the HASPUserSetup.exe program and follow the installation
instructions. After installation of the hardware key install the GSW Telnet
Server as described on page 9 (if it is not already installed). See the GSW SSH
Server User’s Guide for installation instructions of the GSW SSH Server.

3.If
you have User Account Control enabled you may get a prompt that says “Do you
want to allow the following program to make changes to this computer?” Click Yes

To run the Georgia
SoftWorks UTS Server for Windows you must first register the software. This
registration is NOT required if you purchased the Floating License (Page
15). This entails just a few steps that involve obtaining the
Product ID and providing this Identification to Georgia SoftWorks so a Serial
Number can be generated. - NOTE: Read System Signature chapter at
the end of User’s Guide.

Please complete the Customer
Information, the Purchased From and the Sessions Requested
fields in the Registration Screen. Enter the name of the software that will be
your primary application to use with Telnet/SSH in the Application software
field. Examples could be HighJump, SAP, QAD, Catalyst, System Administration,
etc.

Once Georgia SoftWorks
receives the information, we can generate a Serial Number on demand and will
send it to you. You may close the registration program at this time.

3.When the Serial Number is provided, Run the Registration Program again
(by right clicking and Run as Administrator)
and enter the Serial Number. The easiest method to get the serial number is to
highlight the returned Serial Number and copy (ctrl-c).
Then position the mouse in the Serial Number field in the Registration Information box and paste (ctrl-v).

In addition to the GSW UTS clients the Georgia SoftWorks UTS
Server is compatible with all Telnet or SSH compliant third party clients.

All the powerful and popular GSW Client options and features
described in the GSW UTS are available both for the GSW Telnet Server and GSW SSH
Server except where specifically noted. Georgia SoftWorks offers Telnet/SSH
Clients for the following platforms:

Both the SSH and the
Telnet Clients are included with the Georgia SoftWorks UTS. Please note that
only the clients appropriate for the server purchased will be able to connect.
In other words, if you have a Telnet Server, only GSW Telnet and compliant
third party clients will connect. If you have the GSW SSH Server only GSW SSH
and compliant third party clients will be able to connect.

NOTE: SSH
Clients can NOT connect to the Telnet Server and Telnet Clients cannot connect
to the SSH Server.

The robust, full
featured GSW UTS installed at thousands of mission critical location around the
world, coupled with Vangard’s AccuSpeech® Mobile provides a reliable and
innovative solution that is nothing less than a quantum leap in mobile
workforce productivity.

The GSW Windows Clients
are now voice enabled for operation with AccuSpeech Mobile so workforces can
voice-collect, access and transact information, while performing and focusing
on the task at hand.

Installation of the
Client software is simple. Run the setup.exe program. From Windows 7/8/10/VISTA/2008/R2/2012/2016
or Windows NT/XP/2000/2003 or Windows 95/98 perform the following:

Run the setup.exe program.

1. The Welcome screen
of the setup program is displayed and you are reminded and urged to exit all
Windows programs before continuing. The setup program recognizes if it is a Windows
system and prompts you for either a Full Install or a Client only
install. If this is a Windows system then select Client Only using the
Radio Buttons. If this is a Windows 95/98 system then you are prompted for
installation of the Georgia SoftWorks Windows Client. Click Continue.

2. A screen is
displayed indicating the directory that the Georgia SoftWorks Windows UTS
Client will be installed. The default is C:\gs_uts.
You may change the installation directory at this time. Click Continue.

4. The Setup Succeeded
is displayed.

5. A "Program
Group" is created. It contains two shortcuts, the Georgia SoftWorks Telnet
and SSH Client.

To uninstall the
Georgia SoftWorks Windows Software follow these instructions.

1.Click the Start button on the Windows Task bar - go to Programs

2.Find the Georgia SoftWorks line - To the right select uninstall
and follow the instructions. To reinstall the software you will need to
re-register the software.

GSW Mobile Clients

Georgia SoftWorks
provides mobile clients for PPC 2002, PPC 2003, Windows Mobile and Windows CE
.NET 4.2/5.0+ class devices. As with the GSW desktop clients, the GSW Windows
Mobile Clients are no extra cost, which can amount to a substantial savings. For
Android customers, GSW ConnectBot is an Android client product which can be
purchased separately. GSW Windows Mobile Clients are categorized into Universal
Mobile Clients and Enhanced Mobile Clients. An overview of each follows.

GSW Universal Mobile
Clients eliminate the need for operation verification for specific devices by
GSW. The Universal Mobile Client can simply be installed by the customer. This
opens a broad range of compatible devices while maintaining the rich feature
set provided by GSW Mobile Clients.

The
GSW Universal Mobile Clients for Windows CE .NET 4.2/5/6+ are designed to be
compatible with all Windows CE .NET 4.2/5/6+ systems running on ARMv4+, ARMv4i+
and x86 based devices. Each device type requires a particular Universal Mobile
Client. The Mobile Client and the location of its setup program are identified
in the table on page 33.

The
GSW Universal Mobile Clients for Pocket PC 2002 and Pocket PC 2003 are designed
to be compatible with all Pocket PC and Windows Mobile systems running on ARMv4+
based devices. The Windows Pocket PC and Windows Mobile devices that are based
on the ARMv4+ architecture each require a particular Mobile Client. The Mobile
Client and the location of its setup program are identified in the table on
page 32.

In some cases for
particular devices there may be features available that may not be obvious.
When appropriate we have provided special instructions on how to take advantage
of those features. Additionally there may be devices that have been verified
for correct operation. Please review page 36 to see if your particular device
has special instructions, tips or has been officially qualified.

In many mission
critical environments operation verification by GSW may be a requirement. If
your company would like operation verification please contact us at sales@georgiasoftworks.com or call
706.265.1018 for more information.

In addition to the
Universal GSW Mobile Clients, specialized or Enhanced Clients are
available for many devices that take advantage of device specific
features. Device specific features range from special key and light operation
to application locking features. Each Enhanced Mobile Client has a Tips
section that should be reviewed. To determine if your device has Enhanced
Mobile Client please see the table on page 35.

GSW Enhanced Mobile
Clients with verified operation on Windows CE .NET 4.2/5/6+ devices include the
Intermec CK30, CK31, CV60, LXE MX3X, Symbol MC 9060G MC9090G, Psion-Teklogix
7535, Psion-Teklogix 8525, Psion-Teklogix WORKABOUT Pro. Other CE .NET
V4.2/5.0+ based devices may be compatible but have not been certified as of
this writing.

If you have a device
that has unique capabilities and would like custom client features please
contact us at sales@georgiasoftworks.com
or call 706.265.1018 for more information.

·If your device is a PPC 2002 then use
the GSW mobile client setup program ppc2002c.exe

·If your device is a PPC 2003/Windows
Mobile then use the GSW mobile client setup program ppc2003c.exe

·If your device is running Windows CE .NET 4.2/5/6+, look at the
table on page 35 to determine if an Enhanced GSW Mobile Client is available. If
so then use the GSW Enhanced Mobile Client Setup Program Identified in the
table and be sure to look to see if any Tips are available for that
client.

·If your device is running Windows CE .NET 4.2+ and an Enhanced
GSW Mobile Client is not available then you can use a Universal GSW Mobile
Client.

oIf your device
type is ARMv4i+ then use gsce_4ig.exe

oIf your device
type is ARMv4+ then use gsce_4g.exe

oIf your device
type is X86 then use gscex86g.exe

oIf you do not
know the device type then

§First - Try the gsce_4ig.exe client, if that does not
work - then

§Next – Use the gsce_4g.exe client, if that does not
work - then

§Last – Use the gscex86g.exe client

GSW Mobile Client Installation
Programs

GSW
mobile clients are located in a subfolder on the CD or where the download was
unzipped with one of the following names

The GSW Universal
Mobile Clients operate on ARMV4, ARMV4I and X86 devices. In some cases special
instructions or tips may exist to take advantage of unique features or provide
ease of use pointers for that particular device. If there are special tips
or a particular device has been verified for correct operation then it
will be listed in the table below.

If
your device is not in the list above and it is an ARMv4+, ARMv4i+ or X86
devices, it is likely that a Universal GSW Mobile Client will operate. Please
use the steps in section above (page 32) to determine the correct mobile
client.

In
order to facilitate the varied commercial requirements GSW has provided
extended features for the GSW Mobile Clients for Windows CE .NET 4.2/5/6. These
additional features offer useful flexibility and efficiency for both the device
user and the System Administrator. The table below provides a brief description
of the features. The details on configuration and enabling the options follow.

To facilitate the fastest possible operation, the
default GSW Mobile Client operation disables mechanisms that allow the device
to suspend. There may be scenarios that require the device to Suspend. You can
configure the GSW Mobile Client Software to allow the device to Suspend by
setting the optionAllow Suspend

The Simplified Chinese font does not have to be
installed on the Universal Terminal Server. Note: The GB font will not
display in the GSW Desktop SSH/Telnet client or Session Administrator. GSW
engineering has verified correct operation with the GB (True Type) font.

You can create and save a number of Session
Configurations settings that you can use as needed. The Select Configuration
option displays the saved Session Configurations that reside in the same folder
as the GSW Mobile client software. This folder may vary from device to device
so please see the tips section (in this users guide) for your specific device
to determine its location. Put another way, Session Configurations are not
displayed if they do not reside in the same folder that the GSW Mobile Client
software resides.

You select the desired Session Configuration by
using the associated function key (F5). Display the Select Session Configuration by using the
menu bar.

The file format of the Session Configuration is such
that it can be used to clone or duplicate the session configuration on other
devices. Session device settings are kept completely in files with no external
references. This provides a portable configuration file that can be used when
setting up other devices. This can be a significant time saver when 40, 100 or
more devices are being set up.

The configuration files have the gswtc extension. The
file has an “ini” format with Username, Host, etc.

See also the section on application persistence
capabilities to view the usefulness of the GSW automatically created CAB files
when deploying GSW Mobile Clients (page 48).

After a restart the
client returns to the last active session. This works if default .gswtc is not
present (otherwise default.gswtc is loaded).

No Scrollbars
Option

Set this option to
eliminate the use of scroll bars to save screen space. The application should
display itself in the top-left corner of the screen. For example,
this is the position that SAPConsole assumes. Of course this assumes that the
application does not require scroll bars.

Normally
Scrollbars are enabled.

TheNo Scrollbars option is enabled by selecting the
optionNo scrollbars.

Keyboard Macros

Keyboard macros are a powerful and time saving feature
that lets the administrator define custom keys on the device when the session
is active[4]. Macros are used for
remapping Function keys (F1 – F12) to keystroke sequences.
Macros definitions have the form:

The keyboard macros are defined in the session
configuration files. These have gswtc extensions. The configuration files have
the “Windows ini” format. A new section [Macros] needs to be manually added
to the configuration file.

For example, to remap all Functions Keys to send
capital F, followed by function key index and the enter key you
would add the following section to the configuration file on the device
(usuallydefault.gswtc).

Disconnects the session. There may be times when you
want to disconnect the session. To disconnect the client from the server, enter
the Break-Out sequence.

After the session is disconnected, further behavior on
the session observes the rules configured on the server such as Graceful
Termination, Session Saver, etc. The Break-Out is accomplished by entering the
sequence

ctrl-shift-d

Note: Do not confuse this sequence which disconnects
the session with the Ctrl-Shift-b sequence (see page 40 )

Allows Function keys F1-F12 to be used by the
application. Windows Pocket PC, Mobile and CE .NET operating systems may take
control of one or more of the function keys making them unavailable to the
application software.

All GSW Mobile Clients (with the exception of PPC
2002) free the function keys from the operating system so they can be used by
the application. To restore operating system control of the function keys,
reboot the device.

GSW Telnet/SSH client for PPC2003 and Windows Mobile
5/6+ may be configured so it will easily interoperate with application launch utilities
like Intermec’s iLaunch, such that the client will terminate immediately when
the session ends. Additionally, if the feature is enabled the client will turn
off all menu options except ‘Disconnect’.

The configuration is performed by setting the
value of a new parameter ‘Bypass’ that resides in the “cppc2003.ini” file in the section
called ‘Settings’

Possible Values are:

0 –
disabled (default)

1
– enabled

If
the Bypass parameter is not present in the file, then the default value used

Configuration and Application Persistence

It can
be frustrating and time consuming if your configuration information is lost
over a reboot which is common with Windows CE and Pocket PC operating systems.
GSW has provided a reliable mechanism to ensure that the GSW Mobile Client
application and configuration can be persistent across all types of reboots.
Instructions vary depending of the type of GSW mobile client being used. Please
review the appropriate section for your client.

GSW
Enhanced Mobile Clients:

Follow the Tips section for your device. Do not follow
the Configuration Persistence configuration below for the GSW Universal Mobile
Clients. See page 35 for Enhanced Client Tips.

The GSW Mobile Client configuration is saved as a .cab
file, which is a compressed archive package definition format.

For each created Session Configuration there will be a
corresponding CAB file. For example if a session was saved with the name ‘lukexp.gswtc’ then a corresponding cab
file with the name ‘lukexp.cab’ is automatically created.

Non session specific configuration data is stored in
the CAB file c735x.cab. When these files are placed
in the persistent CAB folder on your device the GSW mobile client configuration
is restored upon reboot. The persistent CAB folder location is device
manufacturer and model specific.

When this file is placed in the persistent CAB folder
on your device the GSW mobile client application is restored upon reboot. The
persistent CAB folder location is device manufacturer and model specific.

The GSW Mobile Client configuration is saved as a .cab
file, which is a compressed archive package definition format.

For each created session configuration there will be a
corresponding CAB file. For example if a session was saved with the name ‘lukexp.gswtc’ then a corresponding cab
file with the name ‘lukexp.cab’ is automatically created.

Non session specific configuration data is stored in
the CAB file cppc2003.cab. When these files are placed
in the persistent CAB folder on your device the GSW mobile client configuration
is restored upon reboot. The persistent CAB folder location is device
manufacturer and model specific.

When this file is placed in the persistent CAB folder
on your device the GSW mobile client application is restored upon reboot. The
persistent CAB folder location is device manufacturer and model specific.

Step 3: When satisfied
with the configuration from within the GSW Mobile Client perform the menu item

File|Save

And save the settings in
location below

\My Documents\default.gswtc

The file below will
automatically be generated upon the Save command.

\My Documents\default.cab

Step 4: On the device
launch the File Manager and copy the configuration and application .cab files

\My Documents\default.cab

\Program Files\Georgia
SoftWorks\CPPC2003\cppc2003.cab

to the Persistent CAB folder

Mark the files as Read
Only

The persistent folder is
device manufacturer and model specific

Step 5: Copy the
application cab file defined in the Application Persistence section (page 51) to the Persistence folder
on the device. Mark it as Read Only

Step 6: Now you should
be able to cold boot the device and the client should automatically launch with
the correct configuration

Tips for
Intermec CK30 / CK31

Following are a few Tips
when installing the GSW SSH/Telnet WindowsClient for the above device running
Windows CE .NET Version 4.2+

1.Menu Accelerators / Shortcuts

As of
this writing the Intermec CK30/CK31 does not provide mouse/stylus capability
via a touch screen. In order to provide a more convenient method of
configuration the following accelerator keys are available. They are available
for all Mobile Clients for Windows CE .NET 4.2+ but are especially useful for
the Intermec CK30/CK31.

F2 – Save Session
Settings

F5 – File|Session Configurations …

F6 – Session|Connect

F7 – Session|Settings

F8 – File|Exit

2.Persistence over a ‘Cold Reset’

After
initial installation, please complete these steps as well as anytime the configuration
changes.

Once
the connection settings are configured and tested you can ensure that these
settings will still exist after a ‘Cold Reset’ of the Intermec CK30/CK31. This
is done by saving the file system and registry to flash memory. This is accomplished
by performing the following steps.

System Main Menu|Configuration Utility|File
Backup|Backup the File System

9.LED Color / Blink and beep Association – For use with SAP,
SAPConsole

Using the ABAP Code Generate Bell you can
associate different light-blink-colors based on the notify_bell_signal value.
You can control the number of beeps, the color of the led (green/orange) and
the number of blinks.

Example: notify_bell_signal = XYZ

Where

X = Number of beeps

Y = Color of LED

1 = green (left most light),

2 = orange (right most
light)

Z = Number of blinks

Each blink is
turned on for the same time as the beep

10.Scrolling and Mouse Support

The
Intermec CK30 / CK31 does provide screen scrolling and mouse support via
keyboard control. The Alt-Down
combination puts the CK30 / CK31 into a “Screen Scrolling and Mouse Mode” and
brings up a pointer that can be manipulated by numeric keys. Please see the
Intermec manual for further details. To dismiss the pointer enter the Alt-Down again.

Note:
Keyboard data entry functionality is not fully available when in the “Screen
Scrolling and Mouse Mode”. Simply put, dismiss the pointer prior to entering
text.

Many times System
Administrators request the capability to protect certain configuration values
associated with the application from being inadvertently or accidentally
modified by users. Georgia SoftWorks Mobile Clients either provide this
functionality or integrates and cooperates with devices that contain this
feature.

The GSW Mobile Clients
accomplish this protection by recognizing a user and a password
protected administrator security level. If the device provides a user
and administrative level, the GSW Mobile client integrates and
cooperates with the device feature. Otherwise the GSW Mobile Client provides a user
and administrative security level.

The administrator
security level is allowed unrestricted access to the application. The user
security level is not allowed to modify the configuration values or exit the
GSW Mobile Client application.

The System
Administrator can protect access to operations and values associated with the
following menu items.

oFile|New, File|Open,
File|Exit

oSession|Settings

Upon selecting the menu
item File you will notice that
while at the user security level the menu items New, Open
and Exit are disabled. The same
is true for the Session|Settings
menu item.

When using the GSW
Mobile Client Application Protection you can enable the administrator
security level by selecting the menu item File|Security
as shown above. The File|Security
menu item is enabled on Intermec, LXE and Symbol devices. The File|Security menu item is disabled on
Psion-Teklogix devices because the GSW Mobile Client uses Psion-Teklogix
security levels and is settable under Start|Security.

Upon selecting the
Security menu item the Security level dialog is presented.

To switch from User to
Administrator Security level you select Administrator
and enter the Admin Password. The Admin Password is 7062651018. Click OK. This will enable all configuration
and operations for the Administrator.

To switch from Administrator
to User Security level, select User
and click OK. A user password is not required.

Please see the tips
section for these mobile device clients for any special tips for Application
Protection.

At this prompt, you
should enter the hostname that you wish to connect. The hostname is the name
your Windows computer is referenced by via TCP/IP. This can be a text string or
an actual IP address. This name will appear in the client windows title bar.

Example:

Host: Soloman

OR
(if you know the IP address you can enter the address)

Host: 100.100.100.101

Or

Host: <ENTER>

This will connect to the
local host. You must be at the server for this to work (Useful for testing).

After the Host is found
you will see the Georgia SoftWorks Telnet Server connection banner[5].
The connection banner contains the version of the telnet server as well as the
number of sessions available and connected. You are then presented with the Windows logon prompt.

This is an optional
field. If you do not wish to connect to a specific domain then you may simply
press "<enter>". Otherwise type in the domain you want
to connect. You may eliminate the domain prompt either by using command line
options or by setting a default domain on the Windows Server. To set the default domain for all users follow the instructions on page 269. The Georgia SoftWorks Telnet Client Command line options are described next.

In addition to superior
Perfect PC terminal emulation the Georgia SoftWorks Telnet and SSH Clients have
powerful command line options facilitating faster, easier and more flexible
connections. Many of these options such as the Host, Username, Password and
Domain can be used to eliminate prompting by the client or server when
connecting to the UTS Server. The following optional command line parameters
may be used[6].

Parameter

Description

-4 or -6

Restricts protocol to IPv4 addresses or IPv6 addresses.
Otherwise both are supported.

-a

This specifies that this Georgia SoftWorks Client can
AutoLogon (page 104)

-b

Answerback Text passed to the Server and stored in the
Environment variable gwtn_answerback. See page 77 for more
details and PPC configuration.

-c

TELNET client only: Specifies that the client uses Encryption. This option works only in conjunction with corresponding settings on the server. See page 87 on setting up encryption.

-cCertificateName

SSH client only. Specifies the Certificate name for certificate based authentication. This feature is integrated with Microsoft Certificate Stores.

Specifies the domain of the user. Use '.' if you want to use default domain or no domain

-f[index] or

–F[index]

This allows additional form feed control capabilities. With some applications unexpected form feeds will be generated at the end of the document causing misalign output and paper waste. If this behavior is noticed then the -f option may help in suppressing the extra form feeds. Optional index is the virtual printer index. This option uses the copy command to print.

SSH and Telnet client: Specifies password for the user. Use '.' if user has no password. Notice that this is a lowercase "p".

SSH Client only: If public key authentication is activated then this is the password for a password protected private key file.

-PportNumber

Specifies the port number to use for telnet or SSH. This port must also be set on the Server in the services file. Notice this is an uppercase “P”

-r1=printername

-r2=printername

…

-r9=printername

This specifies Printer1, Printer 2, and Printer 3 … Printer 9 for Enhanced Mode client side printing. No spaces are allowed in the printer name. Please see page 213 for more information.

Continued on Next Page

-scmddelay

This specifies the Command Output Display Delay time (Milliseconds) for the results data displayed in the gs_clnt.exe/gs_ssh.exe window as a result of executing a Client Side Command (page 248 ) from within a telnet or SSH session. A primary function of the Client software is to display and refresh the Telnet or SSH Session Window based on Server Output. So when a Client Side Command displays results in the Session Window, a time is specified for the display of the Client Side Command Output in the gs_clnt.exe/gs_ssh.exe window before the display of server side data is resumed. The default is 2000[ms] (two seconds).

The User has additional control over the caption text displayed in the client window when using the Georgia SoftWorks Telnet or SSH Client. This helps identify specific sessions especially when multiple sessions are opened simultaneously. No spaces are allows in the Client Caption string. See example on next page for further details

-z

Disable the Automatic Update of the Georgia SoftWorks Telnet or SSH Client.

Long Options

The “+” plus sign designates “Long Option” parameters

The list of algorithms that can be used are in the GSW SSH Users Manual.

+Ciphers=

SSH client only - The list of Ciphers provided to the server for Cipher negoation

+KexAlgorithms=

SSH client only – The list of Key Exchange algorithms provided to the server for Key Exchange Algorithm negoation

+HostKeyAlgorithms=

SSH client only – The list of Host Key Algorithms provided to the server for Host Key Algorithm negoation

+Macs=

SSH client only – The list of Message Authentication Codes (MACs) provided to the server for Message Authentication Code negoation

The User has additional control over the caption text
displayed in the client window when using the Georgia SoftWorks clients. This
helps identify specific sessions especially when multiple sessions are opened
simultaneously.

The command-line option

-xText

specifies a text string that is displayed in the caption
on the client window. The text is appended to the caption after space as
x:Text. For instance if the option -xDavid was entered the title bar in the
client window would be displayed as show below (soloman is the hostname).

GSW Telnet and SSH Client command line options -
Usage

Following is an example
for specifying client command line parameters. The GS SSH2/Telnet Client shortcut invokes the batch file GS_SClnt.bat (for Telnet) or GS_SSSH.bat (for SSH) which
in turn launches the Georgia SoftWorks SSH2/Telnet Client. The GS_SClnt.bat and GS_SSH.bat files reside in the GS_UTS installation directory. The contents of
the batch files look as follows.

Always use the
matching version of the Georgia SoftWorks SSH2/Telnet Client with the Georgia SoftWorks UTS Server.

When a Georgia
SoftWorks Client connects to the GSW Universal Terminal Server, the GSW UTS is
able to determine the version of the GSW Windows Client that is connecting. If
the version of the GSW SSH2/Telnet Client is different than the GSW UTS
version, the GSW UTS updates the remote (client) computer with the appropriate
GSW Client for that version of the GSW UTS Server.

As new versions of the
software are released, occasionally matching versions of the GSW Windows Client
and UTS is required to take advantage of certain features. Sometimes this
required the System Administrator to either visit the remote site or via
telephone walk remote users through instructions to install or update the GSW
Client software.

Additionally, System
Administrators may be administering many GSW Universal Terminal Servers
distributed throughout a large region. Different versions of the GSW UTS may be
installed at different sites. Regardless of the version installed the
Administrator will be able to automatically use the appropriate version of the
GSW Windows Client.

Important Note to Customers of Versions Prior to
6.26

Previous versions of the GSW Telnet Client invoked the
client executable directly from the shortcut.

Starting with Version 6.26 the short cut invokes the
batch file GS_SClnt.bat which launches the Georgia SoftWorks Telnet Client.
The batch file must be invoked for the Automatic Client Update to occur.

Note: This feature requires the minimum GSW Telnet Server and
Client version 6.26.

If you want to disable the Automatic Update of the GSW SSH2/Telnet Client then use
the –zcommand line
option.

When the Remote User connects to the GSW UTS Server
computer and the versions do not match the User will see the following screen.
The Text Upgrade initiated is displayed. While the appropriate client is being
transferred a series of periods is displayed indicating the progress of the
transfer.

Developer
Tip: If a client side application must launch the Georgia SoftWorks Client then
the application should check the return code from the call to
gs_clnt.exe/gs_ssh.exe. If the rerun code is two (2) then the client and server
versions are different and newer client was copied to the file gs_clnt.new. It
should be renamed and copied to gs_clnt.exe/gs_ssh.exe and then launched.

You may want the Application Title to display in the title
bar of the Georgia SoftWorks Client Windows Title. This capability is disabled
by default. To enable you should set the gwtn_show_console_title
environment variable in your logon script (Learn more about logon scripts on page
390).

The environment variable for displaying the Application
Title in the Georgia SoftWorks Client Window title bar is:

gwtn_show_console_title

Possible values are Y
(or 'N', or 'y' or 'n')

Y – Enable the
display of the application title in the Georgia SoftWorks Client Window Title

N – Disable
the display of the application title in the Georgia SoftWorks Client Window
Title (default)

For example to enable the display of the Application Title
in the Georgia SoftWorks Client you would enter:

You may not want the ‘x’
(close button) to display in the top-right title bar of the Georgia SoftWorks
Desktop Client. If the ‘x’ is pressed in the top-right corner then the
connection between the client and server is abnormally closed. The session may
get suspended if the system is configured to do so. The administrator may
require a specific method for the user to exit the application and thus may
want to eliminate the ‘x’ (close button) as an option for the user.

The ‘x’ is displayed (enabled)
by default. To disable you should set the gwtn_clnt_no_x
environment variable in your logon script (Learn more about logon scripts on page
205).

The environment
variable for disabling the display of the ‘x’ in the Georgia SoftWorks Desktop
Client window title bar is:

gwtn_clnt_no_x

Possible values are 'Y' or 'N',
or 'y' or 'n'.

Y – Disable the display of the ‘x’ in the title bar in
the Georgia SoftWorks Desktop Client window Title

N – Enable the display of the ‘x’ in the title bar in
the Georgia SoftWorks Desktop Client window Title (default)

For example to disable
the display of the ‘x’ in the Georgia SoftWorks Desktop Client you would enter:

Keyboard
macros are a powerful and time saving feature that lets the administrator
define custom keys on the device when the session is active[8]. Macros are used for
remapping Function keys (F1 – F12) to keystroke sequences.
Macros definitions have the form:

Function Key=Keystroke
Sequence

or

Function
Key=(shift:ctrl:alt) Keystroke Sequence

Where

Function Key is F1 through F12

and

(shift:ctrl:alt)

This is optional extended syntax that provides the
capability to specify the Shift, Ctrl and Alt key states. You may want to
have a Shift F1 or a Ctrl F1, Shift Alt F2, etc. and the syntax of (Shift:Ctrl:Alt ) is a fast way to specify
if the key is pressed. To indicate a key is pressed is by using the value 1 and so specify that it is
not pressed is to use the value 0.

For example

(1:0:0) specifies that the SHIFT key
is pressed but not the CTRL or ALT.

(0:1:0) specifies that the CTRL key
is pressed but not the SHIFT or ALT.

(0:0:1) specifies that the ALT key
is pressed but not the SHIFT or CTRL.

Or combinations can be
specified:

(1:1:0) specifies that the SHIFT key
and CTRL keys are pressed but not the ALT.

Whitespace is optional.

See
the example in the configuration section below for detailed examples.

The Georgia SoftWorks
Windows Universal Terminal Server is packed with features. The aggregation
of the features is geared toward industrial and commercial application. The
features logically group into units called packs. All feature packs are
included with the Georgia SoftWorks UTS at no extra cost!

Security Pack – (see
page 86 )

The Security Pack
provides the system administrator with confidence that the Windows System and the data transferred remains secure. Encryption, access and usage
restrictions are among security features implemented.

Performance Pack – (see
page 103)

Advanced proprietary
algorithms, optimizations and compressions provide for the fastest SSH2/Telnet Server for Windows on the market.

GSW Team Services – (see page 111)

Allow mobile users to
quickly share resources to improve productivity while keeping cost down without
requiring system administrator / IT intervention.

Industrial and
commercial applications demand sophisticated failure detection and recovery
methods. Georgia SoftWorks recognized the requirement and has unequaled
capabilities in this area.

Legacy Pack – (see
page 157)

Proper operation with
Legacy applications is the foundation of a quality SSH2/Telnet server. The Georgia SoftWorks Telnet Universal Terminal Server for Windows will meet or exceed all expectations with respect to running character oriented and
legacy applications.

Emulation Pack – (see
page 159)

The Emulation Pack provides
all the popular emulations required by most 3rd party clients. Not
only are the emulations provided but they are implemented correctly.

Power Features Pack
– (see page 175)

The Georgia SoftWorks
UTS provides the most powerful, needed and useful features on the market.

Compatibility Pack –
(see page 231)

RFC 854 compliance
provides access from other platforms allowing the Telnet Server to be utilized
by a variety of users.

RF Terminal Features
- (See page 231)

Utility Pack – (see
page 246)

Several utilities are
provided for the telnet user to simplify and ease the use of SSH2/Telnet.

Security Pack

Georgia SoftWorks
provides unmatched security when using our Telnet Server for Windows. It
is the only Telnet Server that offers complete Data Stream Encryption.
The Georgia SoftWorks Telnet server has been submitted to the United States
Department of Commerce and has obtained the proper license exceptions so it can
be legally exported around the world[9].

Data Stream encryption can be enabled on a global or a per
user basis with undetectable performance loss. This is useful if users are
running accounting, banking, medical or other applications that contain
sensitive data.

Logon only encryption may also be employed.
This protects User Ids, Passwords and other logon data.

The Georgia SoftWorks Universal Terminal Server is integrated
with Windows Security. All Windows security concepts apply. The Georgia
SoftWorks UTS allows the system administrator to optionally restrict telnet
access based on User ID or IP address. These are additional security measures
above the normal Windows security. The system administrator can specify the
users that are allowed to logon via telnet

Encryption of the Data Stream for Telnet on Windows is another feature pioneered by Georgia SoftWorks. Complete Data Stream
encryption is available on a global or per user basis when using the Georgia
SoftWorks Telnet Client. For encryption to work both the sending and receiving
ends of the data must know to encrypt and decrypt the data. Since third party
clients would not be aware of encryption or decryption, data stream encryption
is only available with the Georgia SoftWorks Telnet Client.

The Setup for Data Stream Encryption requires:

1.The
encryption parameter must be passed when invoking the Georgia SoftWorks Telnet
Client

2.The
setting of an environment variable on the server in either a Global or User
login script

3.The
registry variable EnableEncryption is set to 1.

4.The
proper Microsoft Windows operating system DLLs and API’s are installed on both
the client and server systems.

The variable EnableEncryption
is a registry key value. This Registry key enables or disables the ability to
activate Encryption. If it is disabled then all encryption environment
variables are ignored. Also the client command line parameter must not be
used when the registry value is disabled. The key is:

Encryption requires specific operating system Dll’s (that
are present on most systems) to exist to run the telnet client and server.

These files come with Windows NT 4.0/XP/VISTA/2000/2003/2008/W7/W10
and are included in Microsoft Internet Explorer Version 3.0 and above. If you
do not have these system files encryption will not operate.

If you have Windows 95 then
you must have Windows 95 OSR2 (OEM Service Release 2) or later (or Windows 95 with
IE 3.02 or later).Windows 98 and newer versions have all the
required files.

NOTE:
128-Bit Complete Data Stream is the default version when shipped on a CD.

The
Georgia SoftWorks configuration needed to run the 128-bit encryption is the
same as for the 40-bit encryption. The system requirements needed to run the
encryption are slightly different. In order to run the 128-bit encryption the
system requires either:

Server or Client Requirements

·Windows NT 4.0 with domestic version of SP 3 or domestic version of SP4
or

·Windows 7/8/10/VISTA/2008/R2/2012/2016, XP/2000/2003

Additional Client Options

·Windows 95 with domestic version of Microsoft Internet Explorer 4.0. or

·Windows 98 with domestic version of Microsoft Internet Explorer 4.0.

·Windows ME with domestic version of Microsoft Internet Explorer 4.0

If
you have further questions about of ensuring that your computer systems can
accommodate 128-bit encryption please see the Microsoft Web site.

Both
the client and server must meet the system requirements for the SE version.
Also both the Client and server must be of the SE version.

You may choose to only
encrypt the logon sequence when using the Georgia SoftWorks Telnet Client. This
entails the same steps as described with Complete Data Stream encryption except
there are no environment variables to set in the logon scripts.

In certain situations
it may be desirable to have encryption enabled or disabled based on the IP
Address of the connecting telnet session. Complete Encryption (both Logon and
Data Stream) can be enabled/disabled based on the IP address using the
configuration text file gs_ipenc.txt[10]. The Data Stream Encryption Client
side parameter must also be used when configuring encryption based on IP
addresses as described on page 87.

When configured the
settings in the gs_ipenc.txt file
overrides the normal encryption registry and environment settings.

The GSW SSH Server
offers very strong end-to-end encryption for all data. This includes the
authentication and data stream. Please see the GSW SSH User’s Guide for more
information on the SSH Server encryption.

A Federal Information
Processing Standards Publication (FIPS) 140-2 compliant option is available and
may be purchased for the GSW SSH Server. This standard specifies the security
requirements that will be satisfied by a cryptographic module utilized within a
security system protecting sensitive or valuable data. This option is available
to Federal agencies, including the US Military. It may also be purchased by
other organizations such as state governments, educational and research
institutions, commercial businesses and other entities with the need or desire
to comply with this security requirement for cryptographic modules standard. Please
see the GSW SSH User’s Guide for more information on the SSH Server FIPS option.

When the FIPS 140-2
option is enabled on the GSW SSH server, FIPS 140-2 compliant connections can
be identified by using the Session Administrator.

A True GSW FIPS 140-2
connection is identified by an asterisk “*”
prepended to the username in the session administrator. This means that
a GSW FIPS 140-2 compliant client is connected to a FIPS 140-2 compliant
server. Both ends are compliant and thus you can have confidence that this is a
GSW True FIPS 140-2 compliant connection. Usernames without an asterisk “*”cannot be confirmed as FIPS 140-2
compliant.

The system
administrator may optionally restrict connections via SSH2/Telnet based upon the user id. This is useful when you have a defined set of users
that you would allow access to the Windows Server via SSH2/Telnet . If the system administrator decides to limit the users allowed to logon via SSH2/Telnet then the local group Gwtn Users must be created. If this group
exists then only members of this group will be allowed to logon via SSH2/Telnet . If this group does not exist then all users that can logon locally can log on
via SSH2/Telnet. Once the group Gwtn Users is created, each user allowed
to logon via SSH2/Telnet must be added to this group[11].
Windows does not instantaneously update the group membership after the user
manager is closed. You will have to restart the Windows server after creating the group and adding users.

The system
administrator may optionally restrict connections via telnet based upon the
Host IP address. Remote access may be limited only to specific IP addresses.
The system administrator may also restrict specific IP addresses from
connecting via SSH2/Telnet.

Restrictions based on
IP address are enforced when the file thosts
exists. The IP addresses of interest are listed in the thosts file. In short, only IP addresses listed in the thosts file are allowed to connect via
telnet/SSH. The provision also exists to exclude specific IP addresses from
connecting via SSH2/Telnet. A keyword [Exclude] is used that indicates all IP
Addresses listed in the file should be excluded from logon via SSH2/Telnet.

How to set up Host IP Address Restriction.

Use the GSW GUI Configuration Tool – Edit thosts file 357

Or use legacy style below

You must create the file:

thosts

The file must reside in the Georgia SoftWorks Universal
Terminal Server installation directory. The directive [EXCLUDE] indicates if
the IP Addresses should be excluded from connection.

NOTE: The System account must have
permission to read the thosts
file.

The rules are simple for setting up the thosts file.

1.It
is a text file

2.The
# character is the comment character

3.[EXCLUDE] directive placed in the 1st line will force the interpretation
as the exclusion file, otherwise only IP addresses listed are allowed.

4.Data after the IP address is ignored and therefore can be used for
additional comment data.

Bill and Tom have
machines that are in a public location and are not secure. The system
administrator does not want to allow SSH2/Telnet access from those machines. However Bill and Tom have other machines that need SSH2/Telnet access to the server. This is how to set up the thosts file to exclude those
particular machines.

Information needed:

IP address
of Bill's machine: 198.68.20.21

IP
address of Tom's machines: 198.68.22.25

Edit the file thosts and add the following lines.

[EXCLUDE]

# Here is the list of hosts that are not
allowed to log in via SSH2/Telnet

198.68.20.21 Bob's machine

198.68.22.25 Tom's machine

Now let’s look at the
contents of the file.

The [EXCLUDE] directive
specifies that all IP addresses listed in the thosts file are not allowed to
connect via telnet.

The next line is a
comment reminding the System Administrator that the following Host IP addresses
will not be allowed to connect via SSH2/Telnet .

Next is the list of
Host IP addresses to exclude. The list can be as long as you desire.

ACME Accounting has 3
remote locations. For the machines at each location there may be dozens of
different users that may be connecting at different times of the day. The
system administrator only wants to allow SSH2/Telnet connections from the 3 remote locations.

However the ACME remote
Location 3 office is temporally closed and is under remodeling. Therefore the
system administrator wants to easily comment remove them from the
"allowed" list and quickly add them back as soon as the office
reopens.

Information needed:

IP address of ACME accounting
location 1 machine: 198.68.35.21

IP address of ACME accounting
location 2 machines: 198.68.35.25

IP address of ACME accounting
location 3 machines: 198.68.35.26

Edit the file thosts
and add the following lines.

# Here is the list
of hosts that are allowed to log in via SSH2/Telnet

#

198.68.35.21 ACME
accounting location 1 machine

198.68.35.25ACME accounting location
2 machine

#Let’s not allow
location 3 until the office reopens.

#198.68.35.26 ACME accounting
location 3 machine

#

Restrict users access to a specific application

The system
administrator may optionally limit a user to run a specific application. This
is accomplished using the c_start.bat
file logon scripting technique. A detailed example and description is on page 206.

This feature allows
connections only from the Georgia SoftWorks SSH2/Telnet Client. This is another level of security that the system administrator can
configure. Many times the system administrator will not want users using any
generic client to connect to his or her system.

The variable EnableRFC854Clients is a registry key
value. This Registry key enables or disables the ability to restrict
connection from 3rd party clients. If it is disabled then only users
using the Georgia SoftWorks SSH2/Telnet client are allowed to connect. The key is:

This feature specifies
the total number of connections allowed. This is another level of security that
the system administrator can configure. Many times the system administrator may
want to limit the total number of connections to be a smaller value than the
number of connections purchased.

The variable MaxSessions is a registry key value.
This Registry key enables or disables the ability to restrict connection to the
number of sessions specified. If it is disabled (0xffffffff) then all of the
sessions purchased are available, otherwise then the MaxSessions Registry value is compared to the number of
sessions purchased. The smaller of the two numbers is used as the number of
sessions to allow. The key is:

The system
administrator may want to limit the number of simultaneous logons for specific
User Ids. This is especially useful for ASP environments where an entire
company, department or group is assigned a single User Id that everyone shares.
The system administrator may want to limit the number of simultaneous
connections for that company for a variety of reasons that range from server
resource allocation to purchased access.

Restrictions based on the number of User Id sessions are
enforced when the file gs_l_usr.txt
exists. The User Id’s with connection restrictions counts are listed in the gs_l_usr.txt file. For each entry in
the gs_l_usr.txt file two fields
are specified: The User ID and the Count.

How to set up User ID Count Restriction

Notice the file in the GSW UTS installation directory:

gs_l_usr.txt

The file must reside in the Georgia SoftWorks Universal
Terminal Server installation directory.

NOTE: The System account must have
permission to read the gs_l_usr.txt file.

This file is used for configuration of the User ID Count
Restrictions.

ACME ASP is an
Application Service Provider (ASP) where they have a Specialized Database
Lookup Application (SDLA) located on a server at their headquarters. They sell
access to the SDLA to companies where pricing is based on the number
simultaneous connections. Each company accesses the SDLA via the Internet from
undetermined or varying locations. Each company that purchases access to the
SDLA is provided a User ID on the ACME server, that everyone from their company
shares.

Currently AMCE has sold
access to the SDLA to six companies. Four companies purchased three connections
each; the remaining two companies purchased twelve connections each.

ACME wants to restrict
each company to the number of sessions that they have purchased.

The ACME System
Administrator can configure the gs_l_usr.txt
file that specifies the number of sessions allowed for each User ID.

This is how to set up
the gs_l_usr.txt file to limit the number of connections for each company.

Edit the file gs_l_usr.txt and add the following
lines. (Be sure to start in column one)

bbrain 12

viginv 3

sweeta 3

warstore 3

surship 3

Wiresec 12

Each time a logon
request occurs the GSW Universal Terminal Server determines the number of
active sessions associated with that User ID. If the count of active sessions
exceeds the configured count in the gs_l_usr.txt
file then the logon is denied.

A sample gs_l_usr.txt file with examples is
installed with the software. It can be easily modified and used for your
purposes.

The system
administrator may want to limit the number of simultaneous logons from specific
IP Addresses. This is especially useful for ASP environments where many users
access the GSW UTS from locations that can be identified by a specific IP
Address. The system administrator may want to limit the number of simultaneous
connections for a variety of reasons that range from server resource allocation
to purchased access.

Restrictions based on the number of sessions originated
from specific IP Addresses are enforced when the file gs_l_ip.txt exists. IP Addresses with connection
restrictions counts are listed in the gs_l_ip
file. For each entry in the gs_l_ip
file two fields are specified: The IP Address and the Count.

ACME ASP is an
Application Service Provider where they have a Medical Database Lookup Application
(MDLA) located on a server at their headquarters. They sell access to the MDLA
to companies where pricing is based on the number simultaneous connections. Due
to the sensitive nature of Medical information access is only granted from
specific locations that can be associated with known IP Addresses. In addition,
each User has access to private medical information based on their User ID. The
typical ACME customer may have 300 users that need access to the MDLA but no
more than 20 will be using the system at any given time.

Currently AMCE has sold
access to the MDLA to four companies. Two companies purchased twenty
connections each; the remaining two companies purchased twenty-five connections
each.

ACME only wants to
restrict each company to the number of sessions that they have purchased.

The ACME System Administrator can configure the gs_l_ip.txt file that specifies the
number of sessions allowed for each User ID. The Information for each company
is:

Company Name

IP Address or Range

Number of Concurrent Sessions

Heath Matters Inc.

192.71.34.107

20

Live Long Insurance

170.40.255.231

25

Grow Tall Pharmaceutical

(They want access from any the following IP Addresses to work.)

164.10.15.210

164.10.15.211

164.10.15.212

164.10.15.213

164.10.15.214

164.10.15.215

164.10.15.216

164.10.15.217

164.10.15.218

164.10.15.219

164.10.15.220

164.10.15.221

164.10.15.222

164.10.15.223

164.10.15.224

164.10.15.225

164.10.15.226

164.10.15.227

164.10.15.228

164.10.15.229

164.10.15.230

20

Sharp Doctors for You

(Sharp Doctors for You has a large range of IP Addresses that are valid.)

This is how to set up
the gs_l_ip.txt file to limit
the number of connections for each company.

Edit the file gs_l_ip.txt
and add the following lines.

192.71.34.107 20

170.40.255.231 25

164.10.15.210-164.10.15.230 20

205.20.63.* 25

Each time a logon
request occurs the GSW Universal Terminal Server determines the number of
active sessions associated with that the originating IP Address. If the count
of active sessions exceeds the configured count in the gs_l_ip.txt file then the Logon is denied.

Note 1: An Address range is specified in
line 3

164.10.15.210-164.10.15.230
20

This translates to include all
IP Addresses between:

164.10.15.210
and 164.10.15.230

Note 2: An Address Wilde Chard is
specified in line 4

205.20.63.* 25

This translates to include all IP Addresses
no matter what the values for the last field. The list below helps visualize
the IP addresses included.

164.10.63.0

164.10.63.1

164.10.63.2

…

164.10.63.253

164.10.63.254

164.10.63.255

A sample gs_l_ip.txt file with examples is
installed with the software. It can be easily modified and used for your
purposes.

This feature allows
connections only from the encrypted Georgia SoftWorks Telnet Client. This is
another level of security that the system administrator can configure. Many
times the system administrator wants to ensure that ALL connections to the GSW
UTS are encrypted.

Note: This feature is
only relevant for Telnet. By the nature of SSH all connections are encrypted.

The variable RequireEncryptedSession is a registry
key value. This Registry key enables or disables the ability to restrict
encrypted only sessions. If it is disabled then only users using the Georgia
SoftWorks Telnet client are allowed to connect. The key is:

The default value is
0(Disabled.) The value 1 only allows encrypted session to connect. The value 0
allows both encrypted and un-encrypted sessions to connect to the Georgia
SoftWorks Telnet client. This value must be left set to 0 (the default) if
running the GSW SSH Server.

Use of this feature overrides user settings in
the logon script and force clients to use encrypted session data stream.

Please make sure the registry parameter:

EnableEncryption

is set to 1 and that
the Georgia SoftWorks Telnet Client uses the /c
command line option.

After you complete your
settings you will notice the following:

a. 3rd
party clients will report disconnected session before the user even tries to
type his logon name.

b. GS
clients which do not have /c
option will fail to connect.

This is how to change
the registry key for connection by only Encrypted Sessions.

Note: You must be on
the Windows system that the Georgia SoftWorks Windows UTS is installed. However
you may connect to the Windows Registry from a remote location.

The Georgia SoftWorks
Universal Terminal Server has pioneered and introduced another expected
but missing feature in the Windows world. Typically when a user password is
expired connections are simply refused by Windows SSH2/Telnet servers. This is not the case with the Georgia SoftWorks Universal Terminal
Server. The user is prompted for the new password just as if they were logged
on locally to the Windows Server.

The Georgia SoftWorks
Universal Terminal Server for Windows is integrated with Windows security, adhering to the native security already existing on Windows.

Performance Pack

The Georgia SoftWorks SSH2/Telnet Server is the fastest SSH2/Telnet Server available for Windows . The Georgia SoftWorks UTS is designed to work in the most demanding industrial and
commercial applications. This means that it must have reliable and consistent
operation all of the time. It does not matter if there is one connection or 100
connections. It is dependable, reliable, consistent and robust.

The Georgia SoftWorks
UTS provides incredibly fast screen updates, in fact the fastest on the market.
Several optimizations have been implemented with respect to screen updates. For
example when data is sent from the server to the client only the screen data
that has changed is sent.

Keyboard response is
also incredibly fast. When you type a character, it is displayed immediately. A
fast typist will have to work hard to outrun the keyboard response of the
Georgia SoftWorks Universal Terminal Server.

To accomplish the
desired performance, the GSW SSH2/Telnet Server designers used object oriented C++ for the foundation of the software, providing a modular, easily
extensible and maintainable design. In addition to sophisticated performance
algorithms, all time critical sections of the software are written in highly
optimized C code.

The Georgia SoftWorks
DOSBoss dramatically improves system performance in situations when
MSDOS applications are running under Microsoft Windows NT. In fact some say it
is incredible!

Many MSDOS applications
run under Windows but do not perform well, especially when multiple instances
of them are being used at the same time (This is without SSH2/Telnet in the picture). This is because MSDOS applications do not know about Windows and assume they are the only application(s) running on the computer. As a result the
MSDOS applications are not always Windows friendly.

For example, Start 3
instances of the Microsoft Edit program in 3 separate command prompt windows.
Next start the Performance monitor. You will notice the CPU usage is very high
even though you are not actively using the editors. Your computer does not
perform well when the CPU usage is high. This problem occurs with many MSDOS
applications.

To enable the Georgia SoftWorks DOSBoss put the
following line at the beginning of your logon script:

<telnet_dir>\dosboss

where <telnet_dir> stands for the Georgia
SoftWorks Telnet Server Directory, for example:

c:\gs_uts\dosboss

The above activates the DOSBoss with default
parameters that satisfies most users requirements.

Note for power users

You can specify additional command line parameters
for the DOSBoss. Valid command lines are:

/cnn
- specifies the count of time slices to release. Default is /c3.

In the case where DOSBoss is already loaded the
installed instance will change its parameter(s) to the new value(s).

/h
- to display the help message

/r
- uninstall the resident part of the program (Do not use with /c option)/s - show
statistics of the resident portion (DOSBoss must be loaded first)

This feature allows you
to pre-configure a list of IP addresses that will be able to connect and log on
without any User ID, Password or Domain prompting when using the Georgia
SoftWorks SSH2/Telnet Clients or 3rd Party Telnet Clients.

Autologon is useful in
many situations; however the real power of this feature is realized when coupled
with the Session Saver (page 143) for fast and easy connection establishment.
For example when a connection is broken due to a link failure you can reconnect
without the time consuming UserID, Password and Domain prompts and resume work
exactly where you left off before the link failure.

The configuration
procedure for Automatic Logon is different for GSW Windows Clients and Third
Party Clients. A list of IP address can be associated with either GSW Windows
Clients or 3rd Party Clients but NOT both.

Automatic
Logon for GSW Clients is configured using the gs_auto.txt
file. Automatic Logon for Third Party Clients is configured using the gs_logon.txt file.

Automatic
Logon for GSW Telnet and SSH Clients is configured using the gs_auto.txt file.

Automatic
Logon for Third Party Telnet Clients is configured using the gs_logon.txt file.

Automatic
Logon for Third Party SSH Clients requires the use of Public/Private key
authentication. For more information please contact Georgia SoftWorks support

The format
of the files is exactly the same butit is important to remember which
files are used for each client type.

Note: An IP address cannot be
associated withboth a GSW Client and a Third
Party Telnet Client. No overlap between IP Address ranges defined in
the gs_auto.txt andgs_logon.txt
is allowed. Unpredictable results will occur.

Second, a server side configuration text file is used for
specifying the IP address that will AutoLogon. The name of the file for the
Georgia SoftWorks SSH2/Telnet Client is gs_auto.txt and is installed in the GSW UTS Root Directory.
All Clients connecting with IP addresses specified in the gs_auto.txt file must be
GSW Clients AND the IP Addresses CAN NOT also be used in the 3rd
Party Automatic Logon configuration text file. No overlap between IP Address
ranges defined in the gs_logon.txt and gs_auto.txt is allowed.

An IP address can be
associated to AutoLogon with a Georgia SoftWorks OR a 3rd
Party Telnet Client but NOT both. No overlap between IP Address
ranges defined in the gs_auto.txt and gs_logon.txtis allowed.

For example the following entry in the file:

63.80.112.70 .
rayr sharpbook

Instructs the system
that when a user connects from the IP Address 63.80.112.70
that the connection should be authenticated as ‘./rayr’
with the password set to ‘sharpbook’.

The ‘#’ character in
the first column designates a comment line.

NOTE1: The IP
address must start in the first column. IP Address Ranges and wildcards are
allowed.

NOTE2: For
security reasons it is prudent to set the file gs_auto.txt to allow only SYSTEM – Read Access. NO other
accounts should be allowed to access this file.

NOTE3: The
format of this file is the same as gs_logon.txt,
the automatic logon configuration file used with 3rd party clients.
Only the name of the file is different.

This feature allows you
to pre-configure a list of IP addresses that will be able to connect and log on
without any User ID, Password or Domain prompting when using 3rd
Party Telnet Clients.

Autologon is useful in
many situations; however the real power of this feature is realized when
coupled with the Session Saver (page 143) and/or used with RF Data collection
devices for fast and easy connection establishment. For example when a
connection is broken due to a link failure you can reconnect without the time
consuming UserID, Password and Domain prompts and resume work exactly where you
left off before the link failure.

A server side text file
is used for specifying the IP addresses that will AutoLogon. The name of the
file is gs_logon.txt
and is installed in the UTS Root Directory. No client configuration is required
for 3rd party telnet clients.

An IP address can be
associated to AutoLogon with a Georgia SoftWorks OR a 3rd
Party Telnet Client but NOT both. No overlap between IP Address ranges
defined in thegs_logon.txtandgs_auto.txtis allowed.

For example the
following entry in the file:

63.80.112.70 . rayr sharpbook

Instructs the system
that when a user connects from the IP Address 63.80.112.70 that the connection
should be authenticated as ‘./rayr’
with the password set to ‘sharpbook’.

The ‘#’ character in
the first column designates a comment line.

NOTE1: The IP
address must start in the first column. IP Address Ranges and Wildcards are
allowed.

NOTE2: For
security reasons it is prudent to set the file gs_logon.txt to allow only
SYSTEM – Read Access. NO other accounts should be allowed to access this file.

NOTE3: The
format of this file is the same as gs_auto.txt, the automatic logon configuration file used
with the Georgia SoftWorks Telnet/SSH clients. Only the name of the file is
different.

GSW
UTS x64 Native 64-Bit

Georgia SoftWorks
created a native build optimized for 64-bit platforms. Indeed many 32-bit
applications will run on a 64-bit platform including the standard GSW UTS, but
our philosophy of continuous improvement demands that we put forth the effort
to make the software native on the powerful 64-bit platform. This eliminates
potential compatibility issues of non-native code running while taking full
advantage of the performance and addressing opportunities afforded by the
64-bit platform.

The above is a screen
shot of gs_admin when GSW Engineering performed burst connection testing with
the GSW UTS x64. This is where hundreds of connections are initiated rapidly
over and over taxing the system until several thousand connections are
maintained. Even though this test goes beyond what is considered real world it
provides information as to the benefits of a 64-bit system as well as the
glimpse of the extensive testing performed to ensure the GSW UTS meets and
exceeds the demands of commercial environments. At this point in testing GSW
UTS x64 the screen shot was taken from GS_Admin with over 2400 connections.

The GSW UTS
has a built in interface to work with the GSW RF Directed Terminal Input/output
Engine. The GSW Directed Terminal I/O Engine is an add-on component that
intercepts a specific set of terminal input/output operating system calls
initiated by your applicationand directs
terminal I/O through a specialized high performance interface within the GSW
Universal Terminal Server (UTS).

A new
performance standard is realized when using the GSW Directed Terminal I/O
Engine with the GSW UTS for Windows. Large systems will experience a
dramatic performance improvement as well as a substantial increase in the
number of sessions on a server.

The GSW
DTIO Engine is specialized software, focused on a narrow set of goals.
The objectives are to provide significant performance improvements and a
higher number of sessions on a server than previously possible due to
processing bottlenecks and CPU Limitations

GSW Team Services
provides your mobile device users a breakthrough in telnet/SSH technology that
shatters all prior usability and efficiency standards by allowing for
unprecedented user collaboration and cutting the costs of hardware. The
implications are enormous. GSW Team Services has the potential to radically
transform the client/server applications universe from isolated and fragile
sessions to the world of persistence and creative collaboration of empowered
users.

Team Services furnishes your mobile device users with innovative
session management tools that are initiated from the client. Team Services is
fast and easy to use.

GSW Team Services
empowers the mobile device users to share resources, transfer, swap, share and recover
mobile device sessions from the mobile device! This provides your mobile
device users the capability to quickly solve common mobile device session and device
problems without having to perform administrative operations on the server or needing
to involve Information Technology (IT) personnel.

Incredible
Features – Sharing, Swapping, Transfer and Recovery of sessions.

Fast
and Easy - No technical degree required and the fastest way to resume work.

Team members helping team members. Instead of purchasing
multiple types of devices per user; or all high end devices for the occasional
need for high end features, team members can maximize device utilization by
quickly sharing or swapping devices without even having to log off or
involving the system administrator.

Often user(s) needs to
use a different or an additional device, while preserving their session. GSW
Team Services Transfer, Swap and Share operations addresses this need.

·Transfer – Transfer (move) your
session to another team member’s device. Terminates the existing session on the
second device when the transfer is complete.

·Swap – (Swap devices but
keep your session) Transfer your session to another team member’s device and at
the same time Transfer their session to your device.

·Share – Two devices share
the same session. Either device may be used within a single session. This is
similar to the GSW Session Administrator Shadowing feature, except Share is
initiated from the client. The Share Team Service can be used when a forklift operator
has a vehicle mount device and also needs a wireless mobile device, both using
the same session. It can also be used for training and assistance. The range of
possibilities for Team Service Share is so powerful it is limited only by your
imagination.

Recover dropped sessions. It doesn't matter if
the session is dropped due to battery failure, device destruction, network
problems or simply because the user went out of range. With GSW, the session
is maintained on the server and with Teams Services the session can be recovered
from the same or another team member's device. Of course, you
will resume work at the exact point where you were when the session dropped.

GSW Team Services
increases productivity by allowing your team members to minimize down time when
ordinary work flow interruptions occur and resume work with unmatched speed and
ease.

Strict Teams. Often workflows are specific to
distinct groups (or teams) and the administrator wants to allow only members
within that group to have the capability initiate Team Services operations SHARE,
SWAP, TRANSFER and RECOVER.

With Strict Teams, system administrators can create multipleTeams such that only members within each team
can participate in Team Services operations with other members of their team. This
is particularly useful in Application Server Environments and in situations
when the pool of SSH/Telnet users span multiple departments, locations or
companies.

Individuals may be assigned
to more than one team, allowing flexibility such
as supervisors overseeing multiple teams or specifying floating individuals for
overflow situations.

Only
users defined as part of a team can participate in Team Services
operations with other members in the team.

Organize
groups, departments, locations into Teams such that they can help each
other, but not impact other Teams.

Configuration
instructions and examples are contained in the tsgroups.txt
file. This file resides in the GS_UTS installation root folder.

Team Services
operations are straightforward to understand and use. Below is an overview for using
GSW Team Services. In this document GSW Team Services is often abbreviated
"TS".

The Team Services
Transfer, Swap and Share operations requires the team member who originates
the operation first communicate with the 2nd team member[12]
in order to request that the 2nd team member put their device
(session) in the proper Team Service Accept mode for the operation. The 2nd
team member must affirm that they are willing to accept a Transfer, Swap or
Share. This way the 2nd team member's session is not unknowingly
altered without expressly consenting to the operation.

The 2nd team
member initiates Team Services and enters the “Accept Mode” for the specific
Team Service to consent to the operation. This is done by pressing the
corresponding function key for the Team Service operation. Session
Identification information is displayed and can be quickly communicated to the
originating team member.

The originating team
member then enters Team Services, selects the Team Service operation,
identifies the 2nd team member's session and completes the
operation.

The entire process can
take less than 60 seconds.

In summary, the Transfer,
Swap and Share Team Service operations each have an Accept Mode
and a Team Services Operation.

The Recover Team
Service does not have an Accept Mode. You could consider a suspended session as
consenting by default.

The Transfer, Swap and
Share Team Service general procedural flow is:

1.One team member (originator)
requests a 2nd team member to participate in a Team Service
operation.

2.The 2nd team
member puts their session in Accept Mode for the Team Service operation.

2.Team member identifies
the suspended session, selects and completes operation.

Team Services state and
status information is displayed in the Session Administrator. This allows the
administrator to know which devices are sharing, waiting for Team Service
Transfers, Swaps, Shares and etc. Please view page 139 for more information on
the Session Administrator and Team Services.

Enter Team Services Tasks by typing Ctrl-x (see page
115 for more details) or the configured hot key. The Team Services Tasks menu
is show below.

Each of the Team
Service tasks is initiated by using a function key on the device. Team Service tasks
that require an Accept mode use a pair of function keys, one for the Accept
and the other for the Team Service tasks. When Accept Mode for a Team
Service is performed, the client device display is similar to Figure 58.

The associated Team
Service operation displays a list of sessions available for that operation
similar to Figure 59. The session is selected for the operation by entering
the displayed line number for that session. For example to swap with session s5 the user would enter a 2 since that is the line number for session
s5.

The Transfer operation
uses the F1 key for Transfer Accept Mode and the F2 key to perform the Transfer
operation. The Swap operation uses the F3 key for the Swap Accept Mode and the
F4 key for the Swap operation. The Share operation uses the F5 key for Accept
Share Mode and the F6 key for the Share operation.

A
configurable hot key is used to enter GSW Team Services. The default hot key is
Ctrl-x. When initiated, Team Services presents the user with a menu that
is used to transfer a session, recover a session, swap sessions, share a session
etc. Learn more about the configurable hot key on page 137.

Devices come with a variety
of screen sizes offering large display areas on stationary or truck mount devices
and smaller display areas on smaller hand held mobile devices. With GSW Team
Services the text is automatically adjusted based on the number of columns and
rows defined with the "Mode Con" command (page 285) in your logon script. If there are not enough columns to display the complete Team Service text
then intelligent abbreviations are used so you can view the essential
information in the normal font for your application.

This works well with
the small hand held mobile device displays as well as the larger truck mount
displays. No magnifying glass is required to read the text, nor do you have to be
a detective to decipher the meaning of the abbreviations.

The three most used
Team Services screens are:

·Team Services Main Menu

·Team Services "Accept Mode" Display

·Team Services "Select Session" Menu

Below is an example of
the full text of the Team Services tasks menu on the left and the abbreviated
text on the right. In order to maximize the readability alternate abbreviations
are used based on the number of columns and rows defined.

Team Services Main
Menu

Abbreviated Team
Services Tasks

Set the number of columns and rows for your application
and GSW Team Services will display all the text or abbreviate it based on
your configuration.

Note that
"Accept" is abbreviated "Acc", and "transfer"
uses the common abbreviation "xfer" while the words "session",
"mode" and "suspended" are completely omitted.

Below is an example of
the Team Services Accept Transfer mode display. The Accept modes for the other
operations are similar. The unabbreviated version is on the left and the
abbreviated version is on the right.

Note that the text "My session id is" and
"for transfer" is omitted yet the essential session id (s5) is
presented as well as the "Waiting..." text providing a reminder to
the user.

The TS Select Session display is shown below.

There are a few items
to note.

oIf more than
one page is required to display all the available sessions then the function
key F2 is used to display the
next page. F1 navigates to the previous page. This is true for both the
abbreviated and unabbreviated lists.

oEach page has a
Page x of y count display, where x is the page you are viewing and y is the total number of pages.

oOn each page
the line numbers corresponding to the session id are zero based. Below on page
1, line 0 corresponds to session id (s0).
On page 2, line 0 corresponds to session id (s5).

The Team Services
Transfer operation takes a session on one device and moves it to a 2nd device.
It terminates the existing session on the 2nd device. The session will resume
exactly where it was when the transfer occurred.

In the diagram below we
have two people, Barry and Sam. Each has a session and a device. Sam is going
to lunch and Barry wants to use Sam’s wireless mobile device to scan some items
his truck mount device cannot reach. With TS Transfer, Barry can transfer his
session to Sam’s device without even logging off.

Barry asks Sam if he
can Transfer to his device. Sam consents and enters Team Services (Figure 64) and presses F1 to enter
Accept Transfer mode. Sam’s display shows he is session id “s5” (Figure 65).

Barry enters Team
Services on his truck mount device (Figure 66) and presses F2 to initiate the Transfer
operation. Figure 67 shows a list of sessions in Accept Transfer mode. Barry
does not see session s5 so he presses F2 to go to the next page. Now he sees
session s5 is listed by line
number 0(Figure 68). He presses 0 to complete the transfer to session
s5. Sam’s session is
terminated and Barry's session is on Sam's mobile device and Barry can resume
exactly where he left off.

The Team Services Swap
operation takes two sessions on two devices and moves the session on the 1st
device to the 2nd device and moves the session on the 2nd
device to the 1st device. Each session is preserved and will resume
exactly where it was when the swap occurred.

In the diagram below we
have two people, Doug and Andy. Each has a session and a device. Doug wants to
use Andy’s wireless mobile device to scan some items his truck mount device cannot
reach. Andy still needs to work but can finish his work with the truck mount.
With TS Swap, Doug can transfer his session to Andy’s device, while simultaneously
transferring Andy’s session to Doug’s truck mount device. Both can continue their
work in the application and not even have to log off.

Doug enters Team
Services on his truck mount device and presses F4 to initiate the Swap
operation. Figure 74 shows a list of sessions in Accept Swap mode. Doug sees s5 is listed by the number 2. He
presses 2 to complete the swap with session s5.
Andy’s session is moved to the truck mount device and Doug's session is on the
mobile device and both can resume exactly where he left off.

Notice in the following
diagram that Doug is now using the mobile device yet he is still using his
original session. Likewise Andy is now using the truck mount device and is
still using his original session as well.

The Team Services Share
operation allows two devices to share a single session. Input from either
device is sent to the session. Output from the session is displayed on both
devices. This is similar to the Session Administrator "Shadow"
feature (page 182) but developed for Team Members.

This feature has
several applications. One is to allow a single user to work with two devices in
the same session. Another application is when one team member needs to help
another team member. Share can also be used for quality control purposes. You
may have ideas for your own environment.

In the diagram below we
have two devices and one person - Tom. Tom's device is a truck mount device.
He is the only one working in the warehouse today and also wants
to have a wireless mobile device to scan items his truck mount device cannot
reach. Tom needs all his work be in a single session and he does not want to
log on and off each time he uses each device. Tom can use the TS Share feature
and have two devices connected to a single session. With each scan he can use
the most convenient device.

Tom obtains the
wireless mobile device. He is already connected with his truck mount device.
Tom wants to allow his truck mount device session to be shared. From
the truck mount device he enters Team Services (Figure 77) and then initiates the task Accept Share by
pressing F5.The truck
mount device display shows his session id is “s5”
and waiting for a partner (Figure 78).

Tom takes the wireless
mobile device and connects creating a temporary session. Tom enters Team
Services on his wireless mobile device and presses F6 to initiate the Share task (Figure 79). The list of sessions in Accept Share mode is shown (Figure 80). Tom sees s5 is listed by the number 2. He
presses 2 to join session
s5. Tom's mobile device is now
connected to the same session as the truck mount device. The result is shown
in Figure 81.

Tom's original
temporary session is maintained and he can return to it by undoing the
share by pressing control-x from the wireless mobile device[13].
The truck mount device continues in its session. This is shown in Figure 82.

The Team Services
Recover operation allows a suspended session to be recovered to another device.
This differs from the Session Saver Auto-Reconnect which allows the same device
to recover a suspended session.

In the diagram below we
have two devices and two team members. Amos is working, but laid his device
down to look behind a crate. Barry, just learning to drive the fork lift, ran
over Amos's device. Amos was in the middle of some critical work and cannot
afford to lose his session. Team Services can Recover Amos's session to a
different device.

After Amos's device is
destroyed, his session is suspended but recoverable with TS. Barry has an extra
wireless mobile device. Amos obtains the wireless mobile device. On the mobile device
Amos enters Team Services Recover by pressing F7.
The mobiledevice display
shows a list of suspended sessions (Figure 87).

The GSW Team Services Tasks
menu provides the user access to the Team Services operations.

Enter GSW Team Services
by entering the hot key combination from the
device. The default key combination is Ctrl-x.
This can be changed to meet your requirements (see page 137). To enter the hot key - depress Ctrl then x, and then release the keys. The
Team Services Tasks menu is displayed.

Often with multiple
users, departments, locations, customers it is beneficial to organize users
into distinct teams for participation in Team Services. This strict team
grouping prevents users from accidently sharing, swapping, transferring or
recovering sessions with users outside their assigned group.

Configuration of
Strict Teams is performed through the tsgroups.txt
file.

Using a simple example, if you have seven (7) users
with three (3) in receiving and four (4) in shipping then you may want to have
two strict teams. Matt, David and Luke are in receiving and Diane, Naomi, Doug and
Phillip are in shipping. You want to create two teams with the names Receiving
and Shipping.

Team
Name User Domain Name User Logon Name

receiving highjumpserver_1 matt

receiving highjumpserver_1 david

receiving highjumpserver_1 luke

shipping highjumpserver_1 diane

shipping highjumpserver_1 naomi

shipping highjumpserver_1 doug

shipping highjumpserver_1 phillip

You would modify the tsgroups.txt file by adding the lines
as follows:

receiving,highjupserver_1,matt

receiving,highjupserver_1,david

receiving,highjupserver_1,luke

shipping,highjupserver_1,diane

shipping,highjupserver_1,naomi

shipping,highjupserver_1,doug

shipping,highjumpserver_1,phillip

The ‘#’ character in the first column designates a comment
line.

NOTE1: The team name must start in the first
column.

NOTE2: The ‘#’ character in the first column
designates a comment line.

You are an Application
Service Provider and your customers want to use Team Services and it is
critical that they do not accidentally Share, Transfer, Swap or Recover
sessions from the other companies.

You can organize each
company as its own Strict Team and they will only be able to participate in
Team Services with members in their company. You can even organize multiple
Strict Teams within each company to further segregate team members.

Team
Name User Domain Name User Logon Name

acme_sprockets acme_server_1 acme_user_a

... ... ...

acme_sprockets acme_server_1 acme_user_z

army_complex1 army_intelligence army_user_1

... ... ...

army_complex1 army_intelligence army_user_1000

auto_factory sports_cars_7 emerson

... ... ...

auto_factory sports_cars_7 elliot

train_station public_trans_rr train_point_1

... ... ...

train_station public_trans_rr train_point_400

You would modify the tsgroups.txt
file by adding the lines as follows:

In some environments it may not be appropriate for all
users to have access to all GSW Team Services. The system administrator may
configure the default access settings for each individual Team Service
operation using Registry parameters.

NOTE: For new installations of the GSW UTS the
Registry parameters enable all Team Services by default.

·For upgrades from a pre-Team Services version (pre
v8.01) of the UTS, Team Services is disabled by default for security reasons[15].
You must enable Team Services for operation.

These default settings
can be overridden using environment variables in global or per user logon scripts.

For example you may want to have Team Services disabled
except for certain users. This can be accomplished by disabling each Team
Service with Registry parameters and then overriding them for specific users in
their logon scripts.

Team Services Left
Justify specifies the placement of the Team Services dialog information. If you
are not using the "mode con" command you may see some screens displayed
with part of the information hidden as show in Figure 91. This can be corrected using Left Justify as shown in Figure 92.

You can configure the
TS hot key sequence to use a different key instead of x. The x
is represented in our settings by its virtual key code and the common
values are listed in the tables below. The values in the table are specified in
hexadecimal. In the registry editor when entering a value for TSHotKeyVK be sure that the base is
set to hexadecimal.

The variable TSHotKeyVK
is a registry key value. This registry key sets the default behavior for all
users.