Therefore I always prefer Per User CALs as they are easy to mange and more efficient.
Its correct that device CALs are assigned to devices but note that those CALs are tied to those devices and if a device is retired/crashed then the CAL will not be revoked automaticallyīy the license server wherein for User CALs license is leased to the user per session basis and is checked in to the license pool automatically which means the number of licenses you buy is equal to the number of concurrent connections to the server by any Your understating is correct but i partially agree with your opinions. Using a 'Device CAL' for a web application on a WebServer that authenticates through a 2008DC with external clients satisfy CAL requirements in this scenario? I'm also under the understanding that since our external users auth through AD that a CAL is required, but what's not clear to me is if a device CAL is applicable to our enviorment, in the sense of does device CAL's cover external users. Need to have roaming access to the corporate network using multiple devices, or from unknown devices, or simply have more devices than users in your organization. Purchasing a User CAL might make more sense if your company employees With the User CAL, you purchase a CAL for every user who accesses the server to use services such as file storage or printing, regardless of the number of devices they use for that access. Device CALs may make more economic and administrative sense if your company has workers who shareĭevices, for example, on different work shifts.
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. I'm trying to get a better understanding of CAL's so forgive me if these questions are easy questions.Ĭurrently we have external users (non-company) web-app users who connect remotely that authenticate through AD, my understanding is the following from: