2017 at GSW

Windows Explorer style interface allowing provisioning and configuration
management. Familiar to use operations such as copy, paste, rename, delete, export, import are applied
to configurations on a user or system basis. Create templates and quickly view summary configuration data.

TEAM SERVICES provides your
mobile device users a breakthrough in Telnet/SSH2
technology that shatters all prior usability and
efficiency standards by allowing unprecedented user
collaboration. Now mobile device users are
empowered to share resources, transfer, swap, share and
recover dropped sessions. All from the mobile device, no
system administrator necessary. All operations can be
performed in under 60 seconds.

Video Overviews

Team Services the first feature
set to offer Video overviews. We are excited to provide
additional methods to meet customer expectations. Visit
the
GSW Video Channel!

Request a Webinar

Want to know more about UTS, RC MDMS or GSWBrowse? Request a Webinar. Give us a call or use our
contact form and request a webinar.

Restrict Connection based on Connection Count By UserID

Examples: User ID Count Restriction

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

Note: The system account must have permission to read 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 are example gs_l_usr.txtfile.

Example 1: 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 only 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

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

sunship 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