Client Access
A Client Access License ("CAL") is a term denoted by Microsoft to the various licensing terms that must be purchased and enabled to allow various functionality on Windows NT based servers.
Microsoft offers two different licensing models that customers can opt for. The models are a 'per server licensing' or 'per seat licensing'.
- If a user opts for per server licensing (concurrent licensing). Then through online servers, Windows NT implements a check for concurrency with the number of concurrent file/print users. This number is configured in license manager of the Microsoft server.
- The 'per seat licensing' does not include crosschecking with the license manager. However, the customer must still acquire a client access license for the operating system.
- Server Message Block (SMB) file & print (Windows NT Server)
- NCP file & print (FPNW)
- Services for Macintosh (SFM)
- Remote Access Service (RAS)
- Terminal Services
Using Windows of Workgroups 3.11 to connect to a Windows NT server for a file share or printer share application. Connections of a LAN manager client or a Windows 95 client require CAL. A NetWare client access FPNW requires a separate CAL.
There is general exemption to the requirements of a Windows CAL. A Client Access License is not required if the server software is unauthenticated and accessed through the Internet. An Authentication of server software is an exchange of credentials of a user or application between the server software and the registered device.
Example: unidentified and unauthorized users browse a public Web site. Windows CALs are not required for those users.
Terminal Services CALs
A Client access license for a terminal service is a license for the server itself. The license is unique and can not be compared to other windows installation. A built-in one-user Terminal Services server license is present in Windows XP. In cases of Windows 2000 Server and Windows Server 2003, there are 'remote administration' modes. Windows Server 2003 supports dual connections in a remote administration mode.
Specialized Terminal Services CALs are not required in services or versions prior Windows Server 2003, distant clients are allowed an access automatically even if they have a lower version of the operating system.
For example, Windows NT 4.0 clients can log on to Windows NT 4.0 terminal servers. However these clients will receive an error when trying to log on to Windows 2000. Windows 2000 or Windows XP clients can log on to Windows NT 4.0 or Windows 2000 terminal servers. Regardless of the client operating system, Separate CALs are needed for all clients that are members of Windows Server 2003.
The "Per User" CAL was introduced late for the Windows Server 2003. However, in Windows Server 2003 SP1, the Per User" CAL was not technically enforced and any number of clients could connect to a Windows 2003 network server. Reportedly, this delay occurred because Microsoft did not have time to finalize technical certifications before the release of the operating system.
Get a Free Online Diagnostic Scan with RegCure PC Optimizer (Download Takes 2 Mins)
