Windows OS Hub
  • Windows Server
    • Windows Server 2016
    • Windows Server 2012 R2
    • Windows Server 2012
    • Windows Server 2008 R2
    • SCCM
  • Active Directory
    • Group Policies
  • Windows Clients
    • Windows 10
    • Windows 8
    • Windows 7
    • MS Office
    • Outlook
  • Virtualization
    • VMWare
    • Hyper-V
  • PowerShell
  • Exchange
  • Home
  • About

Windows OS Hub

  • Windows Server
    • Windows Server 2016
    • Windows Server 2012 R2
    • Windows Server 2012
    • Windows Server 2008 R2
    • SCCM
  • Active Directory
    • Group Policies
  • Windows Clients
    • Windows 10
    • Windows 8
    • Windows 7
    • MS Office
    • Outlook
  • Virtualization
    • VMWare
    • Hyper-V
  • PowerShell
  • Exchange

 Windows OS Hub / Exchange / Calculating the Number of Client Access Licenses (CAL) for Exchange Server

February 22, 2017 Exchange

Calculating the Number of Client Access Licenses (CAL) for Exchange Server

In the previous article we discussed the peculiarities of Exchange Server licensing and mentioned that to access a mailbox on Exchange Server a user or a device needs a Client Access License (Exchange Server CAL). You can purchase a license for a device or a user (this is more expensive). Besides, there are two versions of Exchange Server CAL: Standard or Enterprise. The second one can be bought additionally, if a user needs extended Exchange functionality, as a rule, these are archiving, logging, Unified Messaging integration, etc.

If the mailbox is using a feature from the Enterprise package, it requires an Enterprise CAL in addition to Standard one. The presence or absence of a license doesn’t influence the functionality of a client, but to use the product legally an administrator need to count from time to time the number of used client licenses of both types.

In Exchange 2010, you can estimate the number of necessary licenses right in the root of the graphic Exchange Management Console. The information about the number of licenses needed is displayed in the Organization Summary section. In our case, 958 Standard CALs and 464 Enterprise CALs are necessary for licensing customer organization. Exchange 2010 Management Console - CAL in use

Note. Actually, this estimation method of the number of licenses is not very accurate. For more accurate estimation of the number of Exchange 2010 CALs, you’d better use this TechNet script.

In Exchange 2013 (and Exchange 2016), there is no such feature in the graphic interface. Two EMS cmdlets have been added instead:

  1. Get-ExchangeServerAccessLicense allows to get the names of the licenses used in the Exchange organization
  2. Get-ExchangServerAccessLicenseUser allows to request the information  about CALs used by the users

So, using Get-ExchangeServerAccessLicense get the exact license names:

Get-ExchangeServerAccessLicense | ft -AutoSize

Get-ExchangeServerAccessLicense

Tip. In Exchange 2016, the license names are the same: Exchange Server 2016 Standard CAL and Exchange Server 2016 Enterprise CAL.

Copy the names of the licenses to clipboard and display the list of mailboxes that require this license type:

Get-ExchangeServerAccessLicenseUser –LicenseName "Exchange Server 2013 Standard CAL"

Get-ExchangeServerAccessLicenseUser

Count the number of mailboxes in this list:

Get-ExchangeServerAccessLicenseUser –LicenseName "Exchange Server 2013 Standard CAL" | Measure-Object | Select Count

Counting exchange 2016 Client Access Licenses

A similar calculation has to be made for Enterprise CALs.

Tip. Get-ExchangeServerAccessLicenseUser cmdlet doesn’t make the list of mailboxes that require Enterprise CALs very accurately. To make it correct, better use the script by British MVP (http://www.wave16.com/2013/11/calculating-cal-requirements-for.html).

So we have considered how to quickly count the total number of necessary client access licenses so that users could legally work with Exchange Server.

2 comments
2
Facebook Twitter Google + Pinterest
previous post
Exchange Server 2016 Licensing
next post
Activating Windows Server 2016 with KMS Server

Related Reading

Get-MessageTrackingLog: Search Message Tracking Logs on Exchange Server

December 19, 2019

Managing Exchange Mailbox Inbox Rules with PowerShell

August 29, 2019

Fix: Outlook 2016/2013 Always Starts in Offline Mode

July 30, 2019

Configuring Anti-Spam Protection on Exchange 2013, 2016 –...

June 5, 2019

How to Blacklist/Block Sender Domain or an Email...

June 3, 2019

2 comments

Jennifer October 19, 2018 - 5:51 pm

What about mailboxes that are shared or if a user has multiple mailboxes?

Reply
admin October 23, 2018 - 11:21 am

Exchange CAL can be tied to a user or device. If you have the number of used mailboxes more than the number of devices, it is more profitable for you to license Exchange in Per Device mode.

Reply

Leave a Comment Cancel Reply

Categories

  • Active Directory
  • Group Policies
  • Exchange
  • Windows 10
  • Windows 8
  • Windows 7
  • Windows Server 2016
  • Windows Server 2012 R2
  • Windows Server 2008 R2
  • PowerShell
  • VMWare
  • MS Office

Recent Posts

  • Accessing USB Flash Drive from VMWare ESXi

    February 26, 2021
  • How to Sign a PowerShell Script (PS1) with a Code Signing Certificate?

    February 25, 2021
  • Change the Default Port Number (TCP/1433) for a MS SQL Server Instance

    February 24, 2021
  • How to Shadow (Remote Control) a User’s RDP session on RDS Windows Server 2016/2019?

    February 22, 2021
  • Configuring PowerShell Script Execution Policy

    February 18, 2021
  • Configuring Proxy Settings on Windows Using Group Policy Preferences

    February 17, 2021
  • Updating Group Policy Settings on Windows Domain Computers

    February 16, 2021
  • Managing Administrative Shares (Admin$, IPC$, C$, D$) in Windows 10

    February 11, 2021
  • Packet Monitor (PktMon) – Built-in Packet Sniffer in Windows 10

    February 10, 2021
  • Fixing “Winload.efi is Missing or Contains Errors” in Windows 10

    February 5, 2021

Follow us

woshub.com
  • Facebook
  • Twitter
  • RSS
Popular Posts
  • New-MailboxRepairRequest: Fixing Corrupted Mailboxes in Exchange 2016/2013/2010
  • How to Configure DKIM on Exchange Server 2010/2013
  • Outlook 2016: Manual Setup Exchange Account
  • Export Exchange Global Address List (GAL) to CSV
  • Outlook 2016 Slow External Autodiscover with Exchange Server
  • Exchange Error “452 4.3.1 Insufficient system resources”
  • Stellar Exchange Toolkit: All-In-One Admin Utility
Footer Logo

@2014 - 2018 - Windows OS Hub. All about operating systems for sysadmins


Back To Top