  How users connect to the server
Users can connect to your FirstClass server and access its features in a variety of ways such as over a network using TCP/IP, IPX, or AppleTalk, over the telephone system using modems over the Internet using a variety of Internet protocols, or over the telephone using FirstClass Voice Services if you are a FirstClass Unified Communications customer.
Taking this into consideration, you should remember a few things:
• These communication methods are all optional. You only need to configure your system for the methods you actually intend to use.
• Internet Services requires TCP/IP. If you do not install TCP/IP you will not be able to run Internet Services and users will not be able to access your server over the Internet. For informa-tion about Internet Services, see FirstClass Internet Services Administrator’ s Guide .
• Regular users can have the option to work offline using FirstClass Personal. Click here for complete details.
• Voice Services requires additional hardware and software to enable users to connect to the server by telephone. These are explained in detail in the Voice Services section of our online help system.
Understanding sessions
When users log into your FirstClass server, they use sessions. Each login is one session. The session type a user uses depends how she logs in. If a user uses a modem to access the server, she will use a modem session. All other access methods use network sessions.
Network sessions
Network sessions are used by every user who logs into your system, except by those who log in using a modem. Any user logged into your FirstClass server will use a network session for as long as they are connected. Network sessions are configured by you and are limited by the following factors:
• your hardware capacity
• the amount of memory you have
• the type of licence you purchased:
Regular licenses allow up to 250 concurrent sessions. If you require more network sessions, you should have the MP option.
For information about configuring network sessions, see FirstClass Tools Reference.
Modem sessions
The number of modem sessions is simply the number of modems available. A modem session is the way in which you configure the modem to work with the FirstClass server. When a user logs in remotely through a modem configured on the FirstClass server, he will be using a modem session for as long as he is connected to the modem.
For information about configuring modem sessions, see FirstClass Tools Reference.
Understanding how users connect
There are two classes of user: Regular and Remote. When you add a new user, you define the class on the User Information form. Click here for information about adding users.
Both Regular and Remote users can connect using any protocol. Access method does not affect the class of user or the type of user license required. A Regular user logging in from home with a modem will be accepted as a Regular user and will use a regular user license. A Remote user logging in over a local network will be accepted as a Remote user and will use a session license. No matter how you connect, you use the licensing appropriate to your class.
Regular users
Users configured as Regular users require regular user licenses. You can only add as many Regular users as you have regular user licenses. When using FirstClass in a business environment, employees must be Regular users. When using FirstClass in an education environment, students and staff must be Regular users. You can buy additional Regular user licenses at any time.
Remote users
Users configured as Remote users require session licenses. You can add as many Remote users as you wish, but the number that can log in concurrently is limited by the number of session licenses you have. Session licenses are shared by Remote users and you can buy more at any time. When using FirstClass in a business environment, customers must be Remote users. When using FirstClass in an education environment, parents must be Remote users.
For information on all license purchases, contact your FirstClass sales representative.
For licensing instructions, see FirstClass Tools Reference.
How classes of users are treated differently
Now that you understand sessions, classes of users, and user licenses, we can look at how Regular and Remote users are treated slightly differently:
A Regular user can always log in if a network session is available. (Remember, a Regular user has a regular user license that was purchased specifically for him, and the number of network sessions is limited by the level of licensing you purchased (regular or MP option), and your hardware.)
A Remote user can only log in if a network session is available and there is an unused session license available. (Remember, a Remote user shares a number of session licenses with all other Remote users, and the number of network sessions is limited by the level of licensing you purchased (regular or MP option), and your hardware.)
Consider the following scenarios:
Scenario 1 (Business)
• You have 200 employees who have regular licenses and are defined as Regular users on their User Information forms.
• You have 5000 customers who are defined as Remote users on their User Information forms.
• You have 30 session licenses.
• You have 200 network sessions defined.
Under this scenario, you could have the following possible situations:
• All 200 of your employees are logged in. No customers will be able to log in since all network sessions are in use.
• 30 customers are logged in. Only 170 employees will be able to connect.
• 20 customers are logged in. Only 180 employees will be able to connect.
• 150 employees are logged in. Only 30 customers will be able to connect. Even though there will be network sessions available, the customers (Remote users) can only connect if a session license is available and there are only 30 of those.
Scenario 2 (Education)
• You have 50 teachers and staff and 1000 students who have regular licenses and are defined as Regular users on their User Information forms.
• You have 2000 parents who are defined as Remote users on their User Information forms.
• You have 30 session licenses.
• You have 200 network sessions defined.
Under this scenario, you could have the following possible situations:
• All 50 of your teachers and staff are logged in, and 150 students are logged in. No parents will be able to log in since all network sessions are in use.
• 30 parents are logged in. Only 170 teachers, staff or students will be able to connect.
• 20 parents are logged in. Only 180 teachers, staff and students will be able to connect.
• 150 teachers, staff and students are logged in. Only 30 parents will be able to connect. Even though there will be network sessions available, the parents (Remote users) can only connect if a session license is available and there are only 30 of those.
We will use an analogy to explain this concept. Consider your system as a power bar:
Regular user licenses are like two-pronged plugs. When you buy a new license, you get a plug to connect to your server.
 Remote users are like three-pronged plugs. Your server comes with an unlimited supply of these plugs, but you need an adapter to fit them into your power bar.
 The outlets in the power bar represent the network sessions. You can increase the number of sessions by adding power bars. The number you can add is limited by the capacity of your electrical system – or in the case of your server, the amount of memory and disk space you have. In the following example, you have Regular users (two-pronged plugs) plugged into your network sessions (outlets on the power bar).
 In the next example, you have purchased some session licenses. This converts some of your network sessions (outlets) so they can support Remote or Regular users (three-pronged or two-pronged plugs). Note that Remote users can only take as many slots as you have session licenses.
 Even if only two Regular users (two-pronged plugs) were connected, the Remote users could still only use the three licenses (three-pronged outlets) available to them. However, the Regular users can use any network session (outlet).
|