- #Device cal vs user cal software license#
- #Device cal vs user cal software#
- #Device cal vs user cal windows#
I have a large customer right now (about 5K remote users) who plans do do exactly that. For that kind of money, buy a very nice $25,000-$50,000 remoteĪccess gateway from F5 or someone like that and tell Microsoft to go away.
#Device cal vs user cal software#
I don't see how they could expect anyone toĮver license their access solution if it required something like $200,000 to license the log (for 1,000 users, each with a $200 CAL), plus another $50K a year for Software Assurance. Microsoft should get over engineering a DB as a means of generating revenue.
![device cal vs user cal device cal vs user cal](https://cdn.forscope.eu/files/eu/e/2796/product-img-windows-server-2019-rds-device-cal-0-5x_w200.png)
I can't imagine there are that many of them. Anyone or any device that reads the data from that DB also need a CAL. The proxy server needs a device CAL to add records to the DB. The users are not entering or generating any data. Would you please help to find out the apropriate licensing scheme? Others say that as far as the logs are generated by the ISA server itself, it is not "user data", and so far we need only 1 device CAL for the SQL server connection.Īt least, they all agree that if SQL server stores turnstile entries, you don't need a license for everyone who passes it. Microsoft offers a device-based CAL (Device CAL) or a user-based CAL (User CAL).
#Device cal vs user cal software license#
Some people say that the log entries are generated by the users so, ISA server acts as a "multiplexing device" and therefore we need SQL user CALs for all of our employees who are accessing CAL is a commercial software license that allow clients to use server. Now I have two controversal opinions on the licensing. So that means for every TFS CAL we have, if it connects to data on the SQL backend we will need a CAL for that as well. Any user who accesses data through the TFS server to the SQL backend will need a CAL. Is that no user content is stored in the SQL database, no web-cache, only access logs generated by the ISA server. There cannot be just 1 device CAL for the SQL server and 20 people connecting to the TFS server. of named users that need to use your system. of client devices that need to connect to your system.
![device cal vs user cal device cal vs user cal](https://supporthost.in/wp-content/uploads/2017/11/rds-cal-user1.png)
Just make sure you buy enough quantities to cover you systems need. Also, we have SQL server 2000 standard installation on the same server it is used for storing access logs (approx. You mean Device CAL and User CAL You dont need both. In our organization, we have ISA server 2004 installation acting as a proxy server at our corporate network.
![device cal vs user cal device cal vs user cal](https://cdn.shopify.com/s/files/1/0517/1561/products/windows_2012_R2_6132a558-b6a7-473d-b8b5-739b7aa98d42_1024x1024.jpg)
Device CALs may make more economic and administrative sense if your company has workers who share devices, for example, on different work shifts.
#Device cal vs user cal windows#
Even from Microsoft I'm getting controversal answers. With a Device CAL, you purchase a CAL for every device that accesses your server, regardless of the number of users who use that device to access the server. Device CALs allow an unlimited number of users to access Windows Server from a single device When comes to RDS CAL, it is different than CALs stated above but required for users or devices that want to utilize Remote Desktop Service functionality on Windows Server, which also consists of types of Per Device and Per User. I've ran into a serious discussion on SQL server licensing.