Managing network licenses has always been a challenge for network administrators. Each year, administrators prepare their software budgets by trying to determine the number of network and application licenses required. This task is often frustrating because of the complexity of software licensing. After administrators complete their budgets, they often find their budgets are inadequate because of changes in their company. In response to customer requests, Novell has changed its licensing model and made enhancements to its licensing utilities to simplify licensing management tasks.
Beginning with NetWare 6, NetWare uses a User Access License (UAL) model. With this model, you purchase licenses for the total number of eDirectory User objects that will log in to the network. When a User object logs in to the network, it obtains a license unit that allows them to access network services at any time, from any workstation. That license unit is reserved for that user. Users can access as many NetWare servers as they need while consuming only one license. If the user does not log in for more than 90 days, then the license is automatically released and made available to the next user that needs it.
In the User Access Model, non-User objects like Printers and ZENworks® do not consume user licenses.
In previous licensing implementations, users were granted access to network services on a server basis. This meant users consumed a license on each server that they logged in to. This is known as the Server Connection License (SCL) model. Earlier versions of NetWare (NetWare 5 and earlier) used the SCL model, where you purchased licenses for the total concurrent users on each NetWare server.
The Server Connection License model had drawbacks. It was difficult to plan and deploy, customers had to pay for multiple connections for the same person, and there was no easy way to count and audit licenses.
The following table shows the differences between the Server Connection Licensing Model and the User Access Licensing model.
Table 1-1 Licensing Model Comparison
|
Feature |
User Access Licensing Model |
Server Connection Licensing Model |
|---|---|---|
|
License packaging |
Server and user license certificates available together or separately. |
Server and user license contained in same license envelope. |
|
Search |
Search starts at the user’s context and goes up the tree. |
Search starts at the server’s context and goes up the tree. |
|
Context of licenses |
Install license certificates relative to users’ contexts. |
Install license certificates relative to servers’ contexts. |
|
License released when user logs out |
No. |
Yes. |
|
Connection-oriented objects (like Printer and ZENworks objects) consume a user or connection license |
No. |
Yes, until the current Support Pack is installed. To download a Support Pack, see Novell Support. |
The User Access Licensing Model is easier to plan and deploy because you just count the number of eDirectory User objects, customers pay for only one user license, and network usage can be monitored.
User Access Licensing can coexist on a network with servers that are using Server Connection licenses. Depending on the resources being accessed, a user might consume a User Access License and a Server Connection License simultaneously.
For example, a company has six NetWare 5.1 servers, each with a 50-user license. The company has 50 network users. The company upgrades four of the six servers to NetWare. When a user logs in to the network, he will consume one User Access License Unit, which will let him log in to any number of NetWare 6 or later servers. For each NetWare 5 server he logs in to, he will also consume a NetWare 5.1 Server Connection License unit, the same as he always has.
In order for all 50 users to log in to the four NetWare servers, the administrator has to purchase just 50 user licenses.
Since managing network usage is now a network administrator’s priority, Novell has released a metering tool that lets you see the total number of licenses being consumed and when a user last accessed the network. See Metering Network and Product Usage for more information.
The User Access Licensing model uses server licenses and user licenses. These licenses are separate and distinct files.
During the NetWare server installation, you install a server license. Each server in the tree should have a server license associated with it. The server licenses should be installed at or above the eDirectory container where the Server object resides. One server license can license up to unlimited NetWare servers in the same container or subcontainers. The same server license can be installed multiple times in the same eDirectory tree, but only once in a container.
The server license determines the type of user licenses to be consumed. For example, if you install a NetWare Demo server license, NLS will look for NetWare Demo user licenses to be consumed. If a NetWare Demo user license is not found, users will not be allowed access.
This is important to understand when changing licenses. For example, if you install NetWare Demo licenses (both server and user) and later change to a volume licensing agreement like MLA, you need to install the server and user licenses for the MLA and then delete the demo license for both the server and user.
For more information, see Section 2.4, Guidelines for Installing License Certificates.
User licenses are not assigned to servers. They are installed in the eDirectory tree in the same container as or in a container above the User objects that will consume the licenses. You must have enough user licenses for each user that will authenticate to eDirectory. For more information, see Section 2.4, Guidelines for Installing License Certificates.
User licenses are no longer issued by Novell. The maximum user connections allowed are specified in a paper license agreement with Novell.