Licensing mvBase

mvBase licensing reflects the number of users connected to mvBase, not necessarily the number of connections.

NOTE	For mvBase licensing to function properly when using thin client devices, the host names for those devices need to be able to be resolved into an IP address. Otherwise, each connection will consume a user license.

COM Ports

Each COM port connected to and configured for use with mvBase consumes a license.

Printers

Printer models, neither of which consume an mvBase license:

Windows printer model	Mapped Windows printers in mvBase do not consume a license.
Serial printer model	When the Serial Printer field in the Port Info section of the Ports dialog box (which is displayed by selecting the Configure... button) is selected, no license is consumed. This is known as an output only port and cannot be used for serial ports to which a terminal is attached.

Telnets and mvTerm

mvBase 3.1 has been enhanced to support multiple user connections for a single mvBase user license for both mvTerm and telnet clients (connecting to the local mvBase Workstation component) on Windows Terminal Services. Prior to mvBase 3.1, each mvTerm session or telnet client connection caused 1 mvBase user license to be consumed. The licensing change for mvBase 3.1 to support multiple user connections also changes the licensing for mvTerm sessions and telnet clients (connecting to the local mvBase Workstation component) on systems that are not running Windows Terminal Services.

With or without Windows Terminal Services:

An mvTerm client connecting to an mvBase Server will now get 6 mvTerm sessions for 1 mvBase user license when connecting to the same mvBase server. mvTerm sessions are counted across all mvTerm instances on a single client. Sessions can be in the same mvTerm instance or across multiple instances of mvTerm. After the initial 6 mvTerm sessions, each new mvTerm session will consume an additional mvBase user license.

A telnet client connecting to an mvBase Workstation component running on the same system as the telnet client will now get 6 telnet client connections for 1 mvBase user license. After the initial 6 telnet client connections, each new telnet client connection will consume an additional mvBase user license.

mvBase user licenses consumed by mvTerm and telnet clients, connecting to an mvBase Workstation on the same system as the client, are handled independently of each other. For example, 6 mvTerm sessions and 6 telnet clients will consume 2 mvBase user licenses. Prior to mvBase 3.1, opening the same number of connections on Windows Terminal Services would have consumed 12 licenses.

There has been no change to mvBase user license consumption when using a telnet client to connect to an mvBase Workstation component running on another machine. Each telnet client connection will consume 1 user license.