eric3333
asked on
Windows server CAL and WCF service
Hi,
I have a self hosted WCF service running under Windows 2008 server. The service is self hosted, and EndPoint uses Tcp.
The question is regarding the Windows Server 2008 limitation. It is possible that >1000 computers can connect to the service (at the same time)?
Is it necessary to buy CAL (Client Access License) for each computer that connects to the service?
What is the native limitation in Windows Server 2008 without any CAL?
Thanks a lot and best regards!
I have a self hosted WCF service running under Windows 2008 server. The service is self hosted, and EndPoint uses Tcp.
The question is regarding the Windows Server 2008 limitation. It is possible that >1000 computers can connect to the service (at the same time)?
Is it necessary to buy CAL (Client Access License) for each computer that connects to the service?
What is the native limitation in Windows Server 2008 without any CAL?
Thanks a lot and best regards!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Windows 2000 Server offers two licensing modes: per-server and per-seat. Windows Server 2003 replaces per-seat licensing with per-user / per-device. Let's take per-server first.
When you configure Windows Server for per-server mode, you specify the number of CALs you have purchased for the server and Windows Server allows up to that number of concurrent connections. Configure it for 100 CALs, for example, and Windows Server will support up to 100 concurrent connections. Additional connection attempts after the limit is reached fail. Windows Server counts administrator connections against the total but still allows administrators to connect after the limit is reached to allow them to manage the server (and potentially disconnect users if needed). With per-server licensing therefore, Windows Server actively controls connections based on the number of licenses for which you have configured it.
Per-user / per-seat mode is a bit different. A User CAL (per-user mode) allows a single user to connect to the server with any number of devices. If your users work with a desktop computer, notebook, PDA, and smart phone-all accessing an Exchange Server, for example-the logical choice would be to purchase User CALs. Each user could then connect with as many devices as needed.
A Device CAL allows one device to connect to the server application. For example, assume you have a training lab containing 20 computers that are shared by 200 students throughout the day. Rather than purchase 200 User CALs, you would instead purchase 20 Device CALs. Since User CALs and Device CALs cost the same, your licensing cost is only one-tenth what it would be if you purchased User CALs.
An important distinction between per-server and per-user / per-device licensing is that with the latter, Windows Server does not prevent connections even after the limit is reached. The License Logging service does monitor and report connections for both per-server and per-user / per-device, but only with per-server mode does Windows deny connections after the limit is reached.
When you configure Windows Server for per-server mode, you specify the number of CALs you have purchased for the server and Windows Server allows up to that number of concurrent connections. Configure it for 100 CALs, for example, and Windows Server will support up to 100 concurrent connections. Additional connection attempts after the limit is reached fail. Windows Server counts administrator connections against the total but still allows administrators to connect after the limit is reached to allow them to manage the server (and potentially disconnect users if needed). With per-server licensing therefore, Windows Server actively controls connections based on the number of licenses for which you have configured it.
Per-user / per-seat mode is a bit different. A User CAL (per-user mode) allows a single user to connect to the server with any number of devices. If your users work with a desktop computer, notebook, PDA, and smart phone-all accessing an Exchange Server, for example-the logical choice would be to purchase User CALs. Each user could then connect with as many devices as needed.
A Device CAL allows one device to connect to the server application. For example, assume you have a training lab containing 20 computers that are shared by 200 students throughout the day. Rather than purchase 200 User CALs, you would instead purchase 20 Device CALs. Since User CALs and Device CALs cost the same, your licensing cost is only one-tenth what it would be if you purchased User CALs.
An important distinction between per-server and per-user / per-device licensing is that with the latter, Windows Server does not prevent connections even after the limit is reached. The License Logging service does monitor and report connections for both per-server and per-user / per-device, but only with per-server mode does Windows deny connections after the limit is reached.
http://stackoverflow.com/questions/745830/does-each-authenticated-wcf-client-connection-need-a-cal