No special upgrading procedures are required for installing a new version of the license server.

• If the system is running the integrated license server, it is automatically upgraded when you configure the new version of the file server.
• If the system is running the standalone license server, you can install the new version of the license server. You need not upgrade the file server. Upgrade the license server by simply installing and configuring it as described in your Server Installation and Configuration Guide. No additional upgrade procedures are required for standalone license servers.

The file server requires that clients accessing file and print services be appropriately licensed. To meet this requirement, one of the following must be true:

• The client must have acquired a client-based license previous to connecting to the file server.
• A server-based license must be available for each client connecting to a file server without a client-based license.

In either case, the license required to access each version of the file server is listed in Table 1-1, File Server Licenses.

Table 1-1 File Server Licenses

To access this file server...	The client needs this Client Access license...
PATHWORKS for OpenVMS (Advanced Server)	One of the following: PWLMXXXCA06.00 PWLMXXXCA07.02
Advanced Server for OpenVMS	PWLMXXXCA07.02

These licenses can be configured to be used as either client-based licenses or as server-based licenses.

Clients currently using client-based licenses to access PATHWORKS V6 for OpenVMS (Advanced Server) servers need not be changed. These clients will continue to access PATHWORKS for OpenVMS (Advanced Server) servers using their client-based license. However, to access the Advanced Server V7.2 for OpenVMS, they must obtain a new client-based license or a server-based license must be available for them on the file server system.

1.2.1 Server-Based License Management

Server-based licensing grants a specific number of clients connected to a file server (on a first-come, first-served basis) the right to use server software on a single server and allows clients access to file and print services resident on the server.

1.2.1.1 When to Use Server-Based License Management

Server-based licensing is best suited for clients that need access to file and print services on a single server, or for a large number of clients that need occasional access to file and print services. Server-based licenses:

• Are consumed only for the duration of the connection.
• Are consumed only by clients without appropriate client-based licenses.
• Require no license software on the client.
• Use one server-based license for each server session.

On a file server that is not running the license server, Client Access licenses loaded into LMF are automatically used as server-based licenses. From a license management point of view, this is the simplest form of management and does not require use of the PATHWORKS client licensing software, or performing management tasks with the License Manager. License management consists of loading the appropriate Client Access PAKs information into LMF on the file server node.

When a client connects to the file server, one server-based license is consumed and the client is granted access to the file server. If there are no server-based licenses available when the client requests a connection to the file server, the connection request is denied.

After a server-based license has been used to grant a client access to a file server, the client is licensed to access resources on that server until the client disconnects from the file server.

When the client disconnects from the file server, the license assigned to that client is released, the number of available server-based licenses is incremented, and the license becomes available for another client.

1.2.1.3 Server-Based License Management in an OpenVMS Cluster

When using server-based licenses for access to file and print services in an OpenVMS cluster environment, Compaq Computer Corporation recommends that clients connect to the cluster using the Advanced Server cluster alias, if this option is available. Clients connecting using the alias consume one server-based license. Clients connecting directly to specific cluster members consume one server-based license for each connection to a different cluster member.

A client can map multiple drives and printers from a single server while consuming a single server-based license.

1.2.2 Client-Based License Management

A client-based license is assigned on a per-workstation basis. A client-based license for accessing OpenVMS file servers allows a client to access multiple file servers with the single license. Client-based licenses are managed using LMF, the license server, and the License Manager.

After a client-based license has been assigned to a client, the license applies only to that client until it is revoked or released. After a license has been revoked, it is available for assignment by the license server. To revoke a client license, use the License Manager.

A client-based license PAK is loaded in the LMF database on the system running the license server. The license server assigns a client-based license upon request for a license by a client. After the client receives the license, it is stored on the client.

1.2.2.1 How Client-Based License Management Operates

License management for client-based licenses consists of these types of client activities:

• Obtaining licenses from a license server when first started after configuring Advanced Server license management.
• Verifying licenses with the license server each time the client boots after the license has been assigned.
• Presenting license information during the process of accessing file servers.

These interactions require no specific actions on the part of a user once a client is configured to use client-based license management.

1.2.3 Combining Server-Based and Client-Based License Management

You can use both server-based and client-based license management together on one file server, allowing you greater flexibility.

Appropriate client-based licensing assures access to file servers. Clients that do not have client-based licenses may access a file server if sufficient server-based license capacity exists.

1.2.3.1 How Combined License Management Operates

In a combined-license environment, licenses are loaded in the LMF database on the system running the file server and the license server. Client Access licenses loaded into LMF are automatically loaded by the license server. When the licenses are first loaded by the license server, they are allocated to the Default license group to be used as client-based licenses. The License Manager allows you to allocate any number of these licenses to the Server-Based license group so that they can be used for server-based licensing. The remaining licenses, those in the Default group, or allocated to other license groups, are managed as client-based licenses.

1.3 License Management Tasks

The Advanced Server licensing software includes the License Manager. This software provides a user interface for system administrators to manage licenses.

If the licensing environment consists of only server-based licensing, it is not necessary to use the License Manager. When the licensing environment includes client-based licensing, or a combination of client-based and server based licensing, the License Manager is an invaluable tool for managing the licensing software.

The tasks you perform with the License Manager include:

• Manage PATHWORKS client software licenses, as well as Advanced Server client-based licenses.
• Create and manage license groups that allow you to organize client-based licenses into subsets called license groups, or simply groups. After you organize licenses into separate groups, licenses in a particular group are provided only to clients that identify themselves as members of the designated groups.
  For example, you could define three groups called Finance, Engineering, and Sales. You could then place the number of licenses issued to a specific organization into the groups bearing the organization's name. This ensures that their members can always acquire the licenses issued to them.

• Set alert levels that provide log entries in the license server log file when your supply of available client-based licenses goes below the set level. Use this feature on a per-product basis and/or per group basis.
• View the status of the client-based licenses that have been assigned.
• Revoke client licenses.
• Specify which license server events to log in the license server log file so that you can obtain a better understanding of client license related activity.
• Add and remove product licenses from the license services database.
• Enable and disable the license server.
• Generate reports of licenses assigned to clients.

License management can be nearly transparent to both system administrators and users. However, the License Manager provides optional capabilities that allow you to configure your server in a way that best supports your computing environment. This configuration may include client-based licensing, or a combination of client-based and server-based licensing.

This chapter describes how to set up the Advanced Server for server-based licensing, for client-based licensing and for a combination of client-based and server-based licensing. It also provides a set of examples of licensing setup. This information is presented in the following sections:

• Section 2.1, Setting Up Server-Based License Management, describes how to configure server-based licensing.
• Section 2.2, Setting Up Client-Based License Management, describes how to configure client-based licensing.
• Section 2.3, Setting Up Combined Client-Based and Server-Based License Management, describes how to configure the license management to support both server-based and client-based licensing.
• Section 2.4, Examples of Advanced Server License Management, provides examples of license management configurations.
• Section 2.5, Upgrading Client Licenses, describes procedures for upgrading client licenses.

The simplest form of license management is a configuration that supports only server-based licenses. Use the following steps to configure your Advanced Server to support server-based licensing:

1. Register and load the license PAKs using the License Management Facility (LMF) on the system where you will also be installing and running the file server software. For information on the LMF database, see the OpenVMS License Management Utility Manual.
2. Install, configure, and run the file server software.

If no client-based licensing is required, you are finished. You should not configure the license server to run on this system.

2.2 Setting Up Client-Based License Management

For a configuration that supports client-based licensing, there are additional steps required for setting up the system. This configuration requires the use of the license server and loading client software.

Follow these steps to support client-based licenses:

1. Identify the system to be used as the license server system.
2. Register and load the related PAKs in the LMF database on the system chosen as the license server. For information on the LMF database, see the OpenVMS License Management Utility Manual.
3. Install and configure the license server software using the normal installation and configuration process for the server. You can install the license server software either on the same system as a file server, or on a different system, as a standalone license server. The license server normally puts only a very small additional load on a system. For more information on how to load and configure license servers, see your Server Installation and Configuration Guide.
4. Start the license server. For information about how to start the server, see your Server Installation and Configuration Guide.
5. Using the License Manager, create any desired user-defined license groups and allocate licenses to these license groups. By default, all Client Access licenses will be client-based licenses in the default group.
6. Install and configure the PATHWORKS client licensing software on clients that will be using client-based licenses:
   • For clients using PATHWORKS client software (for example, PATHWORKS for Windows 95, or PATHWORKS 32), the client configuration procedure includes all the software and components necessary for clients to fully participate in the Advanced Server license management process.
     Depending on configuration or licensing needs, additional configuration steps might be required. Refer to your PATHWORKS client product documentation for more information.
   • For non-PATHWORKS clients using client-based licensing, the PATHWORKS client licensing software must be loaded on the client before it can participate in the license management process. For details, see the README.TXT file provided in the PWUTIL share on the file server.
7. Restart the network on the client. After the network restart is complete, clients can find a license server and acquire the required license.

For a configuration that supports both client-based and server-based licensing, you must use the License Manager to specify which licenses are to be used as server-based and which are to be used as client-based.

Follow these steps to configure the license server to support both client-based and server-based licensing:

1. Identify the file server system to be used as the license server.
2. Register and load the related PAKs in the LMF database on the system chosen as the license server. See the OpenVMS License Management Utility Manual for more information about how to load PAKs in the LMF database.
3. Install and configure the Advanced Server software using the normal installation and configuration process for the server. For more information about how to install and configure license servers, see your Server Installation and Configuration Guide.
4. Start the file server. See your Server Installation and Configuration Guide By default, all licenses will be client-based licenses.
5. Use the License Manager to configure the server-based licenses required. Use the License Manager to allocate the desired number of server-based licenses from the Default group to the Server-Based group. Licenses allocated to the server-based license group are reserved for use as server-based licenses and can not be assigned to clients by the license server.
6. Install and configure the client software on clients that will be using client-based licenses:
   • For clients using PATHWORKS client software (for example, PATHWORKS for Windows 95, or PATHWORKS 32), the client configuration procedure includes all the software and components necessary for clients to fully participate in the license management process.
     Depending on configuration or licensing needs, additional configuration steps might be required. Refer to your PATHWORKS client product documentation for information.
   • For non-PATHWORKS clients, license management software must be loaded on the client before it can participate in the Advanced Server license management process. For details, see the README.TXT file provided with the Advanced Server license management software for clients.

For more information on how to configure server-based licenses, refer to Section 4.6, Performing License Group Tasks.

2.4 Examples of Advanced Server License Management

The following examples provide step-by-step instructions for using Advanced Server licensing software and PAKs.

Setting Up Client-Based Licensing in a LAN

Configuration:

• The file server is running Advanced Server V7.2 for OpenVMS in a LAN. The license server is on the file server system.
• Clients have Microsoft Windows NT or Windows for Workgroups software already installed.

Components:

• Advanced Server V7.2 for OpenVMS media and documentation kit.
• A PAK for 750 Advanced Server V7.2 Client Access (CA) licenses (PWLMXXXCA07.02).

Procedure:

Step	Action
1.	Register and load PAKs into the License Management Facility (LMF) on the system that will run the license server. Follow the instructions provided in the OpenVMS Guide to Software License Management.
2.	Install and configure Advanced Server for OpenVMS software on one or more systems following the instructions found in the Advanced Server for OpenVMS Server Installation and Configuration Guide. Make sure you run the license server when configuring the Advanced Server on the node that will run the license server.
3.	Load PATHWORKS client license software on the clients and configure them as described in Chapter 5, Configuring Client Software. Clients are running Microsoft LAN Manager software and can access the file servers.
4.	Start the Advanced Server on the node where the license server is enabled. Using the License Manager, optionally create license groups and allocate licenses to each client group as described in Chapter 4, Managing Licenses on the OpenVMS Platform.
5.	Restart the network software on the newly configured clients.

Setting Up Combined Client-Based and Server-Based Licensing in a WAN

The following example demonstrates how to set up a license server to support client-based and server-based licensing in a WAN.

Configuration:

• The file server is running PATHWORKS V6 for OpenVMS (Advanced Server) and the license server is running on the file server system.
• Some clients are running PATHWORKS 32 client software.
• Some clients are running Windows 95 and Windows NT client software.
• Some clients are using client-based licensing.
• Some clients are using server-based licensing.

Components:

• PATHWORKS V6 for OpenVMS (Advanced Server) media kit and documentation.
• PATHWORKS 32 media kit and documentation.
• A PAK for 125 PATHWORKS V6 for OpenVMS (Advanced Server) Client Access (CA) licenses (PWLMXXXCA06.00).
• A PAK for PATHWORKS client software (PWXXWINAT07.01).

Procedure:

Step	Action
1.	Choose a system to run the license server. On the license server system, register and load PAKs into the License Management Facility (LMF). Follow the instructions provided by the OpenVMS License Management Utility Manual.
2.	Install and configure PATHWORKS V6 for OpenVMS (Advanced Server) software on the file server system following the instructions found in the PATHWORKS for OpenVMS (Advanced Server) Server Installation and Configuration Guide. Make sure you run the license server when configuring the PATHWORKS for OpenVMS (Advanced Server) software on the node that will run the license server.
3.	Appropriately install and configure the client software. Refer to Chapter 5, Configuring Client Software, for information and procedures.
4.	Restart the network software on the newly configured clients.
5.	Start the license server and the file server.
6.	Use the License Manager to create license groups. Allocate sufficient licenses to the Server-Based group to support server-based licensing.

Clients requesting assignment of a client-based license will obtain client-based licenses and others will use server-based licenses.

Setting up a V6 Server to Allow Clients to Request PATHWORKS V5 for OpenVMS (LAN Manager) Licenses

The following example demonstrates how to configure the license server so that clients can use PATHWORKS V5 for OpenVMS (LAN Manager) licenses.

Configuration:

• The file server is already running PATHWORKS V5 for OpenVMS (LAN Manager). The license server is not running on the file server system.
• A license server is running standalone using PATHWORKS V5 for OpenVMS (LAN Manager) software, which will be upgraded to use PATHWORKS V6.0B for OpenVMS (Advanced Server) software.
• Clients are using PATHWORKS V6.0 for DOS and Windows software. They have PATHWORKS V6.0 for DOS and Windows CCS licenses (PWLMDOSCC06.00).

Components:

• PATHWORKS V5 for OpenVMS (LAN Manager) media and documentation kit (already installed on both the file server system and the standalone license server system).
• PATHWORKS V6.0B for OpenVMS (Advanced Server) media and documentation kit.
• PATHWORKS V6.0 for DOS and Windows media and documentation kit.
• A PAK for 500 PATHWORKS V6.0 for DOS and Windows (LAN Manager) CCS licenses (PWLMDOSCC06.00) already registered and loaded on the standalone license server system.

Procedure:

Step	Action
1.	Upgrade the standalone license server software by installing and configuring the PATHWORKS V6.0B for OpenVMS (Advanced Server) software on the license server system. During the installation procedure, specify that you do not want to install the PATHWORKS V6.0B for OpenVMS (Advanced Server). Then specify that you do want to install the standalone license server software.
2.	Start the license server. Licenses that were previously served by the license server running the PATHWORKS V5 for OpenVMS (LAN Manager) software will continue to be available and be served using the PATHWORKS V6.0B software. In addition, if the client access licenses (PWLMXXXCA06.00) are purchased, they can be registered and loaded on the license server system and be served to clients requesting them.

Using Server-Based Licensing in a LAN or WAN

The following example demonstrates how to set up server-based licensing in a LAN or WAN.

Configuration:

• The file server is running PATHWORKS V6 for OpenVMS (Advanced Server).
• The license server is not running on the same system that the file server is running on.
• Clients have Microsoft Redirector software already installed.
• All clients use PATHWORKS V6 for OpenVMS (Advanced Server) Client Access (CA) licenses (PWXXXCA06.00) as server-based licenses.

Components:

• PATHWORKS V6 for OpenVMS (Advanced Server) media and documentation kit.
• A PAK for 180 PATHWORKS V6 for OpenVMS (Advanced Server) Client Access (CA) licenses (PWXXXCA06.00).

Procedure:

Step	Action
1.	Register and load the PAKs in the License Management Facility (LMF) on the system where the Advanced Server will be used.
2.	Install, configure, and run the PATHWORKS for OpenVMS (Advanced Server) software. Do not configure the license server software for this system.