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 226). 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 77 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.
The GSW clients are
available on a wide variety of operating system platforms ranging from Windows
to Pocket PC 2003. See the table on page 25 for a detailed list of GSW Windows clients
available for each platform.
For Android customers,
GSW ConnectBot is a GSW Android SSH/Telnet Client product that can be purchased
separately. It has the strongest security of any commercially available SSH
client for Android. Learn more about it here (https://www.georgiasoftworks.com/connectbot-client-android)
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.
Figure 1: GSW UTS Components Overview
The
features, utilities and clients are provided by the GSW UTS. Unless noted all
features and utilities are available to all GSW Server Products.
The
GSW UTS supports a wide set of emulations that allows connections from most third-party
clients. Compliant 3rd party clients can exist on any operating system. Of
course, GSW Windows Clients are offered at no additional cost for Windows operating
systems, Pocket PC 2003 class devices and other Windows RF devices. A list
of these Windows Operating Systems is on page 25 .
GSW Also offers GSW
ConnectBot, a client for Android, which is available for purchase.
The standard protocol
interface included with the GSW Universal Terminal Server is the Telnet Interface.
No application or protocol interface installer is required.
The product purchased
is the GSW Telnet Server. The installation setup is quick and easy. You can be
up and running in the matter of minutes.
Figure 2:
GSW UTS - Telnet Server Components
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.
Figure 3: GSW UTS - SSH Server Components
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.
This edition is for 64-bit editions of Microsoft operating systems (Windows 7/8/10/VISTA/2008/R2/2012/R2/2016/2019
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.
Figure 4: 32-bit platform alert.
The GSW Desktop client
provided with all editions is a 32-bit client and will install on both 32-bit
and 64-bit platforms.
Server Installation
From Windows
perform the following:
Run the gsw_x64.exe
program. (recommended)
The Welcome screen of
the setup program I displayed. Remember that you must have administrative
privileges to install this program. Click Next.
Figure 5: GSW UTS x64 Initial
Setup Dialog - Welcome
Power Users: .msi
is also provided for administrators using mass deployment tools, for example GPO.
Additionally .msi files are suitable for creating customized deployment
configurations using Microsoft Orca and MSI transforms.
Note: You cannot install
the same UTS version with both the .exe and .msi setup package programs. If you
start with one, stick with it.
2. 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 Next.
Figure 6: GSW UTS Installation
Path
4. The Ready to Install
dialog is displayed.
Click Install.
Figure 7: GSW UTS Installation
Progress Meter
A progress meter window
is displayed indicating the installation progress
Figure 8: UTS Installation
Progress meter
5. The Setup Succeeded
screen is displayed. Click Finish. The service has been installed and
is automatically started.
Figure 9: GSW UTS Installation
Setup Succeeded
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.
6. A "Georgia SoftWorks
UTS Program Group" is created.
Figure 10: UTS Program Group
The
items in the shortcuts in the Program Group are:
·
Certificate Mapping Tool for GSW SSH Shield – Certificate to User
account mapping for SSH customers.
·
GS SSH Client – This is the Desktop GSW SSH Client. Use if the
GSW SSH Server is installed.
·
GS Telnet Client – This is the Desktop GSW Telnet Client. Use if
the GSW Telnet Server is installed.
·
Installation Status – This displays the GSW UTS version, the
service status and if the GSW SSH Server is installed. The version and service
status are also displayed for the GSW SSH Server.
·
ReadMe SSH/ReadMe UTS – ASCII text file containing current release
notes and other late breaking important information for both the GSW UTS and SSH
Servers.
·
Registration – Registration utility used to permanently activate
the GSW UTS software.
·
Session Administrator – Powerful tool for monitoring/shadowing sessions,
broadcasting and more.
·
SSH Users Guide
·
UTS Configuration Tool
·
UTS Users Guide – The complete User Guide in MS Word format for
the UTS and SSH.
You can view the GSW Software Installation Status
by double clicking on Installation Status.
Figure 11: GSW Software Installation Status
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
software method that is sent to GSW using the GSTicket system. Instructions for
the software registration are below. The second 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 on page 21.
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 16). 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.
To run the registration
software either -
1.
Click on the Registration Shortcut in the GSW UTS program group OR
2.
Select the Start button on the task bar, select Programs,
then Georgia SoftWorks UTS and then Registration.
The registration screen
is displayed. The Registration software automatically fills in the Product
Information fields as show in Figure 12.
Figure 12: Registration - Initial Screen
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.
Figure 13: Registration:
Customer Information Entry
Save the file using the
“Save to file” button.
The registration
information must be provided to Georgia SoftWorks to obtain the Serial Number.
Several methods are available for your convenience.
a.
Go to: https://www.georgiasoftworks.net/support_gsw/open.php
to submit a ticket for Registration. Complete necessary fields and attach the
file you saved in the previous step. - Preferred method – Fastest response
time.
OR
b.
Email the file to registration@georgiasoftworks.com
c.
Print the information and Fax it to Georgia SoftWorks- 706.265.1020
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).
Figure 14: Registration - Serial
Number Entered
4.
Click Register.
Figure 15: Registration Successful
Figure 16: Registration:
Complete
Now the software is registered.
You may now run the Georgia SoftWorks Windows
Telnet Server. Note that you will be able to obtain Free Updates until the date
specified.
IMPORTANT: READ
SYSTEM SIGNATURE CHAPTER AT END OF USER’S GUIDE (PAGE 420).
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 16.
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.
|
Parallel Port Floating License
|
USB Floating License
|
|
Figure 17:
Floating License – Parallel Port
The Parallel Port Floating License is a Pass Through allowing
normal function of the port.
|
Figure 18:
Floating License - USB Port
Not attached to a
Server
|
|
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.
|
USB LED Lights when Installed
|
Table 1 - Floating Licenses - Parallel and USB Ports
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) 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
Figure 19: Hasp Preparing to Install
4. You will first see the gemalto (formerly
SafeNet) initial Welcome Screen.
Figure 20: Sentinel welcome screen
Click
Next
5. The next screen displayed is the gemalto
License Agreement screen.
Figure
21: SafeNet License Agreement
Read
the license agreement and select “I accept the license agreement”
Click
Next
6. Ready to Install Sentinel Runtime
Setup
Click Next.
Figure 22: gemalto
Sentinel Runtime Setup
7. Install Drivers - Progress bar,
updating system.
Figure 23: gemaltor Sentinel Runtime Setup Progress bar
8. Gemalto Sentinel Successfully
Installed.
Figure
24: SafeNet Validating Install
Click Finish.
9. Plug the hardware key onto the
parallel or USB port on the server.
NOTE: On some systems you may have
to reboot the server after installation. If the Floating License is not
recognized (by the UTS) after installing the driver, please reboot the server.
In the event that you
need to uninstall the Floating License (SafeNet HaspHL) please use the Windows
Control Panel Add/Remove Programs administrative utilities.
NOTE: Removing or
uninstalling the Floating License will disable the GSW UTS Server.
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:
Operating System |
GSW Telnet Client |
GSW SSH Client |
Client Type |
Window 98/ME |
Yes |
Yes |
GSW DESK TOP CLIENT |
Windows NT 4.0 |
Yes |
Yes |
Windows 2000 |
Yes |
Yes |
Windows XP |
Yes |
Yes |
Windows 2003 |
Yes |
Yes |
Windows Vista |
Yes |
Yes |
Windows 2008/2012/2016/2019 |
Yes |
Yes |
Windows 7/8/10 |
Yes |
Yes |
|
|
|
GSW Mobile Pocket PC Device Clients |
Windows CE .NET 4.2/5/6+ |
Yes |
Yes |
GSW Windows CE .NET 4.2/5/6+ Client |
Pocket PC 2003 |
Yes |
Yes |
GSW PPC2003 Client |
Windows Mobile 2003 |
Yes |
Yes |
GSW PPC2003 Client |
Windows Mobile WM5, WM6+ |
|
|
GSW WM56 client or PPC2003 client |
LXE MX3X Teklogix 7535 devices Teklogix 8525 Symbol MC9060G Intermec CK30, CV60 (All of these devices when Running Windows CE .NET 4.2/5/6+) |
Yes |
Yes |
GSW Windows CE .NET 4.2/5/6+, WM6+ Clients |
|
|
|
GSW Java Clients |
Java Client |
Yes |
No |
|
Java Applet |
Yes |
No |
|
Table 2 - GSW SSH Client Platforms
Both the Windows 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.
For Android customers,
GSW ConnectBot is a GSW Android SSH/Telnet Client product that can be purchased
separately. It has the strongest security of any commercially available SSH
client for Android. Learn more about it here (https://www.georgiasoftworks.com/connectbot-client-android)
The following diagram
may be helpful in visualizing the GSW Client to use with various Windows
Operating Systems.
Figure 25: GSW Client and Operating System Diagram
.
Georgia SoftWorks has collaborated
with Vangard Voice Systems, Inc. to develop and implement the required software
to enable the UTS Mobile and Desktop clients to operate with AccuSpeech®
Mobile, their enterprise voice solution. Vangard Voice System’s solution creates
a custom voice-user interface for controlling existing mobile, devices,
application and business processes. Configuration is simple.
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.
GSW UTS Windows Mobile
and Desktop clients support Vangard Voice
Systems, Inc. AccuSpeech® Mobile on Windows and are
enabled by GSW Client configuration.
UTS and GSW Windows clients
version 8.04 or higher is required for Vangard Voice AccuSpeech support.
Configuration of the
GSW UTS clients to enable operation with Vangard Voice AccuSpeech Mobile is
described on page 307.
The GSW Desktop (Telnet
and SSH) clients are automatically installed on the computer that the UTS is
installed.
To install the GSW Desktop
clients on other Windows computers the following:
Run the gsw_uts_clients.exe (recommended) or gsw_uts_clients.msi
program. They are located in the GS_UTS Desktop folder.
The Welcome screen of the
setup program is displayed. Remember that you must have administrative
privileges to install this program. Click Next.
Figure 26: GSW UTS client
Initial Setup Dialog - Welcome
Power Users: .msi
is also provided for administrators using mass deployment tools, for example GPO.
Additionally .msi files are suitable for creating customized deployment
configurations using Microsoft Orca and MSI transforms.
Note: You cannot
install the same UTS Clients version with both the .exe and .msi setup package programs.
If you start with one, stick with it.
2. A screen is displayed
indicating the directory that the Georgia SoftWorks desktop clients 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.
Figure 27: GSW UTS Desktop Client
Installation Path
4. The Ready to Install
dialog is displayed.
Click Install.
Figure 28: GSW UTS Clients “Ready
to Install” dialog
Click Install.
You will get a User Account Control prompt asking if you
want to allow Georgia SoftWorks UTS to make changes to this device. (your computer).
Click Yes
.
Figure 29: GSW UTS Clients Install
is complete.
Click Finish.
You can now use the GSW
Telnet / SSH Clients.
A program group will be
created.
Figure 30: GSW UTS Desktop
programs group.
To uninstall the Georgia
SoftWorks Windows Software, use the Windows Apps & Features Uninstall.
GSW Mobile Clients
Georgia SoftWorks provides
mobile clients for 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.
Universal
Mobile Clients for Windows CE .NET 4.2/5/6+
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 34.
GSW
Universal Mobile Clients for Windows Pocket PC, Windows Mobile 2003/WM5/WM6+
The
GSW Universal Mobile Client for Pocket PC 2003 is 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 33.
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
running Android, then look at the GSW ConnectBot for
Android. It has the strongest SSH security of any commercial SSH client for
Android available. It operates as a 3rd party client meaning it will
connect with any telnet/ssh server that is protocol compliant.
·
If your device is a Windows Mobile 5,
6+ then use the GSW mobile client setup program WM56c.exe. However,
the ppc2003c.exe will also run fine.
·
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.
o If your device
type is ARMv4i+ then use gsce_4ig.exe
o If your device
type is ARMv4+ then use gsce_4g.exe
o If your device
type is X86 then use gscex86g.exe
o If 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
|
|
|
GSW Universal Mobile Clients
|
|
|
Operating
System
|
Device Type
|
GSW
Client Setup Program location / name
|
|
|
Windows CE .NET 4.2/5/6+
|
ARMv4+
|
/clients/gsce_4g.exe
|
|
|
|
ARMv4i
|
/clients/gsce_4ig.exe
|
|
|
|
X86
|
/clients/gscex86g.exe
|
|
|
|
|
|
|
|
PPC 2003
|
ARMv4+
|
/clients/ppc2003c.exe
|
|
|
Windows Mobile 5,6+
|
|
/clients/wm56c.exe or
|
|
|
|
|
/clients/ppc2003c.exe
|
Table 3 - GSW Mobile Client Setup
Program Locations
Note: ARMv4+ includes ARMv4, ARMv5, and ARMv7 etc.
|
|
GSW Enhanced Mobile Clients
for Windows CE .NET 4.2/5/6 Devices
|
|
|
Operating
System
|
Device Type
|
GSW
Client Setup Program location / name
|
|
|
Windows CE .NET 4.2/5/6+
|
ARMv4+
|
/clients/gsce_4.exe
|
|
|
|
ARMv4i
|
/clients/gsce_4i.exe
|
|
|
|
ARMv4i
|
/clients/gsceck30.exe
|
|
|
|
X86
|
/clients/gsce_x86.exe
|
|
|
NOTE: See the table (page 35) for
Enhanced Mobile Clients to determine if your devices can use one of the above
clients.
|
|
|
Table 4 - GSW Mobile Client
Setup Program Locations - continued
Installation steps
- Install
current version of the Georgia SoftWorks UTS Server (Version 6.50 or
higher).
- Determine
the location and name of the GSW Mobile Client Setup program for your
device. See page 33.
- Copy
the appropriate setup executable to the computer which established
partnership with your device.
- Turn
on your device.
- Start
the Mobile Device Center or Active Sync on the device and connect.
- Run
the self-extracting executable on the computer selected in Step 3.
- Confirm
the prompts asking to continue with the installation.
- You
should see the setup program launched on your device.
- Press
the OK button on the device to complete the installation.
Please review any Tips for your device in the Enhanced
(page 35) and Universal clients
section (page 36 ).
GSW
has Enhanced Mobile Clients for the following devices that take advantage of
unique features on the listed devices. Be sure to review the Tips section for each device.
Table 5
- Enhanced GSW Mobile Clients
Universal GSW Windows Mobile Clients Special Tips or Qualifications List
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.
|
Devices
Qualified with Universal GSW Mobile Client for CE
.NET V4.2 +
|
|
|
Device
Model
|
Device Type
|
GSW
Client
|
|
|
PSC Falcon
4410
Tips for PSC Falcon 4410 on page 65
|
ARMv4i
|
gsce_4ig.exe
|
|
|
Datalogic
Elf CE 6.0
|
ARMv5
|
gsce_4g.exe
|
|
|
Datalogic
Falcon X3 CE 6.0
|
ARMv5
|
gsce_4g.exe
|
|
|
Honeywell
Dolphin 6500 CE 5.0
|
ARMv5
|
gsce_4g.exe
|
|
|
Honeywell
LXE Thor CE 6.0
|
X86
|
gsce_x86.exe
|
Table 6 – Devices qualified with
Universal GSW mobile clients for Win CE
|
Devices Qualified with Universal GSW Mobile
Client for CE .NET V4.2+
|
|
Device Type
|
GSW
Client
|
|
|
|
|
Janam XG100
CE 6.0
|
ARMv5
|
gsce_4g.exe
|
|
|
Motorola
MC9190 CE 6.0
|
ARMv5
|
gsce_4g.exe
|
|
|
Motorola
Psion Teklogix Omni XT10 CE 6.0
|
ARMv7
|
gsce_4ig.exe
|
Table 7 - Devices qualified with
Universal GSW mobile clients for Win CE
|
Devices Qualified with Universal GSW Mobile Client for Windows
Mobile
|
|
|
Device
Model
|
Device Type
|
GSW
Client
|
|
|
Bluebird Pidion
BIP-6000 Windows Mobile 6.1 Pro
|
ARMv5
|
ppc2003c.exe
|
|
|
Intermec CK71
Windows Mobile embedded 6.1 Classic
|
ARMv7
|
ppc2003c.exe
|
|
|
Intermec CN3
Windows Mobile 5.0
|
ARMv5
|
ppc2003c.exe
|
|
|
Honeywell
Dolphin 9950 Windows Mobile 6.1 Classic
|
ARMv5
|
ppc2003c.exe
|
|
|
Nautiz X4
|
ARM
Cortex-A53
|
Windows Mobile 6.5
|
Table 8 - Devices qualified with
Universal GSW mobile clients for Win Mobile
|
Devices Qualified with for Correct Operation with GSW UTS
|
|
|
Device
Model
|
Device Type
|
Operating
System/Client
|
|
|
Bluebird Pidion
BIP-6000 Android 2.3.7
|
ARMv5
|
Android
2.3.7
gsw-connectbot.apk
|
|
|
MobileDemand
xTablet T7000 Windows 7
|
X86
|
Windows
7
|
|
|
Nautiz X2
|
Texas Instruments
AM3715
|
Android
6.0
gsw-connectbot.apk
|
|
|
Algiz 10X
|
X86
|
Windows
10
|
|
|
Widefly WF 68
Mobile Computer
|
Intel
|
Android
6.0
gsw-connectbot.apk
|
Table 9 - Other devices that
operate with the GSW UTS
|
Devices Qualified with GSW UTS
|
|
Device Type
|
Device
Model
|
Device Type
|
Operating System
|
|
|
Janam XG100
CE 6.0
|
ARMv5
|
Windows
gsce_4g.exe
|
|
|
Janam XG200
|
Qualcomm Snapdragon
|
Android
gsw-connectbot.apk
|
|
|
Janam XM75
|
Qualcomm Snapdragon
|
Android
gsw-connectbot.apk
|
|
|
Janam
XT2
|
Qualcomm Snapdragon
|
Android
gsw-connectbot.apk
|
|
|
Janam XT100
|
Qualcomm Snapdragon
|
Android
gsw-connectbot.apk
|
|
|
Janam XG3
|
Arm
Cortex A53
|
CE 5.2
ppc2003c.exe
|
Table 10: Janam devices
qualified with GSW UTS
|
Devices
Qualified with GSW UTS
|
|
Device Type
|
Device
Model
|
Device Type
|
Operating System
|
|
|
Cipher Labs
9700 Series
|
Arm
Cortex A53
|
Android
gsw-connectbot.apk
|
|
|
Cipher Labs
RS30
|
Arm
Cortex A53
|
Android
gsw-connectbot.apk
|
|
|
Cipher Labs
RS50
|
Arm
Cortex A53
|
Android
gsw-connectbot.apk
|
|
|
Cipher
Labs RS31
|
CPU Cortex A53 Quad-core
1.3GHz
|
Android
gsw-connectbot.apk
|
|
|
Cipher
Labs RS51
|
Octa-core 1.8GHz
|
Android
8.0 with GMS
gsw-connectbot.apk
|
|
|
Cipher
Labs RK 25
|
Quad-core 1.4 GHz Cortex
A53
|
Android
gsw-connectbot.apk
|
Table 11 -Cipher Labs qualified
devices
|
Devices Qualified
with UTS
|
|
Device Type
|
Device Model
|
Device Type
|
Operating System
|
|
|
Juniper
Archer 3
|
1.2GHz quad-core ARM Cortex A9
i.MX6
|
Android
gsw-connectbot.apk
|
|
|
Juniper Mesa
3
|
Qualcomm® Snapdragon™
Octa-core Kryo™ 260
|
Android
gsw-connectbot.apk
|
|
|
Nautiz
X6
|
Qualcomm® Snapdragon 626 MSM8953 Pro,
8 cores 2.2 GHz
|
Android
gsw-connectbot.apk
|
|
|
Keyence
BT-AT700
|
Qualcomm Octa-core
|
Android
gsw-connectbot.apk
|
Table 12 – Nautiz X6 and Keyence
BTAT700 qualified devices
If your device is not in
the list above and it is an Android device the GSW ConnectBot will most likely
be your best choice. 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 33) 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.
|
|
Mobile Feature
Name
|
Brief
Description
|
|
1
|
Stay Connected
|
Automatically
attempts to reconnect when a session becomes disconnected
|
|
2
|
Allow Suspend
|
Power Saving
Feature
|
|
3
|
Beep Sound
|
Correct
Operation of Beep Sound
|
|
4
|
Menu Accelerators / Shortcuts
|
Function keys
provide quick access to common menu commands
|
|
5
|
Free Function Keys
|
Function Keys,
F1-F12 are freed (released) from operating system control and are available
for the application
|
|
6
|
Raster Font Selection
|
Additional Raster
fonts available - 9x16,10x12,10x13,12x16
|
|
7
|
Simplified Chinese font
|
GSW Mobile
Clients support Simplified Chinese Font GB (True Type)
|
|
8
|
Select Configuration
|
Several configurations
are allowed. This provides a quick way to select the desired configuration.
|
|
9
|
Portable Session Configuration
|
File format for
Session Configuration allows easy cloning of sessions
|
|
10
|
Last Active Session Memory
|
After a restart
the client returns to the last active session
|
|
11
|
No Scrollbars option
|
Save Space on Screen.
Especially useful on devices with small screens.
Also supported
on Pocket PC 2003 devices.
|
|
12
|
Automatic Logon
|
Automatically
logon without Host, Domain, Username, Password prompting
|
|
13
|
Keyboard Marcos
|
Remap Function and
Special Keys to send a sequence of characters.
|
|
14
|
Configuration and Application
Persistence
|
Save Mobile
Client Configuration Across Reboots
- Allows for ease
of configuration deployment to multiple devices
|
|
15
|
Toggle Status
& Task Bar display
|
Use View menu
item to enable or disable the display of the status bar and/or the task bar.
|
Table 13 - GSW Mobile CE .NET
4.2/5.0 Client Extended Features
Automatically attempts to reconnect as soon as a
session is disconnected. Operates as if the connect button was pressed.
Stay Connected is enabled by selecting the option Stay Connected.
Session|Settings|Session|Stay connected
To break out of the automatic
connection loop press
ctrl-shift-b
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 option Allow Suspend
Session|Settings|Session|Allow suspend
Beep sound –
Correct Operation
No configuration
is required.
In order to provide a more convenient
method of configuration for the administration the following accelerator keys
are available.
Note: The following Accelerators
are available for all CE .Net 4.2 devices.
F2 – Save Session Settings
F5 – File|Session Configurations …
F6 – Session|Connect
F7 – Session|Settings
F8 – File|Exit
The GSW SSH/Telnet mobile clients support Simplified
Chinese fonts. Follow the steps below to setup the GSW mobile client:
- GSW
Universal Terminal Server and GSW Mobile Clients must be V7.51 or higher.
- Install
the Simplified Chinese font GB (True Type) on the mobile device.
- Open
the GSW SSH/Telnet client on the mobile device and navigate to:
Sessions -> Settings
Select
the Font tab and select the GB font.
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 user’s 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.
File | Select Configuration …
Figure 31: Mobile Client Select Session
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 53).
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.
The No Scrollbars option is enabled by selecting the
option No scrollbars.
Session|Settings|Session|No scrollbars
Check
the “No
scrollbars”
box to eliminate scrollbars as shown below.
Figure 32: Mobile Client - No Scrollbars Option
Use the view menu item to toggle the display of either
the status bar and/or the task bar. Set this option just see the information
you need to see.
|
Figure 33: Windows CE - Choose
to view status and/or task bars. Neither enabled.
|
Figure 34: Just status bar is
enabled
|
|
|
|
|
Figure 35: Just taskbar enabled
|
Table 14: Both status and task
bar are enabled
|
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 the application does not require scroll bars.
Normally Scrollbars are enabled.
The No Scrollbars option is
enabled by selecting the option No scrollbars.
Session|Settings|Session|No scrollbars
Check
the “No
scrollbars”
box to eliminate scrollbars as shown below.
Figure 36: Mobile Client - No Scrollbars Option
Automatic
Logon for Mobile Clients
Set this option to enable the GSW Mobile client for
Automatic Logon. The GSW Server Side Automatic Logon configuration must also be
completed (See page 111 ).
Critical Note 1: Make sure that Automatic
Logon entries for GSW Mobile clients are made in the gs_auto.txt configuration file.
Critical Note 2: IP addresses configured for
Automatic Logon for GSW Clients must NOT overlap with IP Addresses configured
for Automatic Logon for 3rd party clients.
The Automatic Logon option is enabled by
selecting the option Automatic logon.
Session|SettDjsexton1
ings|Session|Automatic logon
Check the “Automatic logon” box to enable the client
for Automatic Logon as shown below.
Figure 37: Mobile Client – Automatic Logon Option
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. Macros are used for remapping
Function keys (F1 – F12) to keystroke sequences.
Macros definitions have the form:
Function
Key=Keystroke Sequence
Where
Function Key is F1 through F12
and
Keystroke Sequence follows the same format as the GSW Termination
strings (page
158).
The keys that can be remapped are
Function Keys: F1,F2,F3,F4,F5,F6,F7,F8,F9,F10,F11,F12
Configuration
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 (usually default.gswtc).
[Macros]
F1=shift-f,1,ENTER
F2=shift-f,2,ENTER
F3=shift-f,3,ENTER
F4=shift-f,4,ENTER
F5=shift-f,5,ENTER
F6=shift-f,6,ENTER
F7=shift-f,7,ENTER
F8=shift-f,8,ENTER
F9=shift-f,9,ENTER
F10=shift-f,1,0,ENTER
F11=shift-f,1,1,ENTER
F12=shift-f,1,2,ENTER
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 43 )
|
|
Mobile Feature
Name
|
Brief
Description
|
|
1
|
Keyboard Macros
|
Remap Function
and Special Keys to send a sequence of characters.
|
|
2
|
Free Function Keys
|
Function Key’s
(F1-F12) are freed (released) from Operating System control and are available
for the application.
|
|
3
|
Application Launch Bypass
|
Interoperation
with application launch utilities such as Intermec’s iLaunch.
|
|
4
|
Simplified Chinese font
|
GSW Mobile
Clients support Simplified Chinese Font GB (True Type).
|
Table 15 - GSW Mobile PPC 2003
and Windows Mobile 2003/WM5+ Client Extended Features
Keyboard Macros
GSW has provided Keyboard Macros for the GSW Mobile Clients for Windows Pocket PC 2003
and WM5/WM6+. They operate the same as described for the Windows CE .NET
4.2/5.0+ mobile clients.
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 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
is: 0 (disabled).
Simplified Chinese fonts are supported when using the
GSW Mobile Clients for Windows Pocket PC 2003/WM5/WM6+ (Windows Mobile). The
setup is the same as described
for the Windows CE .NET 4.2/5.0+ mobile clients.
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.
- GSW
Pocket PC 2003 Universal Mobile Clients:
Follow the instructions on page 56.
- GSW
Universal Mobile Clients for Windows CE .NET 4.2+
Follow the instructions below.
.
In brief, the steps are simply to configure the
device, save the configuration and move our .CAB files to a persistent folder.
Mobile Client Configuration
Persistence
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.
Mobile Client Application Persistence
The GSW Mobile Client application is available as a
.cab file, which is a compressed archive package definition format. The .cab
file location and name of the application is
|
Location (on your PC)
|
CAB File Name
|
|
C:\Program Files\Georgia
SoftWorks Universal Telnet and SSH Client for Windows CE ARM4\WCEG_4.ARMV4_G.CAB
|
|
C:\Program Files\Georgia SoftWorks
Universal Telnet and SSH Client for Windows CE ARM4I\WCEG_4I.ARMV4I_G.CAB
|
|
C:\Program Files\Georgia SoftWorks
Universal Telnet and SSH Client for Windows CE X86\WCEG_X86.INTEL_X86_G.CAB
|
Table 16
- GSW Mobile Client Application CAB File Location
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.
Mobile Client Persistence
Instructions
Once you have the GSW Mobile Client configuration set
for your implementation you should save the configuration.
Step 1: Install and run the GSW Mobile
Client
Step 2: Configure the GSW Mobile Client
as required for your environment
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.
\Program Files\GSW_Clnt\default.gswtc
The file below will
automatically be generated upon the Save command
\Program Files\GSW_Clnt\default.cab
Step 4: From within the
GSW Mobile Client, switch to ‘User Mode’ using the menu item
File|Security
Figure 38: Switch from Administrator to User Mode
Step 5: On the device
launch the File Manager and copy the configuration and application .cab files
\Program Files\GSW_Clnt\default.cab
\Program Files\GSW_Clnt\c753x.cab
to the Persistent CAB folder.
Figure 39: Note that the files are already marked as
Read Only.
Mark the files as Read
Only.
In this case the persistent CAB folder location is \FlashFX
Disk\CAB,
however the persistent folder is device manufacturer and model specific.
Step 6: Copy the
application cab file defined in the Application Persistence section (page 53) to the Persistence folder on
the device. Mark it as Read Only
Step 7: Now you should be
able to cold boot the device and the client should automatically launch with
the correct configuration.
PPC 2003 Configuration Persistence
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.
PPC 2003 Application Persistence
The GSW Mobile Client application is available as a .cab
file, which is a compressed archive package definition format. The .cab file
location and name of the application is
|
Location (on your PC)
|
CAB File Name
|
|
C:\Program Files\Georgia
SoftWorks Universal Telnet and SSH Client for PPC2003\CPPC2003.PPC2003_ARM.CAB
|
Table 17
- GSW PPC 2003 Mobile Client Application CAB File Location
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.
PPC 2003 Persistence
Instructions
Once you have the GSW Mobile Client configuration set
for your implementation you should save the configuration.
Step 1: Install and run the GSW Mobile Client
Step 2: Configure the GSW Mobile Client as
required for your environment
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 56) 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 Windows Client 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
and
System Main
Menu|Configuration Utility|Save to Flash
3.
Startup – Default Connection Settings
·
The file “\CK_FFS\Georgia
SoftWorks C753X\default.gswtc” is loaded on startup if found.
·
If the security level is ‘user’
then the GSW SSH/Telnet Client will attempt to connect.
4.
Application Protection
Use
the File|Security dialog as
described in the Application Protection
(page 70 ) section.
5.
Warm boot the device after you install the client. The GSW Mobile
Client will automatically launch.
6.
The GSW Mobile Client is also accessible via
System Main Menu|GSW Client
7.
How to disable the automatic launch of the TE2000 client
a.
Either delete or rename the file \Windows\StartUp\TE2000.lnk
b.
Run
System Main Menu|Configuration Utility|File
Backup
8.
BEEP Sound – Complete beep operation. Extended features available
for SAP - See below.
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.
Following are a few Tips
when installing the GSW SSH/Telnet Client for the above device running Windows
CE .NET Version 4.2+
1.
Persistence over a ‘Cold Reset’
After
initial installation, please run START | Shutdown on the device.
Shutdown
saves the device registry to persistent storage.
2.
Uses Standard
Accelerators and Shortcuts for all CE .NET 4.2 devices (page 44).
3.
Startup – Default Connection Settings
·
The file “\Application Data\Georgia SoftWorks
C753X\default.gswtc” is
loaded on startup if found.
·
If the security level is ‘user’
then the GSW SSH/Telnet Client will attempt to connect.
4.
Application Protection
Use the
File|Security dialog as described
in the Application Protection (page 70
) section.
5.
Warm boot or cold boot the device after you install the client.
The GSW Mobile Client will automatically launch.
6.
The GSW Mobile Client is also accessible through
'Program Files' and a Desktop shortcut
7.
How to disable the automatic launch of the TE2000 client
a.
Either delete or rename the file \Windows\StartUp\TE2000.lnk
8.
BEEP Sound – Complete beep operation.
Tips for PSION-TEKLOGIX WORKABOUT Pro, 7535 and 8525 devices
Following are a few Tips
when installing the GSW SSH/Telnet Client for the above devices running Windows
CE .NET Version 4.2+
1.
Persistence over a ‘Cold Reset’
By default,
the GSW Telnet Client is installed to a persistent directory. The directory is
\Flash Disk\Georgia SoftWorks C753X
·
User Fonts – Your fonts need to reside in two locations.
\Windows\Fonts
And ALSO
\Flash Disk\Georgia SoftWorks C753X
2.
Use Standard
Accelerators and Shortcuts for all CE .NET 4.2+ devices (page 44).
3.
Startup – Default Connection Settings
·
The file “\Flash
Disk\Georgia SoftWorks C753X\default.gswtc” is loaded on startup if found.
·
If the security level is ‘user’
then the GSW SSH/Telnet Client will attempt to connect.
4.
Additional Files
The setup program will install the file “\Flash Disk\StartUp\reinst.bat”.
Please
do not delete or modify this file as it is required for persistence and automatic
startup of the client.
5. Application
Protection
GSW
Telnet supports the security settings available on the Psion-Teklogix devices.
The settings are available via Start|Security
Following are a few Tips when installing the GSW SSH/Telnet
Client for the above devices running Windows CE .NET Version 4.2+
1. Persistence
over a ‘Cold Reset’
By default, the GSW Telnet
Client is installed to a persistent directory. The directory is
\Application\Georgia
SoftWorks C753X
·
User Fonts – Your fonts need to reside in two locations.
\Windows\Fonts
And ALSO
\Application\Georgia
SoftWorks C753X
2. Uses
Standard Accelerators and
Shortcuts for all CE .NET 4.2+ devices (page 44).
3. Startup
– Default Connection Settings
·
The file “\Application\Georgia
SoftWorks C753X\default.gswtc” is loaded on startup if found.
·
If the security level is ‘user’
then the GSW SSH/Telnet Client will attempt to connect.
4. Additional
Files
The setup
program will install the file “\Application\StartUp\reinst.bat”.
Please do not delete or modify this
file as it is required for persistence and automatic startup of the client.
5.
Application Protection
Use the File|Security dialog as described in the Application Protection (page 65)
section.
Following are a few Tips
when installing the GSW SSH/Telnet Client for the LXE MX3X running Windows CE
.NET Version 4.2+
Note: Please verify that you are running version MX3XGC4201C or later of the LXE
firmware. You can view the version on your device by
Start|Settings|Control Panel|About|Versions
1. Persistence
over a ‘Cold Reset’
By default,
the GSW Telnet Client is installed to a persistent directory. The directory is
\System\Georgia SoftWorks C753X
·
User Fonts – Your fonts need to reside in two locations.
\Windows\Fonts
And ALSO
\System\Georgia SoftWorks C753X
2.
Uses Standard
Accelerators and Shortcuts for all CE .NET 4.2+ devices (page 44).
3.
Startup – Default Connection Settings
·
The file “\System\Georgia
SoftWorks C753X\default.gswtc” is loaded on startup if found.
·
If the security level is ‘user’
then the GSW SSH/Telnet Client will attempt to connect.
4.
Additional Files
The setup program will install the file “\System\autoexec.bat”.
Please
do not delete or modify this file as it is required for persistence and
automatic startup of the client.
5. Application
Protection
The
LXE MX3X provides Applock application security software. The GSW SSH/Telnet
Mobile clients are compatible with Applock and may be launched from Applock.
In the
Applock configuration you must specify which application is to be launched and
you must specify a full path to the application. Please specify the following
path in the dialog.
\Windows\GSW_lnch.exe
Before
configuring the system for Applock, pre-configure all the settings (in particular
the default.gswtc file) and then
go to File|Security and
configure the security to the user level and press OK.
Following are a few Tips
when installing the GSW SSH/Telnet Client for the above device running Windows
CE .NET Version 4.2+
The PSC Falcon 4410 has
the capability for full application lockout. The steps for implementation of
this feature follows.
1. Application
Protection
Step 1: Run
gsce_4ig.exe
on your PC and install the GSW Universal Mobile Client for ARMV4I.
Step 2: Configure the GSW Mobile Client as
required for your environment
Step 3: When satisfied with the configuration from within
the GSW Mobile Client perform the menu item
File|Save
and save the settings in
\Program Files\GSW_Clnt\default.gswtc.
And this will automatically
generate the file
\Program
Files\GSW_Clnt\default.cab
Step 4: From
within the GSW Mobile Client, switch to ‘User Mode’ using the menu item
File|Security
Figure 40: Switch from Administrator to User Mode
Step 5: On the device launch the
File Manager and create the Folder
\FlashFX Disk\CAB
And copy the device files
\Program
Files\GSW_Clnt\default.cab
\Program
Files\GSW_Clnt\c753x.cab
to the folder created
above.
Figure 41:
Note that the files are already marked as Read Only.
Step 6: Copy the file
C:\Program
Files\Georgia SoftWorks Universal Telnet and SSH Client for Windows CE ARM4I\WCEG_4I.ARMV4I_G.CAB
From your PC (the
PC used in Step 1) to
\FlashFX Disk\CAB on
your Falcon 4410 device, and mark it Read Only
|
Figure 42: File copy from PC to Device
|
 Now, three (3) file exist in this folder.
 Mark file as Read Only
|
|
Step 7: On the device go to:
Start|Programs|Falcon Management|FDU Admin Tool
And set the configuration options as shown using the
different Tabs below.
|
Figure 43: Falcon 4410 Application Title
|
A. Make sure that the Enable Falcon Desktop
checkbox is checked.
|
|
   
Figure 44: Falcon 4410 Application Title
|
B.
Enter the Application Title
 C. Next Click on the ‘…’ button. When you click
the button, it opens up the File Selection dialog below.
|
|
D. Navigate to the
GSW_Lnch.exe in the folder \Program Files\GSW_Clnt Select the GSW_Lnch.exe
Click OK and the filename of the Executable is filled in.
|
Figure 45: File Selection Dialog
|
Next Select
the Win tab and make sure that the Show
Taskbar checkbox is clear.
|
Figure 46: Falcon Clear Win Tab Checkboxes
|
E. Select the Win Tab and
make sure that the Show Taskbar checkbox is clear.
F. Also make sure that the
Windows CE Desktop Enabled checkbox is clear.
|
Make sure the two checkboxes are clear.
Step 8: Cold boot the device.
The GSW Mobile Client
will automatically launch and connect after the boot.
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.
o
File|New, File|Open, File|Exit
o
Session|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.
Figure 47: GSW Mobile Client
Security Levels
Only the administrator
security level has access to these items.
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.
Figure 48: GSW Mobile Client Security
Level Selection
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.
·
Intermec CK30 / CK31
·
Intermec CV60
·
LXE M3X3
·
Psion-Teklogix 7535, Psion-Teklogix
8525
·
Symbol MC 9060G / MC9090G
·
PSC Falcon 4410
At certain times you may
encounter a scenario where your system needs to be rebuilt and you want to transfer
the GSW and its settings. This entails two steps.
1. Back
up the GSW UTS installation directory and all of its subdirectories.
2. Back
up the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\GS_Tnet\Parameters
If you are using the SSH Server
then you need to also back up the following registry key.
HKEY_LOCAL_MACHINE\SOFTWARE\GeorgiaSoftWorks\GSW_SSHD\Parameters
On 64-bit operating systems the key will be:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\GeorgiaSoftWorks\GSW_SSHD\Parameters
On the rebuilt system you will need to:
1. Restore
the GSW UTS Installation directory as on the original system.
2. Re-run
the GSW UTS setup program.
3. If
using the GSW SSH Server, re-run the GSW SSH SHIELD setup.
4. Restore
the registry keys that were backed up in step 2 above.
5. Re-register
the software using the standard registration procedure or install the Floating
license.
Note: The example below
is for the GSW Telnet Server however the same procedures apply to the GSW SSH Client
unless noted.
Follow these instructions to open the Georgia SoftWorks
Client window.
1. Click
the Start button at the bottom left corner of your screen.
2. Click
Programs
3. Move
the mouse cursor to "Georgia SoftWorks UTS" entry.
4. Click
to the right where you see "GS Telnet Client"
At this point, the Client window is open and you will get
the host prompt (Figure 49 ).
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).
Figure 49: Host Prompt
After the Host is found
you will see the Georgia SoftWorks Telnet Server connection banner.
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.
At this prompt you should enter a valid Windows
login id.
Example:
Login: JohnSmith
Figure 50: Logon Prompt
Below is a screen shot of the GSW SSH Connection Banner.
Figure 51: SSH Connection Banner
This is the password
associated with the Login ID. It will not be displayed when typed.
Figure 52: Password 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
282. The Georgia SoftWorks Telnet Client Command line options are described
next.
Figure 53: Domain Prompt
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.
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 110)
|
-b |
Answerback Text passed to the Server and stored in the Environment
variable gwtn_answerback. See page 82 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 93 on setting up encryption. |
-cCertificateName |
SSH client only. Specifies the Certificate name for certificate-based authentication. This feature is integrated with Microsoft Certificate Stores. |
-dDomain |
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. |
-hHostname |
This specifies host name to connect to. |
-Hheartbeat Time |
Specifies our client-side heartbeat. You need that parameter for the session cleanup! See page 156. |
-i |
Enable SSH client to use FIPS 140-2 when connecting to SSH server. Note: SSH Server must be installed and FIPS must be Enabled. Only valid with SSH client. |
-I |
SSH client only. Activates public key authentication by specifying the path to the private key file. -Ipath_to_private_key_file |
-k |
Disables the mouse in the telnet or SSH session |
-m |
SSH client only. Specifies Single Sign-On through Kerberos over GSSAPI |
-n |
SSH client only. Specifies Single Sign-On through NTLM over GSSAPI |
-pPassword |
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 226 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 261 ) 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). |
-uUserName |
Specifies the name of the User
|
-U |
Enable Unicode character processing for input and output. See page 252. |
-vPathXMLFile |
Enable Vangard Voice, specifies path to Vangard XML file See page 314. |
-xClient Caption String |
The User has additional control over the caption text displayed in the Title bar of 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 allowed in the Client Caption string. See example on next page for further details |
-XClient Title Bar String |
SSH and Telnet can change the Title Bar content. Note: This clears the Title Bar and displays the Title Bar String. It overrides the “-x” Client Caption String. |
-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 User’s Manual. |
+Ciphers= |
SSH client only - The list of Ciphers provided to the server for Cipher negotiation |
+KexAlgorithms= |
SSH client only – The list of Key Exchange algorithms provided to the server for Key Exchange Algorithm negotiation |
+HostKeyAlgorithms= |
SSH client only – The list of Host Key Algorithms provided to the server for Host Key Algorithm negotiation |
+Macs= |
SSH client only – The list of Message Authentication Codes (MACs) provided to the server for Message Authentication Code negotiation |
Table 18 - GSW Telnet and SSH
Client Command Line Options
Example
- Georgia SoftWorks Client Caption String
-xClient Caption String
The User has additional control over the caption text
displayed in the title Bar of 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
section of the title bar 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).
Figure 54: Client Title Bar
Caption
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.
@echo off
:start
@if exist once1.bat do call once1.bat
@if exist once1.bat do del once1.bat
@gs_clnt.exe
@if errorlevel 2 goto copy
@exit
:copy
@copy gs_clnt.new gs_clnt.exe > gsnull.txt
@if exist once2.bat do call once2.bat
@if exist once2.bat do del once2.bat
@goto start
The
line @gs_clnt.exe
is the line
that launches the Georgia SoftWorks Telnet Client. For SSH the client
name is gs_ssh.exe.
Command Line Parameters will be added to this line in the batch
file.
In most cases the GS_SClnt.bat/GS_SSH.bat files will be
modified to provide the parameters in a transparent manner to the user.
Example - Georgia
SoftWorks SSH2/Telnet Client Command Line Options
Host: soloman
Heartbeat: 150
UserName: johndoe
Password: fastest
Domain: Use
the default domain.
Encryption: Yes
Client
Caption: System1
The Command Line Parameters used are:
-H150
-hsoloman -ujohndoe -c -pfastest -d. -xSystem1
Note: The last dot is for the
default domain
And thus the GS_SClnt.bat
file will be modified as shown below adding the command line parameters.
@echo
off
:start
@if
exist once1.bat do call once1.bat
@if
exist once1.bat do del once1.bat
@gs_clnt.exe -H150 -hsoloman -ujohndoe -c -pfastest
-d. -xSystem1
@if
errorlevel 2 goto copy
@exit
:copy
@copy
gs_clnt.new gs_clnt.exe > gsnull.txt
@if
exist once2.bat do call once2.bat
@if
exist once2.bat do del once2.bat
@goto start
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 –z command 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.
Figure 55: Automatic GSW Client Upgrade
Initiated
Once the transfer of
the client is complete you will see a screen similar to the one below displayed
requesting a key to be pressed to continue.
Figure 56: Automatic Client
Upgrade – Session Restart
After the session is restarted you will be prompted again
for the Host. Proceed and log on as usual with the proper GSW Client version
for the GSW UTS Server for which you are connected.
Figure 57: Automatic Client
Upgrade - Host Prompt
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.
|
|
Use
the GSW GUI Configuration Tool – See Client Control page 408
Or
use legacy style below
|
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
408).
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:
set gwtn_show_console_title=Y
in the Logon Script for a particular user.
NOTE: No spaces are allowed when setting
environment variables.
For example:
set
gwtn_show_console_title=Y is correct
set
gwtn_show_console_title = Y is
not correct.
|
|
Use
the GSW GUI Configuration Tool – See Client
Control page 408
Or
use legacy style below
|
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
218).
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:
set gwtn_clnt_no_x=Y
in the Logon Script for
a particular user.
NOTE: No spaces
are allowed when setting environment variables.
For example:
set
gwtn_clnt_no_x=Y is correct
set
gwtn_clnt_no_x = Y is not
correct.
The User can pass a text string (up to 20 characters) from
the client to the server when connecting. The received text string is stored the
environment gwtn_answerback. The
command-line option
-bText
specifies a text string that is passed to the server. For Example,
the command line parameter
-bdelta187
would be available on the server in the environment
variable gwtn_answerback. The example
below shows both the client MAC address and the Answerback text.
Figure 58: Answerback and MAC
Address environment variable
GSW Mobile Device
(Windows Mobile and Windows CE .NET V4.2/5.0+) client’s configuration.
Below is a screen shot
of the GSW Mobile Device configuration for the Answerback text.
Figure 59: GSW PPC Client Answerback
text configuration
Desktop 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. 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.
and
Keystroke Sequence follows the same format as the GSW Termination
strings (page
158).
The keys that can be remapped are
Function Keys: F1,F2,F3,F4,F5,F6,F7,F8,F9,F10,F11,F12
Configuration
The keyboard macros are defined in the session
configuration files. The session configuration file for the desktop client is GSWClnt.ini.
For mobile clients the file name is up to the
administrator as long as the extension is .gswtc.
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 GSWClnt.ini.
[Macros]
F1=shift-f,1,ENTER
F2=shift-f,2,ENTER
F3=shift-f,3,ENTER
F4=shift-f,4,ENTER
F5=shift-f,5,ENTER
F6=shift-f,6,ENTER
F7=shift-f,7,ENTER
F8=shift-f,8,ENTER
F9=shift-f,9,ENTER
F10=shift-f,1,0,ENTER
F11=shift-f,1,1,ENTER
F12=shift-f,1,2,ENTER
F1=(1:0:0)SHIFT-S, SHIFT-F, 1
F2=shift-f,2,ENTER
F3=shift-f,3,ENTER
F4=shift-f,4,ENTER
F5=shift-f,5,ENTER
F6=shift-f,6,ENTER
F7=shift-f,7,ENTER
F8=shift-f,8,ENTER
F9=shift-f,9,ENTER
F10=shift-f,1,0,ENTER
F11=shift-f,1,1,ENTER
F12=shift-f,1,2,ENTER
Terminating a session
Type exit at the
client window prompt (command prompt) followed by the ENTER key and the session
will terminate and the window will clear and then close. If you are unable to
get to the command prompt then you should use the client self-termination (see
below).
The client user can terminate
their session by entering Ctrl-X
followed by F9.
In situations where the
client user believes that the application has hung or is not responding, the user
can self-terminate the session without getting the system administrator involved.
Please note that the
Team Services Hotkey (see page 143 ) must be enabled. It is enabled by default.
If it is disabled then the ability for a client to self-terminate is also
disabled.
Please see the section
on Emulations for descriptions in connecting to
the Georgia SoftWorks UTS for Windows using 3rd party clients (page 166).
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 92 )
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 109)
Advanced proprietary
algorithms, optimizations and compressions provide for the fastest SSH2/Telnet Server for Windows on the market.
GSW Team Services – (see page 117)
Allow mobile users to
quickly share resources to improve productivity while keeping cost down without
requiring system administrator / IT intervention.
Failure Detection/Recovery Pack – (see page 149Error! Bookmark not defined.)
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 163)
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 166)
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 187)
The Georgia SoftWorks
UTS provides the most powerful, needed and useful features on the market.
Compatibility Pack –
(see page 244)
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 244)
Utility Pack – (see
page 259)
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.
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
|
Security Pack
|
Configurable
|
GSW Windows
Clients
|
3rd Party Client
|
|
Encrypted Data Stream - Telnet Server Specific
|
Yes
|
Yes
|
No
|
|
Encrypted Data Stream –
Strong 128 Bit*
- Telnet
Server Specific
|
Yes
|
Yes
|
No
|
|
Encryption - Enable or
Disable based on IP Address – Telnet Specific
|
Yes
|
Yes
|
|
|
SSH Strong Encryption -
AES-256
(End to End – Authentication and Data Stream)
- GSW
SSH Server
|
Yes
|
Yes
|
Yes
|
|
Encrypted Logon Session - Telnet Server Specific
|
Yes
|
Yes
|
No
|
|
FIPS 140-2 Compliant Option – SSH Server
|
Yes
|
Yes
|
No
|
|
AES-256 Encrypted Logon
Session – SSH Server
|
Yes
|
Yes
|
Yes
|
|
Connection Restrictions
|
|
|
|
|
-
User Id
|
Yes
|
Yes
|
Yes
|
|
-
IP Address
|
Yes
|
Yes
|
Yes
|
|
-
3rd Party Clients
|
Yes
|
Yes
|
Yes
|
|
-
Connection count
|
Yes
|
Yes
|
Yes
|
|
-
Connection count by User ID
|
Yes
|
Yes
|
Yes
|
|
-
Connection count by IP Address
|
Yes
|
Yes
|
Yes
|
|
Encrypted Sessions Only – Telnet
Server
|
Yes
|
Yes
|
No
|
|
Encrypted Sessions Only – SSH
Server
|
Yes
|
Yes
|
Yes
|
|
Specific
application
|
Yes
|
Yes
|
Yes
|
|
Expired Password Handling
|
N/A
|
Yes
|
Yes
|
|
Integrated with Windows
Security
|
N/A
|
Yes
|
Yes
|
|
|
|
|
|
Table 19 - Security Pack
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 parameter -c
should be passed when invoking the Georgia SoftWorks Windows
Telnet Client. This can be passed from the command line via the following
command:
gs_clnt.exe
-c
The shortcut may be modified to pass Data Stream Encryption
parameter.
An environment variable must be set on either a Global or
Per User basis to activate Data Stream Encryption.
|
|
Use
the GSW GUI Configuration Tool – Global 370
or Per User 408
Or
use legacy style below
|
The environment variable for the complete data stream
encryption is:
gwtn_encrypt_session
in the Logon Script for
a particular user (or the Global Logon Script for all users.).
NOTE: No spaces are allowed when setting environment
variables.
For example: To Activate Data Stream Encryption the
following line should be present in the logon script.
set
gwtn_encrypt_session=1 is correct
set
gwtn_encrypt_session = 1 is
not correct
For example: To De-activate Data Stream Encryption the following
line should be present in the logon script.
set gwtn_encrypt_session=0 is
correct
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:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\GS_Tnet\Parameters\EnableEncryption
The default value is 0(That is disabled.) The value 1
enables the ability to use Encryption. The value 0 disables the ability to use
encryption.
This is how to change the registry key for Encryption.
Note: You must be on the Windows
system that the Georgia SoftWorks Telnet Server is installed. However, you may
connect to the Windows Registry from a remote location.
1. Click
the Start button at the bottom left corner of your screen.
2. Click
RUN
3. Type
REGEDIT
4. Click
OK
5. Select
Registry Key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\GS_Tnet\Parameters\EnableEncryption
6. Select
the menu item Edit and then click on Modify
7. Enter
the new value for the EnableEncryption and click OK
The new EnableEncryption
value will take effect for all new connections.
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.
Georgia SoftWorks Telnet
Server SE: 128-bit Strong Complete Data Stream Encryption.
Some
applications require extremely strong Complete Data Stream Encryption. For
these customers, Georgia SoftWorks offers their Telnet Server in a Strong Encryption
(SE) version. This utilizes a full 128-bit data stream RSA encryption
algorithm.
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/2019, 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. The Data Stream Encryption Client-side
parameter must also be used when configuring encryption based on IP addresses
as described on page 93.
When configured the
settings in the gs_ipenc.txt file
overrides the normal encryption registry and environment settings.
The order of the fields
in the gs_ipenc.txt
file is as follows:
|
Field
|
Description
|
|
IP Address
|
The IP address/IP Address
Range of the client
|
|
Enable or Disable Encryption
Value
|
0=Disable, 1=Enable
|
Table 20
– Encryption based on IP Address - gs_ipenc.txt
when using GSW Clients
For example, the
following entry in the file:
168.92.55.4 0
disables logon and
session encryption for GSW Telnet Clients connecting from 168.92.55.4
Another Example:
205.20.63.* 1
enables logon and
session encryption for GSW Telnet Clients connecting from 205.20.63.*
NOTE1: The IP
address must start in the first column. IP Address Ranges and wildcards are allowed.
Please see the file gs_ipenc.txt for further details.
NOTE2: For
security reasons it is prudent to set the file gs_ipenc.txt to allow only SYSTEM – Read Access. NO other
accounts should be allowed to access this file.
NOTE3: This feature
is for power users that have a thorough understanding of the network and system
security issues and topics.
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.
Figure 60: Session Administrator
view FIPS 140-2 sessions
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 restrict access to the SSH2/Telnet
Server based on a variety of criteria advancing the level of security.
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. 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 371
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.
Following are example thosts
files.
Example - IP Restriction: restrict
certain Hosts from connecting.
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.
Example
- Restriction: allow only specific Hosts to
connect
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.25
ACME 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 219.
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:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\GS_Tnet\Parameters\EnableRFC854Clients
The default value is
1(That is enabled.) The value 1 enables the ability for connection from all
telnet/SSH clients. The value 0 restricts connection to the Georgia SoftWorks
Telnet/SSH client.
This is how to change
the registry key for 3rd Party Client Restriction.
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.
1.
Click the Start button at the bottom left corner of your screen.
2.
Click RUN
3.
Type REGEDIT
4.
Click OK
5.
Select Registry Key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\GS_Tnet\Parameters\EnableRFC854Clients
6.
Select the menu item Edit and then click on Modify
7.
Enter the new value for the EnableRFC854Clients
and click OK
The new value will take
effect for all new connections.
|
|
Use
the GSW GUI Configuration Tool – Set Max Sessions 372
Or
use legacy style below
|
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:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\GS_Tnet\Parameters\MaxSessions
The default value is 0xffffffff (That is disabled). Other
values limit the number of connections allowed to the value chosen.
This is how to change
the registry key to limit the number of connections.
Note: You must be on
the Windows system that the Georgia SoftWorks Universal Terminal Server is
installed. However, you may connect to the Windows
Registry from a remote location.
1.
Click the Start button at the bottom left corner of your screen.
2.
Click RUN
3.
Type REGEDIT
4.
Click OK
5.
Select Registry Key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\GS_Tnet\Parameters\MaxSessions
6.
Select the menu item Edit and then click on Modify
7. Enter
the new value for the MaxSessions
and click OK
The new value will take
effect for all new connections.
|
|
Use
the GSW GUI Configuration Tool – Set Max Sessions 372
Or
use legacy style below
|
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.
The rules are simple for setting up the gs_l_usr.txt file.
-
It is a text file
-
The # character is the comment character
-
Each entry must start in the first column.
-
Each entry consists of the User ID and the Count
-
The User ID and the Count are separated by a single space
Following is an example for using the gs_l_usr.txt file.
Example – USER ID Count Restriction
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.
The Information for
each company is:
|
Company Name
|
User Id Assigned to Company
|
Number of Concurrent Sessions
|
|
BigBrain Intelligence
|
bbrain
|
12
|
|
Vigorous Investments
|
viginv
|
3
|
|
Sweet Apple Suppliers
|
sweeta
|
3
|
|
Warehouse Storage
|
warstore
|
3
|
|
Sure Shipping Co
|
surship
|
3
|
|
Wireless Security
|
Wiresec
|
12
|
Figure 61: Security: Restriction
based on User ID Count.
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.
|
|
Use
the GSW GUI Configuration Tool – Set Max Sessions 372
Or
use legacy style below
|
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.
How to set up IP Address Count Restriction.
Notice the file in the GSW UTS installation directory:
gs_l_ip.txt
The file must reside in the Georgia SoftWorks Windows
Universal Terminal Server installation directory.
NOTE: The System account must have permission
to read the gs_l_ip.txt file.
The file gs_l_ip.txt
is used for configuration of the IP Address Count Restrictions.
The rules are simple for setting up the gs_l_ip.txt file.
-
It is a text file.
-
The # character is the comment character.
-
Each entry must start in the first column.
-
Each entry consists of the IP Address (or IP Address Range) and
the Count.
-
The IP Address and the Count are separated by a single space.
Following is an example for using the gs_l_ip.txt file.
Example – IP ADDRESS Count Restriction
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.) |
205.20.63.0 Through 205.20.63.255 |
25 |
|
|
|
|
Figure 62: Security: Restriction
based on Count. from IP Address
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.
|
|
Use
the GSW GUI Configuration Tool – Telnet Encryption see page 370
Or
use legacy style below
|
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:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\GS_Tnet\Parameters\RequireEnctyptedSession
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.
1.
Click the Start button at the bottom left corner of your screen.
2.
Click RUN
3.
Type REGEDIT
4.
Click OK
5.
Select Registry Key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\GS_Tnet\Parameters\RequireEncryptedSession
6. Select
the menu item Edit and then click on Modify
7. Enter
the new value for the RequireEncryptedSession
and click OK
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.
|
Performance Pack
|
Configurable
|
Georgia
SoftWorks Client
|
3rd
Party Client
|
|
Fast,
Fast, Fast!
|
|
Yes
|
Yes
|
|
Compression
for slow speeds
|
N/A
|
Yes
|
No
|
|
Slow
Link, Internet Support
|
N/A
|
Yes
|
Yes
|
|
Proprietary
performance algorithms
|
N/A
|
Yes
|
Yes
|
|
Proprietary
code optimizations
|
N/A
|
Yes
|
Yes
|
|
DOSBOSS
- MS
DOS application performance booster!
|
Yes
|
Yes
|
Yes
|
|
Automatic
Logon
|
Yes
|
Yes
|
Yes
(page 183)
|
|
GSW
UTS x64 native 64-Bit Software
|
N/A
|
N/A
|
N/A
|
|
RF
DTIO Interface
|
Yes
|
Yes
|
Yes
|
|
|
|
|
|
Table 21
- Performance Pack
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.
The Georgia SoftWorks
Universal Terminal Server for Windows compresses data to increase the overall
throughput of data. Incredible performance optimizations are utilized
when using the Georgia SoftWorks SSH2/Telnet
Clients.
Many access the host
system via slow dialup links or by the Internet. Significant performance
optimizations are realized when using any SSH2/Telnet
client.
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!
NOTE: DOSBoss will
only run on 32-bit platforms.
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)
Examples:
DOSBoss /c5 /s ' Set time
slices to release to 5, dump statistics
DOSBoss /r /s ' uninstall the DOSBoss,
dump statistics.
DOSBoss /h ' display the
help message
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 149) 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 but it is important to remember which files are used for each
client type.
Note: An IP address cannot be associated
with both a GSW Client
and a Third-Party Telnet Client. No overlap
between IP Address ranges defined in the gs_auto.txt and gs_logon.txt is allowed. Unpredictable
results will occur.
|
|
Use
the GSW GUI Configuration Tool – Automatic Logon see page 368
Or
use legacy style below
|
For correct operation
of the AutoLogon feature when using the Georgia SoftWorks SSH2/Telnet Client two steps must occur.
First, the Georgia
SoftWorks Telnet/SSH Client must be enabled for automatic logon.
·
GSW Desktop Clients – Automatic Logon is enabled using the
command line parameter –
when initiating the client (See page 77).
·
GSW Windows Mobile Clients – Automatic Logon is enabled by
checking the Autologon checkbox on the Session|Settings|Session
menu options. (see page 49)
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.
The order of the fields
in the gs_auto.txt
file is as follows:
|
Field
|
Description
|
|
IP Address
|
The IP address of the client
|
|
Domain
|
Specify the dot ‘.’ character
if no domain is used.
|
|
User Name
|
The User ID for the
connection
|
|
Password
|
The Password
|
Table 22 – Automatic Logon Specifications gs_auto.txt when using GSW 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 the gs_auto.txt and gs_logon.txt
is 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.
|
|
Use
the GSW GUI Configuration Tool – Automatic Logon see page 368
Or
use legacy style below
|
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 149) 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.
The order of the fields
in the gs_logon.txt
file is as follows:
|
Field
|
Description
|
|
IP Address
|
The IP address of the telnet
client
|
|
Domain
|
Specify the dot ‘.’
character if no domain is used.
|
|
User Name
|
The User ID for the
connection
|
|
Password
|
The Password
|
Table 23
- Automatic Logon Specifications gs_logon.txt
when using 3rd Party 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 the gs_logon.txt and gs_auto.txt
is 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.
Automatic
Logon requires Server-Side Configuration and Client-Side Configuration for GSW Clients.
|
Server-Side
Configuration
|
|
|
Automatic Logon
Configuration File on Server
|
|
|
GSW Windows Client
|
Third Party Client
|
|
|
|
|
|
Edit
specific Server File that contains Automatic Logon Information
|
gs_auto.txt
|
gs_logon.txt
|
|
|
|
|
Table 24 - Automatic Logon Configuration
Files
Client-Side Configuration
for Automatic Logon
|
Client-Side
Configuration
|
|
|
GSW Desktop Client
|
GSW Mobile Client
|
Third Party
Telnet Client
|
|
|
None Required
|
|
|
Add the command line parameter
-a when
initiating the client (page 77). This tells the client not to send logon
information to the server.
|
 Check
the Box in the configuration options screen (page 49).
|
|
|
Example in the GS_SClnt.bat
file
@echo off
:start
@if exist once1.bat
do call once1.bat
@if exist
once1.bat do del once1.bat
@gs_clnt.exe –a
if errorlevel 2
goto copy
@exit
:copy
@copy gs_clnt.new
gs_clnt.exe > gsnull.txt
@if exist
once2.bat do call once2.bat
@if exist once2.bat
do del once2.bat
@goto start
|
 
|
|
Table 25
- Automatic Logon Client-Side Configuration
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.
Figure 63: Extraordinary High
Session Count (Actual Screen Shot)
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 4999 connections.
This
particular test was performed on a modest 2 GHz dual processor Xeon with 6 GB
RAM running Windows 2008 Server. We have observed over 2400 sessions on a
modest 2 GHz dual processor Xeon with 2 GB RAM running Windows XP!
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 application
and 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
Please visit the GSW website for more
information on the GSW RF DTIO Engine.
Team Services is
about collaboration and efficiency
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.
- Empowers
Mobile Device User – session management operations initiated from the mobile
device. This is a breakthrough feature!
- No
system administrator intervention required.
- Works
with GSW and 3rd party clients.
- 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 multiple Teams 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
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.
3.
Team member
(originator) starts Team Service operation.
4.
Team member
(originator) identifies 2nd team member's session, selects and
completes operation.
The Recover Team
Service operation general procedural flow is:
1.
Team
member initiates the Team Service Recover option.
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 145 for more information on the Session
Administrator and Team Services.
Enter Team Services Tasks by typing Ctrl-x (see page
121 for more details) or the configured hot key. The Team Services Tasks menu
is show below.
Figure 64: Team Services Tasks Menu
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
65.
|
Accept Mode Display
|
|
Session Selection Display
|
|
Figure 65:
Accept Mode Display
|
On the left we see the display after a user has entered
Accept Mode for Team Service Share. Note that the Session Id is s5.
On the right we see the display after the Team Service operation
Swap is entered. A list of all sessions available for a Swap is displayed.
Note: Only sessions in Accept Swap mode are displayed. So, there will be no confusion swapping with
someone that did not consent to a swap.
|
Figure 66:
Session Selection Display
|
The associated Team
Service operation displays a list of sessions available for that operation
similar to Figure 66. 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.
|
|
|
2nd Team Member
|
Originating Team Member
|
|
Team Services Operation
|
Description
|
Accept
Mode
|
Operation
|
|
Transfer
|
Transfers
your session to another device
|
F1
|
F2
|
|
Swap
|
Transfers
your session to another device
Transfers the
other session to your device
|
F3
|
F4
|
|
|
|
Share
|
One session
is shared by two devices
|
F5
|
F6
|
|
|
|
|
|
|
Recover
|
Recovers a
suspended session to your device
|
n/a
|
F7
|
|
My TS Info
|
Display
Session ID, User Name, IP Address
|
n/a
|
F8
|
|
Reserved
|
|
n/a
|
F9
|
|
Cancel
|
Cancel Team
Services Operation, Exit Menu
|
n/a
|
F10
|
|
Enter Team
Services
|
Open Team Services
Menu
|
Configurable hot key
|
Table 26 - Teams Services
Function Keys
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 143.
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 298)
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.
|
|
Table 27 - Team Services Tasks Menu
Abbreviations
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.
|
Accept Transfer Mode
Display
|
|
Abbreviated Accept Transfer
Mode Display
|
|
|
An unabbreviated "Waiting for transfer" dialog
is shown on the left.
On the right is simply the session id (s5) and
"Waiting..."
|
|
Table 28 - Team Services Accept
Mode Abbreviations
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.
o If 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.
o Each 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.
o On 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).
|
Accept Transfer Mode
Display
|
Abbreviated Select
Session Display
|
|
Figure 67: Unabbreviated Select Session
|
Figure 68: Abbreviated Select Session Page 1 of 2
|
Figure 69: Abbreviated Select Session Page 2 of 2
|
Table 29- Team Services - Select
Session Display
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.
Figure 70: Before Team Service - TRANSFER
|
SAM
|
BARRY
|
|
Figure 71:
Enters Team Services (Ctrl-x)
|
Figure 72:
Accept Transfer Mode (F1).
Note session id is s5
|
Figure 73:
Enters Team Services (Ctrl-x)
& presses F2
|
Figure 74:
Session s5 is not listed on
page 1 so Barry presses F2.
|
|
Barry asks Sam if he
can Transfer to his device. Sam consents and enters Team Services (Figure 71) and presses F1 to enter Accept
Transfer mode. Sam’s display shows he is session id “s5” (Figure
72).
Barry enters Team
Services on his truck mount device (Figure 73) and presses F2 to initiate the Transfer
operation. Figure 74 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
75). He presses 1 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.
|
Figure 75:
Presses 1 to select session s5
|
|
|
|
|
The TS Transfer example is described below.
Notice that Barry is now
on the mobile device and is still using his original session. He did not have
to log off or get administrative assistance.
Figure 76: After Team Service - TRANSFER
The session Sam was
using is terminated during the process, freeing Sam to take his lunch break.
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.
Figure 77: Before Team Service -SWAP
Doug asks Andy if they
can Swap devices. Andy consents and enters Team Services and presses F3 to
enter Accept Swap mode. Andy’s display shows he is session id “s5”.
|
ANDY
|
|
DOUG
|
|
Figure 78: Enter Team Services (Ctrl-x)
|
Figure 79: Accept Swap Mode (F3) Note the session id is s5
|
Figure 80:
Enter Team Services (Ctrl-x)
& press F4
|
Figure 81:
Selects 2 to Swap with s5
|
|
|
|
|
|
Doug enters Team
Services on his truck mount device and presses F4 to initiate the Swap operation.
Figure 81 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.
Figure 82: After Team Service - SWAP
If in Andy and Doug
want their original devices back, they can just perform a TS Swap again!
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 195) 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.
Figure 83: Before Team Service -SHARE
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
84) 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
85).
|
Tom's Truck Mount Device
|
|
Wireless Mobile Device
|
|
Figure 84:
Enters Team Services (Ctrl-x)
|
Figure 85:
Accept Share Mode (F5) Note session id is s5
|
Figure 86:
Enters Team Services (Ctrl-x)
& presses F6
|
Figure 87:
Selects 2 to Share session id s5
|
|
|
|
|
|
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
86). The list of sessions in Accept Share mode is shown (Figure
87). 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 88.
Figure 88:
After Team Service - SHARE
Undo Share
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.
The truck mount device continues in its session. This is shown in Figure
89.
Figure 89:
Undoing the Share
This can be useful when
a Team Member is working and needs to temporally join another team member's
session (for assistance, support, quality assurance, etc.) and then needs to
resume his work.
Note: If you exit
the session (from either device) the truck mount session is closed and the
mobile device is returned to its original session as shown below.
Figure 90: Exit
typed in Share
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.
Figure 91: Before Team Service - RECOVER
Figure 92: After Accident but before Team Service
-RECOVER
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 mobile device display
shows a list of suspended sessions (Figure 94).
|
Wireless Mobile
Device
|
|
|
Figure 93: Enters Team Services (Ctrl-x)
|
Figure 94:
List of Suspended Sessions (F7)
and select session.
|
Figure 95: After Team Service - RECOVER
|
|
|
|
Amos is able to
identify his session as s0 by
the User Id and the IP Address. Amos presses number 0 to recover session 0
(s0). Amos can continue his work
exactly where he left off.
Often it is useful to obtain
Session Information about your current session. Team Services "Session
Info" can be viewed using the F8
key.
Figure 96: Team Services - Session Information
The session information displayed consists of:
The
Session Id is a unique number assigned to the session by GSW Team Services.
The
IP Address of the client device.
The User Id is displayed in the bottom right corner
of the screen. In Figure 96 the User Id is "london"
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 143).
To enter the hot key - depress Ctrl
then x, and then release
the keys. The Team Services Tasks menu is displayed.
Figure 97: Team Services Tasks Menu
|
Function Key
|
Team Service Operation
|
|
|
F1
|
Accept Transfer Mode
|
|
|
|
F2
|
|
Transfer
|
|
F3
|
Accept Swap Mode
|
|
|
|
F4
|
|
Swap
|
|
F5
|
Accept Share Mode
|
|
|
|
F6
|
|
Share
|
|
F7
|
Recover
|
|
F8
|
My Team Service
Information
|
|
F9
|
Terminate
my session
|
|
F10
|
Cancel Team
Service Operation
|
|
Configured hot key
|
Opens Team Services Menu
|
Table 30- Team Services Menu
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.
The order of the fields
in the tsgroups.txt
file is as follows:
|
Field
|
Description
|
|
Team Name
|
Unique name assigned to a
team
|
|
User Domain Name
|
Domain Name. Exactly as
specified during logon
|
|
User Logon Name
|
Logon name. Exactly as
specified during logon.
|
Table 31
– Team Services - Strict Teams
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.
Example - Strict Teams - Multiple
companies in an ASP environment
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:
acme_sprockets,acme_server_1,acme_user_a
#Add a line for
each Team Members at Acme Sprockets
acme_sprockets,acme_server_1,acme_user_z
army_complex1,army_intelligence,army_user_1
#Add a line for
each Team Members at Army Complex
army_complex1,army_intelligence,army_user_1000
auto_factory,sports_cars_7,emerson
#Add a line for
each Team Members at the Automotive Factory
auto_factory,sports_cars_7,elliot
train_station,public_trans_rr,train_point_1
#Add a line for
each Team Members at the train station
train_station,public_trans_rr,train_point_400
|
|
Use
the GSW GUI Configuration Tool – Team Services Global see page 379 , Per User - 414
Or
use legacy style below
|
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.
You must enable Team Services for operation.
The registry key location is:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\GS_Tnet\Parameters\
The parameters, types and values are noted below:
|
Team Service
|
Registry Parameter
|
Type
|
Values
|
|
Transfer
|
TSEnableTransfer
|
DWORD
|
0=disable 1=enable
|
|
Swap
|
TSEnableSwap
|
DWORD
|
0=disable 1=enable
|
|
Share
|
TSEnableShare
|
DWORD
|
0=disable 1=enable
|
|
Recovery
|
TSEnableRecovery
|
DWORD
|
0=disable 1=enable
|
|
Other
Team Service Configuration
|
|
|
|
|
|
TSHotKeyCtrl
|
DWORD
|
0=disable 1=enable
|
|
Enter TS hot key
|
TSHotKeyVK
|
DWORD
|
See Section on page 143
|
|
Left Justify TS
Dialog/Text
|
TSLeftJustify
|
DWORD
|
0=disable 1=enable
|
Table 32 - Team Services
Registry Parameters Sizes and Values
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.
The environment variables for Team Services are shown
below.
|
Team Service
|
Environment Variable
|
Values
|
|
Transfer
|
gwtn_ts_enable_transfer
|
'Y' or 'N', or 'y' or 'n'
|
|
Swap
|
gwtn_ts_enable_swap
|
'Y' or 'N', or 'y' or 'n'
|
|
Share
|
gwtn_ts_enable_share
|
'Y' or 'N', or 'y' or 'n'
|
|
Recovery
|
gwtn_ts_enable_recovery
|
'Y' or 'N', or 'y' or 'n'
|
|
Other
Team Service Configuration
|
|
|
|
Enter TS hot key
|
|
|
|
Left Justify
TS Dialog/Text
|
gwtn_ts_left_justify
|
'Y' or 'N', or 'y' or 'n'
|
Table 33 - Team Services
Environment Variables
.
Team Services Recovery
Team Services Recovery works
together with Session Saver and thus Session Saver must be configured for Team
Services Recovery to operate.
The variable TSEnableRecovery is a registry key
value. This registry key sets the default behavior for all users.
0 disables
Team Services Recovery for all users.
1
enables Team Services Recovery for all users.
The key is: TSEnableRecovery
DWORD
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\GS_Tnet\Parameters\TSEnableRecovery
An environment variable
may be set on either a Global or Per User basis to override the default
configuration specified by the Registry parameters described above.
The environment variable
for Team Services Recovery is:
gwtn_ts_enable_recovery
Possible values are Y
(or 'N', or 'y' or 'n')
This allows you to have
a set of users that can have different Team Services privileges than specified
in the Registry key value.
NOTE: No spaces are
allowed when setting environment variables.
For example: To enable
Team Services Recovery the following line should be present in the user's logon
script.
set
gwtn_ts_enable_recovery=Y is correct
set
gwtn_ts_enable_recovery = Y is not correct
The variable TSEnableTransfer is a registry key value.
This registry key sets the default behavior for all users.
0 disables
Team Services Transfer for all users.
1
enables Team Services Transfer for all users.
The key is: TSEnableTransfer
DWORD
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\GS_Tnet\Parameters\TSEnableTransfer
An environment variable
may be set on either a Global or Per User basis to override the default
configuration specified by the Registry parameters described above.
The environment variable for Team Services Transfer is:
gwtn_ts_enable_transfer
Possible values are Y
(or 'N', or 'y' or 'n')
This allows you to have a set of users that can have
different Team Services privileges than specified in the Registry key value.
NOTE: No spaces are allowed when setting
environment variables.
For example: To enable Team Services Transfer the
following line should be present in the user's logon script.
set
gwtn_ts_enable_transfer=Y is correct
set gwtn_ts_enable_transfer = Y is not correct
The variable TSEnableSwap is a registry key value.
This registry key sets the default behavior for all users.
0 disables
Team Services Swap for all users.
1
enables Team Services Swap for all users.
The key is: TSEnableSwap
DWORD
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\GS_Tnet\Parameters\TSEnableSwap
An environment variable may be set on either a
Global or Per User basis to override the default configuration specified
by the Registry parameters described above.
The environment variable for Team Services Swap is:
gwtn_ts_enable_swap
Possible values are Y (or 'N',
or 'y' or 'n')
This allows you to have
a set of users that can have different Team Services privileges than specified
in the Registry key value.
NOTE: No spaces
are allowed when setting environment variables.
For example: To enable
Team Services Swap the following line should be present in the user's logon
script.
set
gwtn_ts_enable_swap=Y is correct
set gwtn_ts_enable_swap = Y is not correct
The variable TSEnableShare is a registry key
value. This registry key sets the default behavior for all users.
0 disables Team Services Share for all
users.
1 enables Team Services Share for all
users.
The key is: TSEnableShare DWORD
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\GS_Tnet\Parameters\TSEnableShare
An environment variable may be set on either a
Global or Per User basis to override the default configuration specified
by the Registry parameters described above.
The environment
variable for Team Services Share is:
gwtn_ts_enable_share
Possible values are Y (or 'N',
or 'y' or 'n')
This allows you to have
a set of users that can have different Team Services privileges than specified
in the Registry key value.
NOTE: No spaces
are allowed when setting environment variables.
For example: To enable
Team Services Share the following line should be present in the user's logon
script.
set gwtn_ts_enable_share=Y is correct
set gwtn_ts_enable_share = Y is not correct
|
|
Use
the GSW GUI Configuration Tool – Team Services see page 379
Or
use legacy style below
|
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
98. This can be corrected using Left Justify as shown in Figure
99.
|
Figure 98:
Left Justify Disabled
|
Notice when
Team Services
Left Justify
is enabled the
dialog box
and the text at
the bottom
are in the
viewable display.
|
