For example, you don't need CALs to allow customers to anonymously access your Web site. All that is required is a single Windows Server license.
If you provide authenticated access to customers or partners, however, you do need to take licensing into account. An External Connector License allows an unlimited number of external users to access the server or server application for which the license applies.
Instead, the EC is designed for customers and partners who need to access your server or application. For example, if you provide authenticated access for your customers to obtain inventory or pricing information about your products, you need an EC to legally provide that data. If you have only a few customers or partners who access your servers, an EC will likely seem fairly expensive. In these situations, you can still purchase and use CALs to allow these users to gain access, rather than purchase the EC.
When you are evaluating the necessity for an EC, consider the cost for the appropriate number of CALs against the cost of the EC, then factor in future growth. Keep in mind that the EC allows an unlimited number of connections, so purchasing an EC now might still be more cost effective if the number of users is relatively low now but will grow in the near future. Managing licenses Windows Server provides two tools to help you manage licensing.
The first of these is the Licensing applet in the Control Panel, which allows you to manage licenses on the local server. However, this is a legal limitation, not a technical one. You can use the Licensing applet at any time to switch between modes.
Managing CALs with the Licensing applet is easy. Open the applet and choose the application you want to manage, as shown in Figure A. If the target application is not configured for Per-Server mode, the Add Licenses and Remove Licenses buttons are dimmed, and you will have to use the Licensing console, explained next, to manage the CALs.
Editor's Picks. The best programming languages to learn in Deploying a Remote Desktop License Server. Deploying TS Licensing.
The Windows Server operating system family provides a client license management system known as Terminal Server Licensing.
An example of this exception would be if unidentified users browsed your public Web site. Windows CALs would not be required for those users. This means you can choose to acquire a Windows CAL for every device used by any user accessing your servers, or you can choose to acquire a Windows CAL for every named user accessing your servers from any device. The option to choose between the two types of Windows CALs offers you the flexibility to use the licensing that best suits the needs of your organization.
For example:. Both modes are available for either type of license. Per Server mode tends to be the most economical designation for Windows CALs in computing environments where a small number of servers have limited access requirements.
You are commenting using your WordPress. You are commenting using your Google account. You are commenting using your Twitter account. You are commenting using your Facebook account. Notify me of new comments via email. Notify me of new posts via email. Home About. Client Access Licensing Requirements In previous Windows Server licensing models, Windows Client Access Licenses were automatically triggered when particular server services were invoked such as file, print, remote access, and terminal services, as well as authenticated access.
0コメント