Solved

License Services

Posted on 1998-08-19
1
401 Views
Last Modified: 2013-12-23
I would like to know somebody would have a documentation about License Services: " Everything what would I have of knowing and did I never have courage of asking " Anybody it could help me? Thanks in advance.
0
Comment
Question by:inhesma
1 Comment
 
LVL 3

Accepted Solution

by:
omb earned 100 total points
Comment Utility
If I have understood your question correctly, the following bits should help you.

Licence Services...
===================

Configuration
-------------
 
When you install or upgrade a server or a license-aware application, you
select the license mode.
 
If you select the Per Seat mode, you may specify the Master Server and the
Replication Frequency (if you work in a domain, all the domain servers use
the PDC Master Server definition).
 
The Master Server will centralize all license data for your organization:
 
 - Purchase licenses history (updated with License Manager utility).
 
 - Client access usage (replicated by all servers to the Master Server at
   each specified replication time).
 
Client Definition and Usage
---------------------------
 
A Per Seat server logs all client connections and replicates this data to
the Master Server.
 
The Master Server gathers all the client information. Each new client
consumes one license (even if this client works with several servers). If
no more licenses are available, the License Logging Service on the Master
Server logs an Event ID 201 in the local application log file.
 
With Per Seat licensing, a client access license applies to a specific
computer. After a computer has a client access license assigned to it, any
user of that computer can access any Windows NT Server product on the
network. Using the Per Seat license mode allows an unlimited number of
computers with client access licenses to connect to each server.
 
Configuration files
-------------------
 
The license service uses the following files to store license data:
 
 - Purchase history:    %systemroot%\System32\Cpl.cfg
 - Connection history:  %systemroot%\System32\LLS\Llsuser.lls
 - Group information:   %systemroot%\System32\LLS\Llsmap.lls
 
These files are created when the License Manager service starts.
 
To reset the License Manager information:
 
1. Stop the License Logging service.
 
2. Delete or rename the following files on the primary domain controller
   or the enterprise server:
 
      Cpl.cfg
      Llsuser.lls
      Llsmap.lls
 
3. Restart the License Logging service.
 
4. Re-add the appropriate license information.


Other information about NT licensing...
=======================================

When do I need to purchase a Client Access License (CAL)?
A Windows NT Server CAL is required only when Windows NT is providing the following network services:
- File Services (sharing and managing files and/or disk storage)
- Printing Services (sharing and managing printers)
- Macintosh connectivity (file sharing and printing services)
 -Remote Access Services (accessing the server from a remote location through a communications link)
 
A CAL for Windows NT Server is required for each computer or workstation that will be accessing or otherwise using these basic network services, either with the Microsoft-provided client software or with third-party software.
 
A Windows NT Server Client Access License is not required when it is operating solely as a platform for a server application. For example, when using Windows NT Server as a platform for Microsoft SQL Server, Microsoft SNA Server, Microsoft Systems Management Server or a third-party server application, and basic networking services are obtained from another Network Operating System (e.g., Novell or Banyan).

Do Windows for Workgroups, Windows 95 and Windows NT Workstation include Client Access Licenses (CALs) for Windows NT Server?
No. Microsoft Windows 95, Windows for Workgroups and Microsoft Windows NT Workstation do not include a license to access Windows NT Server.
 
Do I need to purchase a Client Access License (CAL) for accessing the Internet?
Windows NT Server includes support for telnet and ftp which are often used as means to connect to an Internet server hosted on Windows NT Server. Telnet and ftp connections do not use Windows NT Server basic network services and, therefore, do not require Windows NT Server Client Access Licenses. Internet Information Server or any third party Web server application running on Windows NT Server providing HTTP sharing of HTML files is not using Windows NT Server's basic network services and does not require Client Access Licenses.

How can I keep track of my Windows NT Server licenses?
Windows NT Server provides a tool, License Manager, to assist administrators in managing licensing for computers running Windows NT Server. The License Manager tracks licensing for Windows NT Server and all of the BackOffice. family of server products. It consists of two component tools; 1) The Licensing Option in the Control Panel and 2) The License Manager program in the Network Administration program group.
 
What previous versions of Windows NT Server qualify for a version upgrade to Windows NT Server 4.0?
All registered customers of previous versions of Windows NT Server including Windows NT Server 3.1, 3.5 and 3.51 are eligible to purchase the Windows NT Server 4.0 upgrade and Client Access License Upgrades.

What products qualify for a competitive upgrade to Windows NT Server 4.0?
Competitive pricing is available for all registered users of Microsoft LanManager, Novell NetWare, IBM Lan Server, Banyan Vines, DEC PATHWORKS, Artisoft LANtastic, and the following UNIX network operating systems, SCO (Xenix, UNIX, OpenServer or UnixWare), Sun (Solaris, Solaris X86 or SunOS), Hewlett-Packard HP-UX, IBM AIX, Digital (Ultrix, OSF/1 or UNIX) and SGI Irix.

Per Server Licensing:
The Per Server licensing mode is a new option that has been added for Microsoft Windows NT Server 3.51 or later, Microsoft SNA Server 2.11 or later and, when released, Microsoft Exchange Server 1.0. This option enables users to take advantage of the concurrent connections (Per Server) option that has been available for Microsoft SQL Server 4.21a or later. It is not available for Microsoft Systems Management Server or the Microsoft BackOffice Client Access License.
If you are ever unsure, though, about which licensing mode to choose, select the Per Server option. If your network traffic later increases and more users need to connect at the same time, you are legally permitted to convert from Per Server mode to Per Seat mode at no additional cost. (Use the Licensing option in Control Panel for a server on which you are working and License Manager in the Network Administration program group for local or remote servers.) This is a one-time, one-way conversion option.
It is not necessary for you to notify Microsoft if you elect to make this change. However, you will need to reenter the licensing data in License Manager using the New Client Access License dialog box. You are not legally permitted to change the licensing mode from Per Seat to Per Server.
 
Note   If you purchased Client Access Licenses for Windows NT Server 3.5 (which were in Per Seat mode because that was the only licensing mode available with Windows NT Server 3.5) and now want to use them with Windows NT Server 3.51 in the Per Server mode, you can designate them as Per Server mode when you upgrade (but not later). Normally, converting from the Per Seat mode to the Per Server mode is not allowed. However, since the Per Server mode is new, Microsoft is allowing customers that upgrade to Windows NT Server 3.51 to choose the most appropriate licensing mode for their requirements.
 
Concurrent connections:
With Per Server licensing, each Client Access License is assigned to a particular service (product) on a particular server and allows one connection to that service, such as basic network services, which include the following:
- File services - sharing and managing files and/or disk storage
- Printing services - sharing and managing printers
- Macintosh. connectivity - file sharing and printing services
- File and Print Services for NetWare. connectivity - file sharing and printing services for NetWare clients
- Remote access services - accessing the server from a remote location through a communications link
 
Notice that a connection, in this case, is to a server and not just to an individual share point or printer on that server. If you connect to \\PRODUCT\NEW and \\PRODUCT\OLD, that is considered as only one connection for licensing purposes. However, if you connect, in Per Server mode, to a server from two different computers using the same username, that is considered two connections.
You must have at least as many Client Access Licenses dedicated to a service on that server as the maximum number of client computers that will connect to that server at any point in time. If you select the Per Server option, you must specify during Setup, or upon purchasing new Client Access Licenses, the number of Client Access Licenses (which corresponds to the number of concurrent connections) that you have purchased for that server.
With Per Server licensing, once the specified limit for concurrent connections is reached, the server returns an error to the clients computer and does not allow more computer connections to that server. Connections made by administrators are also considered as part of the total number of concurrent connections. When the limit is reached, though, administrators are still allowed to connect to manage the lockout situation. New users, however, will not be allowed to connect again until enough users (including administrators) have disconnected to get below the specified limit.
 
Note   You can also check the Application log in Event Viewer on the master server to view any license violation alerts, which appear every 6 hours as Error 71 and Event ID 201. Reports can be created using an OLE script or the Crystal Reports for Windows NT utility included on the CD for the Microsoft Windows NT Resource Kit for Windows NT Workstation and Windows NT Server Version 3.51.
 
The Per Server option is often the most economical one for networks in which clients tend to connect to only one server or occasional-use or special-purpose servers, and they do not all need to connect at the same time. If a network environment has multiple servers, then each server licensed in Per Server mode must have at least as many Client Access Licenses dedicated to it as the maximum number of clients that will connect to it at any one point in time.

Per Seat Licensing
The Per Seat licensing mode requires a Client Access License for each computer that will access, on any Windows NT Server, a particular service, such as basic network services (file, print, and communications). Once a computer is licensed, it may be used to access any Windows NT Server computer at no additional charge. Multiple users may also log on to that single computer.
However, having a valid Per Seat mode Client Access License does not guarantee you access to a server that is licensed in the Per Server mode and has reached its specified limit. Such a connection would also consume one of the licenses assigned to the pool of available Per Server licenses, and so you would only be able to connect if there were Per Server licenses available.
For example, if a server in Per Server mode has 50 Client Access Licenses dedicated to that server and has less than 50 simultaneously connected clients, then additional clients can connect. If, however, that server has reached its specified limit, then additional clients cannot connect, even if they have a valid Per Seat mode license for that service.
If you select the Per Seat licensing mode, any number of licensed computers can be used to connect at any time to any Windows NT Server. However, remember that you must purchase a separate Client Access License for each computer even if you use client operating-system software from Microsoft (including Microsoft Windows for Workgroups, Microsoft Windows 95, or Microsoft Windows NT Workstation) or from a third-party vendor, or use any of the other client software supported by Windows NT Server. The Per Seat option is often the most economical one for networks in which clients tend to connect to more than one server.
 
Note   A Client Access License is not included when you acquire Windows for Workgroups, Windows NT Workstation, and Windows 95. The license must be purchased separately in addition to the operating-system software.

Hope this helps.
0

Featured Post

How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

Join & Write a Comment

Many of us in IT utilize a combination of roaming profiles and folder redirection to ensure user information carries over from one workstation to another; in my environment, it was to enable virtualization without needing a separate desktop for each…
This article offers some helpful and general tips for safe browsing and online shopping. It offers simple and manageable procedures that help to ensure the safety of one's personal information and the security of any devices.
Access reports are powerful and flexible. Learn how to create a query and then a grouped report using the wizard. Modify the report design after the wizard is done to make it look better. There will be another video to explain how to put the final p…
This video gives you a great overview about bandwidth monitoring with SNMP and WMI with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're looking for how to monitor bandwidth using netflow or packet s…

744 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

17 Experts available now in Live!

Get 1:1 Help Now